From: Alexandre Gambier <a.gambier@ftemaximal.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Can't read kernel if bad blocks are present in partition
Date: Fri, 27 Apr 2012 09:16:54 +0200 [thread overview]
Message-ID: <4F9A47E6.9070706@ftemaximal.fr> (raw)
In-Reply-To: <4F99A1D5.5030005@freescale.com>
Hi,
>> Did you use "nand write.i" to write the kernel and "nand read.i" to
>> read the kernel? the ".i" tells u-boot to skip bad blocks...
No I use "nand read $load_addr AppKernel" cause I didn't know we can use
"nand read.i" - "help nand" doesn't display this information.
I tried "nand read.i" and now it works fine but I still can't boot the
kernel cause its crc is wrong I will flash the kernel again with "nand
write.i" and check if it works.
> That has been the default for a while now. Why use something as ancient
> as 1.3.1?
Because my embedded linux distribution is STLinux which includes support
for STM chips with this version of u-boot.
Alex.
next prev parent reply other threads:[~2012-04-27 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 11:27 [U-Boot] Can't read kernel if bad blocks are present in partition Alexandre Gambier
2012-04-26 17:11 ` Peter Barada
2012-04-26 19:28 ` Scott Wood
2012-04-27 7:16 ` Alexandre Gambier [this message]
2012-04-27 14:29 ` Peter Barada
2012-04-27 17:39 ` Scott Wood
2012-05-02 6:55 ` Alexandre Gambier
2012-04-27 17:43 ` Scott Wood
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=4F9A47E6.9070706@ftemaximal.fr \
--to=a.gambier@ftemaximal.fr \
--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