1. Configure Virtual Serial Port Driver Registration Code Download
2. Configure Virtual Serial Port Driver Registration Code For Windows 7

Jul 12, 2021 Launch Virtual Serial Port Driver if it is not running yet. Select Help → Activate from the Main Menu. In the invoked window, enter the activation code you’ve received from us: Click the Activate button to finish the activation process. Serial Port Driver PRO is an efficient all-in-one solution that will help you create multiple se.

-->

This topic describes the device-specific registry entries.

Find device information after it enumerates on Windows

E) Click on the 'Port Settings' tab. Click the 'Advanced' button. F) Click on “COM Port Number.” g) Pull down the scrollbar and select “COM1.” h) Click “OK.” If there is no COM port or Other Device showing in Device Manager you need to enable the serial/COM port in the laptop BIOS, assuming the laptop has a COM port. Once the USB Virtual COM port driver is installed and recognized, here is an example of how to achieve serial communication with our instruments: To request a load reading from our instruments via the serial port, first set the baud rate in the software to match the instrument’s baud rate, and open the port.

View the device interface GUID, Hardware Id, and device class information about your device

1. Outdoor kitchen design software mac. Find this registry key and note the DeviceInstance value:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlDeviceClasses

2. Find the device instance registry key and get the device interface GUID:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB<hardware id><instance id>Device Parameters

3. Under the device instance key, note the device class, subclass, and protocol codes:

   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB

Registry settings for configuring USB driver stack behavior

The registry entries described in this topic are found under this key:

In the vvvvpppprrrrr key,

• vvvv is a 4-digit hexadecimal number that identifies the vendor
• pppp is a 4-digit hexadecimal number that identifies the product
• rrrr is a 4-digit hexadecimal number that contains the revision number of the device.

The vendor ID, product ID, and revision number values are obtained from the USB device descriptor.The following table describes the possible registry entries for the vvvvpppprrrrr key. The USB driver stack considers these entries as read-only values.

Registry entry	Description	Possible values
osvc REG_BINARY Supported on Windows XP and later versions.	Indicates whether the operating system queried the device for Microsoft-Defined USB Descriptors. If the previously-attempted OS descriptor query was successful, the value contains the vendor code from the OS string descriptor.	0x0000: The device did not provide a valid response to the Microsoft OS string descriptor request. 0x01xx: The device provided a valid response to the Microsoft OS string descriptor request, where xx is the bVendorCode contained in the response. Hitman 3.
IgnoreHWSerNum REG_BINARY Supported on Windows Vista and later versions.	Indicates whether the USB driver stack must ignore the serial number of the device.	0x00: The setting is disabled. 0x01: Forces the USB driver stack to ignore the serial number of the device. Therefore, the device instance is tied to the port to which the device is attached.
ResetOnResume REG_BINARY Supported on Windows Vista and later versions.	Indicates whether the USB driver stack must reset the device when the port resumes from a sleep cycle.	0x0000: The setting is disabled. 0x0001: Forces the USB driver stack to reset a device on port resume.

Related topics

The Communication Device Class (CDC) is used for implementing virtual communication ports. This example demonstrates a bridge between a Virtual COM Port on the USB Host Computer and an UART port on the evaluation board.

The following picture shows an exemplary connection of the development board and the USB Host Computer.

The Abstract.txt file contained in the Documentation group of the Project window gives you more information on the general setup and the available I/O on the development board.

Open the example project in MDK. The µVision Project window should display a similar project structure:

Source Files

• VirtualCOM.c contains the main C function that initializes the board hardware and the USB Device Component. Furthermore, it contains the code that exchanges the data internally between the USB and the UART port.
• The USBD_User_CDC_0.c is an adapted code template that implements all necessary file access functions. Refer to CDC: Communication Device Class (ACM) for details about these template functions.

If you are using RTOS other than CMSIS-RTOS2 RTX5 for your project please make sure to satisfy USB Device Resource Requirements.

You may now build and download the example project to the evaluation board using the µVision commands:

• Project –> Build target (F7)
• Flash –> Download (F8)

Configure Virtual Serial Port Driver Registration Code Download

After these steps, the project should start executing on your evaluation kit. In case of errors, refer to the Evaluation Board User's Guide for configuration information.

Hardware Setup

Configure Virtual Serial Port Driver Registration Code For Windows 7

The setup of the Evaluation Board hardware is described in the Abstract.txt file.

• Verify all jumper settings on the target hardware.
• Connect the UART on the development board to your PC (you might need an USB to serial RS232 adapter). Use an USB cable to connect your development board to the Host PC and power up your board.
• The Welcome to the Found New Hardware Wizard appears. Installation of the driver is described in detail in the Abstract.txt file.

PC Software

The USB Device Virtual COM example can be tested on a Windows PC using a terminal emulation program. Since Hyperterminal in not part of Windows any more, please download an appropriate program for this purpose (such as PuTTY for example). Open the two COM ports 'COMx' and 'COMy'. Any data from 'COMx' will be echoed on 'COMy' and visa versa:

About Host PC driver for Microsoft Windows

The example folder contains two files relevant for driver installation on the Microsoft Windows:

• Driver setup information file (xxx-vcom.inf) which is used to create a digitally signed driver catalog file (xxx-vcom.cat)
• Digitally signed driver catalog file (xxx-vcom.cat)

The driver files are provided as an example, the driver setup information file should be adapted and digitally signed driver catalog file should be created from adapted driver setup information file.

Driver setup information file should be adapted in the following way:

• c251 in Vendor ID VID_c251 entries should be changed to the vendor ID number assigned to your company by the USB organization (c251 Vendor ID is reserved for Keil Software and should not be used)
• xxxx in Product ID PID_xxxx entries should be changed to the product ID as assigned by your company
• in [DeviceList.xxx] sections, entries not relevant for the device, should be removed or added as described below:
  • if device is pure CDC class device (not composite) then all entries ending with &MI_xx should be removed
  • if device is a composite device with one or more CDC class instances then entries not ending with &MI_xx should be removed and entries ending with &MI_xx should exist for each CDC class instance (example driver contains entries ending with &MI_00 and &MI_02 which are used for composite device containing two CDC class instances and each instance uses 2 interfaces where MI_00 describes first CDC instance and MI_02 entry describes second CDC instance)
• [Strings] section should be changed as desired

Note

Vendor ID and Product ID are configured in the USBD_Config_n.c configuration file of the embedded application.

For producing digitally signed driver catalog file please refer to Microsoft Windows documentation.