ADB over windows problem

ilhoon shin

I ported the gingerbread to beagle-xm.

I tried to install the ADB on WinowsXP according to the TI gingerbread's user guide.

But, It is not working.

After installing the ADB, there is an error message "cannot start the device normally".

I cannot access the board with the command "adb devices".

there is none attached.

Even after reinstalling the windows, the symptom is the same.

I am wondering that the guide is out-of-date or something..

Anyone, have an idea to fix the problem?

Thank you.

over 12 years ago

0 Vishveshwar Bhat over 12 years ago

TI__Genius 10210 points

Which TI Android DevKit Release are you using?

Could you post the kernel logs from Beagleboard when you attach and detatch the USB cable. This may provide us some clues.

Suggest you attach the full logs from power-up itself.

0 ilhoon shin over 12 years ago in reply to Vishveshwar Bhat

Dear Bhat,

Thank you for the reply.

I used TI-Android-GingerBread-2.3.4-DevKit-2.1 UserGuide.

In order to add the cp210x module for the USB-serial converter, I compiled uImage and boot.scr according to TI-Android-GingerBread-2.3.4-DevKit-2.1 DeveloperGuide.

I am afraid that the problem is the adb.exe installed in windows.

When I install the new hardware, there was an error message that the hardware cannot be started normally.

I am using WindowsXP-Korean version, so I roughly translated the error message to English.

And, when I open the device manager, ! is attached to "Android ADB Interface, which means the ADB interface cannot be started.

The below is the kernel logs of the beagle board.

----------- capture --------------

Texas Instruments X-Loader 1.51 (Jan 8 2013 - 17:34:06)
Unsupported Chip!
Beagle xM Rev C
Starting X-loader on MMC
Reading boot sector

213256 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...

U-Boot 2010.06 (Jan 08 2013 - 17:36:11)

OMAP34xx/35xx-GP ES2.1, CPU-OPP2 L3-165MHz
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 384 MiB
NAND: HW ECC [Kernel/FS layout] selected
0 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial
Beagle xM Rev A/C
Die ID #365c00029ff80000016849a905028014
Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0
mmc1 is available
reading boot.scr

455 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

