Posts made by george

@alfek
The DSI node can be enabled as follows.I didn't understand which GPIO C0 C1 corresponds to, please indicate.

diff --git a/arch/arm64/boot/dts/rockchip/rk3588-cpcm5-evb-v11.dts b/arch/arm64/boot/dts/rockchip/rk3588-cpcm5-evb-v11.dts
index 5f52819c2e9b..fa505ddfe99d 100755
--- a/arch/arm64/boot/dts/rockchip/rk3588-cpcm5-evb-v11.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3588-cpcm5-evb-v11.dts
@@ -526,7 +526,7 @@ &sdmmc {
 };
 
 &dsi0 {
-       status = "disabled";
+       status = "okay";
        dsi0_panel: panel@0 {
                status = "okay";
                compatible = "simple-panel-dsi";
@@ -779,7 +779,7 @@ &dsi0_in_vp3 {
 
 
 &route_dsi0 {
-       status = "disabled";
+       status = "okay";
        connect = <&vp3_out_dsi0>;
 };

@Rock
You can download the image again to the 24.04 system directory. If you downloaded to 22.04 before, you must first mount mmcblk0p2 to the system and then find the image you downloaded earlier in the corresponding folder.

@happyday
1,这版镜像是带桌面的吗？为什么我的没有出现桌面，只能在串口启动开发板，并通过命令操作？如何调出桌面
这个是带桌面的镜像，默认是hdmi输出，你也可以尝试使用其它镜像，比如22.04，看是否有输出，排除硬件问题导致。
2,通过笔记本电脑可以运行镜面桌面吗，还是只能通过单个的显示屏？
是可以远程连接的，但是前提是机器要开启DSI的终端。系统至少要有一个显示端口处于激活状态。
3，如果开发板带EMMC，是不是将镜像烧录到SD卡后，上电后，镜像会存储到EMMC中，SD卡在上电一次后就可以拔出了吗？
开发板带EMMC，镜像就可以通过上层的USB3.0接口刷入，不需要TF卡。
4，开发板关机，是向串口发送命令吗？
有图形界面可以使用图形界面的关机对话框，串口shell也可以关机。

@Ranomez
You can try compiling the source code on a 32-bit system. You may encounter some package compatibility issues.

@kingpin1cn
如果机器是板载的EMMC模组，可以尝试进入UMS模式，通过ETCHER软件刷机。

@markerrors
DTS文件里边使能DSI0的节点，需要多大分辨率就配置多大，这样就可以远程登录桌面了。

@Twsuts-0
你仔细看一下我们的那个脚本，实际上思路很简单，先dd一个img镜像（大于你的FS的大小），然后把这个镜像分为2个区（一个放boot，一个放FS），再然后把镜像挂载到系统，再把系统对应分区直接复制到镜像分区，然后做一些文件系统检查的工作即可。

@kingpin1cn
需要插入到上面的那个USB3.0端口，当然也可以使用在线刷机。

@Twsuts-0
我们一直都是使用这个方法和脚本备份的，没有发现有什么问题的。你要做分区备份肯定不能在当前分区操作的。

@Twsuts-0
这个最好使用移动硬盘备份，很多U盘在长时间大数据量写入的时候容易出错。这种情况之前也又遇到过。

@Momo-0
At present, PD charging only supports charging when turned on, and does not currently support charging when turned off. The protocol only supports TYPEC PD format and does not support QC standards. So you need to use an adapter with TYPEC interfaces on both ends as shown in the following figure:

@Rock
Due to compatibility issues with USB3.0 devices, you can try booting with USB2.0 devices.

@traceback
We will update the kernel to 6.1 soon, please be patient.

@markerrors
ubuntu是无线也不行吗？没有看明白。

@Momo-0
The cloud storage provides a 22.04 image, which you can download and upgrade.

@markerrors ubuntu是否正常？

@happyday

systemctl poweroff

@happyday
拍个照片看一下，也可以直接断电重启，第一次启动会格式化扩展磁盘分区，会慢一些。

@Android2002
modules.tar.gz 可以不用拷贝，放其它目录一样的。

@Android2002
可以先删除boot/firmware里边的文件，然后再拷贝。注意删除前最好备份一下，否则错误的文件会导致系统无法正常启动。

5G

4K (3840*2160) LCD

One more thing, everyone guess

@george

Software debugging

• Can recognize the network card normally

FM160-NA

[  209.139782] usb 6-1: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd
[  209.158752] usb 6-1: LPM exit latency is zeroed, disabling LPM.
[  209.159341] usb 6-1: New USB device found, idVendor=2cb7, idProduct=0104, bcdDevice= 5.04
[  209.159345] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  209.159348] usb 6-1: Product: Fibocom FM160 Modem_SN:A5206AEB
[  209.159351] usb 6-1: Manufacturer: Fibocom
[  209.159354] usb 6-1: SerialNumber: a5206aeb
[  209.334460] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB0
[  209.334960] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB1
[  209.335465] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB2
[  209.335869] usb 6-1: GSM modem (1-port) converter now attached to ttyUSB3
[  209.369699] qmi_wwan 6-1:1.4 wwan0: register 'qmi_wwan' at usb-xhci-hcd.4.auto-1, WWAN/QMI device, 0e:2e:b9:55:d8:4f

RM500U-CN

[ 1060.540438] usb 6-1: new SuperSpeed Gen 1 USB device number 4 using xhci-hcd
[ 1060.558057] usb 6-1: New USB device found, idVendor=2c7c, idProduct=0900, bcdDevice= 4.04
[ 1060.558062] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1060.558065] usb 6-1: Product: RM500U-CN
[ 1060.558068] usb 6-1: Manufacturer: Quectel
[ 1060.558071] usb 6-1: SerialNumber: 0123456789ABCDEF
[ 1060.614822] cdc_ether 6-1:1.0 usb0: register 'cdc_ether' at usb-xhci-hcd.4.auto-1, CDC Ethernet Device, 4a:b9:e7:e7:04:47

@Ranomez
This machine is the latest version of V20, and I have understood the issue you have reported:

1. This noise is the bottom noise of the audio codec that is amplified by the power amplifier and output. In fact, the native bottom noise is very small, which can be confirmed by inserting headphones. It's only after being amplified by the amplifier that you can hear it near the ear at the speaker end.
2. To avoid this common problem, the traditional approach is to only turn on the amplifier circuit when there is audio output, and then turn off the amplifier after the audio is played. This way, the normal sound output will cover the background noise, as shown in the driver code below:

static int es8316_mute(struct snd_soc_dai *dai, int mute, int direction)
{
	struct snd_soc_component *component = dai->component;
	struct es8316_priv *es8316 = snd_soc_component_get_drvdata(component);

	es8316->muted = mute;
	if (mute) {
		es8316_enable_spk(es8316, false);
		msleep(100);
		snd_soc_component_write(component, ES8316_DAC_SET1_REG30, 0x20);
	} else {
		snd_soc_component_write(component, ES8316_DAC_SET1_REG30, 0x00);
		msleep(130);
		if (!es8316->hp_inserted)
			es8316_enable_spk(es8316, true);
	}
	return 0;
}

3. Your current operating method is to only turn on the amplifier without normal audio data output, which is equivalent to the amplifier only amplifying background noise data. So what the speaker hears is the amplified background noise. The current situation I have tested here is that the ear needs to be close to the speaker to hear, which cannot be heard in normal usage scenarios.
4. Later, we will try to adjust the gain configuration of the amplifier at the driver end, hoping to reduce the amplitude of this noise, but it is unrealistic to completely eliminate it.

@Ranomez
If you can open the back cover of the machine, please take a photo and send it out, I will confirm the version.

@Ranomez
Can you confirm if your machine is V10 or V20 version? When did you probably purchase the machine?

@Android2002
这个需要使用etcher工具烧录，不是瑞芯微开发工具。

@Rock
1.First, download the image to the COOLPI laptop
2.Then insert the USB drive into the laptop, double-click on the image and the following interface will pop up. 3.Then select the USB drive, and the image will be created into the USB drive
4.Restart the laptop and the machine will boot from the USB drive. After entering the system, copy the 24.04 image into the USB drive.
5.Double click on the 24.04 image in the USB drive directory, select EMMC (starting with AT29), and enter the root password. The image will be flushed into EMMC.

@Rebel-Rider
Regarding the issue of startup speed, it is mainly due to the initialization time of the RTL8852BE driver, not the speed of the EMMC. We are still trying to find ways to optimize this.Think you.

@Rebel-Rider
Thank you very much for your support of Coolpi products. As a DIY laptop, the extreme thickness is not very user-friendly, and the main issue is that there may be a lack of sufficient internal space for secondary development.
Regarding the issue with the kernel version, as the original factory has not yet submitted an update to the hardware encoding and decoding part of the 6. x kernel video, the machine is currently using 5.10.110. We will synchronize the submission once this issue is resolved.
After the mainline kernel 6.8, devices that natively support CM5 have also been designed for laptops based on the CM5 core board, allowing for synchronous use of the mainline kernel. The mainline version of uboot has also been merged into the mainline recently.
Communicate promptly if there are any issues during use. Thank you again for your support.

@happyday
是的U盘相当于硬盘，机器会优先从U盘启动。不需要做其它操作。制作U盘镜像之前建议先格式化一下U盘。