ff255

Hello, I had a similar problem - unbootable Rock64 after kernel upgrade from 6.6.x to 6.12.x (error: Wrong Ramdisk Image Format). You can look in this thread djurny found a solution, that works for me. Maybe it will help.

Yay, it booted! 😃👏 @djurny , thank you very much! 🙏 bootlog from UART console Sorry, I gave wrong size for DT file... That seems right: /boot/dtb-6.12.9-current-rockchip64/rockchip# ls -l |grep rock64 -rw-r--r-- 1 root root 54333 Jan 12 2025 rk3328-rock64.dtb I guess it's ok until DT is smaller than align size So AFAICS if kernel size will grow, I should just re-calc the values? But now I got another problem, with this kernel HDMI suddenly stopped working... and all 3 LEDs (dc in, pwr, stby) are ON at the same time... although this seems to be a separate topic.. UPD: after apt-mark unhold kernel, dtb, firmware packages, apt-updating (to 6.12.58 kernel) and rebooting HDMI started to work again! For me this topic is solved, thank you once again! 👍 (Now I just wonder where that load address values come from, and why they didn't auto-change on kernel upgrade...)

Hello, @djurny 👋 Thank you for helping! I'm happy to provide as much info as I can Yes, I tried to load the same kernel (6.12.9) and got exactly the same error. cd /boot/ ls -al ... -rw-r--r-- 1 root root 17928050 Jan 15 2025 initrd.img-6.12.9-current-rockchip64 ... -rw-r--r-- 1 root root 36473344 Jan 12 2025 vmlinuz-6.12.9-current-rockchip64 As I can guess this is DT file: cd /boot/dtb-6.12.9-current-rockchip64/rockchip/overlay/ ls -al ... -rw-r--r-- 1 root root 2825 Jan 12 2025 rockchip-fixup.scr ...

Hello, sorry for late answer, but I had no time to experiment with my rock64 board. Maybe this issue is already resolved, if so please let me know. I'm still using kernel 6.6.63 and holding kernel packages in order not to break a working home server. So I managed to temporary switch kernel to 6.12.9 again for testing (copied old /boot and corrected symlinks) and enter UART console: Here is output of U-Boot commands you asked: Hit any key to stop autoboot: 0 => setenv b => setenv c => setenv a "a/b" => setexpr b sub "a/" "" a Unknown command 'setexpr' - try 'help' => echo ${b} => setexpr c 1 + 1 Unknown command 'setexpr' - try 'help' => echo ${c} => fdt fdt - flattened device tree utility commands Usage: fdt addr [-c] <addr> [<length>] - Set the [control] fdt location to <addr> fdt move <fdt> <newaddr> <length> - Copy the fdt to <addr> and make it active fdt resize [<extrasize>] - Resize fdt to size + padding to 4k addr + some optional <extrd fdt print <path> [<prop>] - Recursive print starting at <path> fdt list <path> [<prop>] - Print one level starting at <path> fdt get value <var> <path> <prop> - Get <property> and store in <var> fdt get name <var> <path> <index> - Get name of node <index> and store in <var> fdt get addr <var> <path> <prop> - Get start address of <property> and store in <var> fdt get size <var> <path> [<prop>] - Get size of [<property>] or num nodes and store in <var> fdt set <path> <prop> [<val>] - Set <property> [to <val>] fdt mknode <path> <node> - Create a new node after <path> fdt rm <path> [<prop>] - Delete the node or <property> fdt header - Display header info fdt bootcpu <id> - Set boot cpuid fdt memory <addr> <size> - Add/Update memory node fdt rsvmem print - Show current mem reserves fdt rsvmem add <addr> <size> - Add a mem reserve fdt rsvmem delete <index> - Delete a mem reserves fdt chosen [<start> <end>] - Add/update the /chosen branch in the tree <start>/<end> - initrd start/end addr NOTE: Dereference aliases by omitting the leading '/', e.g. fdt print ethernet0. => echo ${fdtfile} rockchip/rk3328-rock64.dtb => echo ${fdt_addr_r} 0x01f00000 => echo ${kernel_addr_r} 0x02000000 => echo ${ramdisk_addr_r} 0x04000000 => ver U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:39 +0000) aarch64-linux-gnu-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0 GNU ld (GNU Binutils for Ubuntu) 2.30 => CTRL-A Z for help | 1500000 8N1 | NOR | Minicom 2.10 | VT102 | Offline | ttyUSB0 I have set up rock64 to boot from SSD connected over USB3-SATA adapter (bought from pine64 store) without SD-card. To make it work I flashed latest U-Boot from ayufan to SPI by this tutorial. Maybe this error because of old U-Boot, and you're right, looks like it doesn't support setexpr command djurny, thank you for looking into this. And one question I don't understand, if I should upgrade U-Boot in SPI or I should erase SPI and wirte U-boot somewhere else? And will I be able to boot directly from USB-SSD without SD-card after that?

Hello/ Yes, I have also stumbled on this. It took me a night to figure out and fix what had happened. My rock64 was set to auto-reboot on unattended upgrades, and after auto upgrade to 6.12.9 on 2025-01-16 it refused to boot (I found 6.12.9 in /boot dir). After connecting UART I got the same error: DDR version 1.13 20180428 ID:0x805 N In SRX LPDDR3 786MHz Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB ddrconfig:7 OUT U-Boot SPL 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:17) board_init_sdmmc_pwr_en setup_ddr_param 1 booted from SPI flash Trying to boot from SPI NOTICE: BL31: v1.3(debug):9d3f591 NOTICE: BL31: Built : 14:39:02, Jan 17 2018 NOTICE: BL31:Rockchip release version: v1.3 INFO: ARM GICv2 driver initialized INFO: Using opteed sec cpu_context! INFO: boot cpu mask: 1 INFO: plat_rockchip_pmu_init: pd status 0xe INFO: BL31: Initializing runtime services WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s dK ERROR: Error initializing runtime service opteed_fast INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x200000 INFO: SPSR = 0x3c9 U-Boot 2017.09-rockchip-ayufan-1065-g95f6152134 (Apr 06 2020 - 08:10:39 +0000) Model: Pine64 Rock64 DRAM: 4 GiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303135000000000e2b23 serial=2e629a67b70686a Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 Card did not respond to voltage select! mmc_init: -95, time 10 starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: Core Release: 3.10a USB3: Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.10 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found Device 0: Vendor: JMicron Rev: 0409 Prod: Generic Type: Hard Disk Capacity: 122104.3 MB = 119.2 GB (250069680 x 512) ... is now current device Scanning usb 0:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 235 ms (12.7 KiB/s) ## Executing script at 00500000 Boot script loaded from usb 0 166 bytes read in 209 ms (0 Bytes/s) 17928114 bytes read in 1128 ms (15.2 MiB/s) 36473344 bytes read in 1935 ms (18 MiB/s) 54333 bytes read in 1433 ms (36.1 KiB/s) 2825 bytes read in 1809 ms (1000 Bytes/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... Speed: 1000, full duplex BOOTP broadcast 1 BOOTP broadcast 2 BOOTP broadcast 3 ... Thanks to your message and recovery instructions, I managed to repeat it and got a working board! 👍 But now I used armbian-config and selected "SY203 - Disable Armbian kernel upgrades" Seems like it's working # apt-mark showhold armbian-firmware linux-dtb-current-rockchip64 linux-image-current-rockchip64 Thank you very much! 🙏