From: Matthias Fend <Matthias.Fend@wolfvision.net>
To: "guenter.gebhardt@rafi.de" <guenter.gebhardt@rafi.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: AW: Antwort: AW: imx53 internal boot from NAND
Date: Tue, 27 Mar 2012 08:35:20 +0200 [thread overview]
Message-ID: <0769D45835157F4282BC17DF611B07F00D1EF3EBA8@wolfserver9> (raw)
In-Reply-To: <OFE9729FBE.75DA1442-ONC12579CD.00510EF3-C12579CD.00512B14@o0802.rafi.inhouse>
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]
>Von: guenter.gebhardt@rafi.de [mailto:guenter.gebhardt@rafi.de]
>Gesendet: Montag, 26. März 2012 16:47
>An: Matthias Fend
>Cc: barebox@lists.infradead.org
>Betreff: Antwort: AW: imx53 internal boot from NAND
>
>Hello,
>
>I have some problems. May you please send me a binary produced with this tool?
>I want to inspect the flash header.
fcb.bin contains a FCB and was generated by this tool. It should instantly work with your i.mx53 barebox.
Note that the FCB image must reside within the first blocks of the NAND. The internal ROM loader will always read 4k blocks from NAND - independent of the actual NAND page size.
The attached FCB must be located at the start of the NAND. The barebox image must be located at page 2.
Assuming a 2k page NAND you should have this: page 0-1: 4k FCB, page 2-n: barebox.
~Matthias
>
>-- Gebhardt
>
>
>
>Von: Matthias Fend <Matthias.Fend@wolfvision.net>
>An: "guenter.gebhardt@rafi.de" <guenter.gebhardt@rafi.de>, "barebox@lists.infradead.org" <barebox@lists.infradead.org>
>Datum: 26.03.2012 11:09
>Betreff: AW: imx53 internal boot from NAND
>________________________________________
>
>
>
>Hi,
>
>For a quick start you can use the provided FCB (fcb.bin).
>This FCB was generated with the attached tool (fcbgen.c) - note that the bad block handling is disabled.
>
>Then you can "merge" your barebox image with the FCB with something like:
>cat fcb.bin barebox-image > barebox-fcb.bin
>
>This works at least on our custom i.MX53 hardware.
>
>~Matthias
>
>Von: barebox-bounces@lists.infradead.org [mailto:barebox-bounces@lists.infradead.org] Im Auftrag von guenter.gebhardt@rafi.de
>Gesendet: Montag, 26. März 2012 10:48
>An: barebox@lists.infradead.org
>Betreff: imx53 internal boot from NAND
>
>Hello,
>
>I tried to use barebox in order to boot from NAND.
>
>The ROM loader needs a FCB (Firmware Configuration Block) table at the beginning of the flash (according to chapter 7.5.2.2 of the reference manual).
>I looked at the existing imx53 boards within the barebox sources but I founx that no one used this mode there.
>
>Has someone done this or can give me some advice?
>
>-- Gebhardt
>[Anhang "fcbgen.c" gelöscht von Guenter Gebhardt/Rafi] [Anhang "fcb.bin" gelöscht von Guenter Gebhardt/Rafi]
[-- Attachment #2: fcb.bin --]
[-- Type: application/octet-stream, Size: 4096 bytes --]
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-03-27 6:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 8:47 guenter.gebhardt
2012-03-26 9:09 ` AW: " Matthias Fend
2012-03-26 14:46 ` Antwort: " guenter.gebhardt
2012-03-27 6:35 ` Matthias Fend [this message]
2012-03-27 5:32 ` Robert Schwebel
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=0769D45835157F4282BC17DF611B07F00D1EF3EBA8@wolfserver9 \
--to=matthias.fend@wolfvision.net \
--cc=barebox@lists.infradead.org \
--cc=guenter.gebhardt@rafi.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