[U-Boot] Regression on ESPRESSObin / status of upstreaming

[Jan Kiszka]

Hi all,

I was playing with upstream u-boot on the ESPRESSObin - what an 
entertaining build process... Anyway, I noticed that, when using latest 
version of Marvell's ATF, a3700-utils and mv-ddr-marvell (all on 18.06), 
I can make u-boot 2018.05 at least boot. However, anything >= 2018.07 
will crash like this:


TIM-1.0 
 
 

WTMI-devel-18.05.0-06b6160 
 
 

WTMI: system early-init 
 
 

CPU VDD voltage default value: 1.155V 
 
 


Fill memory before self refresh...done 
 
 


Fill memory before self refresh...done 
 
 


Now in Self-refresh Mode 
 
 

Restore termination values to original values 
 
 

Exited self-refresh ... 
 
 



Self refresh Pass. 
 
 

DDR self test mode test done!! 
 
 


Self refresh Pass. 
 
 

DDR self test mode test done!! 
 
 


QS GATING 
 
 

============= 
 
 

Calibration done: cycle = 0x00 tap =0x61 
 
 

CH0_PHY_RL_Control_CS0_B0[0xC0001180]: 0x00000061 
 
 

CH0_PHY_RL_Control_CS0_B1[0xC0001184]: 0x00000061 
 
 



QS GATING 
 
 

============= 
 
 

Calibration done: cycle = 0x00 tap =0x5D 
 
 

CH0_PHY_RL_Control_CS1_B0[0xC00011A4]: 0x0000005D 
 
 

CH0_PHY_RL_Control_CS1_B1[0xC00011A8]: 0x0000005D 
 
 


DLL TUNING 
 
 

============== 
 
 

    DLL 0xc0001050[21:16]: [0,28,14] 
 
 

    DLL 0xc0001050[29:24]: [4,33,1b] 
 
 

    DLL 0xc0001054[21:16]: [0,2b,15] 
 
 

    DLL 0xc0001054[29:24]: [8,32,1d] 
 
 

    DLL 0xc0001074[21:16]: [0,3f,1f] 
 
 

    DLL 0xc0001074[29:24]: [0,3f,1f] 
 
 

  DLL: pass  NOTICE:  Booting Trusted Firmware 
 
 

NOTICE:  BL1: v1.4(release):armada-18.05.2:v1.4-454-g80bbf686 
 
 

NOTICE:  BL1: Built : 11:31:27, Aug 25 2018 
 
 

NOTICE:  BL1: Booting BL2 
 
 

NOTICE:  BL2: v1.4(release):armada-18.05.2:v1.4-454-g80bbf686 
 
 

NOTICE:  BL2: Built : 11:31:28, Aug 25 2018 
 
 

NOTICE:  BL1: Booting BL31 
 
 

NOTICE:  BL31: v1.4(release):armada-18.05.2:v1.4-454-g80bbf686 
 
 

NOTICE:  BL31: Built : 11:3 
 
 


U-Boot 2018.09-rc2-00093-g2418734ed4 (Aug 25 2018 - 13:33:43 +0200) 
 
 


DRAM:  512 MiB 
 
 

Comphy-0: UNCONNECTED   2.5 Gbps 
 
 

Comphy-1: UNCONNECTED   5 Gbps 
 
 

Comphy-2: SATA0         5 Gbps 
 
 

SATA link 0 timeout. 
 
 

AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode 
 
 

flags: ncq led only pmp fbss pio slum part sxs 
 
 

"Synchronous Abort" handler, esr 0x96000210 
 
 

elr: 0000000000035c98 lr : 0000000000035c6c (reloc) 
 
 

elr: 000000001ff75c98 lr : 000000001ff75c6c 
 
 

x0 : 00000000d0074000 x1 : 0000000000000000 
 
 

x2 : 00000000d0088000 x3 : 0000000000000008 
 
 

x4 : 0000000000000000 x5 : 000000001ffbf678 
 
 

x6 : 000000000000000a x7 : 000000001ffbf718 
 
 

x8 : 0000000000000020 x9 : 0000000000000008 
 
 

x10: 00000000000013d4 x11: 000000001fb2d3bc 
 
 

x12: 00000000000013e6 x13: 0000000000000a20 
 
 

x14: 0000000000000000 x15: 000000001fb2d648 
 
 

x16: 000000001ffbcb2a x17: 000000001ffbcb2a 
 
 

x18: 000000001fb2fde8 x19: 000000001fb31ae0 
 
 

x20: 000000001fb318c0 x21: 0000000000000000 
 
 

x22: 0000000000000000 x23: 0000000000000000 
 
 

x24: 0000000000000000 x25: 0000000000000000 
 
 

x26: 0000000000000000 x27: 0000000000000000 
 
 

x28: 0000000000000000 x29: 000000001fb2d4d0 
 
 


Resetting CPU ...


Known issue? I was always using the related defconfig.

Moreover, there still seems to be some feature gaps:

- Only 512M of RAM is detected, although ATF was configured for the 1G I
   have on my ESPRESSObin, and downstream Marvell u-boot detect that.

- MMC is not detected, at least in the working version (but I found no
   suspicious commits since then to change that).

So even without the crash, those two issues would be blockers of moving 
to upstream. Are they related to any misconfiguration on my side, or are 
they known limitations? Then what are the plans to resolve them?

Thanks,
Jan