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.

CCS/TMS320F28032: Problem when erease and load program to flash of F2803x

Part Number: TMS320F28032

Tool/software: Code Composer Studio

Hi every one,

I am using TMS320F2803x (incluce: f28032 and f28035), I get a problem when I load program to Flash memory through CCS V6.2 complier.

Following attached pictures will be express the errors in details, after error occured I cannot continuously use my MCU, I always must replace new MCU, could you tell me the reason and the solution for this error.

In addition, I meet this error frequently in many production designed using C2000 MCU.

I using XDS100V2 in LaunchPad - F28027 or XDS100V3 to load program.

Thank you!

 

 Doc1.docx

  • Tien,

    My initial thought is this may be board design issue and not device issue. I assume that you are using CCS flash plugin.

    Can you answer the following question?

    1) Do you happen to get this error on a virgin device? (or) on a already programmed device?

    2) Do you see this problem only with CCS V6.2 complier? Have you tried updating CCS?

    3) Are you able to connect to the device after you get this problem?

    4) Did you check whether the device is locked?

    5) Is this new board design?

    Regards,
    Manoj
  • Hi @Manoj Santha Mohan,

    Thank you for your response,

    1,  Almost of error is occured on already programmed device.

    2, I got this problem not only with Ccs v6.2 but also v6.1 and v7.2

    3, I cannot connect with device after error, it means that I got the announment "Device is locked....". In addition, when I remove jtag and supply Vcc = 3.3v to device, nothing happened (led not blinked as this function....)

    4, as 3

    5, I got this error with many boards with deffirent function in f28032 and f28035 as well.

    For more details, I see that ereasing process are interrupted, can that condition make device is permenantly locked?.

    If that is true, could you give me the reason and method to avoid it?

  • Tien,

    Flash Erase operation should never be interrupted and this certainly has the possibility to permanently lock the device.

    Flash Erase operation internally runs the following algorithm
    - Compaction algorithm
    - Clear algorithm
    - Erase algorithm
    - Compaction algorithm

    If flash erase operation gets interrupted in middle of clear algorithm / erase algorithm, flash passwords become 0x0000s which permanently lock the device. Moreover, interrupting the flash erase operation has the possibility of flash depletion which can render the device unrecoverable

    processors.wiki.ti.com/.../FAQs

    So, you shouldn't interrupt Flash Erase operation. You can increase the timeout condition to 12 - 15 secs / sector to avoid this condition.

    Regards,
    Manoj
  • Tien,

    You can try connecting to a locked device by entering the device in "WAIT BOOT MODE". Once you connect to the device, you can unlock the device by entering CSM password in 0xAE0 - 0xAE7.

    processors.wiki.ti.com/.../Code_Security_Module_FAQ_for_C2000

    Regards,
    Manoj