• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 748 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.

CCS/MSP-EXP430FR5994: How can I debug 2 separate systems, from 2 separate code composer instances, simultaneously on the same computer?

Jason Meyers
Prodigy 50 points
Part Number: MSP-EXP430FR5994
Other Parts Discussed in Thread: MSP430FR5994, MSP-FET

Tool/software: Code Composer Studio

Hello,

I'm working on an embedded system, based on an MSP430FR5994 that presents an SPI slave to an external device.  

For testing, I also programmed up another launchpad-mounted MSP-430FR5994 to act as a master device and spit out a few sequences of commands, and wired the two together.  I tried several ways to debug both of these simultaneously, and ended up starting a second instance of code composer, which pointed to a second workspace, and used that one to load the launchpad with the testing code, while I used the first instance to debug the system.

I was able, yesterday, with attention to the order of plugging in cables and starting debug sessions, to get this to work as I wanted - both devices were running independent debug sessions and I could start/stop/reload new code as desired.  Today, it isn't having it - all iterations yield an "already in use" error when I attempt to start the second session.

How do I get a code composer session/workspace/project to select a specific debugger/emulator so that I can run two at once?

Any suggestions for other ways to debug two separate launchpads/systems simultaneously would also be much appreciated.

Thanks

  • 0
    TI__Guru**** 450031 points

    Hello,

    Jason Meyers said:
    I tried several ways to debug both of these simultaneously, and ended up starting a second instance of code composer, which pointed to a second workspace, and used that one to load the launchpad with the testing code, while I used the first instance to debug the system.

    This is the best (and only) way for MSP430. Sounds like you got this set up right.

    Jason Meyers said:
    Today, it isn't having it - all iterations yield an "already in use" error when I attempt to start the second session.

    Did you power cycle the PC or disconnect/reconnect the usb cables to the MSP-FET? Assuming you didn't change the connect types in the ccxml and have one set to "TI MSP430 USB1" and the other set to "TI MSP430 USB2", it could be an issue with re-enumeration of the MSP-FET. Go back to trying each configuration separately - Start a debug session for each ccxml file on its own. Make sure both succeed on their own first. If this works, the the simultaneous session should work also.

    ki

  • 0 in reply to Ki
    Prodigy 50 points

    Hi,

    Thanks for the suggestions - with this, I've been able to get it to work repeatably.

    -Jason