Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

  • State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 13209 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

USB driver fails to install on Windows XP sp3

Wayne S
Intellectual 365 points
Other Parts Discussed in Thread: MSP430F5528

I cannot get the USB Virtual Com port to install. I'm attempting to use the USB on MSP430F5528 as virtual com port using the MSP-TS430RGC64USB and receive the following error when installing the generated .inf file:

"A Service installation section in this INF is invalid"

Same error occurs with I try to use the example .inf files.

The same .inf installed just fine on Win 7 and other computers.

Someone suggested deleting USB keys with vid_2047 from the registry (HKLM\CurrentControlSet\Enum\USB, which I have, possibly from an older install, but regedit will not let me delete the keys - Cannot delete Vid_2047&Pid_0300: Error while deleting key.

Same error when I try to delete Vid_2047&Pid_03ef - the one I generated from my .inf file. I tried rebooting, not connecting anything, and going straight to regedit.

Is there an uninstall procedure for these .inf files? These files generated with Descriptor tool 3.0.1.0.


[TIUSB.nt]
include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=TIUSB.nt.AddReg

[TIUSB.nt.AddReg]
HKR,,NTMPDriver,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"
HKR,,PortSubClass,1,01

[TIUSB.nt.Services]
AddService=usbser, 0x00000002, DriverService

[TIUSB.nt.HW]
include=mdmcpq.inf

[DriverService]
DisplayName=%DESCRIPTION%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\usbser.sys
LoadOrderGroup=Base

  • 0
    Intellectual 365 points

    I was able to change the permissions on the registry keys and delete them. However I still get the error

    "A Service installation section in this INF is invalid"

    at the end of the install.

    Wayne

  • 0 in reply to Wayne S
    Intellectual 365 points

    The setupapi.log from the install says the following:

    #-035 Processing service Add/Delete section [TIUSB.NT.Services].
    #E339 Add Service: Binary "C:\WINDOWS\system32\DRIVERS\usbser.sys" for service "usbser" is not present.
    #E032 Error 0xe0000217: A service installation section in this INF is invalid.
    #E275 Error while installing services. Error 0xe0000217: A service installation section in this INF is invalid.
    #E122 Device install failed. Error 0xe0000217: A service installation section in this INF is invalid.
    #E154 Class installer failed. Error 0xe0000217: A service installation section in this INF is invalid.
    #I060 Set selected driver.
    #I125 Installing NULL driver for "USB\VID_2047&PID_031F\B33D8A4620000600".
    #I121 Device install of "USB\VID_2047&PID_031F\B33D8A4620000600" finished successfully.

    The usbser.sys file is located in the ...\system32\dllcache\ folder, but not in the ...\system32\drivers\ folder.

    So I copied the file over from dllcache to the drivers directory, and the install works.

    Wayne

  • 0 in reply to Wayne S
    Genius 4680 points

    > So I copied the file (usbser.sys) over from dllcache to the drivers directory, and the install works.

    After all, this is the certain method in many cases of CDC installation trouble. :-)

    I'm not sure, why the INF file doesn't copy usbser.sys to the right place.

    [TIUSB.nt]
    include=mdmcpq.inf
    CopyFiles=FakeModemCopyFileSection

    This part on the INF should do the copy job...
    Driver archive may be lost on your PC. Driver archive is often included in C:\I386 directory. The directory name and location may be changed depending on PC manufacturers.


    > Someone suggested deleting USB keys with vid_2047 from the registry (HKLM\CurrentControlSet\Enum\USB, which I have, possibly from an older install,

    It isn't a recommended method.
    Virtual COM port (VCP) device instance relates to many registry entries, not just one you've deleted. In this topic, registry entries of VCP for SiLabs CP210x is discussed. Device instance of usbser.sys also the same set of registry entries.
    http://www.cygnal.org/ubb/Forum9/HTML/001680.html

    Instead, use a utility like USBDeview
    http://www.nirsoft.net/utils/usb_devices_view.html

    USBDeview lists up all registered USB devices, regardless of current connection. Find the target device of VID/PID on the list, right-click on the line, and choose "uninstall"

    OR

    There is a hack for Device Manager, to display all devices.

    1) Copy these two lines to a blank text file, and rename the file to DevManager.bat

    set devmgr_show_nonpresent_devices=1
    start devmgmt.msc

    2) Double click on DevManager.bat (or choose "run as admin" on right-click menu for Vista and later). Device Manager comes up.

    3) On 'View' menu of Device Manager, select 'Show hidden devices'

    Now you can see all device instance on the registry, regardless of the current connection.

    Tsuneo

  • 0 in reply to Tsuneo Chinzei
    Prodigy 10 points

    Spent a few hours on this problem, found a solution. Snagged a different copy of usbser.sys and threw it in (windows dir)/system32/drivers. Installed just fine. Major headache.

**Attention** This is a public forum