Posts made by zensation

after doing more research it seems you have to compile the dts files into a pre processed file with cpp command before you can compile into a dtb file with the dtc command. so i got that figured out and can change the io pullups.

however im still struggling with the wakeup from suspend conditions. I enabled several of them but none seem to work. usb hubs are suspended so usb wakeup doesnt work, the Uart0 wakeup condition is enabled but doesnt wakeup the processor either. ill have to keep digging, but if you are anyone knows how to wakeup from a source other than the power button that would be great to know. as it stands ill have to add a secondary microprocessor to the system to ground the power button contact physically to wake up the board.

@george so here is where I am at. Ive spent a lot of time trying to figure this out but nothing is making sense so maybe you can give me a direct file of what will work. I have done this:

1. navigate to folder of rk3588s-cp4.dtb (/boot/firmware/rk3588s-cp4.dtb)
2. converted the dtb file to dts file using command: sudo dtc -I dtb -O dts rk3588s-cp4.dtb -o rk3588s-cp4.dts
3. nano to open the file: sudo nano rk3588s-cp4.dts

heres where im stuck...theres nothing in that file that resembles the syntax you have sent me. I will attach the dts file in txt format here. can you edit it with the correction to change pin 32 from pull up to pull down? thanks!
rk3588s-cp4.txt

alternatively, on line 1562 i find there is an entry for wake from suspend such as below.

rockchip,wakeup-config = <0x100>;

can you tell me how to change this line to enable GPIO wake from suspend? then I can use whatever GPIO I wish to wake the cool-pi 4b up when suspended without physically pushing the button. I have tried the syntax below but i get a syntax error when i try to convert it back to dtb file:

rockchip,wakeup-config = <
(0
| RKPM_GPIO_WKUP_EN
)
>;

@george ok this explains things better. I have a HAT that was designed for the raspberry pi 4 and it has a power detection pin on pin 32. it needs to be pulled down in order to function because the hat sends 3.3v to the pin as long as incoming power is detected on the power in lines of the HAT. then when the incoming power dissapears from the hat incoming lines, pin 32 will be pulled low by the pull down resistor and the pi can execute some code. If i can figue out how to edit the dts file and recompile to dtb to change pin 32 to an internal pull down resistor i will do it that way. otherwise i guess i am stuck.

@george thanks for the info george...i tried adding a 2k resistor to ground on pin 32 to change it to change it from pull up to pull down as you mentioned, however that does not work and the pin voltage on 32 reads 1.034 volts. ill try other values of resistors and report which one works.

@george and can i do the same thing with an overlay in the config.txt or something? if so how? thx

@george ok George where can i find this file to modify?

@george have logged into root but only see certain gpio as i still try to piece the missing parts together. How can I then change the pull up and pull down resistors for certain input pins?

@george im trying to access the gpio because i have a custom hardware hat that needs gpio105 (pin 32) to be pulled down and i dont see any other way to pull down the input even though the documentation on the gpio page says that all IO can be set up with pull up or pull down resistors. pin 32 seems only to be pull up

@george yes from the very start: echo 128 > /sys/class/gpio/export does not create a node

ugh per usual on this site none of these commands work :rolls eyes:

it says in the GPIO page that all gpio are configurable with pullup or pulldown mode. How can we access the pull down resistor on a input pin say pin 32 GPIO105 that is default set to pullup? I tried the same convention as raspberry pi python access which is

