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.

TMS320F280037C: TMS320F280037C Error during Flash Programming

Part Number: TMS320F280037C

Hello,

I am attempting to write my program to flash so it may run independently without a debug probe installed.

It appears as though the Universal Motor Control lab code already sets up the linker command files, and runs the necessary flash API commands to write sensitive RAM functions to RAM.

Here is my procedure:

1) Run the program in debug mode

2) Tools -> On-Chip Flash -> Program All (Zone 1)

This returns this error:

This begs so many questions. What is even zone 1 vs zone 2? I don't see any documentation anywhere explaining how or what these zones are doing.

Why is it trying to program to the OTP section at all? (0x078014) I would think this would always fail, since it can only program once.

  • Hi Aric,

    If I understand correctly, you don't want to program any security configuration in the DCSM Security OTP.  You just want to load code to flash or RAM.  Is that correct?  If yes, you shouldn't use the "Program All (Zone1)" button - this button is for programming all the Zone1 security settings.  For loading to flash, you can simply use the Load Program button that you use for loading to RAM - you don't need to open the flash plugin GUI to be able to load to flash - CCS will automatically invoke the flash plugin when it identifies that content is mapped to flash in the given executable.  

    Regarding Zones:  TRM's DCSM chapter will explain about security and dual zones.  Please review it if you want more details about it.

    Thanks and regards,

    Vamsi

  • You are right... I was programming via the 'debug' button. The 'Run -> Load -> (project name) will also load the program.

    I am not using security zones.

    On further investigation, it appears the program is successfully programming. However, on power reset, the device does not re-enter its program. So my issue appears to be a failure to properly reset. In any case, this is particular question is resolved. 

    I can reproduce my reset issue with the Run -> Reset button. I am investigating this further...