- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Hello,
I'm using the eZdsp kit for the TMS320F2808 processor. Recently I have been having problems using Code Composer Studio (version 3.3) to flash the device. I get the following error message.
Flash API Error #24: The Erase operation failed the pre-compaction step.
Right now I'm worried that the Code Security Module is locked. Is there any way to detect or verify that the code security module had been locked on my device? Taking into consideration that I can no longer use the flash utility in CCS is there any other way to run a check on memory to determine if any of the locations are bad? How does the flash tool normally behave when the code security module has been locked?
Up until today I have had no problems programming the development kit. However, this morning the device started behaving strangely up until the point where I was no longer able to flash the device. The strange behavior I noticed today prior to being unable to flash the device is listed below.
1. Normal variable assignments in program code would not work. Say for instance I assigned the value three to an Uint16, the memory location assigned to Uint16 (located in ram) would be 0xFFFF
2. Random parts of my code would execute with out being called. Which lead me to believe that the project code and the program code running from flash was not matching up.
Thanks for any advice....
