mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Raphaël Poggi" <raphio98@gmail.com>
To: Bo Shen <voice.shen@atmel.com>
Cc: barebox@lists.infradead.org
Subject: Re: atmel_nand pmecc on 8k page
Date: Fri, 13 Jun 2014 10:48:33 +0200	[thread overview]
Message-ID: <CACqcpZCNBZ6he2OnqQcdT3dPoeP0nFqSmteHAGYyLKAtAoT=nw@mail.gmail.com> (raw)
In-Reply-To: <539A5353.7090306@atmel.com>

Hi,

I'm testing with a custom board. I have just with the applied test and
it's working ! I can use 8k page nand with atmel_nand driver.

Do I have to wait until Matteo's patches are applied or can I submit
mine right now ?

Best regards,
Raphaël Poggi

2014-06-13 3:26 GMT+02:00 Bo Shen <voice.shen@atmel.com>:
> Hi Raphaël,
>
>
> On 06/12/2014 08:28 PM, Raphaël Poggi wrote:
>>
>> Hi,
>>
>> I'm working on a series of patches, to support 8k nand page in
>> atmel_nand driver.
>>
>> Currently, I can detect the nand and handle an oob size of 448. But i
>> have a problem with the pmecc, when barebox tried to perform pmecc
>> operation, I get the following message:
>>
>> PMECC: Timeout to calculate error location.
>>
>> Example of log:
>>
>> nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x68 (Micron
>> MT29F32G08ABAAAWP), 4096MiB, page size: 8192, OOB size: 448
>> atmel_nand atmel_nand0: Initialize PMECC params, cap: 8, sector: 1024
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> Bad block table not found for chip 0
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> atmel_nand atmel_nand0: PMECC: Timeout to calculate error location.
>> Bad block table not found for chip 0
>> Scanning device for bad blocks
>> Bad eraseblock 90 at 0x000005a00000
>> Bad eraseblock 91 at 0x000005b00000
>> atmel_nand atmel_nand0: PMECC: Timeout to get ECC value.
>> nand_bbt: error while writing bad block table -110
>>
>>
>> I don't know/find why barebox get a timeout...
>>
>> Someone have an idea ?
>
>
> Which board are you test this?
> Can you try to apply two patches from matteo.fortini@gmail.com on 2014-06-06
> with name
> [PATCH 1/2] sama5d3x: fix HSMC MODE register offset and add TIMINGS
> [PATCH 2/2] sama5d3x: HSMC NAND initialize TIMINGS and import values
>
>> Best regards,
>> Raphaël
>
>
> Best Regards,
> Bo Shen
>

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

  reply	other threads:[~2014-06-13  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-12 12:28 Raphaël Poggi
2014-06-13  1:26 ` Bo Shen
2014-06-13  8:48   ` Raphaël Poggi [this message]
2014-06-13 12:48     ` atmel_nand pmecc on 8k page [RFC] Matteo Fortini
2014-06-16  7:19       ` Bo Shen
2014-06-19  4:31         ` Jean-Christophe PLAGNIOL-VILLARD
2014-06-19  5:27           ` Bo Shen

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='CACqcpZCNBZ6he2OnqQcdT3dPoeP0nFqSmteHAGYyLKAtAoT=nw@mail.gmail.com' \
    --to=raphio98@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=voice.shen@atmel.com \
    /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