From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND write error with HW ECC on OMAP3
Date: Wed, 04 Sep 2013 10:54:03 +0200 [thread overview]
Message-ID: <5226F52B.8000705@gmail.com> (raw)
In-Reply-To: <5226E2AF.6090109@gmail.com>
Dear Ash Charles,
On 09/04/2013 09:35 AM, Andreas Bie?mann wrote:
> Dear Ash Charles,
>
> On 09/03/2013 09:34 PM, Ash Charles wrote:
>> Hi,
>>
>> When using 'nandecc hw' on an OMAP3 platform, data is not being
>> correctly written to NAND. I see the issue on 2013.10-rc2 and 2013.07
>> but not on 2012.10. Specifically, when I read back a SPL binary
>> written with hardware Hamming ECC, I don't get a matching CRC. With
>> the BCH8 ECC algorithm, the CRC is correct (but SPL must be written
>> with Hamming otherwise the board doesn't boot)
>>
>> I've shown my steps here: http://pastebin.com/tLZsr9zH
>> The expected CRC is 46745188.
>>
>> Any suggestions/ideas much appreciated!
>
> I'd swear this worked when I changed the command to use BCH ... I'll
> check it again today.
I can't confirm your complaints. Here it works (at least on tricorder,
which utilizes BCH for U-Boot section in SPL):
---8<---
U-Boot SPL 2013.10-rc2-00014-g2d5878e (Sep 04 2013 - 10:39:57)
reading u-boot.img
reading u-boot.img
U-Boot 2013.10-rc2-00014-g2d5878e (Sep 04 2013 - 10:39:57)
OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-200MHz, Max CPU Clock 1 Ghz
OMAP3 Tricorder + LPDDR/NAND
I2C: ready
DRAM: 128 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Board : serial
Die ID #246000029e38000001683b060102002d
Hit any key to stop autoboot: 0
OMAP3 Tricorder # fatload mmc 0 ${loadaddr} MLO
reading MLO
55052 bytes read in 11 ms (4.8 MiB/s)
OMAP3 Tricorder # nandecc hw
1-bit hamming HW ECC selected
OMAP3 Tricorder # nand erase.part SPL
NAND erase.part: device 0 offset 0x0, size 0x20000
Erasing@0x0 -- 100% complete.
OK
OMAP3 Tricorder # crc32 ${loadaddr} ${filesize}
CRC32 for 82000000 ... 8200d70b ==> b182f0a2
OMAP3 Tricorder # nand write ${loadaddr} SPL ${filesize}
NAND write: device 0 offset 0x0, size 0xd70c
55052 bytes written: OK
OMAP3 Tricorder # nand read 0x80000000 SPL ${filesize}
NAND read: device 0 offset 0x0, size 0xd70c
55052 bytes read: OK
OMAP3 Tricorder # crc32 0x80000000 ${filesize}
CRC32 for 80000000 ... 8000d70b ==> b182f0a2
OMAP3 Tricorder #
--->8---
The 14 patches on top of -rc2 are just local board changes (will be sent
soon):
---8<---
2d5878e (HEAD, tricorder-TOT) tricorder: fixup for led.c
c3806ea tricorder: read kernel directly from NAND
c158ec1 tricorder: switch to alternative memtest
9bcc57b tricorder: Make u-boot faster
441857b tricorder: add led support
b8bb65a tricorder: panic() on unknown board
8c5e0a8 tricorder: add tricordereeprom command
4c86cad tricorder: add mtdparts to environment
3ac9838 tricorder: add cmdline history
7fe344d tricorder: move commonargs to common settings
3bd1a05 tricorder: add configuration for a flashcard u-boot
d2578c5 tricorder: use generic provided loadaddr
649f8dc tricorder: update flash partitioning
e34c01a tricorder: remove lcdmode from bootargs
fb18fa9 (tag: v2013.10-rc2, origin/master, origin/HEAD, cs/master)
Prepare v2013.10-rc2
--->8---
Best regards
Andreas Bie?mann
next prev parent reply other threads:[~2013-09-04 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 19:34 [U-Boot] NAND write error with HW ECC on OMAP3 Ash Charles
2013-09-04 7:35 ` Andreas Bießmann
2013-09-04 8:54 ` Andreas Bießmann [this message]
2013-09-04 18:00 ` Ash Charles
2013-09-04 23:02 ` Ash Charles
2013-09-05 8:57 ` Andreas Bießmann
2013-09-07 1:57 ` Ash Charles
2013-09-05 8:42 ` Andreas Bießmann
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=5226F52B.8000705@gmail.com \
--to=andreas.devel@googlemail.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