Cables

From GnokiiWiki

Jump to: navigation, search

Contents

Serial

All serial cables that are marked with DAU-9(P) or DLR-3(P) or DAU-05 should be supported. If there are any problems (not related with hardware failure) please let us know.

DKU-5 and CA-42

USB IDLinux kernel driverStatusComments
0x067b:0x2303pl2303works
0x078b:0x1234pl2303works
0x6547:0x0232ark3116works This chip found in DKU-5 and KQ-U8A datacable with same serial number: WT048000317. For more info see http://avr.auctionant.de/ark3116_linux_driver/ (as of 2.6.17 included in the official Linux kernel). http://www.qbik.ch/usb/devices/showdev.php?id=3705
0x6547:0x1234ark3116works
0x07d0:0x4101cypress_m8worksensure your kernel version has these ids in the module sources. http://www.qbik.ch/usb/devices/showdev.php?id=3565
0x10b5:0xac70cp2101worksensure your kernel version has these ids in the module sources. http://www.qbik.ch/usb/devices/showdev.php?id=3618
0x0451:0x3410ti_usb_3410_5052worksensure your kernel version has these ids in the module sources
0x0ea0:0x6858oti6858worksYou need to use patched Linux kernel.

For Linux 2.6.18 use http://home.elka.pw.edu.pl/~tlukasze/linux-2.6.18-oti6858.patch For Linux 2.6.20 use http://ta.twi.tudelft.nl/ftp/dv/lemmens/linux-2.6.20.3-oti6858.patch http://www.qbik.ch/usb/devices/showdev.php?id=3628

0x0421:0x0800nonedoesn't workgenuine DKU-5 cable
0x0421:0x0802usbserial + cdc_acmprobably workshttp://www.qbik.ch/usb/devices/showdev.php?id=3251

The CA-42 runs the standard usb-to-serial protocol (usbcdc). Thus the usbserial driver can be used. Before plugging the cable use the insmod to bind the usbserial driver to the cable: insmod usbserial vendor=0x0421 product=0x0802. As soon as you plug in the cable a /dev/ttyACMX node should be created.

In case when ids are not in the module sources, you need to add them and recompile the module (no need to recompile whole kernel).

The CA-42 Clone cable from http://www.ca42.com uses the Prolific PL2303 Driver. Since 2.6.16 the Linux kernel correctly supports this device:

  • CONFIG_USB_SERIAL=m
  • CONFIG_USB_SERIAL_PL2303=m

Once this is taken care of, gnokii will be able to use /dev/ttyUSB0 as a serial port.

DKU-2, CA-53 and CA-70

DKU-2 cables are not seen by libusb unless there's a phone attached. I'm not an USB expert but that probably means that all communication, transformation logic is done by the phone, the cable is the silly transmitter (ie. the cable is not usb-to-serial converter).

CA-53 cable is a replacement for DKU-2. I haven't seen a single model yet, but I suspect they are compatible with DKU-2. CA-70 is even newer replacement.

DKU-2 (and probably CA-53) cables are supported by gnokii userspace driver using libusb (works on Linux and partially on FreeBSD). There is also kernel driver nokia_dku2 provided in gnokii sources, but it turned out not to be reliable and hard to maintain (due to large number of the mobile phones). Writing it correctly seemed to be too much work so the driver got deprecated. See also more detailed DKU-2 information.

DKE-2

DKE-2 cables are just adapters from USB to mini-USB, with a male USB A and a mini-USB B connector.

They are handled by the cdc_acm kernel module which creates a /dev/ttyACM* device file compatible only with gnokii AT driver so you might get more functionality via a FBUS connection over Bluetooth.

Note that phones like Nokia 5300 may work only when connected to USB 2.0 ports.

  • config: Linux (Ubuntu Hairy: 2.6.24-16-generic), DKE-2 cable using Linux kernel driver for cdc_acm
model = AT
port = /dev/ttyACM0
connection = serial

Resources

You'll find the USB compatibility table at Nokia site.

Personal tools