GPIO.setup([pin#], GPIO.IN, pull_up_down=GPIO.PUD_DOWN)

and i get the error no PUD_DOWN in the module. Can you post the entire documentation with included commands in this module?

@george ok so i just figured something out. I removed my power supply hat that i have on my pi so i could connect my serial terminal pins and get you a log, and behold the suspend function works when i powered it on with the usb c port. so seems that for some reason supplying power through the gpio pins for some reason wont let me use the suspend function.

@george that is very strange ive been chasing the issue for last 12 hours. mine definitely doesnt act that way. i have the 20230424 ubuntu image....i also see ive downloaded the 20230306 image. i cant say which is running on the micro sd card though. does the 20230306 behave the same way?

@george also can you test on the latest ubuntu 22.04 release as well? The software im developing is having issues on ubuntu 23.04 but works well on 22.04

@george thanks!

@george im on cp4b. any tips on making it work? since the power button just reboots even though i have it set to suspend function.

@george when i sett the power button to suspend mode and press it, it reboots the board it doesnt actually suspend it. tried changing the systemd sleep file as well with the same results in every case. I think its sufficient to say that currently it does not actually support suspend mode. at least not ubuntu. have you tried any of the other images?

@george is the new kernel used in the ubuntu 23.04 image? I have tried the ubuntu 22.04 image and the 23.04 image but when i run $ cat /sys/power/state it returns "freeze mem" not "freeze mem disk" indicating that theres no kernel level support for actually saving the ram swap to the disk to reboot from.

if no, Can someone build a kernel with power management enabled via swap partition or swap file? Is it possible to put the cool pi 4b into suspend or hibernate mode?

@jack_admin i used the most recent debian image on the drive linked here. i burned the image to 2 diferent usb drives. they are nvme ssd's connected over usb. this method works on my other raspberry pi-like sbc's just not the cool-pi

@大法师

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2023.05.17 09:56:49 =~=~=~=~=~=~=~=~=~=~=~=
DDR V1.09 a930779e06 typ 22/11/21-17:50:56
LPDDR4X, 2112MHz
channel[0] BW=16 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=1024MB
channel[1] BW=16 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=1024MB
channel[2] BW=16 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=1024MB
channel[3] BW=16 Col=10 Bk=8 CS0 Row=16 CS=1 Die BW=16 Size=1024MB
Manufacturer ID:0x6
CH0 RX Vref:28.7%, TX Vref:24.8%,0.0%
CH1 RX Vref:29.7%, TX Vref:24.8%,0.0%
CH2 RX Vref:30.7%, TX Vref:22.8%,0.0%
CH3 RX Vref:28.7%, TX Vref:24.8%,0.0%
change to F1: 528MHz
change to F2: 1068MHz
change to F3: 1560MHz
change to F0: 2112MHz
out
INFO: Preloader serial: 2
NOTICE: BL31: v2.3():v2.3-481-g17b41886e:derrick.huang
NOTICE: BL31: Built : 16:20:07, Dec 7 2022
INFO: spec: 0x13
INFO: ext 32k is not valid
INFO: ddr: stride-en 4CH
INFO: GICv3 without legacy support detected.
INFO: ARM GICv3 driver initialized in EL3
INFO: valid_cpu_msk=0xff bcore0_rst = 0x0, bcore1_rst = 0x0
INFO: system boots from cpu-hwid-0
INFO: idle_st=0x21fff, pd_st=0x11fff9, repair_st=0xfff70001
INFO: dfs DDR fsp_params[0].freq_mhz= 2112MHz
INFO: dfs DDR fsp_params[1].freq_mhz= 528MHz
INFO: dfs DDR fsp_params[2].freq_mhz= 1068MHz
INFO: dfs DDR fsp_params[3].freq_mhz= 1560MHz
INFO: BL31: Initialising Exception Handling Framework
INFO: BL31: Initializing runtime services
INFO: BL31: Initializing BL32
INFO: hdmirx_handler: dma not on, ret
I/TC:
I/TC: OP-TEE version: 3.13.0-652-g4542e1efd #derrick.huang (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #5 2022年 09月 20日 星期二 09:41:09 CST aarch64
I/TC: Primary CPU initializing
I/TC: Primary CPU switching to normal world boot
INFO: BL31: Preparing for EL3 exit to normal world
INFO: Entry point address = 0x200000
INFO: SPSR = 0x3c9

COOLPI LOADER BY YANYI(Apr 11 2023)

DRAM: 4 GiB
Using default environment

0 2 1 3 6 8 7 9 hdmi@fde80000 disconnected
Autoboot in 1 seconds
i2c read err!
i2c read err!
i2c read err!
i2c read err!
i2c read err!
can't get edid block:0
failed to get edid
hdmi info isn't saved in main block
mode:1920x1080 bus_format:0x100a
hdmi@fde80000: detailed mode clock 148500 kHz, flags[5]
H: 1920 2008 2052 2200
V: 1080 1084 1089 1125
bus_format: 100a
VOP update mode to: 1920x1080p0, type: HDMI0 for VP0
dclk:148500,if_pixclk_div;2,if_dclk_div:4
rockchip_vop2_init: hdmi1_phy_pll may not define
hdptx_ropll_cmn_config bus_width:16a8c8 rate:1485000
hdptx phy pll locked!
VP0 set crtc_clock to 1485KHz
VOP VP0 enable Esmart0[356x124->356x124@782x478] fmt[1] addr[0xedf21000]
CEA mode used vic=16
mtmdsclock:148500000
bus_width:0x16a8c8,bit_rate:1485000
hdptx phy lane locked!
dw_hdmi_setup HDMI mode
don't use dsc mode
dw hdmi qp use tmds mode
starting USB...
Bus usb@fc000000: usb maximum-speed not found
trsv ln0 mon rx cdr lock timeout
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fc880000: USB EHCI 1.00
Bus usb@fcd00000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fc000000 for devices... cannot reset port 1!?
WARN: interface 0 has 6 endpoint descriptor, different from the interface descriptor's value: 2
2 USB Device(s) found
scanning bus usb@fc880000 for devices... 1 USB Device(s) found
scanning bus usb@fcd00000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Device 0: Vendor: Samsung Rev: RVT2 Prod: SSD 860 EVO
Type: Hard Disk
Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
... is now current device
Scanning usb 0:1...
MMC: no card present
mmc_init: -123, time 2
Card did not respond to voltage select!
mmc_init: -95, time 16
Loading order: usb - tf - emmc
bank id invalid
request for 141 failed:-22
bank id invalid
request for 141 failed:-22
resetting USB...
Bus usb@fc000000: usb maximum-speed not found
trsv ln0 mon rx cdr lock timeout
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
Bus usb@fc880000: USB EHCI 1.00
Bus usb@fcd00000: usb maximum-speed not found
Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus usb@fc000000 for devices... WARN: interface 0 has 6 endpoint descriptor, different from the interface descriptor's value: 2
2 USB Device(s) found
scanning bus usb@fc880000 for devices... 1 USB Device(s) found
scanning bus usb@fcd00000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
reading cmdline.txt
reading config.txt
reading /vmlinuz
12944981 bytes read in 610 ms (20.2 MiB/s)
reading /initrd.img
8775086 bytes read in 419 ms (20 MiB/s)
reading /rk3588s-cp4.dtb
139959 bytes read in 38 ms (3.5 MiB/s)
Uncompressed size: 36805120 = 0x2319A00

Flattened Device Tree blob at 0x17000000

Booting using the fdt blob at 0x17000000
Loading Ramdisk to eb178000, end eb9d65ae ... OK
Loading Device Tree to 00000000eb152000, end 00000000eb1772b6 ... OK
Adding bank: 0x00200000 - 0x08400000 (size: 0x08200000)
Adding bank: 0x09400000 - 0xf0000000 (size: 0xe6c00000)
Adding bank: 0x1f0000000 - 0x200000000 (size: 0x10000000)

Starting kernel ...

I/TC: Secondary CPU 4 initializing
I/TC: Secondary CPU 4 switching to normal world boot
I/TC: Secondary CPU 5 initializing
I/TC: Secondary CPU 5 switching to normal world boot
I/TC: Secondary CPU 6 initializing
I/TC: Secondary CPU 6 switching to normal world boot
I/TC: Secondary CPU 7 initializing
I/TC: Secondary CPU 7 switching to normal world boot
I/TC: Secondary CPU 1 initializing
I/TC: Secondary CPU 1 switching to normal world boot
I/TC: Secondary CPU 2 initializing
I/TC: Secondary CPU 2 switching to normal world boot
I/TC: Secondary CPU 3 initializing
I/TC: Secondary CPU 3 switching to normal world boot
[ 15.175309] rk-pcie fe190000.pcie: IRQ msi not found
[ 15.175326] rk-pcie fe190000.pcie: Missing config reg space
[ 15.175416] rk-pcie fe190000.pcie: Missing config reg space
[ 15.175447] rk-pcie fe190000.pcie: invalid resource
[ 15.178204] mpp-iep2 fdbb0000.iep: allocate roi buffer failed
[ 15.179392] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_a is not found!
[ 15.179397] rkvdec2_init:707: No niu aclk reset resource define
[ 15.179401] mpp_rkvdec2 fdc38100.rkvdec-core: shared_niu_h is not found!
[ 15.179404] rkvdec2_init:710: No niu hclk reset resource define
[ 15.179940] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_a is not found!
[ 15.179944] rkvdec2_init:707: No niu aclk reset resource define
[ 15.179948] mpp_rkvdec2 fdc48100.rkvdec-core: shared_niu_h is not found!
[ 15.179950] rkvdec2_init:710: No niu hclk reset resource define
[ 15.181731] mpp_iommu_probe:405: failed to get device node
[ 15.181736] mpp_av1dec av1d-master: failed to attach iommu
[ 15.308728] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.314246] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.319758] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.325274] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.330786] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.345752] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.351267] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.356779] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.362291] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.367802] dwhdmi-rockchip fde80000.hdmi: i2c read err!
[ 15.446175] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy pll locked!
[ 15.446416] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy lane locked!
[ 15.707367] rk806 spi2.0: no sleep-setting state
[ 15.711984] rk806 spi2.0: no reset-setting pinctrl state
[ 15.717289] rk806 spi2.0: no dvs-setting pinctrl state
[ 15.846322] rockchip-usbdp-phy fed80000.phy: trsv ln0 mon rx cdr lock timeout
[ 16.064729] rockchip-mipi-csi2: Async registered subdev
[ 16.134121] arm-scmi firmware:scmi: Failed. SCMI protocol 17 not active.
[ 16.144586] debugfs: File 'Capture' in directory 'dapm' already present!
[ 16.166139] debugfs: Directory 'fb000000.gpu-mali' with parent 'vdd_gpu_s0' already present!
[ 16.500031] debugfs: File 'Left Hp mixer' in directory 'dapm' already present!
[ 16.507238] debugfs: File 'Right Hp mixer' in directory 'dapm' already present!
[ 16.514535] debugfs: File 'HPCP L' in directory 'dapm' already present!
[ 16.521135] debugfs: File 'HPCP R' in directory 'dapm' already present!
[ 16.527738] debugfs: File 'HPVOL L' in directory 'dapm' already present!
[ 16.534425] debugfs: File 'HPVOL R' in directory 'dapm' already present!
[ 16.542487] ov5648 8-0036: could not get default pinstate
[ 16.547877] ov5648 8-0036: could not get sleep pinstate
[ 16.556039] ov5648 8-0036: Unexpected sensor id(000000), ret(-5)
[ 16.563294] rockchip_headset rk-headset: Can not read property headset_gpio
[ 16.571579] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdab0000-0xfdabffff]
[ 16.580098] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdac0000-0xfdacffff]
[ 16.588608] RKNPU fdab0000.npu: can't request region for resource [mem 0xfdad0000-0xfdadffff]
[ 16.600643] debugfs: Directory 'fdab0000.npu-rknpu' with parent 'vdd_npu_s0' already present!
[ 16.631627] RKNPU fdab0000.npu: failed to find power_model node
[ 16.637538] RKNPU fdab0000.npu: RKNPU: failed to initialize power model
[ 16.644137] RKNPU fdab0000.npu: RKNPU: failed to get dynamic-coefficient

