Micron MT29F4G08ABAFAWP Bad block table not found for chip 0

[bensonyoung]

We are using MT29F4G08ABAFAWP for NAND flash storage.

nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xdc
nand: Micron MT29F4G08ABAFAWP
nand: 512 MiB, SLC, erase size: 256 KiB, page size: 4096, OOB size: 256
gpmi-nand 33002000.gpmi-nand: enable the asynchronous EDO mode 5

We are getting the following message on all reboots. The Bad block table should be created after first boot.

Bad block table not found for chip 0
Bad block table not found for chip 0
Scanning device for bad blocks
Bad block table written to 0x00001ffc0000, version 0x01
Bad block table written to 0x00001ff80000, version 0x01

we are using 4.9.11 kernel base

Rev. L4.9.11_1.0.0-ga+mx8-alpha, 09/2017

[igorpadykov]

Hi Benson

"Rev. L4.9.11_1.0.0-ga+mx8-alpha" is old version and not more supported, recommended to

try latest Linux 5.10.9. Use uuu tool and example_kernel_nand.uuu script included in

Demo Image :

https://www.nxp.com/design/software/embedded-software/i-mx-software/embedded-linux-for-i-mx-applicat...

Best regards
igor

[bensonyoung]

Hi Igor,

I don't understand how using uuu to update the kernel will address the problem?

Bad block table is created by NAND flash gpmi driver when during initialization it will scan the last few flash block of NAND flash to look for BBT. If no 'valid' table is found, it will try to reconstruct the table again by erase-write the last few blocks. As a result, on next boot a valid table will be present when scanned by the driver. I do see this on all first boot (driver complaining about BBT not found), but on subsequent reboots the driver will not have any issue.

What I am observing on my board when using MT29F4G08ABAFAWP, is that the driver will keep complaining it cannot find bad block table.

best regards,

benson

[tsharma]

Hi, Benson.

Did you find solution to your issue with NAND BBT? I am facing same issue with MT29F1G08ABAEAWP.

Regards,

Tanuj