Help - Search - Members - Calendar
Full Version: C3000 Usb Serial
OESF Forums > Distros, Development, and Model Specific Forums > Model Specific Forums > C1000/3x00 General discussions
Bombur
Hi,

I am trying to use a usb-serial converter and minicom to administer via the serial console on my Solaris boxen.

Has anybody done this? The 5500 was much simpler in that you could use /dev/ttyS0.

I don't see anything under /dev/usb for serial nor do I see an appropriate driver under /lib/moduels/2.4.20

If anyone has some pointers, I would greatly appreciate it!


J.
Bombur
ok, I am assuming that no-one else has tried this yet. (minicom and usb-serial converter). I have found that there are no usb-serial drivers. Normally, I should be able to see usb serial drivers like mct_u232 or pl2303 but I don't see any on the 3k. So that means I have to compile my own. I have done it on my pc but not on my new 3k.

I guess the first thing to ask: is there an accepted build environment for the 3k or is everyone kind of just muddling along with zcc and some other odds and ends?

Any comments would be most helpful.

J.
DreamTheater
Hi Bombur,

I am also curious about USB serial, especially pl2303, but I haven't set up build environment ready yet. And for your build environment quiestion, yes I think so. SHARP already uploaded C3000 version of gcc etc.

- C3000 Kernel Source Code location
http://developer.ezaurus.com/sl_j/source/c...rom1_01.tar.bz2

- C3000 Build Procedure page (in Japanese)
http://developer.ezaurus.com/sl_j/source/c..._101J_c3000.htm

- gcc
http://developer.ezaurus.com/sl_j/tool/too...95.2-0.i386.rpm

- glibc
http://developer.ezaurus.com/sl_j/tool/too....2.2-0.i386.rpm

- headers
http://developer.ezaurus.com/sl_j/tool/too....4.6-3.i386.rpm

I just downloaded them, but haven't looked into detail yet. Maybe some of makefiles tell us what the exact module name is.

BTW, the reason why I am curious about this is because I want to let my GPS-360 (Microsoft Street & Trip version) working, where somehow Microsoft version has different Product ID than original Pharos one. The following one line change in /usr/src/linux/drivers/usb/serial/pl2303.h should does the job. Bombur, could you build that for me please???

CODE
// #define PL2303_PRODUCT_ID 0x2303
#define PL2303_PRODUCT_ID 0xaaa0


and here is what I got by lsusb -v command.
CODE
Bus 001 Device 005: ID 067b:aaa0 Prolific Technology, Inc.
Device Descriptor:
 bLength                18
 bDescriptorType         1
 bcdUSB               1.10
 bDeviceClass            0 Interface
 bDeviceSubClass         0
 bDeviceProtocol         0
 bMaxPacketSize0        64
 idVendor           0x067b Prolific Technology, Inc.
 idProduct          0xaaa0
 bcdDevice            3.00
 iManufacturer           1
 iProduct                2
 iSerial                 3
 bNumConfigurations      1
 Configuration Descriptor:
   bLength                 9
   bDescriptorType         2
   wTotalLength           39
   bNumInterfaces          1
   bConfigurationValue     1
   iConfiguration          0
   bmAttributes         0x80
   MaxPower              100mA
   Interface Descriptor:
     bLength                 9
     bDescriptorType         4
     bInterfaceNumber        0
     bAlternateSetting       0
     bNumEndpoints           3
     bInterfaceClass       255 Vendor Specific Class
     bInterfaceSubClass      0
     bInterfaceProtocol      0
     iInterface              0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x81  EP 1 IN
       bmAttributes            3
         Transfer Type            Interrupt
         Synch Type               none
       wMaxPacketSize         10
       bInterval               1
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x02  EP 2 OUT
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               none
       wMaxPacketSize         64
       bInterval               0
     Endpoint Descriptor:
       bLength                 7
       bDescriptorType         5
       bEndpointAddress     0x83  EP 3 IN
       bmAttributes            2
         Transfer Type            Bulk
         Synch Type               none
       wMaxPacketSize         64
       bInterval               0
 Language IDs: (length=4)
    0409 English(US)
