• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 1005 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/MSP430FR2633: Unable to debug with native MAC OSX version of CCS

Lenio Cacula
Genius 16760 points
Part Number: MSP430FR2633


Tool/software: Code Composer Studio

I am afraid I do not have many details about the issue, so please help me ask the correct questions.

When running the MSP430FR2633 captivate demo in Mac OSx, the customer is unable to run the device in debug mode. The code compiles and the debug perspective launches, but it crashes before running the program in debug mode. The customer has already tried uninstalling both CCS and MSPware, but the results are the same. 

When using Windows VM, everything works fine.

Do you have any ideas?

Thank you!

Lenio

  • 0
    TI__Guru**** 173310 points

    Lenio,

    Could we request the following details to start with:

    1) Which exact version of CCS and which version of MacOS are they running?

    2) Which demo example are they running (I see a few different ones in Resource Explorer)? 

    3) Does the program crash immediately after it is put to run? How does the crash manifest - any error message from CCS or it just goes into the weeds? Can they capture and send us the debug server log?  As this log can get very large, have then enable it after starting the debug session but prior to the action that triggers the crash. 

    4) Is it just this specific demo/example that has this issue? Can they try a few other demos/examples in Resource Explorer and let us know if they work ok in MacOS?

  • 0 in reply to AartiG
    TI__Genius 16760 points
    1. Mac OSX = Sierra 10.12.6 (16G29), CCS version 7.3.0.00019
    2. It fails with any of the CapTIvate examples.
    3. The program does not crash immediately. It compiles, programs, and starts debugging. I have requested for the customer to enable debug logging - waiting for results.
    4. Same as #2

    Thank you!
  • 0 in reply to Lenio Cacula
    TI__Guru**** 173310 points

    Lenio Cacula said:
    The program does not crash immediately. It compiles, programs, and starts debugging. I have requested for the customer to enable debug logging - waiting for results.

    To clarify, is it the program that does not work as expected, or does CCS hang/crash in some manner? The debug server log will only help if it is a CCS hang or lock-up, for example, so it is important to know exactly how the debug problems manifest themselves in comparison to a working environment. Some more details about this would be very helpful.

  • 0 in reply to AartiG
    TI__Genius 16760 points
    CCS crashes after the device runs debug mode. I believe the log should help us - I will find out. Thanks!
  • 0 in reply to Lenio Cacula
    TI__Guru**** 173310 points
    Lenio,

    Since I haven’t heard back from you, I’m assuming the customer was able to resolve this issue and will be closing this thread. If the issue is not resolved, just post a reply below with the requested details. Thanks!