Hi,
past days I tried to run usb networking on my ipaq, but with no luck. I traced GPIOs with haret, relevant to USB are 99, 78, 39, 47 - when I plug/unplug the cable to the computer; 13, 78, 99 - when plugging/unplugging to power source, so I believe GPIO #78 is USB_PULLUP. (GPIO #99 was detected as battery door) I tried it and the output was following:
[ 8502.775416] hub 3-0:1.0: connect-debounce failed, port 2 disabled
[ 8528.652338] usb 2-1: new full speed USB device using ohci_hcd and address 15
[ 8528.875957] usb 2-1: configuration #1 chosen from 1 choice
[ 8528.897004] eth0: register 'rndis_host' at usb-0000:00:13.1-1, RNDIS device, 80:00:60:0f:e8:00
[ 8529.133956] udev: renamed network interface eth0 to eth2
[ 8568.003708] usb 2-1: USB disconnect, address 15
[ 8568.005682] eth2: unregister 'rndis_host' usb-0000:00:13.1-1, RNDIS device
[ 8591.561327] usb 2-1: new full speed USB device using ohci_hcd and address 16
[ 8591.766300] usb 2-1: configuration #1 chosen from 1 choice
[ 8591.796861] eth0: register 'rndis_host' at usb-0000:00:13.1-1, RNDIS device, 80:00:60:0f:e8:00
[ 8591.982949] udev: renamed network interface eth0 to eth2
[ 8651.662446] usb 2-1: USB disconnect, address 16
[ 8651.663565] eth2: unregister 'rndis_host' usb-0000:00:13.1-1, RNDIS device
[ 8653.755498] printk: 1 messages suppressed.
[ 8653.755507] hub 3-0:1.0: connect-debounce failed, port 2 disabled
..."hub 3-0:1.0: connect-debounce failed, port 2 disabled" repeating...
I tried connecting usb cable prior to booting, but it didn't help.
I discovered also some other GPIO ( #83 ) is changed when managing USB settings - when I go to "USB settings" and check "enable faster data synchronization", this GPIO value is set to 0 and then to 1. When I check this option in WinCE, new network adapter appear in Windows host. If I uncheck it, the new adapter disappear and GPIO is set to 0 and then to 1.
Is this GPIO relevant too ?
Has anybody some ideas / suggestions what to do?
thanks
Related
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
viewlessguru said:
Hi,
I recently acquired a TF101 and I am trying to do some development on it.
I have USB debugging on and tried to put it in APX mode by powering up using vol + and power button. It is connected to laptop running ubuntu 12.04 and I see following kernel messages
[ 3650.272049] usb 3-1: new low-speed USB device number 38 using ohci_hcd
[ 3650.452045] usb 3-1: device descriptor read/64, error -62
[ 3650.736044] usb 3-1: device descriptor read/64, error -62
[ 3651.016046] usb 3-1: new low-speed USB device number 39 using ohci_hcd
[ 3651.196038] usb 3-1: device descriptor read/64, error -62
[ 3651.484049] usb 3-1: device descriptor read/64, error -62
[ 3651.764103] usb 3-1: new low-speed USB device number 40 using ohci_hcd
[ 3652.172100] usb 3-1: device not accepting address 40, error -62
[ 3652.348103] usb 3-1: new low-speed USB device number 41 using ohci_hcd
[ 3652.756046] usb 3-1: device not accepting address 41, error -62
[ 3652.756060] hub 3-0:1.0: unable to enumerate USB device on port 1
any suggesstions ?
Click to expand...
Click to collapse
If your using USB 3.0 ports to connect the tablet try switching to a usb 2.0 port. usb3 has been known to cause add issues sometimes.
Try each of your USB ports. I have issues with my tablet not being seen on all but one port on my PC. Even though stuff works in the other ports It still was not seen.
Sent from my Transformer TF101 using xda premium
What do you see on "$lsusb"?
Can you see an Nvidia Device?
SOLVED: defective otg cable
useful tools:
any android terminal emulator plus root
dmesg
lsusb
2nd otg cable
I cannot seem to get otg working with any of the various USB storage devices I have.
Any ideas on how I can debug this?
If it were normal Linux it would be easy enough, however it's not.
Any suggestions would be appreciated.
Running AOKP buttered right now but sentinel stock and paranoid all do not work either. So it might be a cable or the tablet even.
Hmm not sure but I wonder if the kernel with this rom is missing the fat kernel modules
Thanks
Sent from my Nexus 10 using xda premium
tazmeister said:
I cannot seem to get otg working with any of the various USB storage devices I have.
Click to expand...
Click to collapse
I had the same problems with rooted Stock and various custom ROMs. Try installing "USB OTG Helper [root]" then retest. This app helped get me RW access to OTG storage from SD cards to powered HDD drives in various formats (ext2,3,4 and NTFS).
It worked so well I paid for the donate version just to support the developer. It even has exFAT support although I never tried it. Personally I think it should be part of standard Android.
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
Thanks more commands to jog my memory and try
I installed a console app and can check dmesg and other stuff.
Lsmod and related seem to be mostly obsolete.
Dmesg shows something is seen but the system keeps failing after this.
I see the same messages regardless of which device I try, powered and unpowered.
<6>[ 6171.135316] s5p-ehci s5p-ehci: S5P EHCI Host Controller
<6>[ 6171.136622] s5p-ehci s5p-ehci: new USB bus registered, assigned bus number 1
<6>[ 6171.137173] s5p-ehci s5p-ehci: irq 103, io mem 0x12110000
<6>[ 6171.145031] s5p-ehci s5p-ehci: USB 0.0 started, EHCI 1.00
<6>[ 6171.145636] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 6171.146150] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.146439] usb usb1: Product: S5P EHCI Host Controller
<6>[ 6171.146925] usb usb1: Manufacturer: Linux 3.4.5-gb44fbc0 ehci_hcd
<6>[ 6171.147202] usb usb1: SerialNumber: s5p-ehci
<6>[ 6171.150947] hub 1-0:1.0: USB hub found
<6>[ 6171.151298] hub 1-0:1.0: 3 ports detected
<6>[ 6171.153725] exynos-ohci exynos-ohci: EXYNOS OHCI Host Controller
<6>[ 6171.156783] exynos-ohci exynos-ohci: new USB bus registered, assigned bus number 2
<6>[ 6171.157031] exynos-ohci exynos-ohci: irq 103, io mem 0x12120000
<6>[ 6171.214330] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
<6>[ 6171.214522] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 6171.214630] usb usb2: Product: EXYNOS OHCI Host Controller
<6>[ 6171.214813] usb usb2: Manufacturer: Linux 3.4.5-gb44fbc0 ohci_hcd
<6>[ 6171.215052] usb usb2: SerialNumber: exynos-ohci
<6>[ 6171.220588] hub 2-0:1.0: USB hub found
<6>[ 6171.220946] hub 2-0:1.0: 3 ports detected
<6>[ 6171.225049] manta_otg manta_otg_work: b_idle -> a_host
<6>[ 6171.705161] usb 2-1: new full-speed USB device number 2 using exynos-ohci
<3>[ 6171.835100] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.070121] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.300093] usb 2-1: new full-speed USB device number 3 using exynos-ohci
<3>[ 6172.430142] usb 2-1: device descriptor read/64, error -62
<3>[ 6172.665754] usb 2-1: device descriptor read/64, error -62
<6>[ 6172.895140] usb 2-1: new full-speed USB device number 4 using exynos-ohci
<3>[ 6173.305043] usb 2-1: device not accepting address 4, error -62
<6>[ 6173.430032] usb 2-1: new full-speed USB device number 5 using exynos-ohci
<3>[ 6173.840038] usb 2-1: device not accepting address 5, error -62
<3>[ 6173.840490] hub 2-0:1.0: unable to enumerate USB device on port 1
Sent from my Nexus 10 using xda premium
None of the org helper apps have helped.
I don't think the org cable is bad though maybe this detail means otherwise
one device starts charging itself of the musb port when i plug it in.
Sent from my Nexus 10 using xda premium
KasF said:
Have you checked "lsusb" or "udevadm" in terminal if the device recognizes anything?
Click to expand...
Click to collapse
udevadm doesn't seem to be present but lsusb lists 2 devices when I have something plugged in.
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0001
Sent from my Nexus 10 using xda premium
ok problem solved.
The final debugging step was to "get another otg cable and test to make sure the first otg cable isn't defective"
Since I only owned a single OTG cable at the start, it was sort of difficult to perform this ultimate debug step.
But once I tried a different cable, almost everything worked just fine.
Only my 64gb micro-sd cards gave me a little trouble, but they all work now.
Hi,
I was trying to flash a new rom, and i did a very bad thing.
I flashed an incorrect file 0-PrimaryGPT.img on my lg g2.
Then i can not get dowload mode, recovery or anything else. In windows i see just an unrecognized device.
In ubuntu i just see using dmesg:
[ 1156.392274] usb 2-1: new high-speed USB device number 7 using ehci-pci
[ 1171.504275] usb 2-1: device descriptor read/64, error -110
[ 1186.720115] usb 2-1: device descriptor read/64, error -110
[ 1186.936293] usb 2-1: new high-speed USB device number 8 using ehci-pci
[ 1202.048161] usb 2-1: device descriptor read/64, error -110
[ 1217.264175] usb 2-1: device descriptor read/64, error -110
[ 1217.480078] usb 2-1: new high-speed USB device number 9 using ehci-pci
[ 1227.888175] usb 2-1: device not accepting address 9, error -110
[ 1228.000258] usb 2-1: new high-speed USB device number 10 using ehci-pci
[ 1238.408064] usb 2-1: device not accepting address 10, error -110
[ 1238.408099] hub 2-0:1.0: unable to enumerate USB device on port 1
[ 1238.672141] usb 6-1: new full-speed USB device number 6 using uhci_hcd
[ 1253.784150] usb 6-1: device descriptor read/64, error -110
[ 1269.000132] usb 6-1: device descriptor read/64, error -110
[ 1269.220059] usb 6-1: new full-speed USB device number 7 using uhci_hcd
[ 1284.332075] usb 6-1: device descriptor read/64, error -110
[ 1299.556068] usb 6-1: device descriptor read/64, error -110
[ 1299.776090] usb 6-1: new full-speed USB device number 8 using uhci_hcd
[ 1310.184174] usb 6-1: device not accepting address 8, error -110
[ 1310.296076] usb 6-1: new full-speed USB device number 9 using uhci_hcd
[ 1320.704056] usb 6-1: device not accepting address 9, error -110
[ 1320.704105] hub 6-0:1.0: unable to enumerate USB device on port 1
There are any option to recover it, someone do recover from a situation like this ?
Thanks in advance.
So I currently am running ubuntu 15 and another computer with mint 17.
ON both computers I have tried heimdall and Jodin. Both have been unable to obtain a pit file. I get that error -7 which appears to be something related to not receiving any packets back from the phone.
When I connect the phone outside of download mode - adb works also
$Dmesg | tail
[email protected]:~$ dmesg | tail
[ 2663.619751] cdc_acm 3-1.1:1.1: failed to set dtr/rts
[ 2663.691610] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[ 2663.693138] usb 3-1.1: USB disconnect, device number 7
[ 2663.911119] usb 3-1.1: new high-speed USB device number 8 using ehci-pci
[ 2664.021218] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=6860
[ 2664.021231] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2664.021238] usb 3-1.1: Product: SAMSUNG_Android
[ 2664.021245] usb 3-1.1: Manufacturer: SAMSUNG
[ 2664.021250] usb 3-1.1: SerialNumber: 4b6bda34
[ 2664.023462] cdc_acm 3-1.1:1.1: ttyACM2: USB ACM device
[email protected]:~$ adb devices
List of devices attached
4b6bda34 device
In download mode...$dmesg | tail
[email protected]:~$ dmesg | tail
1062.584521] usb 3-1.1: new high-speed USB device number 3 using ehci-pci
[ 1062.693317] usb 3-1.1: New USB device found, idVendor=04e8, idProduct=685d
[ 1062.693328] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1062.693334] usb 3-1.1: Product: MSM8960
[ 1062.693339] usb 3-1.1: Manufacturer: Sasmsung
[ 1062.807263] cdc_acm 3-1.1:1.0: ttyACM0: USB ACM device
[ 1062.807597] usbcore: registered new interface driver cdc_acm
[ 1062.807601] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[email protected]:~$ adb devices
List of devices attached
Not quite sure what to make of this. Especally the spelling of "Samsung" ...the product doesn't match. I don't know why its showing as a CDC_ACM modem. I was toying with the idea of blacklisting it again. But I tried that on my mint distro and it had no effect. ADB also shows no devices but Heimdall detects it. Fastboot also shows no devices during download mode. I'm kind of stuck here. Not sure how to fix this error.
-All drivers are installed
- 51 rules don't fix it
-blacklisting cdc doesn't work
-swapping doesn't work
Anyone have any ideas?
?
http://www.droidviews.com/how-to-extract-pit-file-from-samsung-galaxy-devices/
I have been trying to flash some old M2 Note units and so far I can't get the Preloader to talk over USB:
Code:
[ 1774.167123] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[ 1774.320150] usb 1-1: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
[ 1774.320152] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1774.320153] usb 1-1: Product: MT65xx Preloader
[ 1774.320153] usb 1-1: Manufacturer: MediaTek
[ 1774.344085] cdc_acm 1-1:1.0: Zero length descriptor references
[ 1774.344093] cdc_acm: probe of 1-1:1.0 failed with error -22
[ 1774.384238] cdc_acm 1-1:1.1: ttyACM0: USB ACM device
[ 1776.971989] usb 1-1: USB disconnect, device number 35
I tried adding the vendor ID and product ID to the new_id of the cdc_acm driver and also masking/disabling the ModemManager service in case it was interfering.
I had the same issue on WIndows... it would reset immediately and kick into normal Android mode.
Anyone has any advice? I'm going to trying using the OTA zip with the modified/unlocked images for the preloader.
Flashing TWRP via Flashify did not work out.... rebooted into recovery to the default Meizu one.