Msp430 USB CDC example driver not detecting in windows 8 and 10 OS

Nitesh,

Could you double click the catalog file (.cat) for the USB driver and check if Windows 8 and Windows 10 recognize the driver as valid?

Derrick

Hi Todd,

I am using TI RTOS.

Nitesh

Hi Derrick,

In TI RTOS based example folder i am not seeing .cat file. Its available only in MSP Ware based example folder.

Thanks in advance

Nitesh 

Hi Nitesh,

Can you tell me which CDC example you are working with?  Is it the usbserivaldevice_MSP_EXP430F5529LP_TI_MSP430F5529 or one of the SYSBIOS examples found in the MSP430USBDevelopersPackage_5_00_01?

The CDC INF files found in the MSP430USBDevelopersPackage_5_00_01 are signed files which require that you have both the .cat file and the .inf file in the USB_Config directory.  The VID/PID in the .inf file have been certified and these VID/PIDs are also listed in the descriptors.h file.

The .inf file that is in the USB_Config folder of usbserivaldevice_MSP_EXP430F5529LP_TI_MSP430F5529 is not signed and it has not gone through certification.  So you will not find a .cat file in the USB_Config directory.  However, the VID/PID in the .inf file has to match the VID/PID in the descriptors.h file. 

First of all can you verify that the VID/PID you are using in the descriptors.h file for your project matches the ones listed in the .inf file for your project?

On my Windows 10 machine I have no issue with Windows 10 recognizing the usbserivaldevice_MSP_EXP430F5529LP_TI_MSP430F5529 device.   I can see the device in Device Manager which tells me that the device has gone through enumeration.

Regards,

Arthi

Hi Arthi,

Thanks for the reply, I am using same example as mentioned.

I am working on MSP430F5659 controller and using TI RTOS.

I verified on windows 10 and 8. The VID/PID are matching, checked using device manager and details of the ports by right clicking the on port.

Yes in TI RTOS example project .cat file is missing, and now i understand it is due to non certification.

I am seeing device is identified on windows 10, but port name is not matching as we get in windows 7 i.e. "Virtual_Com_Port(COMXX)" .

Thanks in advance.

Nitesh

Hi Nitesh,

I am not sure what is going on.   On the Windows 10 machine I have here I see the TI-RTOS example as a 'USB Serial Device' under the category of Ports(COM & LPT).  In fact I even changed the PID number to 0xDEAA and Windows 10 recognized the device as a Serial Device.

Have you tried re-installing Windows 10?    the next thing you can try is to change the PID to 0xDEAA in the descriptors.h file and the .inf file. 

Regards,

Arthi

Arthi,

Just for understanding com port name in windows 10 and windows 7 will be different?

Since in windows 7 i am getting virtual com port(COMXX)

Please confirm?

Nitesh

Hi Nitesh,

Yes the COM port name will be different in Windows 10.   However the COM port number should show up and not be listed as COMxx.    Also the name being different will not effect functionality of the CDC feature.

Regards,

Arthi

Hi Arthi,

Thanks, We were checking similar name as we are getting for windows 7. Let me try with the com port which is enumerated on connection.

I will get back to you by tomorrow.

Nitesh

Hi Arthi,

Thanks, i am able to communicate with windows 10 machine, As you told there no issue with driver, naming was different.

I have one more question, whenever i connect the CDC example driver 1st time in new machine(windows 7) why it shows "MSP example" in device manager? can we change that ?

Please guide me i want to change generic name of the driver, is it possible? Or any other way to handle this.

Nitesh

Hi Nitesh,

You can only change this name for the RTOS examples since the .inf files for these examples are not signed.   So to change the name, do the following:

1) Open the MSP430_CDC.inf file and go to [Strings] section way at the bottom of the file.  There you will see the variables DESCRIPTION and DESCRIPTION0 populated with names.  Change the names to whatever you want.

2) Then within the same file go to section named [DeviceList] and either leave variable name %DESCRIPTION% as is or change it to variable name %DESCRIPTION0% depending on the name you want displayed.  Then change the PID on the same line to a new PID.

3) Do the same as Step 2 for the section named [DeviceList.NTamd64]

4) Change the PID in descriptors.h file to match.

The name change will not work if you don't select a new PID.

Regards,

Arthi

Hi Arthi,

I am facing one problem, Where my software collogue  is asking whether we can get the .exe for the "MSP430_CDC.inf" i.e. driver file.

Since in our application we are asking the user to load the driver manually(path for the device driver), Is it possible to bundle it in application and let application take care of the driver installation?

Please need clarification,

Its urgent i appreciate your thought and input on this.

Thanks in advance

Nitesh

Hi Nitesh,

Yes .inf files can be packaged with the application and have the installer install it.   An installer like BitRock or similiar application might be able to do this although I have not done this myself.

Regards,

Arthi

Hi Arthi,

Thanks, any reference available please share.

Nitesh