• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 82 subscribers
  • Views 839 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS320F28033: File loader: memory write failed: unknow error when download to OPT zone.

Rayna Wang
Expert 3680 points
Part Number: TMS320F28033

Hi Expert,

My customer meets an issue as below figure shown, that memory write failed when download/bootloader to OPT zone, and the address is origin = 0x3D7800, length = 0x000400. 

By the way, the code could download to flash normally, the issue only occur to OTP on part of F28033 chips, around 500, in production line.

Could you please help to analyze which factors which could cause this issue, and how to debug it? Thanks!

The error information 

The normal phenomenon 

The device part number

Thanks!

Best Regards

Rayna

  • 0
    TI__Guru* 93905 points

    Rayna,

    Was customer successful in programming the OTP of any device or it has failed in all devices? I am trying to understand if there are any issues related to the linker command file. Have they checked the .map file to ensure their section(s) correctly lie in the OTP range?

  • 0 in reply to Hareesh Janakiraman
    TI__Guru 55700 points

    In F28033 device, USER OTP (0x3D7800 - 0x3D7BFF) is protected by CSM. If the device is secured, you can't program to USER OTP unless you unlock the device. Check whether the device is locked? If so, unlock the device and program USER OTP.

    Regards,

    Manoj

  • 0 in reply to Manoj Santha Mohan
    TI__Expert 3680 points

    Hi Hareesh & Manoj,

    • This issue is from production line, and the otp.out file could download to most of device, as the below figure shown. The memory address is divided refer to datasheet.
    • The device is not locked, there's no password in CSM. For the code in flash could be download normally as below.

    What other information do you need about this issue? Thanks!

    Best Regards

    Rayna

  • 0 in reply to Manoj Santha Mohan
    TI__Expert 3680 points

    Hi Hareesh & Manoj,

    • This issue is from production line, and the otp.out file could download to most of device, as the below figure shown. The memory address is divided refer to datasheet.
    • The device is not locked, there's no password in CSM. For the code in flash could be download normally as below.

    What other information do you need about this issue? Thanks!

    Best Regards

    Rayna

  • 0 in reply to Rayna Wang
    TI__Guru* 93905 points

    The fact that you are able to program the same .out file in other devices indicates that there is likely no issue with the .out file itself or the hardware. If you examine the contents of the OTP memory in CCS, what do you see? Could you send us the dump of OTP memory from a few failing devices?

  • 0 in reply to Hareesh Janakiraman
    TI__Expert 3680 points

    Hi Hareesh,

    Do you need all the content of OTP? Could customer send you the .out file?

    By the way, why OTP memory content is different between different chips with the same .out file?

    Thanks!

    Best Regards

    Rayna

  • 0 in reply to Rayna Wang
    TI__Guru* 93905 points

    Do you need all the content of OTP?

    Yes. I would like to look at the OTP content of a few failing devices. Specifically, I would like to see if OTP content is similar across all failing devices.

    Could customer send you the .out file?

    Yes. You could send this (and the above) via email privately.

    By the way, why OTP memory content is different between different chips with the same .out file?

    Is this the case across devices where CCS did not report any error while programming?