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.

All CSM passwords are written 0x00

Other Parts Discussed in Thread: UNIFLASH, TMS320F28035

Hi,

I tried to flash my code to TMS320f28035 and it didn't happen.So i tried to erase DSP flash sectors using uniflash tool.But it stopped with some errors.

I have tried above steps many times but i was not able to flash my code to the DSP.

So on seeing memory locations of this dsp using Memory Browser of Code Composer Studio i have found out that all CSM locations are written with 0x0000.

Can anyone please tell me what could be the possible reasons for happening this error? 

Regards

Deepak

  • Hi Siddharth,

    There are couple of ways it could happen -

    1. Password location in Flash got programmed - Due to wrong map file the password location in Flash got programmed which locks the device. In that case all the location in flash including password locations will show value 0x0.
    2. Interruption during flash operation - If there was interruption during flash programming/erase operation then flash content may be left in CELAR state which will make password location 0x0 and lock the device.

    Please check your map file to see if there is any code mapped in password locations. If yes then you could try to extract password values from .out file which was used to program the device (after which issues started) and use it to unlock the device and then try to erase the whole flash again.

    If it was due to flash content got CLEAR, then nothing much can be done here and you need to replace the part.

    Regards,

    Vivek Singh

  • Hi Vivek,

    I am facing this issue regularly regarding  MCU going to non debuggable state.And thus not able to flash new code to MCU.

    This happens mainly during debugging of code again and again.And while programming it hangs/stops and then when you again try to debug, it encounteres with following error:-

    Error connecting to the target:
    (Error -1015 @ 0x0)
    Device is not responding to the request.  Device may be locked, or the debug probe connection may be unreliable. 

    Above is the snapshot of CCS screen which shows how it stops debugging during my development work and then after this it never debugged again.

    And then when i connected MCU with CCS by Loading Boot ROM Symbols and opening Memory Browser i found out that whole flash including all CSM locations are written 0x00. So basically JTAG debugging has written 0x00 to full flash sectors.

    Like this around 3-4 MCU's has already gone bad.So can you tell me is there any hardware/software to prevent JTAG from writing wrong data(0x00) to flash locations.

    Thanks

    Regards

    Siddharth 

  • Siddharth,

    Sorry to hear that. There is definitely some issue during flash operation which is causing this issue and I would suggest to debug this before more devices go bad because once this issue happens, device is not recoverable.

    Couple of things to check -

    • Please check if there is any issue with power supply. If during Flash program/erase operation there is power glitch then this issue could occur.
    • Please make sure device is not going through reset cycle (internal reset due to watchdog or if there is any external watchdog) because if there is any disruption during flash program/erase operation, this issue may occur.

    Since this is only happening sometime, I don't think .out has any content at flash location which stores security password but it will be good to double check the map to confirm the same.

    Regards,

    Vivek Singh

  • Hi Siddharth, Let me know if you have any further queries on this.

    Vivek Singh