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/MSP430F5234: First time programming the MSP430 results in Error connecting to the target: The Debug Interface to the device has been secured.

Part Number: MSP430F5234
Other Parts Discussed in Thread: MSP-FET,

Tool/software: Code Composer Studio

Hi Everyone, 

I have a custom board and I am using the MSP430F5234. Upon my first attempt to program the MSP through a 4 wire connection (VCC, GND, RSTDVCC/SBWTDIO, TEST/SBWTCK) using the MSP-FET Flash Emulation Tool, I get the following error: "Error connecting to the target: The Debug Interface to the device has been secured".

I have read through the forums, but all of them have mentioned they have somehow locked the JTAG connection. This is not the case for me since this was the first attempt at programming the board and I have not set any value into 2 words in memory to make the JTAG lcok.

Thanks again

  • Hello,

    First, do you have your schematic for the Spy-bi-wire interface configured as shown in figure 2-3 of the users guide below?  Not that there are 2 different configurations depending on the device family.

    https://www.ti.com/lit/ug/slau278af/slau278af.pdf

  • Hi Eddie, 

    Thanks for your response. Yes I have followed the user guide in connecting the Spy-bi-wire interface. I have also sketch how the JTAG and the MSP are connected. 

  • 4923300 said:

    I have read through the forums, but all of them have mentioned they have somehow locked the JTAG connection. This is not the case for me since this was the first attempt at programming the board and I have not set any value into 2 words in memory to make the JTAG lcok.

    Device can be "locked" by downloading "bad" firmware. In this case, there will be problem during entering to SBW mode, and device will respond with fuse blown (secured device) even fuse values are untouched (factory state). (From my experience) this can be resolved by leaving unpowered device on side for some time, or (if this not help) forcing mass erase with ignoring all SBW errors (AFAIK this can not be done with TI tools).

    In some cases device can be "unlocked" also by BSL mass erase.

  • Thanks for your response. As I stated, I was trying to download sample project into the MSP so not sure if the device would get "locked" by it.

    In addition when I try to mass erase using BSL, it does not get acknowledgement. So really don't know what else to do or what has caused this issue.

    Thanks

  • Do you get the same error no matter what code you try to load?  

    Has this issue been seen on multiple boards as well?  If possible, can you swap the IC on a board that has seen the issue and see if the problem persists?

**Attention** This is a public forum