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

Connection with Target Board MSP-TS430PW24 provided with MSP430AFE253 failed

Guenther Weimer
Prodigy 20 points
Other Parts Discussed in Thread: MSP430AFE253, MSP-TS430PW24

Hi All

I am using the MSP430 USB-Debug-Interface 'MSP-FET430UIF' (V1.4a) and the Target Board 'MSP-TS430PW24' (Rev 1.0) provided with the device MSP430AFE253.

When I have built my project I cannot connect the target with the debugger of the 'Code Composer Studio' (5.3.0). If I click DEBUG on the toolbar a window opens with following message: "Error connecting to the target: Unknown device".

In my CCS project folder there are the following device-related files: 'lnk_msp430afe253.cmd' and 'MSP430AFE253.ccxml' [Active]  in subfolder 'targetConfigs'.

I have tried to connect the target by JTAG and Spy-Bi-Wire but all trials failed.

I am not so familiar with MSP430 and CCS. Does anyone have an idea to help me?

Thanks

Guenther

  • 0
    Prodigy 20 points

    The problem has been solved by inserting the device MSP430AFE253 into the target-socket in the opposite direction.

    There is an identification point on the target-socket. But the problem is that this identification point doesn't correlate with the pin_1 marking of the device.

    The device is inserted correct into the target-socket if the pin_1 marking of the device correlates with the "1" marking on the printed-circuit-board of MSP-TS430PW24 and doesn't correlate with the identification point on the target-socket.

    Guenther

  • 0 in reply to Guenther Weimer
    Guru 227245 points

    Originally, the socked didn't have an identification point at all. But without notice, the socket manufacturer added one and nobody noticed when assembling the boards. Apparently, the pin numbering of the socked differs between socket manufacturer and layout.
    I stumbled into the same trap with one of my MSP-TS430P25x100 boards (the other one didn't have a marker on the socket).

**Attention** This is a public forum