Jonathan
Maybe this will help some people who want a quick fix for USB<>SERIAL adaptor cables (and other USB serial devices) on the C3000.

Yesterday I set up the cross compiler on my x86 linux box and compiled the USB serial modules for SL-C3000 from the kernel source on Sharp's website.

I've posted the compiled drivers in the following directory with some rough instructions on installing them:

http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/

I needed to do this to use some Prolific PL2303 and PL2303x based USB<>RS232 converter cables. After installing these drivers all adaptors work well. Note that I needed to find a replacement for pl2303.c to add support for the PL2303X chip, but the standard PL2303 driver is also there in the source (that particular problem was a pain in the ****).

I also had some problem with hotplugging and had to add a line to /etc/hotplug/usb.rc to remove the pl2303 module from memory when the machine goes into standby. On looking at this file again I see that the line was already there, so I don't know if it was just the updated pl2303x driver that solved that problem. dry.gif I don't think anyone will have this problem with these drivers. Mind you, I'm no expert rolleyes.gif

Oh yes, and I use minicom pointing to /dev/ttyUSB0. To make minicom start quickly it helps to disable the modem init string (use 'minicom -o') and hangup strings (delete strings in minicom modem setup screen.)

Hope this helps someone.

Jonathan

[these files may move some time in the future (months rather than days)]
Jonathan
DreamTheater,

I compiled a special pl2303.o for you using your aaa0 id (only took a minute). It should be uploaded with this message. I see that your lsusb command gives the following line:

bMaxPacketSize0 64

From my recent experience this value indicates a pl2303x device and so you need the updated pl2303 driver that I use. A bMaxPacketSize0 value of 8 indicates a pl2303 device, I believe. Your device is unlikely to work properly with the standard pl2303 driver - but I might be wrong.

Rename this file (pl2303_DT.o) to pl2303.o and use in place of the one in my archive. Maybe it will work...

Best of luck.

Jonathan.
DreamTheater
Thank you so much Jonathan!!!

I am also in process of setting up my own x86 Linux box for such use, but I will try your module first.
DreamTheater
it works!!!!

I installed Jonathan provided modules into my C3000 by following included instructions.
When I plugged in Pharos(Microsoft product id) GPS-360 via USB, lsmod shows that drivers are automatically loaded. Then, I started qpeGPS to see if it really works.
- I had to execute qpeGPS as root.
- I set serial device to ttyUSB0 that I got from dmesg result.

and then, it works! Thank you god. Thank you Jonathan. It looks this device can be powered by C3000 USB bus power.
There is one issue I noticed that when I unplugged the USB cable from C3000, then C3000 hangs up. This is probably because gpsd kept running even if qpeGPS was closed. So, I tried killall gpsd before unplugging the cable, then no hang. This is probably a future enhancement point of this driver, if it can successfully catch hot-plug event and unloading the driver or by something else.

Although, I brushed out in the picture below, qpeGPS showed correct Latitude and Longitude of my location. I am impressed.
Jonathan
Great!

Now perhaps you can help me with this little quirk...

I can't get the /dev/ttyUSB0 device to hold its read/write permissions. That is, as root I can change its permission to allow user and group writing...

# chmod 666 /dev/ttyUSB0
# ls -al /dev/ttyUSB0
crw-rw-rw- 1 root root 188, 0 Oct 28 03:24 /dev/ttyUSB0

but when I reboot, the device gets reset to :

crw-r--r-- 1 root root 188, 0 Oct 28 03:24 /dev/ttyUSB0

This happens whether or not the usbserial drivers are loaded at the time of the chmod command.

In other words the Z is automatically resetting the permissions on reboot. Grrr mad.gif

As a rule I don't like doing things as root unless I absolutely need to, so I'd rather the ttyUSB0 device stayed write-able for everyone after reboot.

Could you try changing permissions on /dev/ttyUSB0 and then rebooting?
Something like 'chmod 666 /dev/ttyUSB0' would do it. Not sure if it's just me.

