From mboxrd@z Thu Jan  1 00:00:00 1970
From: Heiko Stuebner <heiko@sntech.de>
Date: Sat, 09 Mar 2019 17:43:24 +0100
Subject: [U-Boot] changes in rk3288 code have made me unable to boot
	u-boot on veyron speedy
In-Reply-To: <20190309071522.lcrjhy5v4vmff7x5@proprietary-killer>
References: <20190309071522.lcrjhy5v4vmff7x5@proprietary-killer>
Message-ID: <6885157.irWvDLHhSX@phil>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
To: u-boot@lists.denx.de

Hi Marty,

Am Samstag, 9. M=C3=A4rz 2019, 08:15:23 CET schrieb Marty E. Plummer:
> Was going to work on getting that usb->uart redirection code from the
> linux kernel into u-boot for rk3288, like we have for rk3188, but
> apparently there have been some changes which render chromebook_speedy_de=
fconfig
> unable to produce a bootable image. Guidance and suggestions welcome.
>=20
> Current chromebook_speedy_defconfig results:
> U-Boot SPL 2019.04-rc3-03639-ge8e3f2d2d4 (Mar 09 2019 - 00:59:05 -0600)  =
                                               =20
> Trying to boot from SPI
> SPI probe failed.
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>=20
> chromebook_speedy_defconfig with CONFIG_SPI_FLASH turned on (didn't get
> moved into the defconfig like the rest)
> U-Boot SPL 2019.04-rc3-03639-ge8e3f2d2d4 (Mar 09 2019 - 01:01:38 -0600)  =
                                               =20
> Trying to boot from SPI
> initcall sequence 001511f4 failed at call 00101ad5 (err=3D-38)
> ### ERROR ### Please RESET the board ###
>=20
> And enabling the full pinctrl driver and the needed libfdt stuff results
> in no output at all.

Maybe you could try the in flight patch from David first:
http://patchwork.ozlabs.org/patch/1040541/

In general I noticed in recent tries that rk3288 scrapes really narrow
at the 32kb limit of the sram, so possibly we'll need TPL on all rk3288
boards similar to what the rk3288-vyasa board already does now.


Heiko