From: Heiko Stuebner <heiko@sntech.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] changes in rk3288 code have made me unable to boot u-boot on veyron speedy
Date: Sat, 09 Mar 2019 17:43:24 +0100 [thread overview]
Message-ID: <6885157.irWvDLHhSX@phil> (raw)
In-Reply-To: <20190309071522.lcrjhy5v4vmff7x5@proprietary-killer>
Hi Marty,
Am Samstag, 9. März 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_defconfig
> unable to produce a bootable image. Guidance and suggestions welcome.
>
> Current chromebook_speedy_defconfig results:
> U-Boot SPL 2019.04-rc3-03639-ge8e3f2d2d4 (Mar 09 2019 - 00:59:05 -0600)
> Trying to boot from SPI
> SPI probe failed.
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
>
> 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)
> Trying to boot from SPI
> initcall sequence 001511f4 failed at call 00101ad5 (err=-38)
> ### ERROR ### Please RESET the board ###
>
> 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
next prev parent reply other threads:[~2019-03-09 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 7:15 [U-Boot] changes in rk3288 code have made me unable to boot u-boot on veyron speedy Marty E. Plummer
2019-03-09 16:43 ` Heiko Stuebner [this message]
2019-03-09 22:45 ` Marty E. Plummer
2019-03-09 23:39 ` Heiko Stuebner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6885157.irWvDLHhSX@phil \
--to=heiko@sntech.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox