• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 697 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Bootloader ECC generation issues.

Dalia Eltinay
Prodigy 90 points
Other Parts Discussed in Thread: TMS320C6424

Hi all,

I’m trying to boot from NAND using TMS320C6424 AIS bootloader, it requires 1 bit ECC, for each 512 bytes, using the hardware ECC calculation provided by the DMP's EMIF module to detect and correct ECC errors.

It used to work properly when using a NAND with a page size of 512 and a spare area of 16 bytes. But when it comes to the MT29F1G08ABADAH4 NAND with a page size of 2048 and a spare area of 64, the spare area has been divided into four equally 16byte, ECC every 512byte generated into the corresponding 16byte space.

, but the boot loader didn’t seem to work,

So how can I arrange the ECC values in the spare area to fit the boot loader requirements?

  • 0
    TI__Mastermind 43955 points
    Hi Dalia,

    Usually, in the data sheer of "MT29F1G08ABADAH4 ", the spare area division for the page sizes would be given.

    And also please mention the name of the package you use for this experiment. Is the bootloader code your own or TI provided?
  • 0 in reply to Shankari G
    Prodigy 90 points

    Hi Shankari G,

    Thank you for your reply, I’m using TMS320C6424 and it has a ROM bootloader provided by TI, which is not accessible, the above mentioned bootloader requirements stated in TI application report (SPRAAK5B).

  • 0 in reply to Dalia Eltinay
    TI__Mastermind 43955 points
    Hi Dalia,

    According to the Application report (SPRAAK5B), the revision 1.30 of the C6424 supports NAND flash boot completely. As you said it works when the page size is 512, then, I hope the revision of your device is 1.30. However, please confirm.

    Secondly, what is the device ID for "MT29F1G08ABADAH4 " ?? Compare the device ID with the tabular column given in the application note. It has somehting like below. Check whether the Device ID of the NAND flash memory falls on these given list.

    Device-ID page size Total memory size
    0×F1 2048+64 128 MB
    0×A1 2048+64 128 MB
    0xAA 2048+64 256 MB
    0×DA 2048+64 256 MB
    0×AC 2048+64 512 MB
    0×DC 2048+64 512 MB
    0×B1 2048+64 128 MB
    0×C1 2048+64 128 MB

    Insert some debug trace / print messages to check where it hangs. That it will give some insights.
  • 0 in reply to Shankari G
    Prodigy 90 points

    Hi Shankari, thank you again,

    Yes, the revision of c6424 is 1.30, besides, the Device ID is 0xF1 (using read ID command), and the program doesn’t get loaded to the RAM (pc counter remains at the ROM (bootloader) address range, around 0x00102B12) so I couldn’t insert a debugger.

  • 0 in reply to Dalia Eltinay
    TI__Mastermind 43955 points
    Hi Dalia,

    I have forwarded your query to one of our bootloaders expert.

    Thanks for your patience till then.