foo Posted June 5, 2020 Share Posted June 5, 2020 Hey guys, bunch of thanks for your great work. Was wondering what's up with the latest buster images (20.05.2-5.4.43) for the 1Gig A versions. Worked great up to 20.02.11-5.4.32. The boot gets up to changing the freq, then nothing : > change freq to 416MHz 0,1 Channel 0: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB Channel 1: LPDDR4,416MHz Bus Width=32 Col=10 Bank=8 Row=14 CS=1 Die Bus-Width=16 Size=512MB 256B stride channel 0 CS = 0 MR0=0x19 MR4=0x3 MR5=0x6 MR8=0x0 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0xFF channel 1 CS = 0 MR0=0x19 MR4=0x3 MR5=0x6 MR8=0x0 MR12=0x72 MR14=0x72 MR18=0x0 MR19=0x0 MR24=0x8 MR25=0xFF channel 0 training pass! channel 0 training pass! channel 1 training pass! channel 0, cs 0, advanced training done Link to comment Share on other sites More sharing options...
Werner Posted June 6, 2020 Share Posted June 6, 2020 Can you try to increase the boot verbosity? https://docs.armbian.com/User-Guide_Fine-Tuning/#how-to-toggle-verbose-boot Link to comment Share on other sites More sharing options...
foo Posted June 6, 2020 Author Share Posted June 6, 2020 Unfortunately this is the output with Verbose=7. Link to comment Share on other sites More sharing options...
Igor Posted June 6, 2020 Share Posted June 6, 2020 On the download pages https://www.armbian.com/rock-pi-4/ its written "1Gb model currently not supported" which means its known that it doesn't work ... probably recent u-boot does not support this memory configuration. Device sits on my desk because of this reason, but time is missing component ... I could allocate it only to write that note and open a Jira https://armbian.atlassian.net/browse/AR-282 Link to comment Share on other sites More sharing options...
foo Posted June 6, 2020 Author Share Posted June 6, 2020 (edited) Understood, is cool Igor, I sow the message, I was just curious to see what is the issue. Btw is the RAM configuration done only here: "/arch/arm/mach-rockchip/sdram_common.c" ? Edited June 6, 2020 by foo Link to comment Share on other sites More sharing options...
piter75 Posted June 6, 2020 Share Posted June 6, 2020 1 hour ago, foo said: I was just curious to see what is the issue From your log it seems that the issue is way before u-boot - in DDR blob from Rockchip. Can you check if booting this image is successful for you? It is built using Armbian master with DDR binary downgraded from v1.24 to v1.20 - the version used by Radxa to build their images. Both versions work on my 4GB unit but I guess v1.20 was thoroughly tested on 1GB unit by Radxa ;-) Link to comment Share on other sites More sharing options...
foo Posted June 6, 2020 Author Share Posted June 6, 2020 @piter75 Cool thanks I will test it! Link to comment Share on other sites More sharing options...
foo Posted June 6, 2020 Author Share Posted June 6, 2020 @piter75 Indeed you are right. Thanks, it neatly works. The log here . Would you mind to share how you patched the build process, i'll try to build a stable "a" version too. Link to comment Share on other sites More sharing options...
piter75 Posted June 6, 2020 Share Posted June 6, 2020 16 minutes ago, foo said: Would you mind to share how you patched the build process I am glad it worked! The fix is pretty straightforward ;-) Link to comment Share on other sites More sharing options...
foo Posted June 6, 2020 Author Share Posted June 6, 2020 (edited) Awesome! hope we get the fix it in 20.05. Wondering what has Rockchip "fixed" with the v1.24 tho. Is there a release doc somewhere to read for this version? Edited June 6, 2020 by foo Link to comment Share on other sites More sharing options...
Recommended Posts