2763904 bytes read
***** Kernel: /dev/mmcblk0p1/uImage *****
***** RootFS: /dev/mmcblk0p2 *****
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2763840 Bytes = 2.6 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (jeje0247@ubuntu-vmware) (gcc version 4.4.3 (GCC) ) #1 Wed Jan 9 12:07:12 KST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3 Beagle Board
Reserving 8388608 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 62976
Kernel command line: console=ttyO2,115200n8 androidboot.console=ttyO2 mem=256M root=/dev/mmcblk0p2 rw rootfstype=ext3 rootdelay=1 init=/init ip=off omap_vout.vid1_static_vrfb_alloc=y vram=8M omapfb.vram=0:8M
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 248MB = 248MB total
Memory: 245260k/245260k available, 16884k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc003c000 ( 208 kB)
.text : 0xc003c000 - 0xc053a000 (5112 kB)
.data : 0xc053a000 - 0xc057ee40 ( 276 kB)
NR_IRQS:409
Clocking rate (Crystal/Core/MPU): 26.0/400/600 MHz
Reprogramming SDRC clock to 400000000 Hz
dpll3_m2_clk rate change failed: -22
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
GPMC revision 5.0
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install interrupt handler for IRQ407
Trying to install interrupt handler for IRQ408
Trying to install type control for IRQ409
Trying to set irq flags for IRQ409
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
omap_mux_init: Add partition: #1: core, flags: 0
OMAP3 Beagle Rev: xM C
Found NAND on CS0
Registering NAND on CS0
Unable to get DVI reset GPIO
hw-breakpoint: debug architecture 0x4 unsupported.
OMAP DMA hardware revision 5.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev4.0 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
regulator: VSIM: 1800 <--> 3000 mV at 1800 mV normal standby
regulator: VAUX3: 1800 mV normal standby
regulator: VAUX4: 1800 mV normal standby
omap_i2c omap_i2c.2: bus 2 rev4.0 at 400 kHz
omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
omap_device: omap_i2c.3: new worst case deactivate latency 0: 30517
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource 32k_counter
musb-hdrc: version 6.0, otg (peripheral+host), debug=0
musb-hdrc musb-hdrc.0: dma type: dma-inventra
musb-hdrc musb-hdrc.0: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
omap-iommu omap-iommu.0: isp registered
AM37x/DM37x Linux PSP version 04.02.00.07 (OMAP3BEAGLE)
ashmem: initialized
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 479
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
omap_uart.3: ttyO3 at MMIO 0x49042000 (irq = 80) is a OMAP UART3
brd: module loaded
loop: module loaded
omap_device: omap_i2c.1: new worst case activate latency 0: 30517
mtdoops: mtd device (mtddev=name/number) must be supplied
omap2-nand driver initializing
No NAND device found.
No NAND device found.
OneNAND driver initializing
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap.0 supply hsusb0 not found, using dummy regulator
ehci-omap.0 supply hsusb1 not found, using dummy regulator
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.37 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for cp210x
usbcore: registered new interface driver cp210x
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
android init
android_probe pdata: c0549f2c
android_bind
android_usb gadget: android_usb ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
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.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
f_acm init
android_register_function acm
f_adb init
android_register_function adb
adb_bind_config
f_mass_storage init
android_register_function usb_mass_storage
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
input: twl4030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
Linux media interface: v0.10
Linux video capture interface: v2.00
omap3isp supply VDD_CSIPHY1 not found, using dummy regulator
omap3isp supply VDD_CSIPHY2 not found, using dummy regulator
omap3isp omap3isp: Revision 15.0 found
omap-iommu omap-iommu.0: isp: version 1.1
mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
isp_register_subdev_group: Unable to register subdev mt9v113
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
twl4030_wdt twl4030_wdt: Failed to register misc device
twl4030_wdt: probe of twl4030_wdt failed with error -16
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
OMAP3 Beagle/Devkit8000 SoC init
usb 1-2: new high speed USB device using ehci-omap and address 2
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
#0: omap3beagle
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000
usb 1-2: New USB device found, idVendor=0424, idProduct=9514
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 01:30:55 UTC (946690255)
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 15
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 16
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.63 GiB
mmcblk0: p1 p2 p3
usb 1-2.1: new high speed USB device using ehci-omap and address 3
usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 66:6c:49:21:ce:d2
usb 1-2.4: new low speed USB device using ehci-omap and address 4
usb 1-2.4: New USB device found, idVendor=046d, idProduct=c326
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.4: Product: USB Keyboard
usb 1-2.4: Manufacturer: Logitech
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.0/input/input2
generic-usb 0003:046D:C326.0001: input: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-ehci-omap.0-2.4/input0
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2.4:1.1/input/input3
generic-usb 0003:046D:C326.0002: input: USB HID v1.10 Device [Logitech USB Keyboard] on usb-ehci-omap.0-2.4/input1
usb 1-2.5: new low speed USB device using ehci-omap and address 5
usb 1-2.5: New USB device found, idVendor=0461, idProduct=4d16
usb 1-2.5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 1-2.5: Product: USB Optical Mouse
input: USB Optical Mouse as /devices/platform/ehci-omap.0/usb1/1-2/1-2.5/1-2.5:1.0/input/input4
generic-usb 0003:0461:4D16.0003: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-ehci-omap.0-2.5/input0
EXT3-fs: barriers not enabled
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): 1 truncate cleaned up
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 208K
init: /init.rc: 135: invalid command 'device'
init: /init.rc: 136: invalid command 'device'
init: /init.rc: 137: invalid command 'device'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
enabling adb
adb_open
# musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status

