Hi,

Am Montag, Februar 03, 2020 20:41 CET, schrieb Kurt Miller 
<li...@intricatesoftware.com>:

> On Sun, 2020-02-02 at 23:01 +0100, Sebastian Reitenbach wrote:
> > Hi,
> >
> > got a Pine64 Rock64_V2.0 2017-0713, which is stuck booting miniroot66.fs.
> >
> > This is how I prepared the miniroot66.fs to boot on it, following 
> > INSTALL.arm64:
> >
> > ftp https://ftp.hostserver.de/pub/OpenBSD/snapshots/arm64/miniroot66.fs
> > dd if=miniroot66.fs of=/dev/rsd2c
> > mount /dev/sd2i /mnt
> > mkdir /mnt/rockchip
> > cp /usr/local/share/dtb/arm64/rockchip/rk3328-rock64.dtb /mnt/rockchip
> > umount /mnt
> > dd if=/usr/local/share/u-boot/rock64-rk3328/idbloader.img of=/dev/sd2c 
> > seek=64
> > dd if=/usr/local/share/u-boot/rock64-rk3328/u-boot.itb of=/dev/sd2c 
> > seek=16384
> >
> > the device itself boots the u-boot-erase-spi-rock64.img from 
> > ayufan-rock64/linux-u-boot
> > as well as NetBSD-evbarm-aarch64-202001141930Z-rock64.img. 
> > However, booting the prepared miniroot66.fs I'm stuck at:
> >
> >  cu -l /dev/cuaU0 -s 115200  
> > Connected to /dev/cuaU0 (speed 115200)
> >
> > U-Boot TPL 2020.01 (Jan 12 2020 - 02:16:54)
> > data training error
> > col error
> > data training error
> > LPDDR3, 800MHz
> > BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB
> >
>
> The 'col error' appears to be fixed after u-boot 2020.01 was
> released.
>
> I've backported the fix for it in the attached diff to our u-boot
> port. I've uploaded the rock64-rk3328 subdir with the fix here:
>
> http://www.intricatesoftware.com/distfiles/u-boot-2020.01p2.rock64-rk3328.tar.gz
>
> Could you test idbloader.img and u-boot.itb from it on both of your
> boards to see if it corrects the TPL memory training error you
> are seeing?

thanks a lot, but  it doesn't seem to help. error persists:
still has that errror:

U-Boot TPL 2020.01 (Feb 03 2020 - 13:20:32)
data training error
col error
data training error
LPDDR3, 800MHz
BW=16 Col=12 Bk=8 CS0 Row=16 CS=1 Die BW=8 Size=4096MB

On the good side, it doesn't seem to break the other one.

Sebastian

Reply via email to