Here is output with lowlevel debug: DDR 03ea844c5d typ 24/09/03-10:42:57,fwver: v1.23 In ... out >rockchip-dmc: rockchip_sdram_size(reg2=1000ea01, reg3=30000031) rockchip-dmc: rank 2 cs0_col 10 cs1_col 10 bk 3 cs0_row 17 cs1_row 17 bw 2 row_3_4 0 rockchip-dmc: rk3568_ram_sizes() = 8589934592 mmu: enabling MMU, ttb @ 0xedf80000 mmu: __arch_remap_range: 0x00000000+0x8000000000 type UNCACHED mmu: __arch_remap_range: 0x8000000000+0x8000000000 type UNCACHED mmu: __arch_remap_range: 0x00a00000+0xef600000 type RWX mmu: __arch_remap_range: 0xee000000+0x2000000 type FAULT mmu: __arch_remap_range: 0x00b00000+0x60000 type RWX
Everything looks good, but it hangs at this step. ср, 20 мая 2026 г. в 09:21, Sascha Hauer <[email protected]>: > > Hi Alexander, > > On 2026-05-20 08:15, Alexander Shiyan wrote: > > Hello Sascha. > > > > The first launch of the new release has failed. > > On the RK3568 platform, BL31 does not start. The size of the final > > binary has decreased from 1.5 MB > > to 930 KB - possibly due to the announced compression, but it seems to > > me that this is too > > large a reduction... > > Are there any additional settings/calls required for custom boards in > > the new release? > > No board level adjustments required. I just re-tested the relase on a > Rock-3a board using rockchip_v8_defconfig. It works here. > > The size reduction depends on the size of your firmware binaries. You > could look at the firmware/*.z files and compare with the original files > to see if that explains the size reduction. The TF-A and OP-TEE files > that I use only have around 700KiB in total, so a size reduction of > 600KiB would be unreasonable in my case. > > Do you have any console output to share? > > Sascha > > -- > Pengutronix e.K. | | > Steuerwalder Str. 21 | http://www.pengutronix.de/ | > 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
