[U-Boot] Booting on RK3399

[Mark Kettenis]

> From: Simon Glass <sjg at chromium.org>
> Date: Sat, 5 Jan 2019 08:56:07 -0700
> 
> Hi Mark,
> 
> On Fri, 4 Jan 2019 at 20:35, Simon Glass <sjg at chromium.org> wrote:
> >
> > Hi Mark,
> >
> > On Fri, 4 Jan 2019 at 13:43, Simon Glass <sjg at chromium.org> wrote:
> > >
> > > Hi Mark,
> > >
> > > On Fri, 4 Jan 2019 at 13:29, Mark Kettenis <mark.kettenis at xs4all.nl> wrote:
> > > >
> > > > > From: Simon Glass <sjg at chromium.org>
> > > > > Date: Fri, 4 Jan 2019 13:12:58 -0700
> > > > >
> > > > > Hi Mark,
> > > > >
> > > > > On Fri, 4 Jan 2019 at 12:43, Mark Kettenis <mark.kettenis at xs4all.nl> wrote:
> > > > > > So obviously that diff is needed to boot properly from uSD.  I'll send
> > > > > > out a git patch with a proper commit messages in a bit.
> > > > >
> > > > > Yes I have the diff. What toolchain version are you using?
> > > >
> > > > I'm using the following OpenBSD packages:
> > > >
> > > > aarch64-none-elf-binutils-2.27p0
> > > > aarch64-none-elf-gcc-linaro-6.3.2017.02p3
> > > >
> > > > which is binutils 2.27 and the Linaro GCC 6.3.2017.02 with minimal
> > > > patches to get them to build on OpenBSD.
> > >
> > > OK thank you. I'll try again when I get back. Something funny is going on.
> >
> > I pushed my tree to u-boot-dm/rk-working
> >
> > export ARCH=arm
> > CROSS_COMPILE=/opt/linaro/gcc-linaro-6.3.1-2017.02-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-
> > O=/tmp/b/firefly-rk3399
> >
> > /tmp/b/firefly-rk3399> ln -s
> > ~/cosarm/arm-trusted-firmware/build/rk3399/release/bl31/bl31.elf
> >
> > make -s firefly-rk3399_defconfig && make -s -j16 && make -s u-boot.itb
> > && /tmp/b/firefly-rk3399/tools/mkimage -n rk3399 -T rksd -d
> > /tmp/b/firefly-rk3399/spl/u-boot-spl.bin idbspl.img && sudo dd
> > if=idbspl.img of=/dev/sdb seek=64 && sudo dd
> > if=/tmp/b/firefly-rk3399/u-boot.itb of=/dev/sdb seek=16384 && sync
> >
> > Output is
> >
> > U-Boot SPL board init
> > abc.d123456 7fe90
> >
> > at which point it hangs.
> >
> > Hopefully I've done something silly in the setup. Any chance you could
> > share your image?
> >
> > Thanks for your help. I am sure I had the board running at one point.
> 
> Thanks for the image - I tried it with the same result. I think my
> board is 4GB - perhaps there is a memory init problem still?

Not inconceivable.  My board indeed only has 2GB.