I am having trouble with CCS intermittently refusing to successfully launch a debug session, sometimes it works sometimes it doesn't. When it doesn't it just displays the following:
I've let it sit there for 5-10 minutes with no change. If I click cancel it doesn't cancel but continues. I have to give it the three fingered salute to kill the app. Then I must reboot the computer just to be able to relaunch CCS (problem is due to a .lock file accessed by process javaw.exe which for the life of me I cannot figure out how to kill.
winxp pro, CCS4, MSP430F5436
It really seems to be hit and miss when this happens. Anyone else experienced this or similar?
Please take a look at this thread for similar issues: https://community.ti.com/forums/p/8739/41831.aspx#41831
In some instances, the javaw.exe process can be killed after unplugging the USB emulator, however this does not seem to work in all cases. At this time the solution in those cases appears to be a reboot of the PC.
If you are able to isolate a sequence of events or settings that can trigger and reproduce this lock up, we would be interested to hear that.
If a post answers your question please mark it with the "Verify Answer" button
Search the wikis for common questions: CGT, BIOS, CCSv3, CCSv4Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box
thanks for the suggestion. Unplugging the FET module did not help. I also tried PSTools to kill javaw.exe with no success.
I changed the project's target processor at one point after the project had been created, could that have anything to do with this?
Changing the target processor of the project shouldn't normally result in a lock up, however there is apparently something that causes the driver to lock up in some instances that it is not able to recover from. If you see this lock up again it will be very helpful if you could send us the steps that led to it.
If I come up with anything I'll definitely let you know. It seems completely random so I'm wondering if it can be related to the state of the processor during the debug connection, i.e. in an interrupt, etc. I'm well beyond my knowledge comfort zone here so obviously that's just a guess.
I have the same problem. Did anyone find a solution?
Did you try cleaning the workspace?
-----------------------------------
Don't forget to verify answers to your forum questions by using the green "Verify Answer" button.
Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.
Having CCSv5 problems? Check out the CCSv5 Troubleshooting Guide
Click here to track an issue. Enter your bug id in the "Find Record ID" box
No I'm still having this problem intermittently and always have to reboot to get up and going again. Still no pattern developing on this end. I haven't tried cleaning the workspace, I'll give that a shot. Though if that were the problem I would expect more consistency to the behavior.
I've filed SDSCM00034753 so that we log more information when the launch becomes unresponsive after two or more minutes.
That's great news! I'm glad to hear this issue hasn't gone completely cold, it's super frustrating. Please let me know if there is anything I can do to help.
I know that this is an intermittent problem, but if you manage to reproduce the problem consistently, let us know.
mitaka I have the same problem. Did anyone find a solution?
mitaka - which MSP device(s) are you developing with when you see the problem?
MSP430F4783
I am having the same problem and it started with CCS V3.1 and now with V4. The device I am working with is the MSP430F248. There does not seem to be a pattern and the only way to fix the problem is to restart the PC.