shangdawei / android-ftdi-usb2serial-driver-package

Automatically exported from code.google.com/p/android-ftdi-usb2serial-driver-package
0 stars 0 forks source link

FTDI Device not detected #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
I have an Ainol Aurora running ICS 4.0.3 - the OTG USB mode work for bluetooth 
devices but it doesn't detect an FT232RL chip on several different Arduino 
boards.

What is the expected output? What do you see instead?
Doing a device refresh says no FTDI chips are detected

What version of the product are you using? On what operating system?
Checked out today, Android 4.0.3

Please provide any additional information below.
Does there need to be a lower level driver installed for this to work?

Original issue reported on code.google.com by webmas...@ediy.co.nz on 2 May 2012 at 1:22

GoogleCodeExporter commented 9 years ago
Here is the DMESG log from the device, is this problem to do with the AllWinner 
USB host driver?

<7>[ 1392.830000] rmmod_host_driver
<7>[ 1392.830000]
<7>[ 1392.830000] [sw_hcd0]: sw_usb_host0_disable start
<7>[ 1392.840000] -------sw_hcd0_soft_disconnect---------
<7>[ 1392.840000] [sw_hcd_host0]: Set USB Power OFF
<7>[ 1392.840000] sw_hcd_stop: sw_hcd disabled
<7>[ 1392.850000] [sw_hcd0]: close_usb_clock
<7>[ 1392.850000] [sw_hcd0]: sw_usb_host0_disable end
<7>[ 1395.890000]
<7>[ 1395.890000]
<7>[ 1395.890000] insmod_host_driver
<7>[ 1395.890000]
<7>[ 1395.890000] [sw_hcd0]: sw_usb_host0_enable start
<7>[ 1395.900000] -------sw_hcd0_soft_disconnect---------
<7>[ 1395.900000] [sw_hcd0]: open_usb_clock
<7>[ 1395.930000] [sw_hcd0]: host_init_state = 0
<7>[ 1395.930000] [sw_hcd_host0]: Set USB Power ON
<7>[ 1395.940000] [sw_hcd0]: sw_usb_host0_enable end
<7>[ 1396.110000]
<7>[ 1396.110000] ------------IRQ CONNECT-------------
<7>[ 1396.110000]
<7>[ 1396.280000] [sw_hcd]: reset port.
<7>[ 1396.340000] [sw_hcd]: reset port stopped.
<7>[ 1396.340000] spurious?
<6>[ 1396.400000] usb 1-1: new full speed USB device number 10 using 
sw_hcd_host0
<7>[ 1396.400000] [sw_hcd]: reset port.
<7>[ 1396.470000] [sw_hcd]: reset port stopped.
<7>[ 1396.530000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
<7>[ 1396.530000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
<7>[ 1396.550000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
<7>[ 1396.550000] [sw_hcd]: sw_hcd_h_disable, epnum = 0
<7>[ 1396.560000] WRN:L1719(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, STALLING ENDPOINT
<7>[ 1396.560000] WRN:L1738(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, ep aborting
<7>[ 1396.570000] WRN:L1719(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, STALLING ENDPOINT
<7>[ 1396.570000] WRN:L1738(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, ep aborting
<7>[ 1396.590000] WRN:L1719(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, STALLING ENDPOINT
<7>[ 1396.590000] WRN:L1738(drivers/usb/sun4i_usb/hcd/core/sw_hcd_host.c):ERR: 
sw_hcd_h_ep0_irq, ep aborting
<6>[ 1398.650000] init: waitpid returned pid 4021, status = 00000000
<3>[ 1398.660000] init: untracked pid 4021 exited
<7>[ 1410.770000] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<7>[ 1410.770000] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<7>[ 1410.810000] rtl8192c_dm_RF_Saving(): RF_Save
<7>[ 1412.770000] rtw_set_ps_mode(): Enter 802.11 power save mode...
<7>[ 1412.770000] rtl8192c_dm_RF_Saving(): RF_Normal
<7>[ 1412.780000] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<7>[ 1414.450000] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save..
<7>[ 1414.460000] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0
<7>[ 1414.770000] rtl8192c_dm_RF_Saving(): RF_Save
<7>[ 1416.770000] rtw_set_ps_mode(): Enter 802.11 power save mode...
<7>[ 1416.770000] rtl8192c_dm_RF_Saving(): RF_Normal
<7>[ 1416.780000] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2
<7>[ 1435.100000] battery vol change: 31->30

Original comment by webmas...@ediy.co.nz on 3 May 2012 at 1:01

GoogleCodeExporter commented 9 years ago
Can also confirm same issue on Samsumg Galaxy SII running Android 4.0.3, 
connected via OTG adapter to a Arduino Nano with FT232RL chip.

Original comment by glaserme...@gmail.com on 5 May 2012 at 4:58

GoogleCodeExporter commented 9 years ago
Hi
Found same issue with FT232RQ used on an Onda VX580W running Android 4.0.3. The 
USB debug interface must be working at some level as I'm able to download the 
App from Eclipse. But connecting get no FTDI chips are detected.

The target boards where a MAX32 and an UNO32 both having the FT232RQ. The right 
VID and PID are in the source files but no response.

Love the idea of not having to rebuild the kernel.

Original comment by stefan.m...@gmail.com on 6 Aug 2012 at 10:10

GoogleCodeExporter commented 9 years ago
Hi Again,

Little bit of progress. Gave up trying to buy an OTG cable, kept being given 
standard one with pin 4 OC and being assured it was the right one. Made my own 
so at least I can be sure. BTW for people that don't know Mini USB B OTG cable 
has pin 4 shorted to pin 5.

The Onda now powers my boards and the Leds hooked to the FTDI device on the 
board flash as if it was being hooked to a PC. The Leds only flash in response 
to the FTDI part being enumerated. The application still refuses to see an FTDI 
part. 

The OS must be trying to do something to the FT232 part so least that is 
encouraging.

Original comment by stefan.m...@gmail.com on 29 Aug 2012 at 12:08

GoogleCodeExporter commented 9 years ago
Hi,

Baby steps. Found an app that shows FTDI can be seen at the kernel level but 
not at the android level. Search for "USB Device Info" in the Goole app store, 
it's free. 

Added usb permissions via adb push and now the android level can see the FTDI 
part. Permission seems generic enough to not be specific to a Nexus 4G Place 
below in 
/system/etc/permissions/

http://code.google.com/p/ics-nexus-s-4g/source/browse/trunk/system/etc/permissio
ns/android.hardware.usb.host.xml?r=18

I rebooted after doing this. Can now see the FTDI part in the application. 
Still not talking to the part but at least I can see it.

Original comment by s.mor...@griffith.edu.au on 3 Sep 2012 at 5:40