Hi Kever, On Wed, Jul 17, 2019 at 6:23 PM Kever Yang <kever.yang@xxxxxxxxxxxxxx> wrote: > > Hi Jagan, > > I'm sure this patch have some problem with evb-rk3399, which I > think make the ddr not init correctly and error happen in ATF. Would you help to share the log for this. I made test on Nanopi-m4 which has same ddr type as evb, LPDDR3 and it booted fine with mainline ATF (with PLAT=rk3399 bl31). Below is the log details. U-Boot TPL 2019.07-00145-gcb5756d9e2-dirty (Jul 18 2019 - 14:55:23) Channel 0: LPDDR3, 933MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=32 Size=2048MB Channel 1: LPDDR3, 933MHz BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=32 Size=2048MB 256B stride Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2019.07-00145-gcb5756d9e2-dirty (Jul 18 2019 - 14:55:23 +0530) Trying to boot from MMC1 U-Boot 2019.07-00145-gcb5756d9e2-dirty (Jul 18 2019 - 14:55:23 +0530) Model: FriendlyElec NanoPi M4 DRAM: 3.9 GiB MMC: dwmmc@fe310000: 2, dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from MMC... *** Warning - bad CRC, using default environment In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: FriendlyElec NanoPi M4 Let me know if have anything to add? Jagan. _______________________________________________ Linux-rockchip mailing list Linux-rockchip@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/linux-rockchip
