• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 77 subscribers
  • Views 2408 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.

MSP430: Trouble Halting Target CPU: Internal error with USB. Once more

Andrey Dodonov
Intellectual 265 points
Other Parts Discussed in Thread: MSP430F6659

Hello,

I have CCS 5.5 and msp-ts430pz100usb Revision 1.25 board with msp-fet430uif. My mc is msp430f6659.

I tried some standard demos and they seem to be OK, but not USB - which I need.

I downloaded latest USB developer package 4_10. I started with C2_ReceiveData CDC Example. It loads OK and unless I plug in usb everything is fine - it loops getting into disconnected state. However, once I plug the board, nothing happens. If i then try to pause application, it gives error - MSP430: Trouble Halting Target CPU: Internal error. However, it is possible to stop it completely. Also if using same USB hub for both programmer and board it results in programmer being without power.

It goes without saying that nothing about the board appears in the device manager. The programmer is there and seems to be OK. Also, I of course set the general properties of project to my 6659. 

Typing this post, i noticed an interesting thing - if I connect board to the same usb group where keyboard  is, keyboard goes off and disappears from device manager. However, nothing seems to appear. 

So, my post is in general close to old http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/49017.aspx

Any help would be appreciated...

Update: After inserting the board's cable into completely free usb hub on the back of my pc and then starting debugging no errors occur, but still the state is disconnected. However, if I plug in usb during debug session (of course, not while hanging on any breakpoint) and wait - nothing happens. If I then try to pause - same "trouble halting..." error.

Thanks in advance 

  • 0
    Intellectual 265 points

    Hello myself,

    after 3 days of triple checking code, running both ccs and iar, experimenting with god knows what and learning half of documentation by heart, I finally took multimeter.

    Voltage from USB was close to zero. I inspected the board very close this time and noticed that 2 of 4 "ground" drops of the USB on the back side of the board were touching together. We separated them after several seconds of soldering and now it works. 

    Don't you guys in TI have any conformation tests for USB in your testboards?

    You've done such a wonderful job with USB API, descriptor tool and many other things to reduce developing time... And such a silly mistake... Seriously?

**Attention** This is a public forum