From: gcombs <gc...@gm...> - 2007-01-11 18:33:25
|
I recently picked up a mini-itx case from Mini-Box.com (aka iTuner). It's got a USBLCD 20x2 in it. iTuner supplies what looks like an old version of usblcd command line app. It works fine, but I'd definitely like to get lcd4linux running on it. My first attempt was just to enable the USBLCD driver ... however when scanning for usblcd devices, the driver complained that it couldn't find any. In examining drv_USBLCD.c, I notice the vendor and product id's don't match. Here's what the /proc/bus/usb/devices said: T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=04d8 ProdID=0002 Rev= 0.01 S: Manufacturer=ITUNER INC S: Product=USB-LCD-20x2 S: SerialNumber=1.57rel. C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 2 Cls=03(HID ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=03(Int.) MxPS= 24 Ivl=1ms E: Ad=01(O) Atr=03(Int.) MxPS= 24 Ivl=10ms So in drv_USBLCD.c, I add the vender (0x04d8) and the product ID (0x0002), recompile and run with -Fvv It looks like it's running, in that lcd4linux doesn't complain about anything, however there's no change in the actual LCD. Am I just using the wrong driver or what? Greg |
From: Michael R. <re...@eu...> - 2007-01-11 19:45:29
|
Hi Greg, > In examining drv_USBLCD.c, I notice the vendor and product id's don't match. > P: Vendor=04d8 ProdID=0002 Rev= 0.01 > S: Manufacturer=ITUNER INC > S: Product=USB-LCD-20x2 Well, I think this is *not* the USBLCD from Adams IT Services. Robin used two different Vendor ID's, the old (inoffical) 0x10D2 and the new (official) 0x1212 (maybe I swapped these two). The problem may be that "USBLCD" is a very misleading name, everyone who designs such a beast will call it USBLCD, regardless of being compatible to whatever. Can you get a datasheet or something? From my experience, it should be easy to write a new (or adopt an existing) driver... HTH, Michael -- Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |
From: gcombs <gc...@gm...> - 2007-01-12 16:44:53
|
I've found some rudimentary SDK instructions: http://resources.mini-box.com/online/picoLCD%2020x2%20(OEM)/Documentation/libusblcd-development-guide.txt >From which I've been able to get a driver up and running in basic form. Unfortunately there doesn't seem to be anything (obvious) that would allow user defined characters on the fly. They offer the capacity to install up to 10 custom characters via a text file, but they don't tell you how to use those characters once installed. This results in no icons and no bar segments ... well, there are bar segments, but it's all garbage characters (even flipping the ascii255bug on and off). Here's the SDK download: http://resources.mini-box.com/online/picoLCD%2020x2%20(OEM)/Software/Linux/SDKSource/usblcd-src-0.1.4.tgz For what it's worth, after talking to Nico Pavel (the developer at ituner.com), it seems like they, too, are working on a lcd4linux driver but it may not be released for a little while yet. g On 1/11/07, Michael Reinelt <re...@eu...> wrote: > Hi Greg, > > > In examining drv_USBLCD.c, I notice the vendor and product id's don't match. > > > P: Vendor=04d8 ProdID=0002 Rev= 0.01 > > S: Manufacturer=ITUNER INC > > S: Product=USB-LCD-20x2 > > Well, I think this is *not* the USBLCD from Adams IT Services. Robin > used two different Vendor ID's, the old (inoffical) 0x10D2 and the new > (official) 0x1212 (maybe I swapped these two). > > The problem may be that "USBLCD" is a very misleading name, everyone who > designs such a beast will call it USBLCD, regardless of being compatible > to whatever. > > Can you get a datasheet or something? From my experience, it should be > easy to write a new (or adopt an existing) driver... > > > HTH, Michael > > -- > Michael Reinelt <re...@eu...> > http://home.pages.at/reinelt > GPG-Key 0xDF13BA50 > ICQ #288386781 > |
From: Michael R. <re...@eu...> - 2007-01-12 20:06:44
|
Hi Greg, > From which I've been able to get a driver up and running in basic > form. =20 How did you implement the driver? Did you use the SDK, or did you use direct libusb calls? > Unfortunately there doesn't seem to be anything (obvious) that > would allow user defined characters on the fly. They offer the > capacity to install up to 10 custom characters via a text file, but > they don't tell you how to use those characters once installed. I did a quick glance over the SDK sources, and I'=C4ve seen all the stuff I'd need. And it looks quite simple. The protocol they use is similar to stuff I've done already. I suppose the display itself is a standard HD44780, and they just built an interface around it... > This results in no icons and no bar segments ... well, there are bar > segments, but it's all garbage characters (even flipping the > ascii255bug on and off). Not havind bars and icons would be a Bad Thing (TM) :-) > For what it's worth, after talking to Nico Pavel (the developer at > ituner.com), it seems like they, too, are working on a lcd4linux > driver but it may not be released for a little while yet. As I said, writing a driver should be easy. But writing it "blind" (without a display to test) may be complicated. As I really like the cute pictures of the display, I'm thinking about ordering one. But shipping and customs may be expensive to Austria.... (maybe they want to donate a "development sample"? :-) bye, Michael --=20 Michael Reinelt <re...@eu...> http://home.pages.at/reinelt GPG-Key 0xDF13BA50 ICQ #288386781 |