This is a convenient dual port USB to serial adapter; it features two high-speed serial RS232 ports which, once the drivers are installed, both will show up in your operating system's Device Manager as a two virtual COM ports each with its own COM port number, which can be used as if. USB to Serial RS485 and RS422: Part no. Description: Processor: Files: Size: US485MIO: USB to RS485 Mini: SilLabs CP2102: Drivers / Datasheets.zip: 11.5MB: MWE820A. Corrupted By Dual Rs232 Hs Winusb: Usb Devices: Initio ASUS External Slim Drive: Up To Date and Functioning: Hewlett-Packard Officejet 7000 E809a (DOT4USB) Corrupted By Dual Rs232 Hs Winusb: Hewlett-Packard HP Deskjet 6980 Series (DOT4USB) Corrupted By Dual Rs232 Hs Winusb: Sound Cards And Media Devices: NVIDIA NVIDIA GeForce GTX 550 Ti: Up To. C: AdvanceBox Turbo Flasher Driver RemoveATFDrivers RemoveATFDrive rs.bat 3. Download FTDI Driver from official FTDI Website (this is for your Dual RS232-HS Problem).

Problem

Both the HiFive1 and the Arty boards use FTDI to access the JTAG interface.

By default, the standard FTDI drivers available on Windows and macOS assume the FTDI chip is used to connect UART ports via USB.

The FTDI chip can be reconfigured to access the JTAG interface via direct drivers, but this requires the presence of a small EEPROM to store the configuration, and neither board has this EEPROM physically installed.

On the HiFive1 board the problem is complicated by the fact that the second FTDI interface is used to forward the trace stream and must remain a virtual UART.

Except on GNU/Linux, where direct access to USB devices is native, for Windows and macOS there is no elegant solution to this problem, but only some work-arounds.

Windows

Windows allows a port to be acceed via the user-space WinUSB driver only after explicitly reconfiguring a specific interface for direct drivers.

This requires installing a special driver, specifically configured for a given VID:PID.

One possible solution is libusbk, which also comes with a tool to generate these drivers. As with usual drivers, this generated driver can be installed and uninstalled, if no longer needed.

An older workaround used a tool called Zadig, but this tool had the major disadvantage that changes were permanent, and it was not possible to return the FTDI device to the default UART.

TODO: provide the driver binaries.

macOS

When dealing with USB drivers, Apple is even stricter; if the USB device has any of the FTDI VID:PID pairs, macOS assumes it should be associated with a virtual UART device, and there is no simple way to reconfigure this.

To view the attached USB devices on macOS, use system_profiler. For example, the HiFive1 board is seen as Dual RS232-HS, PID:VID 6010:0403:

If you already use FTDI based USB/UART adapters, remember the Product ID, since you need to manually enable it in a later step.

By default, macOS identifies the board as a Dual RS232-HS device, and offers to configure it as a network interface. Since the HiFive1 board does not have an EEPROM to store an unique ID, the devices are named using a string containing the address in the HUB hierarchy, so the a13 letters in the name are different when connecting the board to a different USB port.

Attempts to open the trace port (the second UART) are ok:

Use Ctrl-A Ctrl-K to kill the session, or Ctrl-A Ctrl-D to detach and screen -r to reconnect.

Attempts to open the HiFive1 board with OpenOCD fail with:

The workaround it to disable all personalities of the AppleUSBFTDI kernel:

This command will remove the UART associations for all FTDI based devices. All devices will be available for user space drivers, like libusb.

In the HiFive1 case, the first interface should no longer be available as a tty device, but as JTAG, and OpenOCD should be able to connect to the JTAG interface:

This next command will redo the UART association only for the given personality, in this case the second interface of PID 0x6010 (AppleUSBEFTDI-6010-1).

The second interface should be available again to screen, as before.

If you have other FTDI devices that you need to remain associated to UART, issue similar commands, for each one.

The AppleUSBFTDI module has many personalities; to bring them back, start kextutil in interractive mode, or reboot:

Use case

I personaly have two USB/UART DB-9 adapters and the RISC-V HiFive1 and Arty boards.

To make them work, I use a file

that I start with:

