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.

TMS320F28031: Device cannot be connected after first program

Part Number: TMS320F28031

Hi all,

I am helping my customer to solve their production issue on F28031.

During their latest production, they noticed most of their board cannot be connected via CCS after first time program. Even with same PC and emulator.

Customer is sure they did not program any CSM password.  The error report is Error-1015@0x0

I've suggested customer to change the bootmode to waitboot, but the error still cannot be fixed.

Is there any suggestion from BU on the follow up debug test?



  • Brian,

    It is possible that even if customer didn't program the CSM to have it interfere as you have described.  This issue is that even when the CSM is erased(0xFFFF), there still has to be a dummy read of the CSM passwords to "unlock" the device.  If the customer's code is inside one of the CSM protected address ranges when the emulator attempts to connect it will lock out the JTAG if this dummy read has not been performed.

    1)I would ask the customer to insert this dummy read of the CSM password locations(they can see this in our code examples in the SysInit function) in their code early in the main.

    2)Your point about WaitBoot mode SHOULD solve this issue, however.  Even if there was some accidental programming of the CSM wait boot mode would allow us to establish a connection to the device.  I would check with the customer on the drive strength/ resistor pull they are using to set the boot mode.  I believe that the internal pull ups are on the order of 400uA so we need to overdrive that. 

    If customer could try #1 immediately and see that it resolves the issue on new programmed devices we can be sure this is the issue we are dealing with(vs bad CSM).

    For #2, I can't explain why wait boot mode would not allow a connection.  In this case code will always be in a non-secure region and there should be no blocking.