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 14:45:05 -0400	[thread overview]
Message-ID: <53234E31.2070300@icid.cu> (raw)
In-Reply-To: <20140313212810.4179d0c2@e6520eb>

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;

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)

Basically setting it to a value of 218.  I first tried a value of 218 
and it didn't work, with a value of 128 I arrive at the prompt but not 
very cleanly I presume:

nand: ONFI param page 0 valid
OOBSIZE4: 128
nand: ONFI flash detected
nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x38 (Micron 
MT29F8G08ABABAWP), 1028
Bad block table found at page 262016, version 0x01
Bad block table found at page 261888, version 0x01

I'm currently having trouble booting the kernel from the 
/dev/nand0.kernel partition, it boots fine from an SD partition meaning 
the boot mechanism in barebox is fine.  Still moving forward ...

On 03/13/2014 04:28 PM, Eric Bénard wrote:
> Hi,
>
> Le Thu, 13 Mar 2014 15:32:23 -0400,
> raespi <raespi@icid.cu> a écrit :
>> Hi ... I'm using barebox 2014.02.0 to boot with a clone of the mini2440
>> board using the MT29F8G08ABABAWP NAND.
>>
>> I'm getting the following error:
>>
>> barebox 2014.02.0 #1 Thu Mar 13 15:28:57 CDT 2014
>>
>> Board: <NULL>
>> nand: ONFI param page 0 valid
>> nand: ONFI flash detected
>> nand: NAND device: Manufacturer ID: 0x2c, Chip ID: 0x38 (Micron
>> MT29F8G08ABABAWP), 1024
>> nand: No oob scheme defined for oobsize 224
>> BUG: failure at drivers/mtd/nand/nand_base.c:3357/nand_scan_tail()!
>> BUG!
>> no stack data available
>> DIVN_UPLL0
>> MPLLVal [M:61h,P:1h,S:2h]
>> CLKDIVN:7h
>>
>> After this poing the board gets resetted back to the original point.  I
>> can never get to the barebox prompt.
>>
>> Any ideas on how to fix this ??
>>
> you may need to add support for 4k+224 page size to your nand
> controller.
> For example this was done for i.MX in comit
> 632c45795065e6a7471ab82be38e808eb6204341
>
> Eric
>
>



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

  reply	other threads:[~2014-03-14 18:44 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 [this message]
2014-03-14 20:18     ` Eric Bénard
2014-03-14 20:30       ` raespi
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=53234E31.2070300@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