msp430f5659: Driver installation issue - msp430f5659

Hi Manoj,


Current Issue 1:
Some things you might try:
1) Making sure that you are not trying to install the .inf file on a computer that you have already installed it on. This means that if the MSP430_CDC.inf file has the VID/PID of 0x2047/0x0300 then you cannot re-install it on the same OS.
2) lower case commands for RunDLL32.exe, setupapi.dll
2) lower case for RunDLL32.exe but leave SETUPAPI.dll as is
2) add a 'start' at the beginning of the command

Here are some articles I found that might help you with the command:

social.msdn.microsoft.com/.../installing-driver-using-inf-file-from-command-line-on-windows-7-64-bit-failing

community.spiceworks.com/.../1702844-install-inf-file-from-cmd


Current Issue 2:
Which installation method did you try installing the signed driver? Was it the manual method of right clicking on the device or was it from the command line? Also are you trying to installl the signed driver on a machine you have already installed the VID/PID on?

From which USB Developers Package did you get the signed .inf from? Also make sure that the .cat file and the .inf file are in the same directory.

Yes the PID is 0x0300 for all CDC examples that come with the MSP430USBDevelopers Package.


Regards,
Arthi

Hi Aarthi,

Thanks for your response

Regarding Current Issue2:

which installation method did you try installing the signed driver? Was it the manual method of right clicking on the device or was it from the command line?

>> Yes, Manual installation - From Device manager -> Update Driver -> Browse the inf file

Also are you trying to installl the signed driver on a machine you have already installed the VID/PID on?

>>  Existing driver we use is unsigned Driver We unstalled the existing drive then we tried to install signed driver .

But we couldn't install.[I attached the problem driver for reference -signed Driver. Kindly check]

From which USB Developers Package did you get the signed .inf from? Also make sure that the .cat file and the .inf file are in the same directory.

>>Both .cat and .inf file are in the same folder. Still we couldn't install the driver using manual method.

Yes the PID is 0x0300 for all CDC examples that come with the MSP430USBDevelopers Package.

>>ok

8524.USB_config.zip

I shall get back to u on issue 1.

Regards

Manoj

Hi Manoj,

The reason you are having so many issues maybe with installing the .inf file is because you are using the same computer to re-install the same VID/PID.  Just un-installing the driver will not do the right clean up.  You might have to also go into the Windows registry and clean up the VID/PID and other things.  I am not sure how to go about completely removing the installation of a driver and its VID/PID.  You will have to google this issue.  This also holds for the signed .inf file and .cat file.  In fact there might be more involved in cleaning this up then just the VID/PID.  

Now since you are trying to automate the installation of the CDC driver, I can make a suggestion that you create a new PID using the descriptor tool.  You can keep the VID (0x2047) the same but use a different PID.    You can use the descriptor tool to create your own .inf file. (Obviously if you use the descriptor tool, the generated .inf file will not be signed and will not have a .cat file).  The instructions for doing this are in the Programmers Guide.

Regards,

Arthi   

Hi Aarthi,

Thanks a lot for your support!

The installation is successful without unsigned warning in a fresh PC in which driver is not installed before. So may be cleaning up the registry is the issue in problem PC as you said .

I need some more clarification:
I am trying to change existing DESCRIPTION in the INF file "TI MSP430 USB" to Our Product Name "XXX_MRT_DEVICE" and the same name "XXX_MRT_DEVICE" is modified in Descriptor.C file also then prepared the build. In that case if I used the same build in our board and trying to install using the inf file. We got unsigned driver warning but installation successful.

Our requirement is we need to change the name "TI MSP430 USB" to "XXX_MRT_DEVICE" and should install without unsigned warning. Kindly advice.

Regards
Manoj

Hi Aarthi,

1. If we change the VID , we suspect python Firmware Upgrade tool may not work because when we try to open it look for the VID of the device. Please advice on this possibility of this issue.

2. Our Requirement: Device has to be detected as "XXX_MRT_DEVICE"
a) Suppose if we have to change VID and PID together orelse we can change PID alone ?
b) Is there any cost involved to signing process with Driver name in inf file change along with PID change

Regards
Manoj

Hi Manoj,

1. I have not really tried this scenario so I am not sure.  Technically there are two sets of VID/PIDs....one for BSL (0x2047/0x0200) and the other is for the CDC example (0x2047/0x0300).  The signed certification is for the CDC VID/PID and not for the BSL VID/PID.   Changing the CDC VID/PID should not effect the capability of the Python Firmware Upgrade tool to do its FW download job since it is using the BSL VID/PID.  The VID/PIDs are there for the OS to identify the device.  Myabe you can try creating your own VID/PID using Descriptor Tool and then try downloading firmware with Python tool after changing the CDC VID/PID.  I am guessing that this should not be an issue. 

2a. If you are asking whether to change both VID and PID or only PID then the answer is you can do either for your device. 

2b. Yes there is cost involved.  You will have to google this to find out since it is Microsoft's domain.

Regards,

Arthi     

Hi Arthi,

This is our understanding on VID/PID and Driver Name Change. Please correct me if I am wrong

Case 1
We don't want to change VID and want to change only PID, then we have to go with VID sharing program with TI.
1. If we change the PID alone then Driver name also can be changed from "TI MSP430 USB" to "XYZ_MST_DEVICE" . Is it correct?
2. In this case TI will do all the proceeding once we raise the official request for PID change + Driver Name Change. Is it correct?
3. Is this option also cost involved?

Case 2:
If we want to change both VID and PID then we have to approach Microsoft. This is cost involved.
Actually we don't want to go with case 2 .

Please clarify on this request.

Regards
Manoj

Hi Arthi,

We suspend the above VID/PID modification at this moment.
Now we are facing new issue please go through the below issue description.

The Signed Driver is working fine for windows 7 64 bit machine.

The Driver installation setup for windows 7 64 bit machine is below
The Installation folder contains(.cat, .inf ,.bat) then we run the batch as administrator.
Batch file contain the commands pnputil -i -a c:\Driver\msp430_ti_signed.inf

The Driver is not working for the windows 7 32 bit machine with the same setup and error we are getting is" windows encountered an error while installing driver for your computer"
Is this inf file common for 64 bit and 32 bit machine or it is only for 64 bit machine?

Please advice on this issue

Regards
Manoj

Manoj,

The inf file should be for 32-bit Windows 7 OS also.   You can verify that it works for Windows 32 bit by installing it via the Device Manager and not through the command line.    Also verify that the VID/PID is not already installed on the Windows 32-bit machine. 

Arthi

  

Hi Arthi,

We tried manual installing (From Device Manager)of signed driver in 32 bit windows 7 machine but manual case also there is an error in installing of signed driver in 32 bit windows 7 machine.

Same signed Driver can install manually in 64 bit windows 7 machine without any issue's.

Note:
In windows 7 32 bit machine ,Problem in installing the signed driver only but unsigned driver can install successfully.

Kindly advice on this.

Regards
Manoj

Hi Aarthi,

Driver is working in windows 7 32 bit PC. We tried in PC in which driver is not installed. Then it is woking fine.
Kindly close this issue.

Thanks and Regards
Manoj

Hi Arthi,

The Driver is working fine in both 32 bit also. We tried in PC in which driver is not installed before. Then it worked fine
Please close this issue.

Thanks and Regards
Manoj