MSP-FET: Not recognizing microcontroler and other issues

Hi Felipe,
Could you describe how you are using the MSP-FETs? Also, when you mention stopping work, can you describe how it usually happens? Regarding time-life and guarantee, this device is tied to our standard terms and conditions of sale for evaluation items. 
Best Regards,
Diego Abad

Hi!

Thanks for you response.

I attach to this post the schematics for JTAG connection on my board:

The problems starts showing the following error while trying to flash or debug:

* Error initializing emulator: MSP-F430 is already in use

* Error connecting to the target: Unknown device

Both errors don´t let us keep debugging or flashing micro controllers. Once it starts showing these messages, JTAG messages starts appearing sometimes, and sometimes it allows to work; but then, starts showing these messages until we can not keep working.

We've tried (according to several posts on e2e FORUM):

1. Changing computer.

2. We've already done the MSP-FET HID COLD BOOT shown in "MSP DEBUGGERS USER'S GUIDE / DEBUG PROBES HARDWARE AND SOFTWARE / 5.6.5.3 MSP-FET HID COLD BOOT" whit no success.

3. We've already deleted drivers, and re-installed them.

4. We've tried with CCS and MSP FLASHER TOOL.

The concern is that we have worked with these MSP-FET for a while, and we've observed this behavior.

Greetings.

Hi Felipe,
Could you confirm with me that neither of the devices you are programming are being overstressed, and that you are not using SBW Cables that are longer than the ones provided with the MSP-FET?

Best Regards,

Diego Abad

Hi!

I can tell we've not overstressed them.

We use a 6in and 2in connector to set out board configuration set in addition to the cable provided with the MSP-FET. None of them works.

Thanks for your fast response.

Hello!

I had a misunderstanding, I'm not using SBW connection, but 4-wire JTAG Communication. The "SBW CABLE PROVIDED WITH MSP-FET" is the black cable that comes with the MSP-FET TOOL.

I attached the RST/NMI RC connection, according to the schematics provided.

We do followed the recommendations, I just missed to upload the image the last time. So the issue should be something else.

How is "VCC Tool" or "VCC Target" from the MSP-FET connected to your board? That is required to set the correct IO drive levels from the MSP-FET. Not being connected may explain most if not all of your issues.

Hi!

We use "VCC TARGET" connected and "VCC TOOL" disconnected. Last days we've tried with "VCC TOOL" connected and "VCC TARGET" disconnected, but we are having the same error.

Hi Felipe,
Sorry for the late response. Is the board you are using to program the devices a custom board? Also, what version of CCS are you using? 
Best Regards,
Diego Abad

Hi.

Right, is a custom board.

I've used:

*20.0.0

*12.8.1

*12.8.0

*12.3.0

*11.2.0

Greetings.

Hi Felipe,
Since the device was working initially (and assuming there wasn't any overstressing of the parts,) this issue seems to be more likely to be similar to what this costumer faced: https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/1340945/msp430fr2355-msp-fet430uif-is-already-in-use---still-crazy-after-all-these-years/5149343#5149343
Besides the advice above, I recommend to double check the connections from your board to the MSP-FET. 

Best Regards,

Diego Abad

Hi!

I've just tried the last link information, but we are still in the same issue. We followed all steps but we stay the same.

Is there any possible solution?

Hi Felipe,

I found another E2E Thread in regards of Unkown device error: https://e2e.ti.com/support/microcontrollers/msp-low-power-microcontrollers-group/msp430/f/msp-low-power-microcontroller-forum/838768/msp430f5529-msp430-error-connecting-to-the-target-unknown-device

Let me know if that made it work.

Best Regards,

Diego Abad

Hi!

Thank you for the response.

As mentioned before, the issue is that they've been working fine until the problem occurs, and then it stops working; this means we've a good header configuration. I've already checked the pins configuration, and there is no problem.

Regards

Hi Felipe,
In the E2E Thread I sent, there is a debug method they recommend, which is to scope or capture the JTAG and RST signals with an LSA and to look for a start sequence from the JTAG and a response on the TDO line. I recommend trying this just to verify this is the case. 
Best Regarss,
Diego Abad