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.

Laptop won't go to sleep when CCS is running and then crashes

Twice when I have put my Dell laptop to sleep by closing the lid with CCS 6.1 running it hasn't gone to sleep.  When I try to wake it up it hasn't gone to sleep and has effectively crashed,  Note the battery hadn't run all the way down.  Once it had a blue screen.  Both times when I restarted it pointed out the crash and asked about safe mode.     Once it had actually continued running and had gotten very hot.     I have closed the lid on the laptop hundreds of times when CCS wasn't running with no issue.

From reading other posts I noted that maybe the problem wasn't CCS directly but that I put it to sleep before I unplugged my Launchpad (MSP432) from USB. 


Thanks,
Andy 

  • Andy,

    Interesting; I don't recall seeing this. What I have seen is the opposite scenario: CCS losing the JTAG connection due to the PC entering a power saving mode. Perhaps this is a feature of a newer release of CCS or one of its components - namely the TI emulators package that is the component that touches hardware and is used by the MSP432 Launchpad board?

    In order to try and reproduce this, would you mind providing the details of your Code Composer Studio install and the version of the "TI Emulators" component (go to menu Help --> Installation details --> scroll down to find this component)?

    Regards,
    Rafael
  • Thanks. TI Emulators is 6.0.14.5. I tried it once without a board hooked up and it went to sleep properly. I need to try it again with a board.
  • After some more experimentation it turns out the problem appears to be tied to 432 LP being plugged into USB rather than CCS. When I put it to sleep a blue screen comes up it references something about the USB driver but it disappears too quickly to read all of it.
  • Actually this seems to be a board or jumper issue also. I'm not sure that a jumper issue should be able to crash the PC but.....