public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Wed, 02 May 2012 08:55:01 +0200	[thread overview]
Message-ID: <4FA0DA45.4090702@ftemaximal.fr> (raw)
In-Reply-To: <4F9AD9D7.6060009@freescale.com>

>> Assuming you load the kernel to ram with tftp (and that "AppKernel" is
>> an mtdparts partition in NAND), then you could do:
>>
>> nand erase.part AppKernel
>> tftp $load_addr uImage
>> crc32 $load_addr $filesize
>> nand write.i $load_addr AppKernel $filesize
>> nand read.i $load_addr AppKernel $filesize
>> crc32 $load_addr $filesize
>>
>> To verify the CRCs match between what you load off tftp and what you
>> read back from NAND.
Everything works fine now.
I now use "nand write.i" and "nand read.i" instead of "nand write" and 
"nand.read".
>> Does STLinux have a support contact?
>>
>> This list is for mainline U-Boot.  Have you checked whether these chips
>> are supported in current mainline U-Boot?
It was just a misunderstanding of u-boot commands.

Thank you guys for your help.

  reply	other threads:[~2012-05-02  6:55 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
2012-04-27 14:29       ` Peter Barada
2012-04-27 17:39         ` Scott Wood
2012-05-02  6:55           ` Alexandre Gambier [this message]
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=4FA0DA45.4090702@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