Reply
Thread Tools
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#31
How did you make the .so file?
I ran make on the tablet and I get alot of errors.
__________________
machinegrid.com
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#32
if you are talking about the minicom deb, I did not build on the tablet. I built in a scratchbox environment. What .so are you talking about.
__________________
David Smoot
 
Posts: 90 | Thanked: 10 times | Joined on Aug 2007
#33
I got it.
This post from fanoush was helpful
http://www.internettablettalk.com/fo...12&postcount=5

I got both the ftdi and pl2303 chipsets to work.
__________________
machinegrid.com
 
Posts: 631 | Thanked: 837 times | Joined on May 2007 @ Milton, Ontario, Canada
#34
I'm getting a strange problem on my N800 here... the USB adapter I'm using is based on the pl2303 and works perfectly on my Fedora box, but when I load usbserial.ko and pl2303.ko from Fanush's post earlier then connect the device it doesn't seem to register properly. Here's my dmesg output related to it:

[179836.171875] usb 1-1: new full speed USB device using musb_hdrc and address 17
[179836.304687] usb 1-1: default language 0x0409
[179836.304687] usb 1-1: new device strings: Mfr=1, Product=2, SerialNumber=0
[179836.304687] usb 1-1: Product: USB-Serial Controller
[179836.304687] usb 1-1: Manufacturer: Prolific Technology Inc.
[179836.304687] usb 1-1: device v5372 p2303 is not supported
[179836.304687] usb 1-1: uevent
[179836.304687] usb 1-1: usb_probe_device
[179836.304687] usb 1-1: configuration #1 chosen from 1 choice
[179836.304687] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
[179836.304687] usb 1-1:1.0: uevent
[179836.304687] usbtest 1-1:1.0: usb_probe_interface
[179836.304687] usbtest 1-1:1.0: usb_probe_interface - got id
[179836.304687] usbserial_generic 1-1:1.0: usb_probe_interface
[179836.304687] usbserial_generic 1-1:1.0: usb_probe_interface - got id
[179836.304687] drivers/usb/core/inode.c: creating file '017'
[179836.304687] hub 1-0:1.0: 100mA power budget left
[179836.304687] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002
[179836.304687] hub 1-0:1.0: port 1 enable change, status 00000103
[179838.304687] usb 1-1: usb auto-suspend
[179840.328125] hub 1-0:1.0: hub_suspend
[179840.328125] usb usb1: usb auto-suspend

It seems like the problem is with the usb_probe_interface - got id... is there perhaps something in the pl2303 or usbserial module in general that lists which versions of the chip it supports or doesn't? With a working pl2303 the output of the lines immediately following that are:

[180168.335937] usbserial_generic 1-1:1.0: usb_probe_interface
[180168.335937] usbserial_generic 1-1:1.0: usb_probe_interface - got id
[180168.335937] pl2303 1-1:1.0: usb_probe_interface
[180168.335937] pl2303 1-1:1.0: usb_probe_interface - got id
[180168.335937] pl2303 1-1:1.0: pl2303 converter detected
[180168.335937] usb 1-1: pl2303 converter now attached to ttyUSB0
[180168.335937] drivers/usb/core/inode.c: creating file '018'
[180168.335937] hub 1-0:1.0: 100mA power budget left

which seems to indicate that the pl2303 module has now started doing it's thing, where previously it wasn't being invoked. Is there some specific setting in the pl2303 source that needs to be updated for this specific adapter, or?

Thanks for any help guys!

-Rob
 
Posts: 10 | Thanked: 3 times | Joined on Apr 2008
#35
I need some help getting this to work. I have installed minicom and the usbSerial driver. I can see that the adapter was recognized and there's a /dev/ttyUSB0. However, when I start minicom I get the following error:

root@rhodium:/etc# minicom -s
minicom: WARNING: configuration file not found, using defaults
No termcap entry for xterm

I must be doing something wrong. Can anyone help me please? Thanks!
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#36
No, you're not doing anything wrong; there's not a configuration file yet, so it's setting all parameters default; when you get it configured right, save the file, and it won't bring up the message again.
 

The Following User Says Thank You to Benson For This Useful Post:
Posts: 10 | Thanked: 3 times | Joined on Apr 2008
#37
Well, minicom exits after the "No termcap entry for xterm" message so I can't even configure it. How do I get past that?
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#38
Oh... I missed that.

Not sure... sorry to be so little use and yet so voluble.
 
Posts: 227 | Thanked: 51 times | Joined on Feb 2006
#39
As root, enter "minicom -s". Configure minicom to use your USB to serial adapter then save that setup as default. exit from minicom and then restart.

Be warned, by default minicom spits out an AT modem init string when it starts. Either disable that or don't connect your adapter until a few seconds after minicom starts.
__________________
David Smoot
 
Posts: 10 | Thanked: 3 times | Joined on Apr 2008
#40
Originally Posted by djs_tx View Post
As root, enter "minicom -s". Configure minicom to use your USB to serial adapter then save that setup as default. exit from minicom and then restart.

Be warned, by default minicom spits out an AT modem init string when it starts. Either disable that or don't connect your adapter until a few seconds after minicom starts.
Here's the problem: minicom exits right after the "No termcap entry for xterm" line. It doesn't let me configure anything. Any suggestions? Thanks.
 
Reply


 
Forum Jump


All times are GMT. The time now is 18:35.