GNU/Linux

GNU/Linux systems do not need suplimentary drivers to access the FTDI devices, but only some configuration tweaks.

TODO: explain how to use openocd rules file.

Last modified on Mon Jun 4 19:50:15 2018 UTC.

Windows 7 64-bit & 32-bit, Windows Vista 64-bit & 32-bit, Windows XP, Windows 2000, Windows Me, Windows 98

Important note regarding Windows 7 and Vista:
The driver MUST be installed 'as Administrator'
Right-click the downloaded EXE file and choose Run as administrator

Dual Rs232 Hs Driver

Download the Windows installer for the USB RS-232 adaptor:
Download for Windows 7/Vista/XP (32-bit)
Download for Windows 7/Vista (32-bit and 64-bit)

If for some reason the above driver does not work, try one of the following:
Download for Windows 7/Vista/XP (32-bit and 64-bit - Alternate driver)
Download for Windows XP, 2000, 98/ME (32-bit only)

For older cables (purchased prior to October, 2010):
Download for Windows 7/Vista/XP (32-bit and 64-bit)
Download for Windows Vista (32-bit only)

Run the installer, then after rebooting, plug the USB end of the adapter into one of the USB ports on the computer.

NOTE: For Windows 7, please use RC build 7100 or RTM Final version. (Installer program will not run on early Windows 7 or Beta versions)

Check the software driver installation

1) Open the Device Manager dialog from Control Panel

• Windows Vista: Start >> Control Panel >> System >> Hardware >> Device Manager
• Windows XP: Start >> Control Panel >> System >> Hardware >> Device Manager
• Windows 2000: Start >> Settings >> Control Panel >> System >> Hardware >> Device Manager
• Windows 98/ME: Start >> Settings >> Control Panel >> System >> Device Manager
  

2) Click the plus sign (+) next to 'Ports'.

3) If the device is properly installed, 'Serialio.com USB Serial Port' or 'Prolific USB-to-Serial COM Port' will be displayed.

The software driver is properly installed, but the USB-RS232 adaptor does not work as expected

One of the common reasons that software may not work as expected with a USB-Serial adaptor when the devcie is properly installed, is many older programs (and even some new ones) only support a limited number of COM ports (e.g. only COM1 - COM4)

If the USB-RS232 adapter is installed as COM5, it may need to be reassigned to COM1 - COM4 to work with some software.

The following outlines how to to reassign the COM port on Windows XP/2K/Me/98SE

Windows XP

1) Follow steps 1-3 of 'Check the software driver installation'above.

2) Right-click on the 'Prolific USB to Serial Port', then click Properties

3) Click on the 'Port Settings' tab. Click the 'Advanced' button.

4) In the 'COM Port Number' drop-down select the desired port number. For example if the software requires COM2, select COM2. Note the COM port must have '(in use)' listed next to it, if it does then another device with that name is already installed in the system. After selecting the desire port number, click 'OK.'

5) Click 'OK' again, and the device will show up as being on the same COM port that it was before (i.e., COM5), but should show up on the selected port name when the Device Manager dialog is closed and opened again.

6) Close the Device Manager. Launch the software to use with the new COM port.

Dual Rs232-hs Driver Windows 7

Windows 2000, Me, and 98 SE (Second Edition)

1) Follow steps 1 2 of 'Check the software driver installation'above.

2) Right-click on the 'Prolific USB to Serial Port', then click Properties.

3) Click on the 'Port Settings' tab. Click the 'Advanced' button.

4) Uncheck 'Use automatic settings'.

5) Select 'Input/Output range'. Click on 'Change Settings'.

6) Type '02E8-02EF' in the Value box. This value will change the port to COM 4. If COM 4 is in use, you must choose another port. The values for each port are.

• COM 1: 03F8-03FF
• COM 2: 02F8-02FF
• COM 3: 03E8-03EF
• COM 4: 02E8-02EF

7) Enter the value, then click OK. Click OK again, then click Yes when the 'Creating a Forced Configuration' window appears. Click OK.

8) Restart the computer. The Device Manager can be checked, to see the COM port change.

Note: Adaptor may not be exactly as pictured above.
back