---------after disconnect the cable -------------------------
musb android_usb gadget disconnected.
warning: `zygote' uses 32-bit capabilities (legacy support in use)

---------after connecting the cable, no message --------------------
---------after disconnect the cable again -------------------------
musb android_usb gadget disconnected.
binder: release proc 1323, transaction 2342, not freed
binder: release proc 1357, transaction 2412, not freed
binder: release proc 1357, transaction 2405, not freed
binder: release proc 1357, transaction 2425, not freed
binder: release proc 1357, transaction 2430, not freed
---------after connecting the cable, no message --------------------

0 ilhoon shin over 12 years ago in reply to ilhoon shin

I attach the captured message of the board when I first installed the ADB in windows.

In the end of the message, there is an error message.

I hope you can find some clue in this capture.

Thank you.

usb usb1: Manufacturer: Linux 2.6.37 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for cp210x
usbcore: registered new interface driver cp210x
cp210x: v0.09:Silicon Labs CP210x RS232 serial adaptor driver
android init
android_probe pdata: c0549f2c
android_bind
android_usb gadget: android_usb ready
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 2
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.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
f_acm init
android_register_function acm
f_adb init
android_register_function adb
adb_bind_config
f_mass_storage init
android_register_function usb_mass_storage
mice: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
input: twl4030_pwrbutton as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl40
30_pwrbutton/input/input1
using rtc device, twl_rtc, for alarms
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
omap_device: omap_i2c.1: new worst case deactivate latency 0: 30517
i2c /dev entries driver
Linux media interface: v0.10
Linux video capture interface: v2.00
omap3isp supply VDD_CSIPHY1 not found, using dummy regulator
omap3isp supply VDD_CSIPHY2 not found, using dummy regulator
omap3isp omap3isp: Revision 15.0 found
omap-iommu omap-iommu.0: isp: version 1.1
mt9v113 2-003c: chip id mismatch read 0x0, expecting 0x2280
isp_register_subdev_group: Unable to register subdev mt9v113
omap_device: omap_wdt.-1: new worst case activate latency 0: 30517
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
twl4030_wdt twl4030_wdt: Failed to register misc device
twl4030_wdt: probe of twl4030_wdt failed with error -16
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com

usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
usb 1-2: new high speed USB device using ehci-omap and address 2
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
OMAP3 Beagle/Devkit8000 SoC init
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
#0: omap3beagle
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000
usb 1-2: New USB device found, idVendor=0424, idProduct=9514
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:01:44 UTC (946684904)
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 15
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 16
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.63 GiB
mmcblk0: p1 p2 p3
usb 1-2.1: new high speed USB device using ehci-omap and address 3
usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx U
SB 2.0 Ethernet, 32:5e:df:2d:ae:9e
usb 1-2.2: new full speed USB device using ehci-omap and address 4
usb 1-2.2: New USB device found, idVendor=10c4, idProduct=ea60
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.2: Product: CP2102 USB to UART Bridge Controller
usb 1-2.2: Manufacturer: Silicon Labs
usb 1-2.2: SerialNumber: 0001
cp210x 1-2.2:1.0: cp210x converter detected
usb 1-2.2: reset full speed USB device using ehci-omap and address 4
usb 1-2.2: cp210x converter now attached to ttyUSB0
usb 1-2.4: new low speed USB device using ehci-omap and address 5
EXT3-fs: barriers not enabled
usb 1-2.4: New USB device found, idVendor=046d, idProduct=c326
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.4: Product: USB Keyboard
usb 1-2.4: Manufacturer: Logitech
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2
.4:1.0/input/input2
generic-usb 0003:046D:C326.0001: input: USB HID v1.10 Keyboard [Logitech USB Key
board] on usb-ehci-omap.0-2.4/input0
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2
.4:1.1/input/input3
generic-usb 0003:046D:C326.0002: input: USB HID v1.10 Device [Logitech USB Keybo
ard] on usb-ehci-omap.0-2.4/input1
usb 1-2.5: new low speed USB device using ehci-omap and address 6
usb 1-2.5: New USB device found, idVendor=0461, idProduct=4d16
usb 1-2.5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 1-2.5: Product: USB Optical Mouse
input: USB Optical Mouse as /devices/platform/ehci-omap.0/usb1/1-2/1-2.5/1-2.5:1
.0/input/input4
generic-usb 0003:0461:4D16.0003: input: USB HID v1.11 Mouse [USB Optical Mouse]
on usb-ehci-omap.0-2.5/input0
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 208K
init: /init.rc: 135: invalid command 'device'
init: /init.rc: 136: invalid command 'device'
init: /init.rc: 137: invalid command 'device'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instea
d.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
enabling adb
# adb_open
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
warning: `zygote' uses 32-bit capabilities (legacy support in use)
binder: release 1414:1449 transaction 2756 out, still active
binder: release 1414:1450 transaction 2762 out, still active
binder: release 1414:1451 transaction 2782 out, still active
binder: 1287:1304 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2782, target dead
binder: 1287:1356 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2762, target dead
binder: 1287:1299 transaction failed 29189, size 28-4
binder: send failed reply for transaction 2756, target dead

Texas Instruments X-Loader 1.51 (Jan 8 2013 - 17:34:06)
Unsupported Chip!
Beagle xM Rev C
Starting X-loader on MMC
Reading boot sector

213256 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader...

U-Boot 2010.06 (Jan 08 2013 - 17:36:11)

In: serial
Out: serial
Err: serial
Beagle xM Rev A/C
Die ID #365c00029ff80000016849a905028014
Hit any key to stop autoboot: 0
mmc1 is available
reading boot.scr

