|
Problem
Dual rs232-hs - Descarga de controladores para su sistema Windows desde un sitio web verificado. Relacionado Controladores Dual rs232-hs dt-5002a dt01aca100-driver dt4-d1534 dtc-aal03 dtc550-driver dtech-driver dtech-utv332-driver dtp-600w dts-audio-driver-windows-7 dts-sound-driver-download dts-sound-driver-for-hp-pavilion dts-sound-driver.
Both the HiFive1 and the Arty boards use FTDI to access the JTAG interface.
If I connect the board to my macOS 10.12, with the default FTDI drivers installed in the system, I automatically get two 'Dual RS232-HS' interfaces: Product ID: 0x6010 Vendor ID: 0x0403 (Future Technology Devices International Limited) Version: 7.00 Speed: Up to 12 Mb/sec Manufacturer: FTDI Location ID: 0xfd122300 / 4 Current Available (mA. The USB-232A-1 is a port-powered, bi-directional USB to RS232 adapter / converter that can be used to convert any standard USB port (USB 2.0 - backward compatible) into two RS232C ports and vice versa. This high-quality, high-performance USB to dual RS232 adapter uses the latest FTDI chipset and is. Adds 4 RS232 serial COM ports without system conflict with IRQ and DMA. Set the created oboard virtual machine and choose the FTDI Quad RS232-HS 0800 USB device. It can t find a device with VID0403&PID6010 named Dual RS232-HS. The RS232 HS in length and DMA. USB to serial drivers for most serial RS232 devices. Unfortunately I do not have the same kit as you, therefore I can only give some tips. I am unsure what you mean by Dual RS232-HS drivers but, if the development kit you have is similar to this one, it contains a XDS100 emulator that is in fact a dual USB-RS232 FTDI device.The device drivers for this emulator are automatically installed with CCSv5.x and newer.
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.
Dual Rs232-hs Driver Downloads
TODO: explain how to use openocd rules file.
Dual Rs232-hs Driver Reviews
Last modified on Mon Jun 4 19:50:15 2018 UTC.