• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 79 subscribers
  • Views 206 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.

MSP430F5510: CCS stopped communicating with MSP430 Dev kit via MSP430-FETUIF

ANDREW JAMES
Prodigy 50 points

Part Number: MSP430F5510

Hello, I have:

  1. TI's CCS12.8.1 
  2. TI  MSP-TS430RGC64USB dev kit with a MSP430F5510 cpu 
  3. TI MSP430-FET430UIF debugger connected via ribbon cable
  4. Known working firmware that communicates to host PC via USB and CCS project.
  5. This firmware enuemerates itself as HID KB with the host PC

Last week I could either update the target CPU with firmware or debug it with breakpoints etc sucessfully but as of today the same setup mysteriously no longer functions.  

When I either try Run>Load>... or Run>Debug>.... from CCS the following appears:

image.png

and debuggers green "power" led & red "mode" led are lit, but are followed with these messages:

image.png  image.png

What was a functioning debugger has suddenly decided to stop recognising a functioning MSP430 devkit which is still running the firmware from last week.

Something odd has happened to the debugger without human intervention!

Any Ideas?

 Thanks

Ps I have tried different USBcables, turning thing off/on again etc

  • 0
    TI__Expert 8841 points

    Hi Andrew,

    Here are some suggestions:

    • Confirm that the headers are properly connected on the target socket board.
    • Is VCC configured to be externally or internally supplied? Ensure that power is being supplied.
    • Double check that the MSP430F5510 is properly aligned in the socket.
    • Do you have any other socket boards or MSP430F5510 that you can test with?
    • If I'm understanding this correctly, the debugger wasn't touched, but what about the socket board? Was anything changed?

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 50 points

    Hello Owen, my checks have resulted in the following:

    • Headers are connected as before, devkit is thus connected to debugger via ribbon cable and USB cable to host PC but disconnecting it results in the same error message (which isnt surprising).
    • Vcc is 3v12 plus target MSP430 is still running previous USB HID firmware which windows enumerates and functions ok
    • MSP430 is running its last firmware ok so must be aligned in socket ok.
    • I tried another devkit with the same MSP430 IC and the same errors and red Mode LED are seen.
    • While nothing has physically changed the debugger had its internal firmware upgraded as CCS kept nagging about this so I did OK this update, but the debugger continued to function afterwards but without the upgrade nagging.

    My concern is the upgrade of firmware initially worked (and improved my workflow), but after the debugger is power cycled it becomes "bricked" in some way .

    My other concern is the 10way IDC connector electronics within the debugger has failed but I dont have a spare ribbon cable to eliminate that possibility.

    One thing I do have access to is a logic analyzer to inspect signal lines if that could be useful?

  • 0 in reply to ANDREW JAMES
    TI__Expert 8841 points

    Hi Andrew,

    Thanks for your thorough response.

    If you have any jumper cables available, you can test to see if you are able to connect to the device.

    Probing the signal lines may be helpful. If you are able to do so, please share the capture.

    I believe some older debuggers had the ability to be factory reset, but I don't believe the MSP-FET430UIF has this ability. It may be worth installing the drivers again: https://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_FET_Drivers/latest/index_FDS.html

    You can also try using the MSP Flasher to check for firmware updates using your command line. Section 5 of this document outlines this.

    Best,

    Owen

  • 0 in reply to Owen Li
    Prodigy 50 points

    Hello Owen, I have done a bit of debugging of the FET430UIF debugger and noticed an accidental workaround....

    • My Devkit is connected to the host PC via a USB cable (as the firmware functions as a HID device),
    • Devkit is connected to the FET430UIF via a ribbon cable.
    • The FET430UIF also connects to the host PC via USB to CCS V12. 

    If I power up the test setup with the FET430UIF to HostPC USB cable disconnected then connect it once the dev kit is powered up, CCS can program and debug the target CPU as expected.

    It's as if the FET430UIF maybe running before the target CPU and its 10w connector electronics get latched into some state which the FET430UIF firmware cant recover from. Very odd all the same!

  • 0 in reply to ANDREW JAMES
    TI__Expert 8841 points

    Hi Andrew,

    Very interesting finding. I'm glad to hear that you have found a solution.

    Before, was the the USB cable from the target socket board connected to your PC after connecting the MSP-FET430UIF, or was it not connected at all?

    Best,

    Owen

**Attention** This is a public forum