RockPro64 with u-boot 2010.01

[Bernd Walter]

I'm trying to use the newer u-boot version, but failed.
Reason is that my 4G board only probes to 2G RAM with 2019.10.
According to that link it was during the 2010.01 release candidates:
http://u-boot.10912.n7.nabble.com/rockchip-rk3399-TPL-rockpro64-Wrong-memory-size-detected-td382441.html

I naively tried the following:
Index: u-boot-master/distinfo
===================================================================
--- u-boot-master/distinfo      (revision 527638)
+++ u-boot-master/distinfo      (working copy)
@@ -1,6 +1,8 @@
 TIMESTAMP = 1573202420
 SHA256 (u-boot/u-boot-2019.10.tar.bz2) = 8d6d6070739522dd236cba7055b8736bfe92b4fac0ea18ad809829ca79667014
 SIZE (u-boot/u-boot-2019.10.tar.bz2) = 14214608
+SHA256 (u-boot/u-boot-2020.01.tar.bz2) = aa453c603208b1b27bd03525775a7f79b443adec577fdc6e8f06974025a135f1
+SIZE (u-boot/u-boot-2020.01.tar.bz2) = 14716125
 SHA256 (u-boot/939129/raw) = 2a4ebf283aec8e74ec77b3cb071c6883f73807454ca94fea78361c7391187b97
 SIZE (u-boot/939129/raw) = 310
 SHA256 (u-boot/1036621/raw) = 28dbd66d14fab9dc782ce091d3c132a226b8425f6503c329ee8a7031b79b52f7
Index: u-boot-rockpro64/Makefile
===================================================================
--- u-boot-rockpro64/Makefile   (revision 527638)
+++ u-boot-rockpro64/Makefile   (working copy)
@@ -2,6 +2,7 @@
 
 MASTERDIR=     ${.CURDIR}/../u-boot-master
 
+UBOOT_VERSION?=        2020.01
 MODEL=         rockpro64
 BOARD_CONFIG=  rockpro64-rk3399_defconfig
 FAMILY=                rk3399

It build, but fails to boot:
U-Boot TPL 2020.01 (Mar 02 2020 - 23:33:30)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=16/15 CS=1 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...

U-Boot SPL 2020.01 (Mar 02 2020 - 23:33:30 +0100)
Trying to boot from MMC1


That's it - no further output.
Are there any other known traps when using a new u-boot version,
or does it have to be debugged the hard way?

I've left the first 10MB space untouched by partitions, since the u-boot
get's written starting at 8MB offset.
Geom name: da0
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 62333951
first: 63
entries: 4
scheme: MBR
Providers:
1. Name: da0s1
   Mediasize: 52428800 (50M)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 10485760
   Mode: r0w0e0
   efimedia: HD(1,MBR,00000000,0x5000,0x19000)
   attrib: active
   rawtype: 12
   length: 52428800
   offset: 10485760
   type: fat32lba
   index: 1
   end: 122879
   start: 20480
2. Name: da0s2
   Mediasize: 31851544576 (30G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 62914560
   Mode: r0w0e0
   efimedia: HD(2,MBR,00000000,0x1e000,0x3b54000)
   rawtype: 165
   length: 31851544576
   offset: 62914560
   type: freebsd
   index: 2
   end: 62332927
   start: 122880
Consumers:
1. Name: da0
   Mediasize: 31914983424 (30G)
   Sectorsize: 512
   Mode: r0w0e0

-- 
B.Walter <bernd at bwct.de> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.