@大法师 为什么新的引导加载程序不支持从我的 cool pi 4 上的 USB 驱动器引导？

@george I did this procedure and now my board wont boot from my emmc module or from usb. maybe it wont boot at all. is there a fix?

I updated the boot loader with the most recent version on the drive but i still cant boot the debian 11 image from USB. Do you know a fix?

@jack_admin it does not work. i have the official raspberry pi touchscreen plugged into dsi and it doesnt work.

dsi does not work with this unit. caution before you buy.

@大法师 said in Pi板DSI配件测试:

RK3588集成DWC-MIPI-DSI2 ，它是一个实现 MIPI-DSI2 规范中定义的所有协议功能的控制器，兼容 D-PHY 和 C-PHY 的物理接口，支持两路的 Display Stream Compression (DSC) 数据传输，RK3588 有两个 DSI-2 控制器和两个独立的物理的 D/C-PHY，可以同时最多支持两路 MIPI 输出。

DSI displays do not work with this unit. caution before you buy.

coolpi/coolpi is the username and password for the debian build. people need to do a better job of documenting on this forum.

@george its exactly correct based on other screenshots of the ubuntu 22.0.4 builds seen on here that also show a username of ubuntu and somewhere someone shared their password as coolpi. i was able to figure it out when i plugged in an hdmi cable. before that was just trying to access terminal through UART.

@george i was trying to log in via com port but on serial connection. i didnt find it documented so anyone else that runs into the issue the username is ubuntu and the password is coolpi