Usb rs232 драйвер linux

FTDI FT232RL драйвер для windows 7-10 / Linux / MacOS

Как правило, платы Arduino имеют встроенный USB-TTL преобразователь, позволяющий без труда подключить Arduino к компьютеру для загрузки прошивки. Оригинальные Arduino, как правило, используют для этих целей программатор FTDI от Шотландской компании FTDI Chip и в стандартных сборках Windows этот драйвер поставляется вместе с ОС.

Драйверы доступны под огромное количество различных ОС:

• Windows
• Linux
• Mac OS X
• Windows CE 6.0/7.0
• Windows CE 2013

Единственная ОС, которая требует определенных модификация для подключения драйвера FTDI программатора – Android.

Для Windows самой стабильной версией является 2.08.14

Как установить драйвер FTDI на компьютер?

Установка драйвера FTDI FT232RL для Windows производится в несколько простых шагов:

1. Скачиваем драйвера по ссылкам выше
2. Распаковываем архив с установочными файлами
3. Открываем диспетчер устройств
4. В диспетчере устройств выбираем неизвестное устройство, кликаем правой кнопкой мыши, в появившемся окне выбираем пункт обновить драйвер
5. В появившемся окне выбираем пункт “Выполнить поиск драйверов на этом компьютере”
6. Если нужно, то указываем путь к файлам, которые мы извлекли из архива ранее
7. Перезагружаем компьютер для корректного обновления данных в реестре

После установки драйвера заново подключаем контроллер и смотрим, чтобы плата корректно отобразилась в списке диспетчера устройств.

Источник

USB serial¶

Introduction¶

The USB serial driver currently supports a number of different USB to serial converter products, as well as some devices that use a serial interface from userspace to talk to the device.

See the individual product section below for specific information about the different devices.

Configuration¶

Currently the driver can handle up to 256 different serial interfaces at one time.

The major number that the driver uses is 188 so to use the driver, create the following nodes:

When the device is connected and recognized by the driver, the driver will print to the system log, which node(s) the device has been bound to.

Specific Devices Supported¶

ConnectTech WhiteHEAT 4 port converter¶

ConnectTech has been very forthcoming with information about their device, including providing a unit to test with.

The driver is officially supported by Connect Tech Inc. http://www.connecttech.com

For any questions or problems with this driver, please contact Connect Tech’s Support Department at support @ connecttech . com

HandSpring Visor, Palm USB, and Clié USB driver¶

This driver works with all HandSpring USB, Palm USB, and Sony CliГ© USB devices.

Only when the device tries to connect to the host, will the device show up to the host as a valid USB device. When this happens, the device is properly enumerated, assigned a port, and then communication _should_ be possible. The driver cleans up properly when the device is removed, or the connection is canceled on the device.

This means that in order to talk to the device, the sync button must be pressed BEFORE trying to get any program to communicate to the device. This goes against the current documentation for pilot-xfer and other packages, but is the only way that it will work due to the hardware in the device.

When the device is connected, try talking to it on the second port (this is usually /dev/ttyUSB1 if you do not have any other usb-serial devices in the system.) The system log should tell you which port is the port to use for the HotSync transfer. The “Generic” port can be used for other device communication, such as a PPP link.

For some Sony CliГ© devices, /dev/ttyUSB0 must be used to talk to the device. This is true for all OS version 3.5 devices, and most devices that have had a flash upgrade to a newer version of the OS. See the kernel system log for information on which is the correct port to use.

If after pressing the sync button, nothing shows up in the system log, try resetting the device, first a hot reset, and then a cold reset if necessary. Some devices need this before they can talk to the USB port properly.

Devices that are not compiled into the kernel can be specified with module parameters. e.g. modprobe visor vendor=0x54c product=0x66

There is a webpage and mailing lists for this portion of the driver at: http://sourceforge.net/projects/usbvisor/

For any questions or problems with this driver, please contact Greg Kroah-Hartman at greg @ kroah . com

PocketPC PDA Driver¶

This driver can be used to connect to Compaq iPAQ, HP Jornada, Casio EM500 and other PDAs running Windows CE 3.0 or PocketPC 2002 using a USB cable/cradle. Most devices supported by ActiveSync are supported out of the box. For others, please use module parameters to specify the product and vendor id. e.g. modprobe ipaq vendor=0x3f0 product=0x1125

