TMS320DM8127: Failed to boot from NAND MT29F4G08ABAEAWP

Chris Meng

Part Number: TMS320DM8127
Other Parts Discussed in Thread: CCSTUDIO

Hi,

My customer wants to use MT29F4G08ABAEAWP from Micron, but failed to boot from it. This nand is ONFI compliant. From DM814x TRM, it says that for NAND boot, the rom code will send ONFI Read ID first to check if it an ONFI nand, if it is, it will use the ONFI info. If the ONFI Read ID command fails, it will check if the nand is in the support nand list or not.

Would you pls help to double confirm the flow, that is, the rom will check ONFI info first? MT29F4G08ABAEAWP's id is in the support nand list, but the page size is not match. I am suspecting this cause the problem. But as our rom will check ONFI info first as TRM mentioned, I can't find out why the boot failed.

Do you have any other suggestion on this boot fail issue? Any comment is welcome!

over 7 years ago

0 Chris Meng over 7 years ago

TI__Mastermind 35235 points

Hi,

Which version of ONFI does DM8127 ROM support?

0 Pavel Botev over 7 years ago in reply to Chris Meng

TI__Guru**** 170625 points

Chris,

"Which version of ONFI does DM8127 ROM support?"

I see your NAND chip is ONFI 1.0 compliant, and DM81xx ROM code should be able to support ONFI 1.0

"Would you pls help to double confirm the flow, that is, the rom will check ONFI info first? "

Yes, ONFI first. If NAND part is ONFI, then "Table 4-14. Supported NAND Devices" is not checked.

I see your NAND chip is 8-bit (x8), make sure btmode[12] = 0

I see your NAND chip has page size of: 4320 bytes (4096 + 224 bytes). This might be the root cause, we have the below ROM Code requirement:

4.7.3.1 NAND Features
Support for large page size (2048 bytes + 64 spare bytes) or very large page size 4096 bytes + 128 / 218 spare bytes).

See the below e2e threads for more info:

e2e.ti.com/.../233142
e2e.ti.com/.../1577294

e2e.ti.com/.../221595
e2e.ti.com/.../224695
e2e.ti.com/.../308384
e2e.ti.com/.../369572
e2e.ti.com/.../1540871

Regards,
Pavel

0 Chris Meng over 7 years ago in reply to Pavel Botev

TI__Mastermind 35235 points

Pavel,

Thanks for your reply!

From the first post you shared, I got below info:

ROM will use the maximum BCH that it can fit into the spare area.

BCH16 needs 208 bytes of spare area.

So with 224-byte spare area of nand, customer needs to burn the uboot min with BCH16, then ROM code can read right image. But our software only supports BCH8, so I think customer currently is using BCH8 to burn the uboot min.

Do you have any tool which can calculate ECC data with BCH-16 on PC?

0 Pavel Botev over 7 years ago in reply to Chris Meng

TI__Guru**** 170625 points

Hi Chris,

I see these options to burn u-boot-min with BCH16:

1. use 3rd party tool to flash u-boot-min
2. update TI814x CCStudio tool to support BCH16 and use it to flash u-boot-min
3. update u-boot to support BCH16 and use it to flash u-boot-min
4. use the latest ti81xx 2.6.37 kernel (which comes with BCH16 support) and MTD-utils (flash_eraseall, nandwrite)

Regarding 3 and 4, see the below links:

processors.wiki.ti.com/.../TI81XX_PSP_NAND_Driver_User_Guide
processors.wiki.ti.com/.../Linux_Core_NAND_User's_Guide

arago-project.org/.../

Regards,
Pavel

0 Pavel Botev over 7 years ago in reply to Pavel Botev

TI__Guru**** 170625 points

See also the below e2e thread:

e2e.ti.com/.../214942

Regards,
Pavel

0 Anuj Kumar Gupta over 7 years ago in reply to Pavel Botev

Genius 4030 points

Hi,

I hope above inputs were helpful in solving your issue.
If the issue is resolved then please close the thread by verifying answer.

Regards,
Anuj
Pathpartner Technology Pvt Ltd

Processors

Processors forum

TMS320DM8127: Failed to boot from NAND MT29F4G08ABAEAWP