We are having an issue with a 2812 on a custom board we are developing. We have been running the 2812 DSP chips from flash for some weeks. Recently when load images into Flash memory of the F2812 using code composer 8.0.0 and 7.4 on Windows 7 the erase part of the load failed leaving memory with all zeros rather than the all ones it is supposed to have when erased. When we have observed the issue Code composer stopped with an error stating it could not access the image. This was in the middle of the erase rather than at the start of the erase like it usually does when updating memory.
On the boards with the flash set to zero Code composer seems to be able to read data from the F2812 flash rather than reporting that the chip is locked. Previously we had a flash problem updating flash from code on an eZdsp, it left the CSM locked and completely unaccusable. With the previously locked chip Code Composer could not view memory at all. Code composer does not seem to consider the chip as locked but the CSM region shows zeros as does the rest of memory and we get the generic con connected or locked message when trying to flash the chip. Is there a way to recover from this? The chip does not seem to be secured is it actually locked? Since the libraries that update flash seem to write all of flash to various values when erasing a region of memory it seems like there needs to be a way for the hardware to distinguish between cleared memory in region A (where the keys are stored) and the chip being locked.