• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 1378 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2355: Error connecting to the target: The Debug Interface to the device has been secured

Zegeye Alemu1
Prodigy 155 points
Part Number: MSP430FR2355
Other Parts Discussed in Thread: MSP-FET

Good afternoon,

I run into this error when attempting to program the FR2355 device.

"MSP430: Error connecting to the target: The Debug Interface to the device has been secured"

I have looked into the map file and see no Password set.

I need to re-program this device. It is the first time for me. However, it was programmed by a previous employee.

I am currently using CCS version:  

    Version: 10.1.1.00004

I have attempted to slow down the debug clock from the xcml file. It did not work.

I am using the MSP Flash Emulator to program the device.

Would you please help in getting access to the device?

I do have the source code and with your direction I can identify information that I might have failed to recognize.

Thanks again and best regards,

Ziggy

  • 0
    Guru 34483 points

    This device can be unlocked (mass erased, back to factory state) by SBW / JTAG mailbox (user code erase) or by BSL.

    e2e.ti.com/.../2937741

  • 0
    Prodigy 155 points

    Finally found the window for the configuration. It has it in the version of CCS I am using. 

    I did place check marks on both boxes and still I am unable to access the device.

    Thanks again and best regards,

    Ziggy

  • 0 in reply to Zegeye Alemu1
    TI__Mastermind 39690 points

    Are you sure you have enabled the those operations in the CCS like this?

    If it still not work, could you give some pictures about the hardware connections on your side?

  • 0 in reply to Gary Gao
    Prodigy 155 points

    Good morning Gary,

    See attached. Thanks.

  • 0 in reply to Zegeye Alemu1
    TI__Mastermind 39690 points

    Could you give more information about hardware you use now? Do you use the MSP-FET?

    How you connect between the emulator with MSP430 and PC?

  • 0 in reply to Gary Gao
    Prodigy 155 points

    Good morning Gary,

    I am connected to the target from the PC as follows.

    - USB cable with Ferrite (Type A) connected to PC side and (Mini B) connected to MSP-FET Emulator.

    - A 14pin Cable connected from MSP-FET to the Target

    Side question:

    What causes the device to be secured if have not secured it. The source code handles update via BSL and the scripts used use 'default password' for password entry.

    I am puzzled how and why it's secured.

    Another question:

    Could any of the 14 pin state cause the lock up?

    Thanks and look forward to a response.

    I am surprised that TI support is not replying to the question.

    Best regards,

    Ziggy

  • 0 in reply to Zegeye Alemu1
    Guru 34483 points

    JTAG fuse is not a fisical fuse, it is just value stored in FRAM, that can be overwritten by firmware. You can find it in device datasheet, but AFAIK for all FRAM devices it is (word) located at address FF80h. JTAG lock is not related to BSL password (vector). I found that in some cases bad (erratic) code/firmware also can cause JTAG lock reported error even JTAG fuse value is untouched (default 0FFFFh).

    While some other MSP430 device can be bricked (with disabled/corrupted BSL and locked JTAG), FR2xx can not, because TI implemented mass erase (back to factory state) that is triggered by JTAG mailbox system that stays enabled with locked JTAG. I don't know why this is not working in your case, because it should. If you didn't disable BSL (and that is also for FRAM devices on address 0FF84h, check device datasheet), than you can trigger mass erase by BSL, that should reset JTAG fuse value (to default 0FFFFh)..

    No, other pins can't cause lock-up. Master device with SBW interface just use RESET / TEST pins on target devices, others are irrelevant.

  • 0 in reply to zrno soli
    Prodigy 155 points

    Good morning all,

    Thank you very much for all who participated and helped. I appreciate it very much.

    After going through a whole lot of debug found out the problem was a hardware issue. Some of the JTAG signals were not correctly connected making the BSL access working and crippling the h/w debugger comms.

    This problem manifested itself as a device security issue when it was actually not.

    Thank you again for all your help.

    Best regards,

    Ziggy

**Attention** This is a public forum