I have a nasty feeling this is build into the ROM and not a config file feature. I've tried searching for this 'feature' across the whole filesystem but come up blank. The only other mention of /dev/ttyUSB0 is in the usbserial module sources.

Many thanks,

Jonathan.
Jonathan
Got around it for now by putting the chmod command in /etc/rc.local and making sure that script gets executed at boot time, as in the following page...

http://www.zaurususergroup.com/modules.php...=Server%20Setup

Still, not a very elegant solution.

Jonathan.
(mind going a bit dull at 2am ph34r.gif )
Bombur
Thanks Jonathan,

I hadn't had a chance to do this yet as I am in Mexico on vacation. Only one internet connection in the whole hotel! and no Wifi...argh.

I will give it a try when I get back next week.

J.
DreamTheater
Jonathan,

I was playing around with srial driver further and I found a way to hook hotplug/unplug events. Put the following scripts and chmod 755 them.
/etc/hotplug/usb/pl2303
CODE
#!/bin/sh
. /etc/hotplug/hotplug.functions
if [ ! -L /var/run/usb/%proc%bus%usb%* ]; then
 # echo $PRODUCT > /home/zaurus/product.txt

 # Pharos(Microsoft) GPS-360
 if [ $PRODUCT = "67b/aaa0/300" ]; then
   ln -s /etc/hotplug/usb/usb-gps.off $REMOVER
   mesg make REMOVER in $REMOVER
   chmod 666 /dev/ttyUSB0
   mesg make serial port available to usr
 fi

 # put your if...fi clause here
 # ...
 # ...
fi

/etc/hotplug/usb/usb-gps.off
CODE
#!/bin/sh
. /etc/hotplug/hotplug.functions
mesg kill gps processes
#killall qpegps
killall gpsd

# these may not be necessary
rmmod pl2303
rmmod usbserial



Here is how those scripts work.
C3000 USB agent calls 'module nama' script in /etc/hotplug/usb if it exists. So, in this case, /etc/hotplug/usb/pl2303
There may be multiple devices you want to use that are all rely on pl2303 module, so I look at PRODUCT environment variable to do device specific hot-plug/hot-unplug actions. PRODUCT environment variable contains VenderId, ProductId and bcdDevice, but better to make sure by uncomment the 'echo' line to see what the exact string is. In the 2nd if clause, I also register REMOVER program which is invoked at unplugging event. C3000 kernel will create symbolic link to this REMOVER iunder /var/run/usb, so make sure if your REMOVER is successfully registered by looking at that path.

In my GPS case, simply 'chmod 666 /dev/ttyUSB0' allowed me to run qpegps/gpsd as usr level, and also C3000 doesn't hang up at cable unplug even if gpsd is running. So, rc.local method was good enough for my own purpose. Still, if qpegps is running at cable unplug time, C3000 hangs. I will figure out more graceful and perfect way.

Hope this helps.
Jonathan
DreamTheater,

I just got round to using your scripts. They worked fine, and your explanation is very clear. Many thanks.

A word to anyone trying to program in C on the Zaurus with these pl2303 USB<>SERIAL devices - don't do it!

I've just spent quite some time getting these devices to replicate what my x86 linux box does with a normal hardware serial port. I have to communicate with a number of small robots and down(up?)load eeprom data. It's not just a case of copying and compiling a C file. Clarification finally came in the form of Perry Harrington's simple terminal program for Zaurus: (http://www.dainst.com/info/programs/terminal/)

Now time to get that GPS dongle...

Jonathan
Bombur
Jonathan,

thank you for the pl2303 driver. I used my Serial-IO USB to Serial cable for the first time to administer a Sun 280R server without a hitch. I tried both minicom and tipterm (terminal) successfully.

Cheers!

J.
gjarboni
Just to let everyone know, the alternate solution is to use the serial cable for the SL-C5500 (et al). I can confirm that this works with the SL-C3000 (the serial port is /dev/ttyS0). But the version of minicom I have leaves garbage characters all over the screen. Is there a link to a better version?

Thanks,

Jason M.
Jonathan
Well that is good news.

