public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Bo Shen <bard.shen@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] AT91SAM9M10 Custom Board U-boot reboot after Wrong Image Format
Date: Fri, 15 Mar 2013 10:09:09 +0800	[thread overview]
Message-ID: <514282C5.4010203@gmail.com> (raw)
In-Reply-To: <63f3857f52f5657a4a4817c11a38e566@netopen.com.br>

Hi Marcio,

On 3/14/2013 20:23, marcio at netopen.com.br wrote:
>
> Hi Bo Shen
>
> I have used a SAMBA old version and I managed to write
> the Linux Kernel that can be recognized by U-boot but now it sends a
> message "Veritying Checksum ....: Bad Data CRC. It seems that U-Boot is
> only reading the first sector OK and the rest of the Kernel is being
> worngly read.

Bad Data CRC don't help. Because, many possible issue will cause this issue.

Consider you use 16bit NAND flash. Have you define 
CONFIG_SYS_NAND_DBW_16 in board configuration header?

BTW, which bootstrap version do you use? (As I suspect the bootstrap has 
enabled for supporting 16bit NAND, so it read u-boot OK)

Please provide the log information output from dbgu.

>
> Thanks for your attention
>
> Marcio

Best Regards,
Bo Shen

  reply	other threads:[~2013-03-15  2:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 12:26 [U-Boot] AT91SAM9M10 Custom Board U-boot reboot after Wrong Image Format marcio at netopen.com.br
2013-03-14  1:26 ` Bo Shen
2013-03-14 12:01   ` marcio at netopen.com.br
2013-03-14 12:23   ` marcio at netopen.com.br
2013-03-15  2:09     ` Bo Shen [this message]
2013-03-15 18:46       ` marcio at netopen.com.br
2013-03-16  0:02         ` Bo Shen
2013-03-16 11:27           ` marcio at netopen.com.br
2013-03-16 14:58           ` marcio at netopen.com.br
2013-03-17  2:45             ` Bo Shen
2013-03-17 13:24               ` marcio at netopen.com.br
2013-03-15 19:56       ` marcio at netopen.com.br

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=514282C5.4010203@gmail.com \
    --to=bard.shen@gmail.com \
    --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