The driver presents a serial interface (usually on /dev/ttyUSB0) over which one may run ppp and establish a TCP/IP link to the PDA. Once this is done, you can transfer files, backup, download email etc. The most significant advantage of using USB is speed — I can get 73 to 113 kbytes/sec for download/upload to my iPAQ.

This driver is only one of a set of components required to utilize the USB connection. Please visit http://synce.sourceforge.net which contains the necessary packages and a simple step-by-step howto.

Once connected, you can use Win CE programs like ftpView, Pocket Outlook from the PDA and xcerdisp, synce utilities from the Linux side.

To use Pocket IE, follow the instructions given at http://www.tekguru.co.uk/EM500/usbtonet.htm to achieve the same thing on Win98. Omit the proxy server part; Linux is quite capable of forwarding packets unlike Win98. Another modification is required at least for the iPAQ — disable autosync by going to the Start/Settings/Connections menu and unchecking the “Automatically synchronize …” box. Go to Start/Programs/Connections, connect the cable and select “usbdial” (or whatever you named your new USB connection). You should finally wind up with a “Connected to usbdial” window with status shown as connected. Now start up PIE and browse away.

If it doesn’t work for some reason, load both the usbserial and ipaq module with the module parameter “debug” set to 1 and examine the system log. You can also try soft-resetting your PDA before attempting a connection.

Other functionality may be possible depending on your PDA. According to Wes Cilldhaire @ hotmail . com>, with the Toshiba E570, …if you boot into the bootloader (hold down the power when hitting the reset button, continuing to hold onto the power until the bootloader screen is displayed), then put it in the cradle with the ipaq driver loaded, open a terminal on /dev/ttyUSB0, it gives you a “USB Reflash” terminal, which can be used to flash the ROM, as well as the microP code.. so much for needing Toshiba’s $350 serial cable for flashing!! 😀 NOTE: This has NOT been tested. Use at your own risk.

Keyspan PDA Serial Adapter¶

Single port DB-9 serial adapter, pushed as a PDA adapter for iMacs (mostly sold in Macintosh catalogs, comes in a translucent white/green dongle). Fairly simple device. Firmware is homebrew. This driver also works for the Xircom/Entrega single port serial adapter.

basic input/output (tested with ‘cu’)

blocking write when serial line can’t keep up

changing baud rates (up to 115200)

getting/setting modem control pins (TIOCM)

sending break (although duration looks suspect)

device strings (as logged by kernel) have trailing binary garbage

device ID isn’t right, might collide with other Keyspan products

changing baud rates ought to flush tx/rx to avoid mangled half characters

parity, 7 vs 8 bits per char, 1 or 2 stop bits

HW flow control

not all of the standard USB descriptors are handled: Get_Status, Set_Feature, O_NONBLOCK, select()

For any questions or problems with this driver, please contact Brian Warner at warner @ lothar . com

Keyspan USA-series Serial Adapters¶

Single, Dual and Quad port adapters — driver uses Keyspan supplied firmware and is being developed with their support.

The USA-18X, USA-28X, USA-19, USA-19W and USA-49W are supported and have been pretty thoroughly tested at various baud rates with 8-N-1 character settings. Other character lengths and parity setups are presently untested.

The USA-28 isn’t yet supported though doing so should be pretty straightforward. Contact the maintainer if you require this functionality.

More information is available at:

For any questions or problems with this driver, please contact Hugh Blemings at hugh @ misc . nu

FTDI Single Port Serial Driver¶

This is a single port DB-25 serial adapter.

Devices supported include:

TripNav TN-200 USB GPS

Navis Engineering Bureau CH-4711 USB GPS

For any questions or problems with this driver, please contact Bill Ryder.

ZyXEL omni.net lcd plus ISDN TA¶

This is an ISDN TA. Please report both successes and troubles to azummo @ towertech . it

Cypress M8 CY4601 Family Serial Driver¶

This driver was in most part developed by Neil “koyama” Whelchel. It has been improved since that previous form to support dynamic serial line settings and improved line handling. The driver is for the most part stable and has been tested on an smp machine. (dual p2)

Chipsets supported under CY4601 family:

CY7C63723, CY7C63742, CY7C63743, CY7C64013

DeLorme’s USB Earthmate GPS (SiRF Star II lp arch)

Cypress HID->COM RS232 adapter

Cypress Semiconductor claims no affiliation with the hid->com device.

Most devices using chipsets under the CY4601 family should work with the driver. As long as they stay true to the CY4601 usbserial specification.

The Earthmate starts out at 4800 8N1 by default… the driver will upon start init to this setting. usbserial core provides the rest of the termios settings, along with some custom termios so that the output is in proper format and parsable.

