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.

MSP430FG6426: MSP430: Trouble Halting Target CPU - while connecting load to my module

Part Number: MSP430FG6426

Dear Team,

I have MSP430FG6426 actuating around 80 inductive loads (each 25mA) activated through a comination of TI's 74HC595 shift register and ULN2803.

I get the debug session running very fine while activating the ULN channels in the manner i want.

But when i try to connect the load of the 80 inductive loads, the debug session gets messed up with an error "MSP430: Trouble Halting Target CPU", and this happens all the time when i try to switch ON more than 10 solenoids here. (if i keep it less than 10 then i have no issues)

Another point here is that, i dont see any issues with the controller and its able to run without any issues even if all 80 loads are activated. Its just the debugger that fails at this time.

I am using  Code composer - 9.2.0

Debugger- MSPFET430UIF with SpyBiWire

Would be really helpful if i can get a clue here why the debugger misbehaves ?

Thanks

Surya

  • It is most likely due to those connected inductive loads and electrons going where they want to go instead of where you think they should. Since it works until the debugger is connected my first guess would be a ground loop. If the power supplies for the target and the debugger happen to have their grounds tied to safety ground, you get a loop and voltage drops where you didn't expect them.

  • Thanks a lot for your response here, and i made the below try's which solved the problem.

    1) As you mentioned i made the ground lines strong with providing the grounds directly to the load rather than routed from the PCB module which shares a common ground between the electronics and the inductive load..

    2) I had a non standard SMPS powering my modules, and now i have replaced with Meanwell's branded SMPS which also solved the problem if i power up the load from the common PCB.

    Thanks for the hint that really helped to fix the problem.

**Attention** This is a public forum