As there is a USB host-mod port in A500, Is there any way to get a USB to serial converter working with it?
From time to time, I need to access to some Cisco devices' serial consoles. I used to use the laptop (which has neither a serial port) with a USB to serial converter for this. If the converter can also works in A500, it would be very nice that I don't need to bring the heavy laptop.
jackycxh said:
As there is a USB host-mod port in A500, Is there any way to get a USB to serial converter working with it?
From time to time, I need to access to some Cisco devices' serial consoles. I used to use the laptop (which has neither a serial port) with a USB to serial converter for this. If the converter can also works in A500, it would be very nice that I don't need to bring the heavy laptop.
Click to expand...
Click to collapse
I also need this, and I think the original acer 3.0 rom already support pl2303(usb to serial ), because I test my gps in the terminal emulator and it can get the data. But m-dj's roms don't support.
are the stock rom support it ?
sanaell said:
are the stock rom support it ?
Click to expand...
Click to collapse
Yes! I have tested my usb gps(pl2303) and it got the data. I think it just recognize this device but maybe you need some app to deal with it. I search the web and find some information. they said linux supports pl2303 and so android might support also and really stock rom support this chip pl2303 but m-dj's mod rom not.
Not sure if mine is pl2303. I will check it out.
but it does not recognized when I plug it in A500.
I got below information from dmesg.
<6>[ 387.721955] usb 1-1: new full speed USB device using tegra-ehci and addres
s 2
<6>[ 389.787681] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
<6>[ 389.788352] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumbe
r=3
<6>[ 389.788998] usb 1-1: Product: usb serial converter
<6>[ 389.789346] usb 1-1: Manufacturer: ftdi
<6>[ 389.790054] usb 1-1: SerialNumber: ftEFW35C
jackycxh said:
Not sure if mine is pl2303. I will check it out.
but it does not recognized when I plug it in A500.
I got below information from dmesg.
<6>[ 387.721955] usb 1-1: new full speed USB device using tegra-ehci and addres
s 2
<6>[ 389.787681] usb 1-1: New USB device found, idVendor=0403, idProduct=6001
<6>[ 389.788352] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumbe
r=3
<6>[ 389.788998] usb 1-1: Product: usb serial converter
<6>[ 389.789346] usb 1-1: Manufacturer: ftdi
<6>[ 389.790054] usb 1-1: SerialNumber: ftEFW35C
Click to expand...
Click to collapse
I think your device is not used pl2303. Because the manufacturer is not prolific.
Hmm, I tried when I was on 3.0.1 and could not get it to work. Just got the 3.1 update yesterday and plugged in my prolific today and yep /dev/ttyUSB0 shows up. Now I don't have to rely on bt for gps.
GonzoCSU said:
Hmm, I tried when I was on 3.0.1 and could not get it to work. Just got the 3.1 update yesterday and plugged in my prolific today and yep /dev/ttyUSB0 shows up. Now I don't have to rely on bt for gps.
Click to expand...
Click to collapse
You mean you can use use usb gps? How? With or without any addtional apk?
It should be pretty easy to write your own app to read /dev/ttyUSB0 or modify an app like BlueGPS4Droid (which receives serial NMEA over Bluetooth and feeds a mock location listener). I am not sure if the standard Java libraries for serial connections are supported under Android or not. I will be looking more into this in the next few days and I will post back here when I figure out more.
GonzoCSU said:
It should be pretty easy to write your own app to read /dev/ttyUSB0 or modify an app like BlueGPS4Droid (which receives serial NMEA over Bluetooth and feeds a mock location listener). I am not sure if the standard Java libraries for serial connections are supported under Android or not. I will be looking more into this in the next few days and I will post back here when I figure out more.
Click to expand...
Click to collapse
It is nice! And I think it will be successful. And I use the terminla emulator and gps can get data and even it fixed the location (led of my gps flash and meant it got the postion). However I need the tab support my gps because I am not using the stock rom, I am using galaxy 1.05
And I see the kernal resource on the web and see it really support and the code is here
https://github.com/roggin/iconia-a500-kernel/tree/iconia_kernel_11.2.9/drivers/usb/serial.
Not only the pl2303 also other usb2serial. And can anyone make this to my galay rom and let it supported?
Related
Hi all
Unlocked my XDA yesterday using a bog standard USB to serial converter lead from the USB hub attached to my Sony Vaio laptop (that has no serial interface) and a standard serial cable for the XDA.
No problems - Manipulator 1.1 communicated fine even though it isnt 'true' RS232.
Just thought people with USB only computers might like to know that unlocking / serial communication IS possible!
Rog
Before we get any confusion: this means you can unlock from a computer that has no serial port. It does not mean you can unlock XDAs without a serial cable.
Computer's USB port <->
USB to serial adapter <->
serial XDA cable <->
XDA
Yes thats correct. it does NOT mean you can unlock using the XDA's USB port!
Rog
Hi Guys!
I have a self powered: FTDI(FT232R) - micro USB-A (Nokia OTG CA-157) - Archos 70
with custom kernel. It works like a charm BUT
The driver picks the FT232R only if I connect it in the following sequence:
1. First connect the micro USB-A dongle (FT232 not attached)
2. As second connect FT232R to the USB dongle
Then I got the following dmesg:
1.
Code:
Code:
usb_switch_print_state: 3 ATTACHED_HOST
usb_switch_print_state: 3 ATTACHED_HOST
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v5 enabled 0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v8 enabled 0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb3v1 enabled 0
musb_hdrc: version 6.0, musb-dma, peripheral, debug=0
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb3v1 enabled 1
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v8 enabled 1
twl4030_usb twl4030_usb: regulator_enable twl4030_usb-usb1v5 enabled 1
musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
musb_hdrc musb_hdrc: MUSB HDRC host driver
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '002'
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: default language 0x0409
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.29-omap1 musb-hcd
usb usb2: SerialNumber: musb_hdrc
usb usb2: uevent
usb usb2: usb_probe_device
usb usb2: configuration #1 chosen from 1 choice
usb usb2: adding 2-0:1.0 (config #1, interface 0)
usb 2-0:1.0: uevent
hub 2-0:1.0: usb_probe_interface
hub 2-0:1.0: usb_probe_interface - got id
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
hub 2-0:1.0: standalone hub
hub 2-0:1.0: individual port power switching
hub 2-0:1.0: no over-current protection
hub 2-0:1.0: power on to power good time: 10ms
hub 2-0:1.0: 100mA bus power budget for each child
hub 2-0:1.0: local power source is good
hub 2-0:1.0: enabling power on all ports
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '001'
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0000
hub 2-0:1.0: hub_suspend
usb usb2: bus auto-suspend
2.
Code:
Code:
usb usb2: usb resume
hub 2-0:1.0: hub_resume
hub 2-0:1.0: port 1: status 0101 change 0001
hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
usb 2-1: new full speed USB device using musb_hdrc and address 2
usb 2-1: ep0 maxpacket = 8
usb 2-1: default language 0x0409
usb 2-1: New USB device found, idVendor=0403, idProduct=6001
usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: RFID_EM
usb 2-1: Manufacturer: FTDI
usb 2-1: SerialNumber: A9UMG98I
usb 2-1: uevent
usb 2-1: usb_probe_device
usb 2-1: configuration #1 chosen from 1 choice
usb 2-1: adding 2-1:1.0 (config #1, interface 0)
usb 2-1:1.0: uevent
usbserial_generic 2-1:1.0: usb_probe_interface
usbserial_generic 2-1:1.0: usb_probe_interface - got id
ftdi_sio 2-1:1.0: usb_probe_interface
ftdi_sio 2-1:1.0: usb_probe_interface - got id
ftdi_sio 2-1:1.0: FTDI USB Serial Device converter detected
usb 2-1: Detected FT232RL
usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
/home/archos/kernel/gen8/gen8-gpl-froyo/linux/drivers/usb/core/inode.c: creating file '002'
hub 2-0:1.0: 100mA power budget left
hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
hub 2-0:1.0: port 1 enable change, status 00000103
This is a very verbose fine dmesg showing ttyUSB0 is created.
My problem is that if I connect the micro-A dongle with FT232R already connected, then just the 1st sequence runs (till bus suspend) the second not. The same thing is with soft reboot, it is not working I need to manually disconnect then connect dongle first then FT232R.
I tried to tune msusb_hdrc config but with no sucess. What is the problem, what causes to stuck at suspend when it is not attached in 2 step??????
I have a pic from the hw look but yet I can't post it (till 8 posts) if needed I can in private.
UPDATE is that I tried to disable auto suspend and it is still not working. The general thing is that the musb_hdrc host driver recognizes the OTG as a hub with one port and if the peripherial (FT232R in this case) is already attached it is not enumarated and picked by the FTDI driver. Furthermore the state switching is not done properly. If the periph. is not attached it goes to a_idle but if yes it stays in b_idle mode (sys/devices/platform/musb_hdrc/mode).
Thanks, cheers
sodjas
As the title states, I have installed 4.0.4 Tegraowners ICS ROM v170 and see that i have a 3g signal bar, however no connection. I am not sure how to check and see if my 3g dongle is even being seen correctly other than the green lights on the device it self.
**edit**
O.K. a little more information:
Qualcomm 3g device
dmesg log shows device seen, connected, and drivers loaded: See below
Code:
[ 3982.060685] usb 1-1.2: new full speed USB device number 8 using tegra-ehci
[ 3982.092684] usb 1-1.2: New USB device found, idVendor=1199, idProduct=0301
[ 3982.092791] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=4
[ 3982.092968] usb 1-1.2: Product: Sierra Wireless Device
[ 3982.093067] usb 1-1.2: Manufacturer: Sierra Wireless, Incorporated
[ 3982.093246] usb 1-1.2: SerialNumber: 4Vx«Íïÿÿÿÿ
[ 3982.096237] sierra 1-1.2:1.0: Sierra USB modem converter detected
[ 3982.097713] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB0
[ 3982.098625] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB1
[ 3982.101019] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB2
[ 3982.102181] usb 1-1.2: Sierra USB modem converter now attached to ttyUSB3
[ 3983.590674] usb 1-1.1: new high speed USB device number 9 using tegra-ehci
[ 3983.622387] usb 1-1.1: New USB device found, idVendor=198f, idProduct=0220
[ 3983.622694] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3983.623193] usb 1-1.1: Product: Mobile WiMax SS
[ 3983.623471] usb 1-1.1: Manufacturer: Beceem Communications Inc.
Now I have tried adding sprint APN in via the GUI but nothing stays. I guess i need to figure out how to add it to the APN file and upload it that way to my device.
O.K. maybe i am missing something.
Do I need to add an app, or turn something else on to have the ROM use the 3g dongle for connectivity? I am on an A500 so I do not think i need to make this change "a501 3g modem(comment ro.carrier=wifi-only in /system/build.prop)" as stated i have the 3g bars with an x through them even when the dongle is plugged in. Anyone familiar with this willing to try and help me figure this out.
I am not a noob to android just a noob to modding my tablet.
Still any help would be appreciated, even if its to tell me i need some kind of app to enable the modem.:silly:
For support on tegraowners Rom, you need to go to their site.
Thank you for the reply ....
The same post has been on the tegraowners support forum for about a week. Almost 100 views, and only my 1 reply to my self with the extra information. Was hoping someone over here could help me out.
Alas, the TO ROM is kinda persona non-grata around here, due to the lack of GPL compliance. We're really not generally meant to discuss it all that much as it usually devolves into a slanging match.
TO is the best place to go to get support.
FloatingFatMan said:
Alas, the TO ROM is kinda persona non-grata around here, due to the lack of GPL compliance. We're really not generally meant to discuss it all that much as it usually devolves into a slanging match.
TO is the best place to go to get support.
Click to expand...
Click to collapse
Gotcha, and thanks for the info. I will keep trying over there, unless someone can point to another a500 rom supports the 3g dongle.
If u have an android phone get foxfi app from market and use ur phone as modem. I who needs a Dingle.
I'm playing with kernel builds on my NST - and haven't yet popped the back to try and put a uart on; I'm trying to enable TLS but it's
not fully booting NookManager if I do and I'm wondering if there is a way to get some debug out of it;
During boot I see the Loading.. for NookManager come up and then very little - but I assume that's uboot that loads that?
My host also, briefly sees the device change from being TI to being SimpleTouch, and to showing a pair of usb-storage devices;
I'm assuming this means it's got to userspace?
What's the boot process - i.e. where must it have got to if it's presenting usb-scsi-devices, and has anyone got any debug/logging
hacked in at that point.
Dave
P.S. USB as seen by the host; I've once had one of the SCSI devices respond to a mount by saying no media present, but it's a VERY short window!
[47897.082374] usb 1-1.4: unable to get BOS descriptor
[47897.083713] usb 1-1.4: New USB device found, idVendor=0451, idProduct=d00e
[47897.083718] usb 1-1.4: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[47897.083722] usb 1-1.4: Product: OMAP3630
[47897.083726] usb 1-1.4: Manufacturer: Texas Instruments
[47900.321399] usb 1-1.4: USB disconnect, device number 70
[47930.231996] usb 1-1.4: new high-speed USB device number 71 using ehci-pci
[47930.260415] hub 1-1:1.0: unable to enumerate USB device on port 4
[47930.484271] usb 1-1.4: new high-speed USB device number 72 using ehci-pci
[47930.583055] usb 1-1.4: New USB device found, idVendor=2080, idProduct=0003
[47930.583062] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[47930.583066] usb 1-1.4: Product: NOOK SimpleTouch
[47930.583070] usb 1-1.4: Manufacturer: B&N
[47930.583073] usb 1-1.4: SerialNumber: 11223344556677
[47930.589989] scsi38 : usb-storage 1-1.4:1.0
[47931.703186] scsi 38:0:0:0: Direct-Access B&N NOOK SimpleTouch 0100 PQ: 0 ANSI: 2
[47931.711480] scsi 38:0:0:1: Direct-Access B&N NOOK SimpleTouch 0100 PQ: 0 ANSI: 2
[47931.711942] sd 38:0:0:0: Attached scsi generic sg4 type 0
[47931.712277] sd 38:0:0:1: Attached scsi generic sg5 type 0
[47931.727659] sd 38:0:0:0: [sdd] Attached SCSI removable disk
[47934.364242] usb 1-1.4: USB disconnect, device number 72
[47934.371347] sd 38:0:0:1: [sde] Attached SCSI removable disk
[47934.635652] usb 1-1.4: new high-speed USB device number 73 using ehci-pci
[47934.728849] usb 1-1.4: unable to get BOS descriptor
You had me confused there for a second thinking that log was out of the Nook and not the host.
(The missing BOS descriptor is expected. The Nook is not USB 3 updated.)
The two USB Mass Storage points shows that the kernel is booting.
The fact that nothing is there shows that things are not going far enough to let vold (the volume daemon) mount /media and /sdcard.
I like using the UART to debug even when some deep thinking might have solved the problem.
My setup with a new connector: http://forum.xda-developers.com/showthread.php?p=35371364
Renate NST said:
You had me confused there for a second thinking that log was out of the Nook and not the host.
(The missing BOS descriptor is expected. The Nook is not USB 3 updated.)
The two USB Mass Storage points shows that the kernel is booting.
The fact that nothing is there shows that things are not going far enough to let vold (the volume daemon) mount /media and /sdcard.
I like using the UART to debug even when some deep thinking might have solved the problem.
My setup with a new connector: http://forum.xda-developers.com/showthread.php?p=35371364
Click to expand...
Click to collapse
Thanks for the reply!
Ah ok; I'd assumed that the presense of mass storage points had assumed something in user space must have set them up.
OK, in that case I guess it's UART time - are there any tricks to getting the case open without doing too much damage?
Thanks again for the reply?
Dave
I find that the easiest way to pop the power switch is to use a small knife blade
(like the small blade on a penknife).
Slip it under the top seam, don't push it straight up, pull it a bit in the upward direction.
The screw underneath is a Torx T-5. Mine had a sticker on top a long time ago.
Slide the two case halves about 1/4" apart.
Don't forget to pull the SD card first!
Renate NST said:
I find that the easiest way to pop the power switch is to use a small knife blade
(like the small blade on a penknife).
Slip it under the top seam, don't push it straight up, pull it a bit in the upward direction.
The screw underneath is a Torx T-5. Mine had a sticker on top a long time ago.
Slide the two case halves about 1/4" apart.
Don't forget to pull the SD card first!
Click to expand...
Click to collapse
Right that's erm kind of done the trick (my soldering is awful I suspect the pad is somewhat screwed up, because it requires a bit of pressure to work - it took me two goes; I made the mistake of using ribbon cable the first time and it just wouldn't have it; a thin bit of solid core did the trick).
I also found the ifixit teardown Nook+Simple+Touch+with+GlowLight+Teardown/9301/1 which is a nice pictorial walk though of how to get it open.
As for the bug I was chasing; hmm - it's an Attempted to kill init! - why I guess will take a bit more chasing down.
(It's a pity that the android kernel USB gadget stuff doesn't have a debug channel - a usb serial console, or even a firewire-like DMA would be doable I'd have thought).
Thanks again,
Dave (1 more post and I'll be able to include URLs/post to dev)
Hi all. I've tried using USB joysticks and gamepads with my G5+, but without success. They are detected (i.e. by looking at logcat/dmesg), and they power off (lights go on), but I can't actually use them in any way. I've tested by using a Joystick test app, and a couple of games. In all cases there is no joystick detected.
I tried this with stock unrooted before, and again now under Lineage 14.1. Has anyone had any luck with this? Could another kernel enable joysticks? Other USB peripherals work fine, e.g. keyboard/mice/USB sticks.
Also, has anyone tried bluetooth joysticks/gamepads? If I'm out of luck with USB joysticks, might consider just getting a bluetooth one if I know they work.
Here's an example of the output from dmesg:
[ 126.407593,3] usb 1-1: new low-speed USB device number 3 using xhci-hcd
[ 126.557281,3] usb 1-1: New USB device found, idVendor=046d, idProduct=c20a
[ 126.557328,3] usb 1-1: New USB device strings: Mfr=4, Product=32, SerialNumber=0
[ 126.557347,3] usb 1-1: Product: WingMan RumblePad
[ 126.557364,3] usb 1-1: Manufacturer: Logitech Inc.
[ 126.558716,3] usb 1-1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 126.558778,3] usb 1-1: ep 0x1 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 126.868193,2] QSEECOM: qseecom_load_app: App (cppf) does'nt exist, loading apps for first time
[ 126.871609,2] QSEECOM: qseecom_load_app: App with id 19 (cppf) now loaded
Well I've used all sorts of peripherials on stock, including a universal gamepad. It works flawlessly and gets detected, though I do have to add a keylayout file for it to work with games in its native mode. When switching to xbox input mode it's supported natively on Android.
Mine uses a 2.4GHz usb dongle which uses very little power, maybe it's a power draw related thing?
I had considered of it was a power drain issue as well. I tried hooking up the same gamepad to an old Samsung galaxy s3, and it worked fine. Not sure that that tells us much.
In any case I decided to purchase a cheap Bluetooth gamepad to test, and I can use it with my laptop if it doesn't work with my g5+. So when it arrives, hopefully I can get it working.