Cypress semiconductor usb to serial linux driver

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 Low-Full-High Speed Peripherals

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

» means nesting-related): — Failed at: #assign isEmailVerified = liql(«selec. [in template «custom.add.roles» at line 4, column 1] —- —>

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

linux driver for (ID 0665:5161) Cypress Semiconductor USB to Serial

i am using a power inverter with an integrated Cypress Semiconductor USB to Serial interface thats found as an HID device in Rasbian/ Linux. I am gettig crasy here and didnt found any solution how to mapp to a tyyusb or ARm or what ever .

I think i need an driver who mapping the device first to a serial port.

All i can see is:

Bus 001 Device 004 : ID 0665:5161 Cypress Semiconductor USB to Serial

2.034918] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:06:0f:13

[ 2.129262] usb 1-1.2: new low-speed USB device number 4 using dwc_otg

[ 2.297863] usb 1-1.2: New USB device found, idVendor=0665, idProduct=5161

[ 2.297884] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0

[ 2.312837] hid-generic 0003: 0665:5161 .0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.2/input0

I hope there is an linux driver or any how to do avaible to get this usb device on running

Источник

USB Low-Full-High Speed Peripherals

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

» means nesting-related): — Failed at: #assign isEmailVerified = liql(«selec. [in template «custom.add.roles» at line 4, column 1] —- —>

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

linux driver for (ID 0665:5161) Cypress Semiconductor USB to Serial

i am using a power inverter with an integrated Cypress Semiconductor USB to Serial interface thats found as an HID device in Rasbian/ Linux. I am gettig crasy here and didnt found any solution how to mapp to a tyyusb or ARm or what ever .

I think i need an driver who mapping the device first to a serial port.

All i can see is:

Bus 001 Device 004 : ID 0665:5161 Cypress Semiconductor USB to Serial

2.034918] smsc95xx 1-1.1:1.0 eth0: register ‘smsc95xx’ at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:06:0f:13

[ 2.129262] usb 1-1.2: new low-speed USB device number 4 using dwc_otg

[ 2.297863] usb 1-1.2: New USB device found, idVendor=0665, idProduct=5161

[ 2.297884] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=0

[ 2.312837] hid-generic 0003: 0665:5161 .0001: hiddev0,hidraw0: USB HID v1.11 Device [HID 0665:5161] on usb-3f980000.usb-1.2/input0

I hope there is an linux driver or any how to do avaible to get this usb device on running

Источник

Public Archive

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

» means nesting-related): — Failed at: #assign isEmailVerified = liql(«selec. [in template «custom.add.roles» at line 4, column 1] —- —>

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Email to a Friend
• Report Inappropriate Content

Communicating with Cypress USB to Serial chip on Linux

I am trying to establish a communication and read data from an Inverter device which uses Cypress USB to Serial chip. The ‘lsusb’ command reports that the device has vendorID 0665, and productID 5161, with description «Cypress Semiconductor USB to Serial». And the device appears on a Linux machine as ‘/dev/usb/hiddev0’. Unfortunately I am having difficulty with establishing the communication with this device.

I am hoping get some help in figuring out how to communicate with this device:

• Is there any existing device-driver/library that I can use to establish communication with this device?
• Am I supposed to directly use low-level USB messages to communicate with the device? If yes, can I get some references/examples of how this can be done?

So far, I have tried to communicate with this device as usb-serial but it hasn’t worked. I have tried following so far:

• I have tried to directly connect to the device using serial communication tools (e.g., picocom) but I get ‘Fildes not a tty’.
• I have tried to modify existing kernel driver for usb-serial communication (cp210x.ko) to support 0665:5161 vendor/product-ID, but this lead to ‘input/output error’ when connecting to the device.
• I have also tried using ‘cypress_m8.ko’ kernel module from CYPRESS by editing to support 0665:5161 vendor/product-ID, but that lead to kernel-panic!
• I have experimented with ‘CyUSBSerialTestUtility’ from CyUSBSerial_SDK_Linux from CYPRESS to see if it detects anything, but it does not detect any device.

Any suggestions/tips on to help in establishing communication with this device will be helpful!

Источник