mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: raespi <raespi@icid.cu>
To: "Eric Bénard" <eric@eukrea.com>
Cc: barebox@lists.infradead.org
Subject: Re: problem booting with Micron MT29F8G08ABABAWP ...
Date: Fri, 14 Mar 2014 16:30:53 -0400	[thread overview]
Message-ID: <532366FD.509@icid.cu> (raw)
In-Reply-To: <20140314211858.05897c4e@e6520eb>

So what I'm understanding here is that it isn't enough to fix an oobsize 
also the 4k support is needed. I'm guessing it's not something so 
trivial then, I'll have to delve in deeper.  Any tips on how to code it 
as simple as possible?? I'm a programmer but I'm not familiarized with 
the inner workings of a NAND flash or how to initialize it from the 
bootloader.

On 03/14/2014 04:18 PM, Eric Bénard wrote:
> Hello,
>
> Le Fri, 14 Mar 2014 14:45:05 -0400,
> raespi <raespi@icid.cu> a écrit :
>
>> Hello again ... diving through the drivers/mtd/nand/nand_base.c code I
>> managed to boot with this little modification in the
>> nand_flash_detect_onfi() function just before exiting from it:
>>
>>       if ( mtd->oobsize > 128 )
>>         mtd->oobsize = 128;
>>
> then you tell your flash has an OOB of 128 when it has more ...
>
>> Apparently the only allowed oobsizes are 8, 16, 64 and 128 according to
>> the nand_scan_ident() function.  I followed Eric's advice in seeing how
>> the i.Mx manages it and it's something like this:
>>
>> NFC_V3_CONFIG2_SPAS(((mtd->oobsize > 218) ?
>>               218 : mtd->oobsize) >> 1)
>>
> that's specific to the i.MX NAND controller : you need to adapt the
> code of _your_ CPU's NAND controller to get it to properly support 4k
> page flashes.
>
> Eric
>
>



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

  reply	other threads:[~2014-03-14 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 19:32 raespi
2014-03-13 20:28 ` Eric Bénard
2014-03-14 18:45   ` raespi
2014-03-14 20:18     ` Eric Bénard
2014-03-14 20:30       ` raespi [this message]
2014-03-17  6:39     ` Sascha Hauer

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=532366FD.509@icid.cu \
    --to=raespi@icid.cu \
    --cc=barebox@lists.infradead.org \
    --cc=eric@eukrea.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