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.

TMS320F28035: Device has been locked

Genius 3095 points
Part Number: TMS320F28035

Hi teams:

We are using TMS320F28035PNQ controller in one of our project and we made a custom board for that. We are trying to implement OTA feature and started with 'f2803x_flash_kernel' example code. While we are debugging this example code in CCS and suddenly we are unable to program controller, it gives error 1015. And as per TI documentation, there is a chance of writing zeros at CSM locations if erase operation is interrupted which locks device permanently. Is that the reason why my device is locked?What could be the reason in this case for device being locked?

If so, while doing Firmware upgradation through OTA in the field, if power goes off during flash erase device gets locked. And need to replace the chip?How to get rid of this and any precautions to eliminate this situation? Is there any way to do flash operations without affecting CSM locations?

In the field if power goes off while doing FW upgrade there is a chance of device gets locked. Is that correct? In this case how to get rid of this situation and how to avoid locking the device?

  • Hello,

    Concerned experts have been notified.
    Please note that the response might be delayed due to holidays.

    Regards,

    Sudhakar
  • Hi F.F.,

    Are you able to connect to the device? Can you use CCS to read the CSM values using a memory browser? What are they?

    sal
  • Hi,

    Ist, as mentioned by Sal, please check if device is indeed locked. You can connect to CCS and check the Flash content if it's all zero then you are right that flash is locked.

     In the field if power goes off while doing FW upgrade there is a chance of device gets locked. Is that correct? In this case how to get rid of this situation and how to avoid locking the device?

    Yes, if this happens then device get permanently locked and only option is to replace the chip. To avoid this, one need to have stable power supply while doing FW upgrade.

    Regards,

    Vivek Singh

  • Hi Vivek,

    I have tried to connect to device using XDS200 debugger to check memory locations. But I am unable to connect to the device. I have replaced with new controller and now I am able to connect to the target.

    Currently, the issue is resolved but is there any way to disable this feature(we don't need this locking feature) completely and avoid locking of device accidentally?

    Thanks,

    Hari Priya

  • Hi,

    If it has happened by accident like power loss during flash operation then no, it can not be disabled. You need to make sure you have stable power supply. If you have issue with .out (have something mapped in password location) then you need to correct the linker cmd file (use type = DSECT) so that nothing gets programmed into password locations. 

    Regards,

    Vivek Singh