From: Jonathan Gray <jsg@jsg.id.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] rk3288 SPL size
Date: Tue, 16 Apr 2019 16:49:12 +1000 [thread overview]
Message-ID: <20190416064912.GC16930@largo.jsg.id.au> (raw)
In-Reply-To: <8d0d7b3e-b50d-4b9e-3b3a-142b793e649c@phytec.de>
On Fri, Apr 05, 2019 at 12:10:21PM +0200, Wadim Egorov wrote:
> Hi,
>
> it seems the new common rockchip pinctrl driver does not really fit into
> our phycore-rk3288 SPL setup. It works for every other rk3288 based
> board because they don't need special power configurations at the SPL stage.
It turns out tinker-rk3288 SPL no longer fits in 2019.04 and previously
worked fine in 2019.01.
Warning: SPL image is too large (size 0x8800) and will not boot
Error: image verification failed
built with gcc-linaro 6.3.2017.02
bisecting led to the pinctrl changes.
with SPL_PINCTRL_ROCKCHIP disabled it fits and U-Boot output on
serial gets as far as the efi loader then no output appears on serial
when a kernel is loaded.
>
> So my question is: is there any work going on to reduce the SPL size
> even more?
>
> Besides that, I think I can remove the power stuff at the SPL stage from
> our board. The SOM was redesigned and is equipped with an STM8 connected
> to the RK818. The required setup we did before in the SPL is now done by
> the ST controller. I know there are only a few SOMs without the STM8 out
> in the wild. So if I remove it it will affect only a few people who
> probably already have both boards.
>
> Regards,
> Wadim
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
next prev parent reply other threads:[~2019-04-16 6:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 10:10 [U-Boot] rk3288 SPL size Wadim Egorov
2019-04-05 10:22 ` Heiko Stübner
2019-04-05 17:41 ` Philipp Tomsich
2019-04-16 6:49 ` Jonathan Gray [this message]
2019-04-16 7:12 ` Jonathan Gray
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=20190416064912.GC16930@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--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