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.

TMS320F28P650DK: Potentially Bricked C2000

Part Number: TMS320F28P650DK
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi,

Today I was playing around a bit with setting up my program on the CLA and tried to have the CPU write the program code from FLASH BANK0 to RAM at runtime. I was making some changes to ensure the code was being copied over when I noticed at some point during my changes, I was no longer able to connect to the device (GEL onConnect() and onReset() would hold forever) after a specific change that I made when I did the following.

   /* CLA specific sections */
    Cla1Prog        : LOAD = FLASH_BANK0,
                      RUN = RAMLS8_CLA,
                      LOAD_START(_Cla1ProgLoadStart),
                      RUN_START(_Cla1ProgRunStart),
                      LOAD_SIZE(_Cla1ProgLoadSize),
                      ALIGN(4)
and called
memcpy((void *)&_Cla1ProgRunStart,
(const void *)&_Cla1ProgLoadStart,
(size_t)&_Cla1ProgLoadSize)
I was wondering if there was any way that I could have corrupted something with the boot sequence during this process or if this was even possible. I flashed a sample project on a different board successfully and once I flashed this new "rouge" firmware, the device was no longer able to be reset. I am able to pass the JTAG integrity scan but I cannot debug, flash or read memory through CCS or UNIFLASH. Any help on the matter would be appreciated.