• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 100 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.

MSP430FR6043: Spy-By-Wire doesn't always run and hangs up in startup code

Brent Weight
Prodigy 150 points
Part Number: MSP430FR6043
Other Parts Discussed in Thread: MSP-FET

We have been using a dev board for several months with no issues.

We are switching to custom boards.  Using CC and MSP-FET with spy-by-wire setup. 

At times, the debugger works great, we run it and it hits the first line in Main and we can work away. 

But then it just stops working.  When running, the debugger hangs up in the Startup code (It highlights a random line of startup code) and never hits Main, but appears to be stuck in the startup code.   Nothing we do will get it to move on.  

If we swap to another board, it will often work fine for a while until it hangs up (same symptoms).  Then we can go back to the first board and it "magically" is working again.   We've checked and double checked connectors (including switching them out) and power.  All seems fine from that end.

Additional information:

We have a 1000 pF capacitor and 47K pull up resistor on SBWTDIO and a 750 pull down resistor on  SBWCLK.  Note that these components are on an adapter board attached to the MSP-FET. This adapter board is then attached by a 7 inch ribbon cable to our custom boards.

Any ideas on where to look are appreciated. 

  • 0
    TI__Genius 10870 points

    Hi Brent,

    Thanks for the updated info. So this is only occurring on the custom boards, correct?

    When you were creating your custom device, did you refer to the TIDM-02003 reference schematic to help create the design?

    For what you mention about the pull up and cap on SBWTDIO and the pull down on SBWCLK, it may be best to post an image of the circuit so it is 100% clear what you mean.

    I don't necessarily think that the ribbon cable is causing the issue but its never a bad idea to swap it for another to be sure.

    Are you just running one of the demo codes we provide in the SDK, or are you running custom code on the device?

**Attention** This is a public forum