From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks
Date: Fri, 26 Apr 2013 03:13:33 +0200 [thread overview]
Message-ID: <201304260313.33532.marex@denx.de> (raw)
In-Reply-To: <5175D8E1.5080304@acm.org>
Dear Paul B. Henson,
> On 4/19/2013 6:22 PM, Trent Piepho wrote:
> >> Hmm, possibly; I guess that would be conceptually simpler but
> >> require more commands to execute to get done.
> >
> > Don't see why. If mxsboot wrote both files at once, there'd be the
> > same number of commands to generate them.
>
> Well, you'd have to copy two files instead of one to say SD, and run the
> mmcload command twice instead of once, but now I'm just being pedantic :).
>
> > While U-boot gets the first one correct (other than the bad block
> > marker), it doesn't write the 3 after it correctly.
>
> So if the first one were ever corrupted, the boot would fail. It seems
> like that would be worth fixing.
>
> > supports two firmware images to boot from. That's one of the reasons
> > why the output of mxsboot is so big, as it contains two images. It's
> > not clear to me if the bootloader supports switching between image in
> > any useful way.
>
> From the limited understanding I have of it, no, the second image is
> only loaded if the first one fails.
I didn't really track the thread and I'm plenty busy, besides I had quite a
clash with Trent in another thread, sorry about me being plenty unpleasant.
Anyway, can you please sum what is going on and what you came up with?
Please also always CC Fabio, he is of great help.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-04-26 1:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 0:50 [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks Paul B. Henson
2013-03-19 23:23 ` Scott Wood
2013-03-20 21:20 ` Paul B. Henson
2013-03-20 21:24 ` Scott Wood
2013-04-04 10:09 ` Trent Piepho
2013-04-06 4:28 ` Paul B. Henson
2013-04-06 7:18 ` Trent Piepho
2013-04-11 0:20 ` Paul B. Henson
2013-04-11 12:03 ` Trent Piepho
2013-04-11 18:33 ` Paul B. Henson
2013-04-11 23:25 ` Trent Piepho
2013-04-20 1:03 ` Paul B. Henson
2013-04-20 1:22 ` Trent Piepho
2013-04-23 0:42 ` Paul B. Henson
2013-04-26 1:13 ` Marek Vasut [this message]
2013-04-29 20:54 ` Paul B. Henson
2013-04-29 21:01 ` Marek Vasut
2013-05-04 0:08 ` Marek Vasut
2013-05-04 6:21 ` Trent Piepho
2013-05-04 13:20 ` Marek Vasut
2013-04-13 14:42 ` Marek Vasut
2013-04-13 16:31 ` Trent Piepho
2013-04-13 18:26 ` Marek Vasut
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=201304260313.33532.marex@denx.de \
--to=marex@denx.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