• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 452 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Unintended CSM lock while flashing

Henry Luong
Intellectual 290 points

I was trying to flash an ezdsp F2812. It failed midway, so I reset it and tried again. Now the status says its locked and cannot be flash. I never set a password, so somehow it got locked and I dont know the password. Is there anyway to recover from this?

  • 0
    Intellectual 290 points

    some more info. I've inadvertently used flashAPI v1.0 when I should be using v2.1 for silicon rev G. Which may be what caused the failure.

    I know TI warns against writing 0's as password, or interrupting the erase process midway. Could this be what happened? If so, then the DSP is permanently locked, and there is no way to recover?

  • 0 in reply to Henry Luong
    TI__Guru* 93800 points

    Henry said:

    some more info. I've inadvertently used flashAPI v1.0 when I should be using v2.1 for silicon rev G. Which may be what caused the failure.

    I know TI warns against writing 0's as password, or interrupting the erase process midway. Could this be what happened? If so, then the DSP is permanently locked, and there is no way to recover?

    Henry,

    Wow - that is a very old API.

    Running the 1.00 API on rev G of 281x will have no effect.  The API will eventually return with an error code.  The attempt to erase or program will have no affect  however and the API cannot make a change to the flash.

    Are you sure that the device is locked?  If you open code composer and a memory window to the password locations (0x3f7ff8-0x3f7fff) what does the memory read back? (you may need to refresh the window). 

    Regards

    -Lori

     

  • 0 in reply to Lori Heustess
    Intellectual 290 points

    Yeah its an old api. It was the one that came with CCS v3.1.  I had to reinstall v3.1 after a failed attempt with CCS4 (I posted about that in another thread). I only had 3.1 on a CD, no 3.3. And I forgot to update the flash API to 2.1.

    I know it is locked because all options in the on-chip flash programmer are grayed out, except for the input for KEY and the unlock button. Also, when the emulator is connected or reset, the status updates and says the device is locked.

    The memory at the PWL reads all zeros.