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.

Code Composer Studio Version: 6.1.0.00030 MacOS X (10.10.3) Build/Crash Problem

Other Parts Discussed in Thread: MSP430F2012, MSP-FET

I have been using the MacOS beta (Version: 6.1.0.00030) on on Yosemite (10.10.3) for the past week without any problems until earlier today.  I attempted to run a debug session on an MSP430F2012 using the MSP-FET tool and the program crashed just after building the code and reflashing the chip prior to entering the debug session.  This is the same configuration I have been using all week, same target device even.  I tried relaunching the program and a similar problem occurred, this time after building the code but prior to re-flashing the device.  It generated an error and did not crash CCS. (see screenshot below)  

I rebooted my computer, unplugged/reattached the MSP-FET and cycled power on the target devices which produced the same error message.  I then tried an uninstall followed by a reinstall with a reboot which also did not fully fix the problem as I instead got an error message since an executable wasn't generated.  In the console compile output there was something mentioning not being able to find "/bin/sh" during the make process in the console window.  (sorry, I forgot to copy the full message) I then decided to create a new project and add the code files from the original project.  This worked fine.  Any thoughts for preventing this from happening again?  I can certainly try creating a new project and adding my code without the reinstall to see if that works if the problem happens again.   I have been spoiled using CCS on my Mac, certainly worth some occasional inconveniences!

Thanks,
Mike

  • Mike,

    Unfortunately there is not necessarily a way to prevent such collapses to happen, especially on beta-quality software. Therefore, the safest path is to simply rely on the "usual suspects" such as a backup and a version control system.

    My suspicion to the explanation of the problem is:

    Technically speaking, the error message you got is due to the fact the "green bug button" (the button that launches a debug session) performs several steps including building the project. At this point it seems to me that a component of the workspace that deals with the CCS debugger was corrupt, as well as a file of the project itself - the combination threw the infamous java.lang.NullPointerException.

    Once CCS was re-installed, it usually launches itself at the very first time with a -clean option, which resets and clears several temporary files. This partially fixed the faulty workspace failed component but the project still had a fault that was evidenced by the /bin/sh message. With the new project created, the corruption went away.

    For these cases we strongly recommend to take a look at the page below, especially sections 3 and 4:
    processors.wiki.ti.com/.../Troubleshooting_CCSv6

    For several other technical details about CCS projects and the debugger, check the two other pages.
    processors.wiki.ti.com/.../Projects_and_Build_Handbook_for_CCS
    processors.wiki.ti.com/.../Debug_Handbook_for_CCS

    I apologize for the inconvenience,
    Rafael