help - how to get /dev/usb/hiddevx

Hi,

I've just got a mini usb LED message board (tenner from Maplins) and was hoping to be able to control it from my AAO [standard Linpus].

http://www.maplin.co.uk/module.aspx?moduleno=227123

The company that make the message board (Dream Cheeky - yes really) have released details of the protocol and someone has written a linux program to communicate with it.

The protocol is described here ..

http://www.dreamcheeky.com/dream/forum/ ... e.php?id=8

the linux program is here ..

http://www.last-outpost.com/~malakai/dcled/index.html

The program expects to find the device in /dev/usb/hiddevx

Does anyone know how to get this kind of device path under LINPUS on the AAO ????

I guess that some kind of USB 'scanner' is required to recognise USB devices that have been plugged in. [There must already be something in the kernel as a USB mouse is detected]

Thanks,

Simon.

 

Use the commands

lsusb

and

dmesg

before and after plugging it in ( in a terminal: use alt-F2 ).
Post what seems relevant.

--Japser.

 

Hi,

First off lsusb reports an additional entry as follows :-

Bus 002 Device 003: ID 1d34:0013

The verbose output from lusb for this device gives :

[user@localhost ~]$ lsusb -d 1d34:0013 -v

Bus 002 Device 004: ID 1d34:0013
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x1d34
idProduct 0x0013
bcdDevice 0.01
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 16
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10

Which looks just as it should be based upon the notes with the linux driver program (that needs the /dev/usb/hiddev)

The dmesg output (I may have complicated things by plugging in/removing/plugging in again) gives ..

usb 2-1: new low speed USB device using uhci_hcd and address 3
usb 2-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
hiddev96: USB HID v1.10 Device [Dream Link USB LED Message Board v1.0] on usb-00
00:00:1d.0-1
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
drivers/hid/usbhid/hid-core.c: input irq status -75 received
usb 2-1: USB disconnect, address 3
usb 2-1: new low speed USB device using uhci_hcd and address 4
usb 2-1: configuration #1 chosen from 1 choice
hiddev96: USB HID v1.10 Device [Dream Link USB LED Message Board v1.0] on usb-00
00:00:1d.0-1
drivers/hid/usbhid/hid-core.c: input irq status -75 received
drivers/hid/usbhid/hid-core.c: input irq status -75 received


So it looks as though quite a few good things in the right direction are happening.

In fact I've just noticed that a 'hiddev0' appearing/disappearing in the /dev directory - I wonder if that's equivalent to the /dev/usb/hiddevx under Ubuntu?

Will try the program with this as a path and report what happens.

Thank,

Simon

 

Problem solved!!!!

Rather than /dev/usb/hiddev0 the message board actually appears as /dev/hiddev0

I guess other USB might go the same way on the AAO

The dinky message board works great on the AAO !

Simon