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

MSP430FR2355: reconnecting debugger without stopping operation -- switch settings question?

steve wenner
Expert 2355 points
Part Number: MSP430FR2355
Other Parts Discussed in Thread: MSP-EXP430FR5969, MSP430FR5969, MSP-FET

I have multiple EVMs connected over various USB connections.  I can only run a single instance of Code Composer Studio.  I would like to know how to connect to an existing running EVM and peer into it's variables without resetting the target....I have attached two highlighted areas from the debug configuration switches.....Can someone tell me whether or not these should be checked or not?  I believe they should NOT be checked but I do not know CCS all that well and am unsure...

Thanks

8637.Debug Settings.docx

  • 0
    TI__Mastermind 28955 points

    Hey Steve,  

    The first definitely needs to be unchecked.  The 2nd one I don't think matters. I just tested this out on my side using JTAG (not SBW) and these are the steps I did to get this working in CCS v9.3.

    1. At the top menus, Go to Run -> Debug configurations 
    2. On the "Program" tab, set it to load symbols only.  This will allow you to debug the c project and not have to look through the assembly.
    3. On the "Target" tab, make sure the following are unchecked:
      1. Program/Memory Load Options -> Connection Options ->  "Halt the target on connect" and "Reset the target on a connect"
      2. Auto Run and Launch Options -> Launch Options -> Connect to the target on Debugger startup
    4. Apply and save.  
    5. Connect JTAG to your target and click the debug in CCS.  
      1. This is going to start the debugger but will not connect to the MSP430 yet.  
    6. In the debugger view, go to "Run -> Connect Target"  

    At this point, you should be connected to the MSP430 and it should still be running.  You should be able to pause the MCU and see the current status.  

    When I tried with SBW, the MSP430 always reset.  I think it might have to do with SBW using the RESET line for communication.  I'd have to look into this further to see if it's possible.  

    Let me know if this helps!

    JD

  • 0 in reply to JD Crutchfield
    Expert 2355 points

    Hi JD....

    Thanks for the response....

    I am using MSP430FR2355 EVMs, so I am using SBW.....please let me know if you can get it working using that?

    Thanks

    Steve

  • 0 in reply to steve wenner
    Expert 2355 points

    Also JD....

    I am doing everything you mentioned above but I don't seem to be running even though the target says running.....If I place a breakpoint in my RXISR I never get the characters even though I see them on the logic analyzer and the RXIE and GIE are on?  Also when I connect up and load the application and run it I do get my data sets....Can you help here?

  • 0 in reply to JD Crutchfield
    Guru 92251 points

    JD Crutchfield said:
    When I tried with SBW, the MSP430 always reset.

    I got it to work with SBW on a MSP-EXP430FR5969, without the MSP430 being reset, using CCS 10 by launching a Project-less debug session.

    In the target configuration used for the project-less debug session:

    • Under Program/Memory Load Options -> Connection Options "Halt the target on a connect" and "Reset the target on a connect" were un-ticked.
    • Under Auto Run and Launch Options -> Launch Options "Connect to the target on debugger startup" was un-ticked.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Chester Gillon said:
    I got it to work with SBW on a MSP-EXP430FR5969, without the MSP430 being reset, using CCS 10 by launching a Project-less debug session.

    When I connected to a running MSP430FR5969 without resetting it, I was using the ez-FET Rev 1.2 on the launchpad.

    When i tried instead using a MSP-FET, the target MSP430FR5969 does get reset at the point attempt to launch a debug session. Will try and work out if the target device reset is caused by some action the CCS debugger is performing, or the MSP-FET firmware.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Chester Gillon said:
    When i tried instead using a MSP-FET, the target MSP430FR5969 does get reset at the point attempt to launch a debug session. Will try and work out if the target device reset is caused by some action the CCS debugger is performing, or the MSP-FET firmware.

    When the target MSP430FR5969 got reset when starting a debug session, the MSP-FET was supplying the power to the target, and the target got reset when the CCS debugger called the MSP430_VCC function.

    Found the following in Using the MSPDebugStack:

    When the target configuration was changed to use an external power supply, i.e. power from the target connected to the MSP-FET VCC TARGET pin 4, then the MSP430FR5969 target didn't get reset when started a debug session, and was able to connect to the running device.

  • 0 in reply to Chester Gillon
    Expert 2355 points

    Chester.....

    Thanks....I will give this a whirl!.....My EVM has an ez-FET debugger....I will make sure I remove the power jumper.

    Steve

**Attention** This is a public forum