From: "Michael D. Burkey" <mdburkey@gmail.com>
To: barebox@lists.infradead.org
Subject: i.MX6Q Boot from NAND
Date: Wed, 26 Feb 2014 15:49:37 -0500 [thread overview]
Message-ID: <CAO6XYUt7KaraGNUkTuEkQXKbh0f6MH4Ywn8dDJQpo1RkT2CaSw@mail.gmail.com> (raw)
>Hi ANdreas,
>
>On Wed, Feb 26, 2014 at 07:30:59AM +0100, andreas.willig at rafi.de wrote:
>> Hi,
>>
>> has anyone in the community successfully managed to get Barebox
>> running out of NAND on i.MX6Q/DL? I cannot find any support for BCB /
>> FCB in the BB sources and am hitting problems while migrating from
>> i.mx28 (MXS?) sources of BCB. U-Boot seems to run from NAND on i.MX6Q
>> but is not an option for our project.
>
>So far I used kobs-ng for doing this, I didn't have luck with migrating
>the i.MX28 BCB code so far. Somebody asked the same question a while
>ago, but I can't remember who it was. He didn't report success so far
>either.
>
>Sascha
Andreas,
The person Sascha remembers asking about this was probably me.
I've started working on porting the bcb generation code from kobs-ng
over to barebox but haven't gotten it working either (and haven't had
time to work on it in several weeks).
That said, barebox itself works and boots fine from NAND as long as
you use kobs-ng to put it there. The other partitions can be written
to without issue from barebox directly (i.e. kernel, environment,
root, etc).
What I do:
Boot all the way to Linux command line on the target, making sure that
my barebox-*.img file is available either on USB flash or SD.
Then from the Linux command line:
kobs-ng init barebox-(whatever).img --search_exponent=1
After this, barebox should boot up nicely from NAND.
Eventually, I may get back to finishing up porting the bcb code, but
it won't be in the near future due to other schedule constraints.
Michael Burkey
PS...
Out of curiosity, which SOM are you using that boots from NAND?
I'm currently working with Variscite's SOM -- and life would have been
much simpler if someone had just put a SPI NOR on it!
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2014-02-26 20:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 20:49 Michael D. Burkey [this message]
2014-02-27 7:38 ` Sascha Hauer
-- strict thread matches above, loose matches on Subject: below --
2014-02-26 6:30 andreas.willig
2014-02-26 7:06 ` Sascha Hauer
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=CAO6XYUt7KaraGNUkTuEkQXKbh0f6MH4Ywn8dDJQpo1RkT2CaSw@mail.gmail.com \
--to=mdburkey@gmail.com \
--cc=barebox@lists.infradead.org \
/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