TMS320F2808: TMS320F2808

Part Number: TMS320F2808
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

The problem is that something happened unexpectedly, and I can’t figure out the cause. My MCU is now locked, and I can’t debug it. When I try to enter Debug mode, I get the error shown in the image below.

                                                                                                                 

After this happened, I searched for the reason behind the error and found that it might be related to the password sectors or the CSM registers in ROM. However, I don’t know what to do next or how to solve it.

  • Hello,

    Are you able to erase the flash?

    Thank you,

    Luke

  • Hello Luke,

    I should have access to a JTAG debugger to erase the flash memory, but unfortunately, I don’t have one available at the moment. Could you let me know if there’s another possible way to recover or fix the issue without JTAG, or any other method you’d recommend?

    Thank you,
    Tamer

  • Hello Luke,

    I should have access to a JTAG debugger to erase the flash memory, but unfortunately, I don’t have one available at the moment. Could you let me know if there’s another possible way to recover or fix the issue without JTAG, or any other method you’d recommend?

    Thank you,
    Tamer

  • So you have a debugger but this debugger does not have the ability to erase the flash? You should be able to open the On-Chip flash tool with any debugger if you select Tools -> On-Chip flash tool after you've launched a target configuration file and connected to the target.

  • Hi Support Team,

    I have the same problem, My Tms320f2808 MCU on the control card on doc-station is locked when i was booting from flash. 
    i think it is because power supply problem because i was using the mcu standalone and connecting power supply 5v external.
    anyway, the password is shown in debugger in CCS with zeros because its now secured. i tried to erase the flash but it always shows that the mcu is locked. 
    Also, i tried to read the device memory on the CCS but it was zeros. But when i used Uniflash programmer the sections of passwords are prevented by memory map to be read.

    1- can u please tell me how can i read the target device especially the address 0x003f7ff8 that stores the csm password?
    2- can u please tell me if i have debugger jtag like xdsv2, Will I be able to erase the flash contents without any error?
    3- can you please tell me any solution i can make to unlock the mcu again?

  • Hello,

    Let me see if another one of our CSM experts would be able to assist with this question.

    Thank you,

    Luke

  • Hey Luke,
    Is there any updates? 

  • Hi Abdelrahman,

    Did you intentionally program  specific password, or was the device unintentionally locked due to a power supply issue during programming? If you accidentally locked the device without specifying a password, the only possible method would be to erase the flash but I'm not sure this is possible if there was a power supply issue during programming.

    Thank you,

    Luke

  • Yes it because power supply maybe, but i am sure that i am not programmed the password with specific values.

  • Hi Abdelrahman,

    I discussed this with one of my colleagues, it is very likely that the device will become permanently bricked if there is a power loss or power glitch while the flash is being erased. If you are interested in steps to help prevent this in the future I can assist on best practices, but you won't be able to unlock this device unfortunately.

    Thank you,

    Luke

  • Hi Luke,
    it wont be unlocked again? even if there is a force erase for flash.

    Also, I will be appreciated if u give me steps to help me to prevent this happen again in the future.
    Thanks,
    Abdelrahman

  • Hi Abdelrahman,

    Yes you won't be able to unlock it, since the erase operation tries to read back the flash and check if there is all 1s in the erased location. Since secured memory locations read back as all 0s, this verify operation will fail and halt further erase operations.

    To help prevent this issue you can avoid programming in section A or D of the flash if your application code is small enough. If that is not an option you may need to check that our LDO is able to support all of the max current specs of the device in the datasheet so that enough current is always being supplied to the flash pump.

    Thank you,

    Luke