• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 4821 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/MSP430FR5994: The debug interface to the device has been secured.

sachin lashkare
Prodigy 30 points
Part Number: MSP430FR5994
Other Parts Discussed in Thread: MSP-FET

Tool/software: Code Composer Studio

 We are having customized MSP430FR5994 board for our application. While debugging/programming we’re facing severe error i.e. “debug interface secured”

Once the error popped up on debug window we are unable to program/debug the customized board.

 If we are replacing the Microcontroller (MSP430FR5994) on customized board the error got resolved and it will allow us to program/debug for several times. Again, after executing the program/debug cycles few times the replaced Microcontroller also goes in to same secured mode and the pop up window with error “debug interface secured” display on debugger.

 

To overcome the above error, we gone through few forum post and tried to follow below process using document, Ref slau319s we given a pulse from a function generator as suggested in point 1.3.1 To enter in BSL mode.

After following above process, we observed that the Microcontroller goes in to “Unknow device” rather than “debug interface secured” We observed the similar behavior using Code composer studio & MSP flasher command line tool.

Below are the FRAM memory details used by our application and we have also added protection in software to do not write on “JTAGSIGNATURE” section.

 

.map file snapshot:

name                           origin          length      used          unused      attr          fill
----------------------          --------            ---------  --------        -------- -        ---         --------

FRAM                          00004000 0000bf80  00003bf8   00008388   RWIX
JTAGSIGNATURE       0000ff80  00000004  00000004  00000000   RWIX   ffff 
BSLSIGNATURE         0000ff84  00000004  00000004  00000000   RWIX   ffff 
IPESIGNATURE          0000ff88  00000008  00000008  00000000   RWIX   ffff

Below are the development tools details:

 

Debugger: MSP-FET Flash Emulation Tool

Compiler: Code composer studio Ver:Ti Ver18.1.1.LTS

 

Could you please suggest us how to resolve both the errors (Unknown device & debug interface secured)

  • 0
    TI__Genius 12315 points

    Hello,

    It seems that your electronic security fuse was blew. You can try "On connect, erase user code and unlock the device" option. This option will erase JTAG Signature and unlock the secured state.

    B.R

    Winter Yu

  • 0 in reply to Winter Yu
    Guru 34453 points

    Winter Yu said:

    It seems that your electronic security fuse was blew. You can try "On connect, erase user code and unlock the device" option. This option will erase JTAG Signature and unlock the secured state.

    USER_CODE_ERASE (0x1A1A) is working only on FR4xx devices, not on FR5xx/6xx. First unchecked box on Connection options is related to FR5xx/6xx (MAIN_ERASE 0x1A1A, TOTAL_ERASE 0x1B1B), but it is working only if JTAG fuse is not blown.

    For unlocking FR5xx/6xx devices, I am using BSL that will do mass erase (back to factory state).

  • 0 in reply to zrno soli
    Prodigy 30 points

    Thanks for answers.

    I was able to solve “debug interface secured” problem by enabling the memory protection unit(MPU), Previously it was disabled

    I have attached the snapshot of memory protection unit (MPU) setting.

    Thanks!

  • 0 in reply to sachin lashkare
    Prodigy 30 points
    After enabling the MPU “debug interface Secured” problem not occurred in new controller.


    Thanks.

**Attention** This is a public forum