• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 445 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.

CCS/MSP430FR5994: Is there a way to power cycle the MSP430FR5994 without losing the debugger tool

James Nadir
Expert 1120 points
Part Number: MSP430FR5994


Tool/software: Code Composer Studio

I would like to use the debugger to examine code behavior coming out of a power cycle.

What I tried:

  1. Removed the 5v and 3.3v jumpers on the launchpad. This failed because enough power was supplied through the SBW/COMM Interface to keep the MSP430 alive and board LEDs dim.  
  2.  Disconnect and reconnect the USB interface. The MSP430 power cycles but I lose the debugger.  

Any suggestions on how I can power cycle the MSP430 without losing the Debugger?

  • 0
    TI__Genius 14775 points

    James,

    I do not know of a way to power cycle the device without losing the debugger connection because once the power is removed, the debugger will not be able to communicate to the device and will abort.

    What might help you is the discussion in this E2E post where Katie explains how to physically power cycle your launchpad and then reconnect without reloading code. Hopefully this helps point you in the right direction.

    Best regards,

    Matt

  • 0 in reply to Matt Calvo
    Expert 1120 points

    Hi Matt

    thanks for the quick response and the link to Ms. Katie Pier's post. I didn't know there was a way to debug code without the debugger doing a code reload (i.e a mass erase of the FRAM/Flash). That is indeed useful. I think Jens-Michael Gross's comment (immediately above Ms. Katie Pier;s)  may be my solution. Prior to his comment I was under the impression that while a BOR was the most extensive it was not the same as what  happens at  power-on. But it may be close enough. My thought is to assert a RST on the MSP430 while the debugger is running instead of doing a power cycle. This shouldn't drop the debugger and I should be able to then follow the code out of reset. Luckily my MSP430 board has a RST button.  I will let you know if it worked.

    jim

  • 0 in reply to James Nadir
    Expert 1120 points

    Well that failed. RST has no effect when the debugger is in operation. RST works when the code is not under debugger control. Looks like I will have to find another way. 

**Attention** This is a public forum