Tomogo Posted June 5 Posted June 5 Hi, I have tried Rock 5b images with Kernel 6.8.10. Any of image I've tested will not start. No LED flashing, no HDMI signal.. nothing. The others with Kernel 6.1.43 starts fine. 0 Quote
Solution Tomogo Posted June 5 Author Solution Posted June 5 Hi, I hate you (sorry just joke) 🙂 I have no UART to USB cable so I found old Teensy 3.2 board. Made program for Serial to USB bridge. Updated SPI flash with new firmware with debug mode. And.... It works now! Dam or huray... 😉 LPDDR4X, 2112MHz channel[0] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[1] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[2] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB channel[3] BW=16 Col=10 Bk=8 CS0 Row=17 CS1 Row=17 CS=2 Die BW=8 Size=4096MB Manufacturer ID:0x6 CH0 RX Vref:27.5%, TX Vref:25.8%,25.8% CH1 RX Vref:25.8%, TX Vref:25.8%,25.8% CH2 RX Vref:27.9%, TX Vref:24.8%,24.8% CH3 RX Vref:27.1%, TX Vref:24.8%,24.8% change to F1: 528MHz change to F2: 1068MHz change to F3: 1560MHz change to F0: 2112MHz out U-Boot SPL board init U-Boot SPL 2017.09-gd1cf49135ee-220414-dirty #stephen (May 23 2024 - 19:39:28) Trying to boot from MMC2 MMC: no card present mmc_init: -123, time 0 spl: mmc init failed with error: -123 Trying to boot from MTD2 Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking atf-1 0x00040000 ... sha256(a7d1d8d191...) + OK ## Checking uboot 0x00200000 ... sha256(25a398ffe0...) + OK ## Checking fdt 0x0031e9f8 ... sha256(5bee414074...) + OK ## Checking atf-2 0xff100000 ... sha256(4b2065349b...) + OK ## Checking atf-3 0x000f0000 ... sha256(aa71013e72...) + OK Jumping to U-Boot(0x00200000) via ARM Trusted Firmware(0x00040000) Total: 489.724/719.766 ms INFO: Preloader serial: 2 NOTICE: BL31: v2.3():v2.3-682-g4ca8a8422:derrick.huang, fwver: v1.45 NOTICE: BL31: Built : 10:11:21, Dec 27 2023 INFO: spec: 0x1 INFO: code: 0x88 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: l3 cache partition cfg-0 INFO: system boots from cpu-hwid-0 INFO: disable memory repair 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 WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initialization. SMC`s destined for OPTEE will return SMC_UNK 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-gd1cf49135ee-220414-dirty #stephen (May 23 2024 - 19:39:28 +0800) Model: Radxa ROCK 5B MPIDR: 0x81000000 PreSerial: 2, raw, 0xfeb50000 DRAM: 16 GiB Sysmem: init Relocation Offset: eda3f000 Relocation fdt: eb9f96c0 - eb9fecc8 CR: M/C/I Using default environment DM: v2 mmc@fe2c0000: 1, mmc@fe2e0000: 0 Bootdev(assign): mmc 0 MMC0: HS400 Enhanced Strobe, 200Mhz PartType: EFI No misc partition boot mode: None FIT: No boot partition Failed to load DTB, ret=-2 No valid DTB, ret=-22 Failed to get kernel dtb, ret=-22 Model: Radxa ROCK 5B MPIDR: 0x81000000 CLK: (sync kernel. arm: enter 1008000 KHz, init 1008000 KHz, kernel 0N/A) b0pll 24000 KHz b1pll 24000 KHz lpll 24000 KHz v0pll 24000 KHz aupll 24000 KHz cpll 1500000 KHz gpll 1188000 KHz npll 24000 KHz ppll 1100000 KHz aclk_center_root 702000 KHz pclk_center_root 100000 KHz hclk_center_root 396000 KHz aclk_center_low_root 500000 KHz aclk_top_root 750000 KHz pclk_top_root 100000 KHz aclk_low_top_root 396000 KHz Net: No ethernet found. Hit key to stop autoboot('CTRL+C'): 0 starting USB... No working controllers found USB is stopped. Please issue 'usb start' first. MMC: no card present mmc_init: -123, time 0 pcie@fe150000: PCIe Linking... LTSSM is 0x0 pcie@fe150000: PCIe Linking... LTSSM is 0x0 pcie@fe150000: PCIe Linking... LTSSM is 0x6 pcie@fe150000: PCIe Linking... LTSSM is 0x210023 pcie@fe150000: PCIe Link up, LTSSM is 0x230011 pcie@fe150000: PCIE-0: Link up (Gen3-x2, Bus0) pcie@fe150000: invalid flags type! Device 0: unknown device Device 1: unknown device switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3920 bytes read in 8 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0:1 172 bytes read in 8 ms (20.5 KiB/s) 26373283 bytes read in 112 ms (224.6 MiB/s) 32436736 bytes read in 142 ms (217.8 MiB/s) 163397 bytes read in 28 ms (5.6 MiB/s) Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' Fdt Ramdisk skip relocation No misc partition ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 26373219 Bytes = 25.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0x08300000 Booting using the fdt blob at 0x08300000 reserving fdt memory region: addr=8300000 size=8e000 Using Device Tree in place at 0000000008300000, end 0000000008390fff can't found rockchip,drm-logo, use rockchip,fb-logo WARNING: could not set reg FDT_ERR_BADOFFSET. failed to reserve fb-loader-logo memory WARNING: could not set reg FDT_ERR_BADOFFSET. Adding bank: 0x00200000 - 0xf0000000 (size: 0xefe00000) Adding bank: 0x100000000 - 0x3fc000000 (size: 0x2fc000000) Adding bank: 0x3fc500000 - 0x3fff00000 (size: 0x03a00000) Adding bank: 0x4f0000000 - 0x500000000 (size: 0x10000000) Total: 2321.467/3095.859 ms Starting kernel ... 0 Quote
Igor Posted June 5 Posted June 5 9 hours ago, Tomogo said: The others with Kernel 6.1.43 starts fine. Kernel 6.8.y is hit and miss. We need to separate download links somehow ... for now it was added "Kernel 6.8.y is at experimental support level! Not all features work but it runs fairy stable." to warn you. Its good to be there, as they are usable - where they work. I run several github runners on Rock5 without any troubles for months. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.