Garmin Support Center is where you will find answers to frequently asked questions and resources to help with all of your Garmin products. Welcome to the Hitex Download Page. This area contains evaluation versions of Hitex tools and other free tools, data and information for getting your products to. On Windows 10, a device driver is an essential piece of code, which allows the system to interact with a specific hardware (such as graphics card, storage driver, network adapter, Bluetooth, etc. Code 19 means there is a driver conflict such as two devices trying to use the same resources. Do these to clear corruption and repair/replace damaged/missing system files. Run DiskCleanup - Start - All Programs - Accessories - System Tools - Disk Cleanup.
-->
Versions supported
- Windows 10
- Windows 8.1
Applies to
- Device manufacturers of CDC Control devices
Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
In Windows 10, the driver has been rewritten by using the Kernel-Mode Driver Framework that improves the overall stability of the driver.
- Improved PnP and power management by the driver (such as, handling surprise removal).
- Added power management features such as USB Selective Suspend.
In addition, UWP applications can now use the APIs provided by the new Windows.Devices.SerialCommunication namespace that allow apps to talk to these devices.
Usbser.sys installation
Load the Microsoft-provided in-box driver (Usbser.sys) for your Communications and CDC Control device.
Note
If you trying to install a USB device class driver included in Windows, you do not need to download the driver. They are installed automatically. If they are not installed automatically, contact the device manufacturer. For the list of USB device class driver included in Windows, see USB device class drivers included in Windows.
Windows 10
In Windows 10, a new INF, Usbser.inf, has been added to %Systemroot%Inf that loads Usbser.sys as the function device object (FDO) in the device stack. If your device belongs to the Communications and CDC Control device class, Usbser.sys is loaded automatically.You do not need to write your own INF to reference the driver. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows.
USBClass_02
USBClass_02&SubClass_02
- If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. With this approach, you are not required to distribute INF files for your device because the system uses Usbser.inf.
- If your device specifies class code 02 but a subclass code value other than 02, Usbser.sys does not load automatically. Pnp Manager tries to find a driver. If a suitable driver is not found, the device might not have a driver loaded. In this case, you might have to load your own driver or write an INF that references another in-box driver.
- If your device specifies class and subclass codes to 02, and you want to load another driver instead of Usbser.sys, you have to write an INF that specifies the hardware ID of the device and the driver to install. For examples, look through the INF files included with sample drivers and find devices similar to your device. For information about INF sections, see Overview of INF Files.
Note
Microsoft encourages you to use in-box drivers whenever possible. On mobile editions of Windows, such as Windows 10 Mobile, only drivers that are part of the operating system are loaded. Unlike desktop editions, it is not possible to load a driver through an external driver package. With the new in-box INF, Usbser.sys is automatically loaded if a USB-to-serial device is detected on the mobile device.
Windows 8.1 and earlier versions
In Windows 8.1 and earlier versions of the operating system, Usbser.sys is not automatically loaded when a USB-to-serial device is attached to a computer. To load the driver, you need to write an INF that references the modem INF (mdmcpq.inf) by using the Include directive. The directive is required for instantiating the service, copying inbox binaries, and registering a device interface GUID that applications require to find the device and talk to it. That INF specifies 'Usbser' as a lower filter driver in a device stack.
The INF also needs to specify the device setup class as Modem to use mdmcpq.inf. Under the [Version] section of the INF, specify the Modem and the device class GUID. for details, see System-Supplied Device Setup Classes.
For more information, see this KB article.
Configure selective suspend for Usbser.sys
Starting in Windows 10, Usbser.sys supports USB Selective Suspend. It allows the attached USB-to-serial device to enter a low power state when not in use, while the system remains in the S0 state. When communication with the device resumes, the device can leave the Suspend state and resume Working state. The feature is disabled by default and can be enabled and configured by setting the IdleUsbSelectiveSuspendPolicy entry under this registry key:
To configure power management features of Usbser.sys, you can set IdleUsbSelectiveSuspendPolicy to:
'0x00000001': Enters selective suspend when idle, that is, when there are no active data transfers to or from the device.
'0x00000000': Enters selective suspend only when there are no open handles to the device.
That entry can be added in one of two ways:
Write an INF that references the install INF and add the registry entry in the HW.AddReg section.
Describe the registry entry in an extended properties OS feature descriptor. Add a custom property section that sets the bPropertyName field to a Unicode string, 'IdleUsbSelectiveSuspendPolicy' and wPropertyNameLength to 62 bytes. Set the bPropertyData field to '0x00000001' or '0x00000000'. The property values are stored as little-endian 32-bit integers.
For more information, see Microsoft OS Descriptors.
Develop Windows applications for a USB CDC device
If you install Usbser.sys for the USB CDC device, here are the application programming model options:
Starting in Windows 10, a Windows app can send requests to Usbser.sys by using the Windows.Devices.SerialCommunication namespace. It defines Windows Runtime classes that can use to communicate with a USB CDC device through a serial port or some abstraction of a serial port. The classes provide functionality to discover such serial device, read and write data, and control serial-specific properties for flow control, such as setting baud rate, signal states.
In Windows 8.1 and earlier versions, you can write a Windows desktop application that opens a virtual COM port and communicates with the device. For more information, see:
Win32 programming model:
.NET framework programming model:
Related topics
Available MCAL driver packages :
Basic AUTOSAR package MC-ISAR:
- MCU (Microcontroller Unit) driver: provides services for basic microcontroller initialization, power down functionality, reset and microcontroller specific functions
- WDG (Watchdog) driver: provides services for initialization, changing the operation mode and triggering the watchdog
- GPT (General Purpose Timer) driver: uses the hardware timer channels of the general-purpose timer unit
- SPI handler/driver: provides services for reading from and writing to devices connected via SPI busses (e.g. EEPROM, Watchdog, I/O ASICs).
- PORT driver: provides the service for initializing the whole PORT structure of the microcontroller. The DIO driver works on pins and ports which are configured by the PORT driver.
- DIO driver: provides services for reading and writing to/from DIO channels (pins), DIO ports, DIO channel groups
- ICU (Input Capture Unit) driver: for demodulation of a PWM signal, counting pulses, measuring of frequency and duty cycle, generating simple interrupts and also wakeup interrupts
- PWM (Pulse Width Modulation) driver: generates pulses with variable pulse width. It allows the selection of the duty cycle and the signal period time.
- ADC (Analogue Digital Converter) driver: provides services to start and stop a conversion respectively to enable and disable the trigger source for a conversion.
MC-ISAR COM package:
- CAN driver: provides services for CAN transmissions
- CanTrcv CAN transceiver driver: provides services to control the transceiver hardware which detects electrical malfunctions, supports power supply control and wake up via the bus.
- LIN driver: applies to LIN 2.0 master nodes
Hitex Port Devices Driver
MC-ISAR MEM package:
- FLASH driver: provides services for reading, writing and erasing flash memory and handling write / erase protection
- FEE driver: provides services for the Flash EEPROM Emulation
In addition to standardized modules AUTOSAR provides the possibility of complex driver for non-standardized hardware module. To efficiently exploit the hardware MCAL Complex Drivers are an essential component for hardware abstraction.
MC-ISAR MCAL CD (MCAL Complex Driver) package:
Hitex Port Devices Driver Booster
- UART driver: provides services for handling the UART communication
- MEMCeck driver: handles the CRC module
- FADC (Fast Analogue Digital Converter) driver: provides services for the Fast ADC module
- Additional driver for non standardized modules are available