Bad block table not found for chip 0 for BSC9131RDB

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Bad block table not found for chip 0 for BSC9131RDB

2,400 Views
manjanagoudapat
Contributor III

Hi,

                     I am working with a BSC9131RDB  board.  We are booting from NAND Flash using Micron MT29F2G08ABAFAWP(256Mb) by replacing K9F1G08U0B(128Mb) NAND.

                     I can program the nand using jtag and uboot recognizes the NAND, Uboot successfully boots to the command prompt.

                      During boot "Bad block table not found for chip 0  No space left to write bad block table" is displayed and I cannot write to the nand chip from u-boot to save the environment or program new u-boot.

  The chip is 256MByte and has a block size = 64 pages (128K + 4K bytes), and 2K pagesize same as K9F1G08U0B but only density increased from 28Mb to 256Mb.

If I run nand bad the whole flash chip is reported as bad.

Has anyone had a similar experiance?  Any ideas what might be causing this?

Thanks for any help.

And the log is :

U-Boot 2011.06.913x_WUSDK_1.5 (Feb 04 2014 - 11:54:19)

CPU:   BSC9131E, Version: 1.1, (0x86080011)

Core:  E500, Version: 5.1, (0x80212251)

Clock Configuration:

       CPU0:1000 MHz,

       CCB:400  MHz,

       DDR:800  MHz (800 MT/s data rate) (Asynchronous), IFC:100  MHz

L1:    D-cache 32 kB enabled

       I-cache 32 kB enabled

Board: BSC9131RDB

I2C:   ready

SPI:   ready

DRAM:  880 MiB (DDR3, 32-bit, CL=6, ECC off)

L2:    256 KB enabled

NAND:  256 MiB

Bad block table not found for chip 0

Bad block table not found for chip 0

No space left to write bad block table

*** Warning - readenv() failed, using default environment

In:    serial

Out:   serial

Err:   serial

Net:   eTSEC1 connected to Vitesse VSC8641

eTSEC2 connected to Vitesse VSC8641

eTSEC1, eTSEC2

Hit any key to stop autoboot:

=> save

Saving Environment to NAND...

Erasing Nand...

Skipping bad block at  0x00080000

Skipping bad block at  0x000a0000

Skipping bad block at  0x000c0000

Writing to Nand... FAILED!

Labels (1)
0 Kudos
Reply
3 Replies

1,742 Views
scottwood
NXP Employee
NXP Employee

Check whether any timings need to change for the new chip.

0 Kudos
Reply

1,742 Views
manjanagoudapat
Contributor III

Hi Scott,

Problem solved by changing the Row Address Length 2 Bytes to 3 bytes.

Thank you for the support

0 Kudos
Reply

1,742 Views
manjanagoudapat
Contributor III

Hi Scott,

How to get the values for these registers

FTIM0 ,FTIM1 and FTIM2 .what are the factors which decides the values for these? My Nand chip is MT29F2G08ABAFAWP(256Mb) Micron make.

0 Kudos
Reply