• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 79 subscribers
  • Views 1621 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.

CCS/MSP430F149: "MSP430: Error connecting to the target: Unknown device" with known working target platform

Steve White
Prodigy 20 points
Part Number: MSP430F149

Tool/software: Code Composer Studio

I have a simple target board based on MSP430F149 which I originally programmed using IAR compiler and the old USB programmer MSP-FET430UIF. Having gone back to the target board after some years I am now using CCS V7 and the latest black USB programmer MSP-FETFlash Emulation Tool to attempt to reprogram device. Unfortunately, I get the error "MSP430: Error connecting to the target: Unknown device" despite having turned off all AV sotware. I have looked through the forums for answers, but nothing seems to match my problem.

The target board is simple using the old 12-way programming header and I have a number of these target boards which give the same error. The old system did not use pin 13 so that is unconnected.

It should really have been a simple drop in. Code compiles fine. 'Finished building target: "MET04.out"' seems to indicate build OK.

When debug is run I get the "configuring debugger" and then the error "Error connecting to the target: Unknown device".

Target voltage is set to 3300mV and target device set correctly in MSP430149.ccxml as MSP430F149 which is what is printed on the device.

Does anyone know some simple tests to find out where the problem lies?

To add more information the mode red LED flashes when the debug is launched and device manager shows tool drivers installed in Ports as "MSP application UART1 (COM8)" and "MSP debug interface (COM7)". I believe when CCS was installed the MSP-FET did a firmware update when it was plugged in.

I think I am right in thinking that using the old 12-way header is still valid as that is what my target board is designed for and pins 6,8,10,12,13 and 14 are not used.

Thus I only use TDO, TDI, TMS, TCK, GND, RST and VCC_TOOL shorted to VCC_TARGET.

  • 0
    TI__Genius 14745 points

    Steve,

    With this specific error, there can be so many possibilities of what the root cause could be. Some major culprits tend to be incorrect JTAG connections, improper supply voltage, USB cable malfunctions, and USB port malfunctions.

    The most common of those listed are incorrect JTAG connections. Please be sure to follow the steps outlined in page 19 of the Hardware Tools User's Guide to ensure that the correct JTAG connections are made. Pins 2 and 4 of the 14 pin connector are very important because only ONE can be connected to the device at any time. The other must be left open. Once we can confirm that the JTAG port is connected properly, then we can proceed to debug further.

    Best regards,

    Matt Calvo

  • 0 in reply to Matt Calvo
    Prodigy 20 points
    Thanks Matt, You went straight to the problem. I had not changed my target board or cable since 2006 using the old MSP-FET430UIF programming tool which was a 12-way connector. However, with that programmer the advice was to short 2 and 4 if using the tool to power. I simply removed link and used pin 2 to connect power to target. I now have old program flashed in and working so can design a new MSP430 system. I may not use the MSP430F149, but I had to use something to fire up CCS and new progamming tool. I can now enable my AV, etc and see if the system continues trouble free for new development.

**Attention** This is a public forum