But, er, um, I`m not sure what cable you are talking about. Can you give a URL for it?

I was, and still am, under the impression that the only way to get serial IO on the C3000 is either via the USB host or via a dedicated CF card.

I was sure the "hidden" port connector of the C3000 doesn`t do serial, but I`d love to be corrected.

Jonathan
gjarboni
QUOTE(Jonathan @ Jan 29 2005, 09:46 AM)
Well that is good news.

But, er, um, I`m not sure what cable you are talking about.  Can you give a URL for it? 

I was, and still am, under the impression that the only way to get serial IO on the C3000 is either via the USB host or via a dedicated CF card. 

I was sure the "hidden" port connector of the C3000 doesn`t do serial, but I`d love to be corrected.

Jonathan
*


No problem, just click here for a link to the cable (on Amazon). It's the CE-170TS, the serial cable for the 5500 & 6000 (and also the C700,750, etc.). I successfully connected to a Cisco router and a SBC (Single Board Computer) and was able to enter commands, etc.

Now here's the strange thing. There are three, count them, three serial ports that show up in dmesg. The first one is the one for the serial cable above & the second says it's IrDA. But what about the third?
Jonathan
Aha! So it _is_ connected to the hidden sharp IO port then?

Does that mean you removed the "don`t remove me" cover to the hidden IO port and just plugged it in? Just want to be sure before I do something to my Z that I really shouldn`t do...

Not sure about the ports showing up in dmesg, but I do recall other kernel modules doing similar things. Maybe the controller chip is dual port but there is only one port connector. That way the two ports show up in dmesg but only one is physically accessible.

Thanks,

Jonathan.
zaurian
I want to use SL-C3000 to send command to RS-232 port of a controller device.
I need confirmation that this port can do RS-232 communication.
gjarboni
QUOTE(Jonathan @ Jan 29 2005, 05:58 PM)
Aha! So it _is_ connected to the hidden sharp IO port then?

Does that mean you removed the "don`t remove me" cover to the hidden IO port and just plugged it in?  Just want to be sure before I do something to my Z that I really shouldn`t do...

Not sure about the ports showing up in dmesg, but I do recall other kernel modules doing similar things.  Maybe the controller chip is dual port but there is only one port connector.  That way the two ports show up in dmesg but only one is physically accessible.

Thanks,

Jonathan.
*


Yep, all I did was remove the cover and plug in the cable. I remember reading on the web that the USB cable wouldn't work (no surprise there -- I'm sure the pins got routed to the mini-AB port), but that they hadn't checked the serial cable.
Jonathan
QUOTE
Yep, all I did was remove the cover and plug in the cable. I remember reading on the web that the USB cable wouldn't work (no surprise there -- I'm sure the pins got routed to the mini-AB port), but that they hadn't checked the serial cable.


Great! Thanks for clearing that up. I read exactly the same thing and assumed the serial was also crippled.

Now how do you take off the little plug/cover without breaking it or scratching the pretty finish of the C3000?

I wonder if removing the plug voids the warranty?

I`d prefer using the built-in serial to using a USB serial port adaptor which has crippled drivers.

Cheers,

Jonathan
gjarboni
QUOTE(Jonathan @ Jan 30 2005, 02:59 AM)
QUOTE
Yep, all I did was remove the cover and plug in the cable. I remember reading on the web that the USB cable wouldn't work (no surprise there -- I'm sure the pins got routed to the mini-AB port), but that they hadn't checked the serial cable.


Great! Thanks for clearing that up. I read exactly the same thing and assumed the serial was also crippled.

Now how do you take off the little plug/cover without breaking it or scratching the pretty finish of the C3000?

I wonder if removing the plug voids the warranty?

I`d prefer using the built-in serial to using a USB serial port adaptor which has crippled drivers.

Cheers,

Jonathan
*



The cover comes off with a fingernail and reattaches just as easily. IMHO, it's not really designed to keep you from using the port, it's just there to make the case look cleaner.

By the way, do you have a working serial terminal program for the C3000? My copy of minicom can't draw any ascii boxes (for the dialogs) and leaves the screen looking a mess. If you have a better version, could you please let me know where you got it?

