I use CM4s on the Turing Pi board. I have been able to flash images to the CM4s without any problems. However, when I tried to flash a U-Boot image I think something went wrong. From this moment on I am unable to boot up the CM4 and no matter what I do I get the following output:
When I flashed images I always wrote them to the eMMC storage. I think the U-Boot image has somehow changed the boot order and therefore that the CM4 is no longer booting from the eMMC. I tried to set the CM4 into USB Boot Mode and use rpiboot to access the CM4 but this didn't work. The CM4 is not recognized by Windows or Linux. I also flashed a SD-card with the SD Card Boot image and put it into the SD-card slot of the CM4 carrier board but this also didn't change the situation. How can I troubleshoot this when I am unable to change the boot order of the CM4? Is there another solution I can try?
Code:
OTP boardrev d03141 bootrom 48b0 48b0RPi: RPIBOOT release VERSION:8ba17717 DATE: 2023/01/11 TIME: 17:40:52BOOTMODE: 0x07 partition 0 build-ts BUILD_TIMESTAMP=1673458852 serial 6c98e803 boardrev d03141 stc 2930095PM_RSTS: 0x00001000part 00000000 reset_info 00000000uSD voltage 3.3VInitialising SDRAM 'Micron' 32Gb x2 total-size: 64 Gbit 3200DDR 3200 1 0 64 152Boot mode: RPIBOOT (03) order f1Read config.txt bytes 0 hnd 0x0SIG pieeprom.sig 0000000000000000000000000000000000000000000000000000000000000000 0Bad signature pieeprom.sigRead start4.elf bytes 301628 hnd 0x0Read fixup4.dat bytes 0 hnd 0x00x00d03141 0x00000000 0x00000fffMEM GPU: 76 ARM: 948 TOTAL: 1024Starting start4.elf @ 0xc1000200 partition -1+[ 1.595114] brcm-pcie fd500000.pcie: link down[ 1.582315] brcm-pcie fd500000.pcie: link downStatistics: Posted by WSwinks — Mon Mar 10, 2025 10:45 pm — Replies 0 — Views 39