The device can be put into sirf mode by issuing NMEA command:

As far as I can tell it supports pretty much every sirf command as documented online available with firmware 2.31, with some unknown message ids.

The hid->com adapter can run at a maximum baud of 115200bps. Please note that the device has trouble or is incapable of raising line voltage properly. It will be fine with null modem links, as long as you do not try to link two together without hacking the adapter to set the line high.

The driver is smp safe. Performance with the driver is rather low when using it for transferring files. This is being worked on, but I would be willing to accept patches. An urb queue or packet buffer would likely fit the bill here.

If you have any questions, problems, patches, feature requests, etc. you can contact me here via email:

(your problems/patches can alternately be submitted to usb-devel)

Источник

USB-Serial Port adapter (RS-232) in Ubuntu Linux

There are two other articles on a serial port adapter for Windows. Below is the instructions for Linux and how to connect your serial adapter while using Linux. This should work for most people using Linux and a serial adapter or usb to rs232 driver which is being discussed.

USB to RS 232 driver Linux

1. Log into Linux under the root account;

2. Plug the USB-Serial adapter into the computer;

3. Give it a minute to discover the USB-Serial adpater;

4. Type in this command dmesg

5. The dmesg command will echo back the most recent few lines of the system message console, and you should see something like this:

• usb 2.0: new full speed USB device using uhci and address 2
• usb 2.0: configuration #1 chosen from 1 choice

6. Unplug the USB-Serial adapter to see a list of USB devices without it being plugged in.

7. Type this command to list the USB devices: lsusb

8. You should see a list of USB devices that looks like this:

• Bus 001 Device 001: ID 0000:0000
• Bus 002 Device 007: ID 03f0:4f11 Hewlett-Packard
• Bus 002 Device 006: ID 05e3:1205 Genesys Logic, Inc. Afilias Optical Mouse H3003
• Bus 002 Device 004: ID 15d9:0a33 Logitec-mouse

9. Then plug the USB into our device Then use the lsusb command again and observe the changes

• Bus 001 Device 001: ID 0000:0000
• Bus 002 Device 007: ID 03f0:4f11 Hewlett-Packard
• Bus 002 Device 003: ID 018a:3754 Unknown device
• Bus 002 Device 006: ID 05e3:1205 Genesys Logic, Inc. Afilias Optical Mouse H3003
• Bus 002 Device 004: ID 15d9:0a33 Logitec-mouse

10. Determine the vendor ID and the product ID by inspecting this additional line. In this example they are 018a and 3754. For a Trip•Lite USB-Serial adapter, they are 2303 and 067B. In this example it is a Minicom USB-Serial device. The first numbers identifies the vendor and the second numbers identifies the product.

11. Now use the following command to load the kernel module called usb serial and pass the vendor and product ID values to it. The driver can then associate itself with the correct hardware device on the USB bus.

• sudo modprobe usbserial vendor=018a product=3754

12. Now c heck whether the new Serial Port device is available

• sudo dmesg | grep ttyUSB

13. You should now see something like this

• usbserial_generic 1-1:1.0: generic converter detected
• usb 1-1: generic converter now attached to ttyUSB0
• usbcore: registered new interface driver usbserial_generic

14. This tells you that the serial device has now been mapped to the /dev/ttyUSBO serial port

15. Now we want to list the devices under the /dev/ path to see if the interface is visible with this command:

18. Instruct Ubuntu to load this module automatically by including the following line in the /etc/modules file. Substitute your own vendor and product ID if they are different.

• usbserial vendor=018a product=3754

That should be about it however if you have not installed the driver then you would have to install it now. If you are installing a Minicom serial device then you would do the following:

• sudo apt-get install minicom
• sudo minicom -s

Press A and then edit to / dev / ttyUSB 0 ( this value, see dmesg | grep ttyUSB )

Press E and then edit to 9600 8N1

Press F and the value will change from Yes to No

Once set up and finish off mode serial port setup.

Save setup as df1 finished off. Settings by Exit from Minicom

Other Issues:

This is for Ubuntu Linux for Red Hat the drivers should be in your OS however TrippLite does have Red Hat drivers on their website if you do not have them on your system.

If you are trying to connect a Zigbee through this serial port you can do the following:

Make a symbolic link between ttyUSB0 and com2 by typing in terminal: (assuming you are using com2)

• ln -s /dev/ttyUSB0 /home/your_home/.wine/dosdevices/com2

Источник