Thanks,

Jason M.
Bombur
QUOTE(gjarboni @ Jan 30 2005, 07:32 AM)
QUOTE(Jonathan @ Jan 30 2005, 02:59 AM)
QUOTE
Yep, all I did was remove the cover and plug in the cable. I remember reading on the web that the USB cable wouldn't work (no surprise there -- I'm sure the pins got routed to the mini-AB port), but that they hadn't checked the serial cable.


Great! Thanks for clearing that up. I read exactly the same thing and assumed the serial was also crippled.

Now how do you take off the little plug/cover without breaking it or scratching the pretty finish of the C3000?

I wonder if removing the plug voids the warranty?

I`d prefer using the built-in serial to using a USB serial port adaptor which has crippled drivers.

Cheers,

Jonathan
*



The cover comes off with a fingernail and reattaches just as easily. IMHO, it's not really designed to keep you from using the port, it's just there to make the case look cleaner.

By the way, do you have a working serial terminal program for the C3000? My copy of minicom can't draw any ascii boxes (for the dialogs) and leaves the screen looking a mess. If you have a better version, could you please let me know where you got it?

Thanks,

Jason M.
*



Jason,

have you used tipterm? It is like Solaris tip command.

J.
gjarboni
QUOTE(Bombur @ Jan 30 2005, 12:22 PM)
Jason,

have you used tipterm?  It is like Solaris tip command.

J.
*

Nope I haven't used tipterm, but I've heard good things about it. Thanks for uploading!
jpmatrix
Jonathan,

does your driver work with ALL usb-to-serial cable ?


QUOTE(Jonathan @ Jan 13 2005, 11:17 AM)
...
Rename this file (pl2303_DT.o) to pl2303.o and use in place of the one in my archive.  Maybe it will work...

Best of luck.

Jonathan.
*
Jonathan
Nope, the pl2303 drivers work for pl2303 (and pl2303x) devices only.

But I did compile all the other serial drivers in the kernel source at the same time and they should be included in this file:

usb-serial (zip)
or
usb-serial (tgz)

Give them a try. Instructions included in these archives.

(Note that pl2303_DT.o is a special driver for a pl2303 device with aaa0 id. It was compiled for DreamTheater and you're unlikely to need it.)

Jonathan.


QUOTE(jpmatrix @ Apr 25 2005, 08:25 PM)
Jonathan,

does your driver work with ALL usb-to-serial cable ?


QUOTE(Jonathan @ Jan 13 2005, 11:17 AM)
...
Rename this file (pl2303_DT.o) to pl2303.o and use in place of the one in my archive.  Maybe it will work...

Best of luck.

Jonathan.
*

*

jpmatrix
oh i've just discovered that pc-mobile.net does sell an usb-serial cable with the pl2303 chipset ! so i think i'll buy this cable as i now know it does work with the Zaurus smile.gif

http://www.pc-mobile.net/usb2s.htm
datajerk
I have to ask, why any did not use BT-serial? A drawback with BT-serial is that you need to power it, but you can build a USB power cable for your adapter and power it from your Z.
madeddie
good question. in fact, i've used the Aircable zaurus bluetooth adapter

it works perfectly with the SL-C3K, i want to power the serial side of it with a battery pack though, because most routers don't have a ps/2 or usb port to get power from

i use it to dial-in with GPRS using my nokia 6310i, the bluetooth connectivity is a bit flakey (i developed a healthy hate towards nokia for this), but once the 2 bluetooth devices sync and connect I can sent AT commands and set up a PPP connection over GPRS

--
edwin
jpmatrix
great!
I've just bought the MCL Samar USB-110 usb serial adapter, installed Jonathan's drivers and ....... it WORKS !!!!!
pl2303 is detected and driver is loaded smile.gif
tomorrow i'll try my garmin serial gps !

thanks again all

Z is beautiful smile.gif
jpmatrix
QUOTE(jpmatrix @ Jul 26 2005, 11:27 PM)
...
tomorrow i'll try my garmin serial gps !



success!!!
i just had to chmod 666 /dev/ttyUSB0 , launch qpeGPS and my Garmin GEKO (switched to NMEA 4800) was discovered comme un charme :-)

thanks again !
Raybot
QUOTE(Jonathan @ Apr 27 2005, 11:08 AM)
Nope, the pl2303 drivers work for pl2303 (and pl2303x) devices only. 

But I did compile all the other serial drivers in the kernel source at the same time and they should be included in this file:
*


I can quite happily confirm that the driver works beautifully with the FTDI FT232BL chip :-)

Thanks heaps Jonathan!


- Raymond

P.S. I assume you had to fight your way through the "configure" process somehow (and if so, how did you do it in the crosscompile environment)? Or was there an easier way for you to get all this working?
Jonathan
QUOTE(Raybot @ Oct 13 2005, 11:12 AM)
P.S. I assume you had to fight your way through the "configure" process somehow (and if so, how did you do it in the crosscompile environment)? Or was there an easier way for you to get all this working?
*


As I recall I just did the usual "make config" (or maybe it "make menuconfig") but made sure I used the correct example config file (for the Spitz I think.) That was, of course after a successful run of "./configure".

That way you set the options for video4linux (which I see you also need...) and everything else before the final make.

Best of luck with your robot project - keep us posted. I got my C3000 to compile JAL programs and then program the Microchip PIC series of microprocessors in my robot cars through a USB<>serial cable. It then interacts with the operating robot cars through the same interface - no vision though sad.gif

Jonathan
Raybot
QUOTE(Jonathan @ Oct 14 2005, 02:47 PM)
QUOTE(Raybot @ Oct 13 2005, 11:12 AM)
P.S. I assume you had to fight your way through the "configure" process somehow (and if so, how did you do it in the crosscompile environment)? Or was there an easier way for you to get all this working?
*


As I recall I just did the usual "make config" (or maybe it "make menuconfig") but made sure I used the correct example config file (for the Spitz I think.) That was, of course after a successful run of "./configure".
*



Did you run that on your desktop (in a crosscompile environment) or was this all working off the Zaurus? I guess the problem is I'm not familiar with crosscompilation, I'm not sure where one would start setting this up so obvious things, like configure configuring for the desktop (and not the Zaurus) won't be a problem (let alone less obvious things like making sure the Zaurus versions of all the relevant files are used and not the desktop's) ... maybe I'm looking in the wrong place but there doesn't seem to be much docs that I can find on setting up a desktop crosscompile environment for "systems'y" stuff (rather than console/QT/X11 applications).

QUOTE(Jonathan @ Oct 14 2005, 02:47 PM)
That way you set the options for video4linux (which I see you also need...) and everything else before the final make.
*


Of course, my other hope was to be able to do this all with the Sharp ROM (and load what I need as modules) ... not possible seems to be the consensus?

QUOTE(Jonathan @ Oct 14 2005, 02:47 PM)
Best of luck with your robot project - keep us posted.  I got my C3000  to compile JAL programs and then program the Microchip PIC series of microprocessors in my robot cars through a USB<>serial cable.  It then interacts with the operating robot cars through the same interface - no vision though sad.gif

Jonathan
*


I'm using a prototyping board with an AVR AtMEGA32 and an FT232BM serial-USB converter chip hooked up to its USART (and running a bootloader so I dump programs to it via the USB cable). It's nice - I press a button on the board to put it in bootloader mode, copy the program down, press the reset button and it runs biggrin.gif

I'll put more stuff about the robot up if people are interested once I've got time to do up a proper webpage but it's got some pretty nice stuff on it ... omnidirectional camera (hopefully a webcam hooked up to the Zaurus but I'll fall back onto a wireless camera pointed up at a parabolic mirror), Hokuyo URG scanning laser rangefinder and a 2 axis accelerometer to measure tilt ... all on a platform that can climb stairs and do other nice things and with the Zaurus (with wireless LAN) acting as the communications and control hub smile.gif

- Raymond
RGRICH
QUOTE(Jonathan @ Oct 14 2005, 02:47 AM)
QUOTE(Raybot @ Oct 13 2005, 11:12 AM)
P.S. I assume you had to fight your way through the "configure" process somehow (and if so, how did you do it in the crosscompile environment)? Or was there an easier way for you to get all this working?
*


As I recall I just did the usual "make config" (or maybe it "make menuconfig") but made sure I used the correct example config file (for the Spitz I think.) That was, of course after a successful run of "./configure".

That way you set the options for video4linux (which I see you also need...) and everything else before the final make.

Best of luck with your robot project - keep us posted. I got my C3000 to compile JAL programs and then program the Microchip PIC series of microprocessors in my robot cars through a USB<>serial cable. It then interacts with the operating robot cars through the same interface - no vision though sad.gif

Jonathan
*



I'm trying to get a garmin gps unit working with my C3000 but I'm running the Cacko ROM and not the Sharp Rom. I have a U232-P9 USB - Serial converter to connect the C3000 to the Garmin. It seems that the hotplug scripts detect the USB-serial device but can't find a driver to load. According to the usb.distmap file matching vendor/product codes from the lsusb -v it should be loading mct_u232.o.
I tried copying this driver from Jonathan's usb_serial package but depmod -a gives unresolved symbols in module mct-u232.o. How do I go about getting this to work with the Cacko Rom?
Thanks
rmako
Gents,

Any idea if this will work with the 6000? I am trying to read a GPS through the USB port.

I get the following in dmesg

usb.c: USB decive 29 (vend/prod 0x67b/0xaaa0) is not claimed by any driver.

Thanks,

rmako
javahack
QUOTE(Jonathan @ Jan 13 2005, 01:58 AM)
Maybe this will help some people who want a quick fix for USB<>SERIAL adaptor cables (and other USB serial devices) on the C3000.

Yesterday I set up the cross compiler on my x86 linux box and compiled the USB serial modules for SL-C3000 from the kernel source on Sharp's website.

I've posted the compiled drivers in the following directory with some rough instructions on installing them:

  http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/

I needed to do this to use some Prolific PL2303 and PL2303x based USB<>RS232 converter cables.  After installing these drivers all adaptors work well.  Note that I needed to find a replacement for pl2303.c to add support for the PL2303X chip, but the standard PL2303 driver is also there in the source (that particular problem was a pain in the ****).

I also had some problem with hotplugging and had to add a line to /etc/hotplug/usb.rc to remove the pl2303 module from memory when the machine goes into standby.  On looking at this file again I see that the line was already there, so I don't know if it was just the updated pl2303x driver that solved that problem. dry.gif I don't think anyone will have this problem with these drivers.  Mind you, I'm no expert rolleyes.gif

Oh yes, and I use minicom pointing to /dev/ttyUSB0.  To make minicom start quickly it helps to disable the modem init string (use 'minicom -o') and hangup strings (delete strings in minicom modem setup screen.)

Hope this helps someone.

Jonathan

[these files may move some time in the future (months rather than days)]
*



i can't get the DT version of the file, could you re-post it or zip it somewhere, I just bought and MSFT GPS-360 and need it working on sl-c3100 and pl2303.o from the tgz does not work..

Thanks,
Code Happy and Free smile.gif
javahack
QUOTE(rmako @ Nov 19 2005, 06:29 PM)
Gents,

Any idea if this will work with the 6000?  I am trying to read a GPS through the USB port.

I get the following in dmesg

usb.c: USB decive 29 (vend/prod 0x67b/0xaaa0) is not claimed by any driver.

Thanks,

rmako
*



if i can get it to compile i will post it
javahack
QUOTE(javahack @ Jan 20 2006, 08:35 PM)
QUOTE(Jonathan @ Jan 13 2005, 01:58 AM)
Maybe this will help some people who want a quick fix for USB<>SERIAL adaptor cables (and other USB serial devices) on the C3000.

Yesterday I set up the cross compiler on my x86 linux box and compiled the USB serial modules for SL-C3000 from the kernel source on Sharp's website.

I've posted the compiled drivers in the following directory with some rough instructions on installing them:

  http://www.enm.bris.ac.uk/teaching/enjmr/Zaurus_SL-C3000/

I needed to do this to use some Prolific PL2303 and PL2303x based USB<>RS232 converter cables.  After installing these drivers all adaptors work well.  Note that I needed to find a replacement for pl2303.c to add support for the PL2303X chip, but the standard PL2303 driver is also there in the source (that particular problem was a pain in the ****).

I also had some problem with hotplugging and had to add a line to /etc/hotplug/usb.rc to remove the pl2303 module from memory when the machine goes into standby.  On looking at this file again I see that the line was already there, so I don't know if it was just the updated pl2303x driver that solved that problem. dry.gif I don't think anyone will have this problem with these drivers.  Mind you, I'm no expert rolleyes.gif

Oh yes, and I use minicom pointing to /dev/ttyUSB0.  To make minicom start quickly it helps to disable the modem init string (use 'minicom -o') and hangup strings (delete strings in minicom modem setup screen.)

Hope this helps someone.

Jonathan

[these files may move some time in the future (months rather than days)]
*



i can't get the DT version of the file, could you re-post it or zip it somewhere, I just bought and MSFT GPS-360 and need it working on sl-c3100 and pl2303.o from the tgz does not work..

Thanks,
Code Happy and Free smile.gif
*




navermind i got it working

thanks
xjqian
QUOTE(rmako @ Nov 19 2005, 08:29 PM)
Gents,

Any idea if this will work with the 6000?  I am trying to read a GPS through the USB port.

I get the following in dmesg

usb.c: USB decive 29 (vend/prod 0x67b/0xaaa0) is not claimed by any driver.

Thanks,

rmako
*


same problem here, anybody care to compile for 6K user?
BarryW
Anybody have the dt version?? I could really use it.
javahack
QUOTE(BarryW @ Apr 2 2006, 08:47 PM)
Anybody have the dt version??  I could really use it.
*



I compiled the driver (pl2303.o) with added support for GPS360 and works fine, but I compiled it from the Cacko 1.23 kernel.

What Rom do you run, and what kernel ver? (2.4.20/????)

Thanks
javahack
QUOTE(xjqian @ Feb 25 2006, 02:07 AM)
QUOTE(rmako @ Nov 19 2005, 08:29 PM)
Gents,

Any idea if this will work with the 6000?  I am trying to read a GPS through the USB port.

I get the following in dmesg

usb.c: USB decive 29 (vend/prod 0x67b/0xaaa0) is not claimed by any driver.

Thanks,

rmako
*


same problem here, anybody care to compile for 6K user?
*



see my post below , btw what kernel do you use on what rom for sl-6000
speculatrix
I just tried an FTDI usb serial adaptor on my C3100 to use as a serial console for a disk array at work... no problem at all, dmesg proclaimed
CODE
hub.c: new USB device -2, assigned address 2
usb.c: USB device 2 (vend/prod 0x403/0x6001) is not claimed by any active driver.
usb.c: registered new driver serial
usbserial.c: USB Serial support registered for Generic
usbserial.c: USB Serial Driver core v1.4
usbserial.c: USB Serial support registered for FTDI SIO
usbserial.c: USB Serial support registered for FTDI 8U232AM Compatible
usbserial.c: USB Serial support registered for FTDI FT232BM Compatible
usbserial.c: FTDI FT232BM Compatible converter detected
usbserial.c: FTDI FT232BM Compatible converter now attached to ttyUSB0 (or usb/tts/0 for devfs)
usbserial.c: USB Serial support registered for USB-UIRT Infrared Tranceiver
usbserial.c: USB Serial support registered for Home-Electronics TIRA-1 IR Transceiver
ftdi_sio.c: v1.3.5:USB FTDI Serial Converters Driver


using cacko 1.23, I installed minicom "ipkg install minicom", having previously installed ncurses (kismet command line needs that).

started up minicom with "minicom -s" (having had to add a softlink in /usr/lib/ncurses.so.4 to the .so.4.2 file), set serial port to ttyUSB0, and voila!

the only snag was that none of the installed fonts showed up like either a PC or VT100 character set, so the on-screen boxes came up as various odd blobs.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.