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-EXP432P401R: USB 3.0 Issues with CCS Cloud?

Part Number: MSP-EXP432P401R

Tool/software: Code Composer Studio

Hello,

I was helping some students get up and running with MSP432 LaunchPad Rev 2.1 and CCS Cloud. Most were able to go smoothly but a few had a common problem flashing the out of box code example from Resource Explorer to their LaunchPad. This has been on Windows 10 with some newer computers. The LaunchPad properly initializes under ports in the Device manager (2 com ports stating XDS110 like it should). CCS Cloud can also see the com ports from inside the IDE. But when clicking run it returns "Run Failed! Module closed."


We then tried to use Energia but we also get an error over there "an error occurred while uploading the sketch" and we even went through installing the MSP432 windows drivers manually which makes me start to suspect it might be USB port or Debugger related. These are really new computers which have the newer USB ports so they were not burned out and we tried swapping the LaunchPads and the different ports.

I'm wondering if it is USB 3.0 port related or is there a known issue with the newer Rev 2.1 LaunchPad?

  • Hi Mark,

    I see a message in one of the screenshots about needing to update the firmware for the debug probe. Was the firmware update successful?

    As there any specific reason you mentioned USB 3.0? have you tried using USB 2.0 ports and it worked fine?

    One other thing that comes to my mind is that we have had a rash of CCS debugger crashes on Windows 10 machines. You mentioned that the issue was observed on Windows 10. Has anyone tried a non-Windows 10 machine? I'm wondering if the issue you've observed is related.

    Thanks

    ki

  • If I remember correctly the students said the firmware was updated correctly, but I did not see that with my own eyes. They even reinstalled the cloud agent and browser plug-in to no avail.

    Yes most of the students still had windows 10 but did not encounter problems. I think for non-windows 10 it is also pretty smooth normally. also had a similar experience with students recently.
  • I've encountered similar issues with Windows 10 machines and USB 3.0 ports. As Mark stated, the XDS110 shows up correctly in device manager and CCS Cloud and Energia both recognize the ports. The problem is particular common when the USB port is also a charging port, indicated by a lightning bolt next the USB SS logo. I've occasionally fixed this issue by manually deleting and manually installing the drivers but this sometimes doesn't work. I believe this is a USB 3.0 driver issue present on certain laptops.
  • Ok more information. I have a Windows 10 laptop with one SS charging port USB type A and one regular USB type A. I ran through CCS cloud MSP432 out of box example through the SS charging port and was successful in loading the drivers and flashing the program. I'm not sure how to verify if my USB port is 3.0 as it doesn't have the blue connector. Device manager says the host controller is 3.0.

    Also my primary laptop running Win 7 has all SS charging port USB type A and I did not encounter the same issue when downloading code.

    I will see if I can run some more tests at another workshop session today and isolate the issue and verify that the "first time" setup is occurring.
  • Ok so again I ran through another group of students doing the out of box example for MSP432. We had of about 40 students, 4 had the issue again. All 4 were running Windows 10 and had newer computers. All 4 did have the first time setup dialog box pop up for them and everything appear to be installed correctly. I also had them delete their XDS110 driver from the device manager but that did not help. All 4 did have the SS charging ports only but I think many of the other students that did not have the issue were using the SS charging port like I was, so I no longer suspect it is related to that.

    I'm leaning towards it being a windows 10 related issue again but most copies of windows 10 seem to work so I'm lost as to how to reproduce the issue. Maybe service pack version might be a clue?

    The one procedure I didn't try yet was to delete the XDS110 drivers and then manually install the XDS110 driver zip file manually after that step, but going directly from CCS Cloud never resolves it.