MSP432 AppleUSBCDCACMData: start - Find CDC driver for data interface failed

Hi Jon,

I'm trying to loop in the right person to help you - thanks for your patience.

-Katie

Hi Jon,

I don't think any driver installation is needed for the MSP432 LaunchPad on Mac OSX as stated on the Energia page.

- Could you please tell me which OSX version are you running so we can try to root cause the issue?

Thanks,
Eric C.

Hey Eric,

I appreciate the reply. I'm still running Mac OS X 10.6.8. Energia seems to work fine with the MSP430G2553 which did require a driver install, but I since removed that due to the error that I had seen from MSP430LPCDC.

Please let me know if there is anything else you need from me to help solve this.

Thanks,

Jon

There is indeed no driver required for OS X. With that said, the lowest version that I have tested with is 10.7.5.

When you run system_profiler SPUSBDataType in a terminal you should see something like the below. 

      XDS110 (02.02.04.00) with CMSIS-DAP:

          Product ID: 0xbef3
          Vendor ID: 0x0451  (Texas Instruments)
          Version: 1.00
          Serial Number: 0
          Speed: Up to 12 Mb/sec
          Manufacturer: Texas Instruments
          Location ID: 0x1a200000 / 3
          Current Available (mA): 500
          Current Required (mA): 500

Hey Robert,

Thanks, but, yeah, I have that defined in the Profiler.   I did notice that I had to reboot my Mac with the MSP432 plugged in to get this to show in Profiler though.

I did a bit a searching for similar issues to this and apparently the AppleUSBCDCACMData driver in the older Mac OS X (10.6.8 in this case) is less tolerant then the more current driver in 10.7 and beyond. One suggestion was to change the call management descriptor in the driver to something other than 0 or if set to 3 set it to 2.

One interesting thing to note is that is in both Robert's case as well as mine, the Serial number for the MSP432 is showing as '0'; '00000000' in my case. With the MSP430, the serial number shows what appears to be a valid number. Also, the Location ID has a '/2' for the MSP430 rather than a '/3' as in the MSP432 case. Could this be a clue to the issue? The MSP430 does require a driver though.

Cheers,

Jon

Okay, so I discovered the xdsdfu tool and was able program a serial number to the MSP432. Also, I updated the FW to 2.2.4.1 from CCS but it still does not work with Mac OS X 10.6.8. I was able however to get connected to the MSP432 from a Ubuntu VM on my Mac and loaded the Blink example from Energia Linux, but after updating the FW on the board I was not able to get a Serial connection to the board from the VM again. Energia is now complaining about "Incompatible XDS110 firmware detected".
Is there a location where I can download the firmware.bin for 2.2.4.0?

Seems to be fine with CCS in Windows 8.1 though.

Hi Katie,

I installed Energia version 0101E0016 and it still is not working on my Mac. Also, I still get a failure in the Linux VM on the system, so nothing has changed.

This is the error I see from a Debian VM but it looks similar to the one I see with Ubuntu:

Thanks,

Jon

Hi Jon,

Thanks for trying, and I've made sure that our team is still looking into this. I'll let you know as soon as we know more.

Regards,
Katie

Hi Jon,

Eric is right, you will, unfortunately, need to downgrade to XDS110 firmware 636. Given that you were able to update means that it is detecting the MSP432 LaunchPad correctly. I think it is just a matter of firmware and programmer application being out of sync.
I just did an experiment here and updated the launchpad to the latest XDS110 firmware. As expected, it did not work with the programmer (XDSLite) that is shipped with Energia. When I downgrade to 636 all works as expected. I will as a not on the Energia website with instructions to downgrade to 636.
The next release of Energia will have the latest and greatest DSLite which ever version that is.

Robert

One other thing to make sure of is that the "JTAG SWITCH" is set to "XDS-ET" and NOT "Ext Debug"

Eric,

I was just now able to get back to this, but after downgrading the FW back to 2.2.4.0 on the MSP432, as well as having an updated Mac OS X (10.10.5) , I am now able to code the board from Energia on my Mac.
Very cool!

Thanks for assist.

Jon

Robert,

Yep, downgrading the FW cured the issue.

Thanks,

Jon

I guess I spoke too soon. After a few code loads to the board from Energia, the download the board hung and the following was seen in the console messages and I had to reboot the system to clear the issue.

9/15/15 9:23:02.700 PM ReportCrash[3263]: Saved crash report for DSLite[3217] version 0 to /Users/user/Library/Logs/DiagnosticReports/DSLite_2015-09-15-212302_Users-MacBook-Pro.crash
9/15/15 9:23:14.000 PM kernel[0]: process DSLite[3068] caught causing excessive wakeups. Observed wakeups rate (per sec): 207; Maximum permitted wakeups rate (per sec): 150; Observation period: 300 seconds; Task lifetime number of wakeups: 45004
9/15/15 9:23:14.156 PM ReportCrash[3263]: Invoking spindump for pid=3068 wakeups_rate=207 duration=218 because of excessive wakeups
9/15/15 9:23:15.764 PM spindump[2628]: Saved wakeups_resource.diag report for DSLite version ??? (???) to /Library/Logs/DiagnosticReports/DSLite_2015-09-15-212315_Users-MacBook-Pro.wakeups_resource.diag
9/15/15 9:24:23.651 PM com.apple.xpc.launchd[1]: (com.apple.ReportCrash[3352]) Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
9/15/15 9:24:24.372 PM ReportCrash[3352]: Saved crash report for DSLite[3306] version 0 to /Users/user/Library/Logs/DiagnosticReports/DSLite_2015-09-15-212424_Users-MacBook-Pro.crash
memory 0x00006578
94% .data: 0 of 8 at 0x70ac
Info: CORTEX_M4_0: Flash Programmer: Writing 8 bytes to flash memory 0x000070ac
94% .data: 0 of 320 at 0x20000000
95% .data: 0 of 1272 at 0x20001888
95% Finished
95% Setting PC to entry point.
Resetting device and running...
Error: CORTEX_M4_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.630.0)
Error: CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.630.0)

memory 0x00006578
94% .data: 0 of 8 at 0x70ac
Info: CORTEX_M4_0: Flash Programmer: Writing 8 bytes to flash memory 0x000070ac
94% .data: 0 of 320 at 0x20000000
95% .data: 0 of 1272 at 0x20001888
95% Finished
95% Setting PC to entry point.
Resetting device and running...
Error: CORTEX_M4_0: Can't Run Target CPU: (Error -2134 @ 0x0) Unable to control device execution state. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.630.0)
Error: CORTEX_M4_0: Trouble Halting Target CPU: (Error -2062 @ 0x0) Unable to halt device. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.630.0)

Katie, is there any news on this problem?

I have the same problem with my MSP432 LP, Energia 16 on a Mac running OSX 10.10.5.

Scott

Hi Scott, Jon,

I'd really have to get Robert Wessels to help with this one I think. I'll try to reach out to him about it.

-Katie