mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Tibault Damman <tibault.damman@basalte.be>
To: Sascha Hauer <sha@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: nand "BCH decoding failed" when using bch8_hw_romcode ecc mode
Date: Mon, 21 Mar 2022 09:04:59 +0100	[thread overview]
Message-ID: <5bdd9e3c-aa62-bf0e-fee3-ff49072f7617@basalte.be> (raw)
In-Reply-To: <20220318115925.GC12181@pengutronix.de>

On 18/03/2022 12:59, Sascha Hauer wrote:
> Have a look at "md -s /dev/nand0.raw 0+2112", then you can see how the
> OOB data should look like and compare it with the data read in
> omap_gpmc_read_page_bch_rom_mode(). The ".raw" is important, I saw you
> printed 2112 bytes from a non raw device. I meant to print a single
> page, on a non raw device that would be 2048. 

Oh thank god, I'm not gonna lie, I was kinda worried when I saw no
non-data bytes.

> You might have to enable CONFIG_MTD_RAW_DEVICE to get the raw device.

Thanks, that's exactly why I couldn't find the raw device.

Linux writes:
> ...
> 000007f0: 0a363335 0a373335 0a383335 0a393335                536.537.538.539.
> 00000800: a060ffff 7286981b 604c42b1 002b5238                ..`....r.BL`8R+.
> 00000810: 9ed8f629 4709bc76 8b658d4d 606e000c                )...v..GM.e...n`
> 00000820: 0d54d92c 98ec3c7d 0048f800 4e9ee01e                ,.T.}<....H....N
> 00000830: 3b4d302e 72844fa4 ffff0099 ffffffff                .0M;.O.r........
                                  ^^
Barebox writes:
> ...
> 000007f0: 0a363335 0a373335 0a383335 0a393335                536.537.538.539.
> 00000800: a060ffff 7286981b 604c42b1 002b5238                ..`....r.BL`8R+.
> 00000810: 9ed8f629 4709bc76 8b658d4d 606e000c                )...v..GM.e...n`
> 00000820: 0d54d92c 98ec3c7d 0048f800 4e9ee01e                ,.T.}<....H....N
> 00000830: 3b4d302e 72844fa4 ffff6e99 ffffffff                .0M;.O.r.n......
                                  ^^

So, interestingly, there does appear to be a 1 byte difference as well...

I'll have a look at the code you mentioned.


Thanks again

Tibault

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox


      parent reply	other threads:[~2022-03-21  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 13:45 Tibault Damman
2022-03-17  7:46 ` Sascha Hauer
2022-03-18  9:49   ` Tibault Damman
2022-03-18 10:32   ` Tibault Damman
2022-03-18 11:59     ` Sascha Hauer
2022-03-18 21:41       ` Trent Piepho
2022-03-21  8:04       ` Tibault Damman [this message]

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=5bdd9e3c-aa62-bf0e-fee3-ff49072f7617@basalte.be \
    --to=tibault.damman@basalte.be \
    --cc=barebox@lists.infradead.org \
    --cc=sha@pengutronix.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