455 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage

Starting kernel ...

usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
usb 1-2: new high speed USB device using ehci-omap and address 2
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
usbcore: registered new interface driver snd-usb-audio
OMAP3 Beagle/Devkit8000 SoC init
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
#0: omap3beagle
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
SmartReflex Class3 initialized
clock: disabling unused clocks to save power
platform mpu.0: omap_voltage_scale: Already at the requestedrate 600000000
usb 1-2: New USB device found, idVendor=0424, idProduct=9514
usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-2:1.0: USB hub found
hub 1-2:1.0: 5 ports detected
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:05:33 UTC (946685133)
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 15
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 16
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.63 GiB
mmcblk0: p1 p2 p3
usb 1-2.1: new high speed USB device using ehci-omap and address 3
usb 1-2.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
smsc95xx v1.0.4
smsc95xx 1-2.1:1.0: usb0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx U
SB 2.0 Ethernet, 66:6c:49:21:ce:d2
usb 1-2.2: new full speed USB device using ehci-omap and address 4
usb 1-2.2: New USB device found, idVendor=10c4, idProduct=ea60
usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.2: Product: CP2102 USB to UART Bridge Controller
usb 1-2.2: Manufacturer: Silicon Labs
usb 1-2.2: SerialNumber: 0001
cp210x 1-2.2:1.0: cp210x converter detected
usb 1-2.2: reset full speed USB device using ehci-omap and address 4
usb 1-2.2: cp210x converter now attached to ttyUSB0
usb 1-2.4: new low speed USB device using ehci-omap and address 5
EXT3-fs: barriers not enabled
usb 1-2.4: New USB device found, idVendor=046d, idProduct=c326
usb 1-2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.4: Product: USB Keyboard
usb 1-2.4: Manufacturer: Logitech
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2
.4:1.0/input/input2
generic-usb 0003:046D:C326.0001: input: USB HID v1.10 Keyboard [Logitech USB Key
board] on usb-ehci-omap.0-2.4/input0
input: Logitech USB Keyboard as /devices/platform/ehci-omap.0/usb1/1-2/1-2.4/1-2
.4:1.1/input/input3
generic-usb 0003:046D:C326.0002: input: USB HID v1.10 Device [Logitech USB Keybo
ard] on usb-ehci-omap.0-2.4/input1
usb 1-2.5: new low speed USB device using ehci-omap and address 6
usb 1-2.5: New USB device found, idVendor=0461, idProduct=4d16
usb 1-2.5: New USB device strings: Mfr=0, Product=2, SerialNumber=0
usb 1-2.5: Product: USB Optical Mouse
input: USB Optical Mouse as /devices/platform/ehci-omap.0/usb1/1-2/1-2.5/1-2.5:1
.0/input/input4
generic-usb 0003:0461:4D16.0003: input: USB HID v1.11 Mouse [USB Optical Mouse]
on usb-ehci-omap.0-2.5/input0
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 208K
init: /init.rc: 135: invalid command 'device'
init: /init.rc: 136: invalid command 'device'
init: /init.rc: 137: invalid command 'device'
init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instea
d.
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
enabling adb
adb_open
# warning: `zygote' uses 32-bit capabilities (legacy support in use)
binder: release 1312:1312 transaction 2124 out, still active
binder: 1098:1302 transaction failed 29189, size 744-0
binder: send failed reply for transaction 2124, target dead
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
musb android_usb gadget disconnected.
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status
musb_g_ep0_irq 799: SETUP packet len 0 != 8 ?
musb_g_ep0_irq 707: SetupEnd came in a wrong ep0stage out/status

0 Manuel Contreras over 12 years ago in reply to ilhoon shin

TI__Genius 10545 points

You could try isolating the issue, some suggestions are

1. using latest Android SDK from android.com. Some times using a very old release from the PC and newer for Android release leads to fails.

2. using a Linux PC, to discard an issue with PC's Operating System.

3. using one Android FS release up or one down, to see if it was a newly introduced issue.

5. if you are using customizations try removing those and check if device/adb are ok.

6. check that you are using correct USB port at device, or remove any HUB in between to check.

at the end of the log there are 2 or 3 error indicating that something went wrong went started, it could be that adbd is getting instable.

init : /init.rc: 135: invalid command 'device'

init : /init.rc: 136: invalid command 'device'

init : /init.rc: 137: invalid command 'device'

Processors

Processors forum

ADB over windows problem