From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul B. Henson Date: Mon, 22 Apr 2013 17:42:09 -0700 Subject: [U-Boot] freescale i.MX28 mxsboot NAND booting on mx28evk bad blocks In-Reply-To: References: <5147B63F.4020407@acm.org> <515FA485.1090709@acm.org> <516601B6.2050801@acm.org> <516701FD.5060407@acm.org> <5171E972.8000400@acm.org> Message-ID: <5175D8E1.5080304@acm.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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.