public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND on Davinci boards
Date: Wed, 16 Mar 2011 13:36:52 +0100	[thread overview]
Message-ID: <4D80AEE4.4060406@denx.de> (raw)
In-Reply-To: <4D80A927.6010307@ge.com>

On 03/16/2011 01:12 PM, Nick Thompson wrote:
> You may be correct, but maybe you have another problem first...

Yes, you are right...

>>
>>>
>>> Have you tried "nand dump" of a Linux programmed Kernel and compared it with
>>> "nand dump" of a U-Boot programmed Kernel?
>>
>> I have tried now to get the first page (=2048 bytes) from both and I
>> have compared byte-per-byte. They are identical, inclusive the oob part.
>>
>>> You would be able to see
>>> identical data in each case, but you will be able to compare the differences
>>> in the OOB. You only need to look at the first page to see if the OOB data
>>> or position of the OOB data differs.
>>
>> No differences at all. For both, I get in the oob:
>>
>> OOB:
>>         ff ff ff ff ff ff ff ff
>>         ff ff ff ff ff ff ff ff
>>         ff ff ff ff ff ff ff ff
>>         00 00 00 00 00 00 00 00
>>         00 00 00 00 00 00 00 00
>>         00 00 00 00 00 00 00 00
>>         00 00 00 00 00 00 00 00
>>         00 00 00 00 00 00 00 00
> 
> Is this really from the OOB for the first _kernel_ page. It looks wrong.

Yes. this is when I write the kernel from linux.

> 
> I see:
> 
>> nand dump 0x100000
> <snip>
>         ff ff ff ff ff ff ff ff
>         ff ff ff ff ff ff ff ff
>         ff ff ff ff ff ff ff ff
>         9a ea 40 97 85 bc 5f f5
>         2e 15 91 c2 c6 93 14 c0
>         03 e3 b6 4c 35 40 2d 8f
>         7e 74 10 13 59 47 cf 09
>         24 10 6a 0a 8b e2 f1 b0
> 
> The part after all the ff's is the ECC. IIRC a zero ECC implies all the
> data in the page is zero also. That would be an odd start to a Kernel
> image.
> 
> Can you confirm what it is you dumped?

Yes. This
However, when I write the kernel with u-boot, I get:

OOB:
	ff ff ff ff ff ff ff ff
	ff ff ff ff ff ff ff ff
	ff ff ff ff ff ff ff ff
	a7 af c5 ed 87 86 2f 1c
	f9 31 10 92 4a 34 5a 7d
	91 cf e0 fd b6 3f 4b ae
	ca 63 86 9c 2d 91 d2 6c
	95 73 1b 4b e0 09 ed a3

It looks like Linux has not written the ECCs at all....

Stefano

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de
=====================================================================

  reply	other threads:[~2011-03-16 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16  8:22 [U-Boot] NAND on Davinci boards Stefano Babic
2011-03-16 10:01 ` Nick Thompson
2011-03-16 12:01   ` Stefano Babic
2011-03-16 12:12     ` Nick Thompson
2011-03-16 12:36       ` Stefano Babic [this message]
2011-03-16 12:58         ` Nick Thompson
2011-03-16 13:05 ` Ben Gardiner
2011-03-16 14:44   ` Stefano Babic
2011-03-16 17:24     ` Stefano Babic
2011-03-16 17:46       ` Ben Gardiner

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=4D80AEE4.4060406@denx.de \
    --to=sbabic@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