TMS320F280025C: Failed unlocking device

Hello,

Our expert on this topic is currently out of office and is expected to be back by 28th November. Please expect delay in response.

Regards,

Varsha

Yogini,

            It is conceivable that the ECSL is kicking in and disconnecting the debug probe connection.

Yogini Joshi said:

3. But I am getting error while connecting.

Please post a screenshot of the error you are getting.

Yogini Joshi said:

So, do we need to modify the target configuration file or gel file in order to be able to connect the controller via JTAG?

No.

Yogini Joshi said:

We tried this on our PCB, hence it is difficult to modify hardware.

Please provide a screenshot of your schematics that shows how the boot-mode-select pins (GPIO24 and GPIO32) are connected.

Yogini,

            These 4 easy-to-understand videos explain how the DCSM module works:

https://www.ti.com/video/6336140498112?keyMatch=DCSM

https://www.ti.com/video/6336138543112?keyMatch=DCSM

https://www.ti.com/video/6336139910112?keyMatch=DCSM 

https://www.ti.com/video/6336139622112?keyMatch=DCSM

Thanks Hareesh for your response. Below is the snapsot of error from Uniflash.

On the PCB, we have connected both boot pins to high, for booting it from flash.

Attaching one more snapshot, where I tried unlocking device via uniflash, and then tried reading the memory.

Hi Yogini,

Could you try this same procedure using the CCS On-Chip flash tool, and compare the result using both the ECSL Unlock and the standard Unlock? This could be a potential issue with Uniflash.

Thank you,

Luke

Based on the below, it does appear the UNLOCK operation succeeded. 

I presume you have pull-up resistors for the boot-mode-select pins. Is there any way you could remove them and try SCI bootmode?

yes, we have 2.21K pullup resistor on boot pins. It is difficult to modify hardware.

from where, I should enter password in CCS? 

If I click debug, debugger tries to connect but disconnects suddenly showing below error;

error:

C28xx_CPU1: Trouble Halting Target CPU: (Error -1156 @ 0x0) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device. (Emulation package 9.4.0.00129)
C28xx_CPU1: Error: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.4.0.00129)
C28xx_CPU1: Unable to determine target status after 20 attempts
C28xx_CPU1: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
C28xx_CPU1: GEL: Error while executing OnTargetConnect(): Could not write 0x0005F412@Data: target is not connected
at *((int*) (0x0005F400+0x12))=0x0003 [f280025c.gel:186]
at OnTargetConnect()

Hi Yogini,

After launching your target configuration you should be able to navigate to Tools -> On-Chip Flash Tool. From there you should scroll down to your CSM passwords and click ECSL Unlock after providing your passwords. Let me know if this prevents the debugger from disconnecting.

Are you using JTAGLOCK? If so you will also need to modify your target configuration file to restore JTAG access to the device.

Thank you,

Luke

Hello Luke,

CCS is immediately getting disconnected after launching. Adding recording of procedure here. please let me know if I am missing anything.

One more doubt;

The flashed application is having CAN implementation. So, I tried connecting it over CAN , but controller is not getting connected over CAN.

is it because of locking?

I have protected all flash sectors and entire RAM. 

Note: There is not JTAGLOCK functionality available for this series for controller.

Thanks,

Yogini

Hi Yogini,

My apologies, I was mistaken in my previous response. Hareesh and I tested the ECSL unlock on our side when using flash boot but were also unable to connect. Due to the ECSL tripping, it is only possible to connect via wait boot if the flashed application is accessing secured resources. Let us know if it is possible to modify the boot mode select pins.

If you are still having CAN specific issues we can have this thread reassigned  to one of our CAN experts.

Thank you,

Luke

Okay. Thank you for your suggestion.

Does this mean , for accessing secured memory via JTAG, we always need to modify hardware?

What is the case, if we want to unlock the memory access via software itself in free run mode? Do we still need this Hardware modification?

Hi Yogini,

It is possible for the application code to unlock the security zones. Your code would need to perform the password match flow, which requires performing a dummy read of the CSM passwords and writing the correct passwords to the CSMKEY registers.

Thank you,

Luke