From: Helmut Raiger <helmut.raiger@hale.at>
To: u-boot@lists.denx.de
Subject: [U-Boot] Chain loading an u-boot from an u-boot
Date: Thu, 13 Feb 2014 10:45:01 +0100 [thread overview]
Message-ID: <52FC941D.5070705@hale.at> (raw)
In-Reply-To: <1392242383.6733.455.camel@snotra.buserror.net>
On 02/12/2014 10:59 PM, Scott Wood wrote:
>>
>> Most operations are read (we use a separate YAFFS partition for time
>> predictable writes),
>> so UBI will relocate read-only blocks anyway (due to read disturbances),
>> I think the
>> effect wont be too dramatic, but don't make me proof that ;-)
> This sounds like a very bad idea.
Agreed.
>> SPL on i.MX31 is limited to 2kB so we can't use BCH 4 here, just as you
>> guessed.
> You could use TPL (three stage extension of SPL). 2K SPL loads 126K
> TPL, which has BCH code and can load the real U-Boot.
>
> See doc/README.TPL, and include/configs/p1_p2_rdb_pc.h for an example.
Yes I read that, but it's not done for i.mx31 and I thought it might
be harder to do, than just a second u-boot. This might proof wrong.
>> jumping to it.
>> If I set a breakpoint in the do_go_exec() I can step right into the
>> second u-boot.
> Make sure you're cleaning the cache for that second load, if required.
Currently I turned off cashes in the first u-boot and hoped that would
do.
Helmut
--
Scanned by MailScanner.
next prev parent reply other threads:[~2014-02-13 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 11:11 [U-Boot] Chain loading an u-boot from an u-boot Helmut Raiger
2014-02-10 12:14 ` Andreas Bießmann
2014-02-10 12:57 ` Helmut Raiger
2014-02-12 21:59 ` Scott Wood
2014-02-13 9:45 ` Helmut Raiger [this message]
2014-02-11 9:38 ` Stefano Babic
2014-02-12 9:56 ` Helmut Raiger
2014-02-12 10:41 ` Stefano Babic
2014-02-12 10:45 ` Andreas Bießmann
2014-02-13 9:03 ` Helmut Raiger
2014-03-31 11:29 ` Helmut Raiger
2014-04-03 23:13 ` Simon Glass
2014-04-04 9:25 ` Stefano Babic
2014-04-09 14:07 ` Helmut Raiger
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=52FC941D.5070705@hale.at \
--to=helmut.raiger@hale.at \
--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