Android ADB

[Michaël Javault]

Hi all,
I'm having trouble setting up ADB for debugging android on the pico-sam9g45.
When I connect the board to my computer (Windows 7 x64) using the microUSB port, no ADB interface shows up, only the following devices:
- Linux File-CD Gadget USB Device
- USB Mass Storage device
- Mobile device (F:\)
It looks like the devices is not in the proper mode (UMS instead of ADB), but ADB is properly enabled in Android.
What am I missing?
I'm using the latest stable android version (2.3 stable 2 - based on kernel version 3.1 (2012-03-13)).
Thanks a lot for your help,
Mike

[Nicu Pavel]

Hi,

On 3.1 kernel and Android 2.3 Android is setup by this commands (taken
from init.rc):

write /sys/class/android_usb/android0/enable 0
write /sys/class/android_usb/android0/functions adb
write /sys/class/android_usb/android0/enable 1

(write is actually an echo "value" > "path")

So might worth checking is functions are setup (cat
/sys/class/android_usb/android0/functions) and if enable is 1

Nicu

[Michaël Javault]

Hi Nicu,
Thanks for your reply.
I don't have the /sys/class/android_usb folder, that should explain why usb is not working.
Any idea?
I've also noticed that the UMS devices appears as soon as I plug the board (long before Android has finished booting). Would the bootloader be responsible for this?
I'll try playing around with the latest BOOT.bin and uImage and see if that changes anything.
Mike

[Nicu Pavel]

> Hi Nicu,
> Thanks for your reply.
> I don't have the /sys/class/android_usb folder, that should explain why usb
> is not working.
> Any idea?
> I've also noticed that the UMS devices appears as soon as I plug the board
> (long before Android has finished booting). Would the bootloader be
> responsible for this?
> I'll try playing around with the latest BOOT.bin and uImage and see if that
> changes anything.

Also check if Drivers->USB->USB Gadget Support -> USB Gadget Drivers
(Android Gadget) is enabled in your kernel config.

I will check the Android images posted to see if it's included in the
default build.

Nicu

[Michaël Javault]

Hi Nicu,
I've replaced the uImage from the "2.3 stable 2 - based on kernel version 3.1" archive (http://arm.mini-box.com/releases/android-2.3-gingerbread-kernel-3.1-2012-03-13.zip) with the latest precompiled from http://arm.mini-box.com/releases/kernel_bootstrap/latest/uImage and it works (the device is recognized as an Android ADB interface).
Oh, and just so you know, the BOOT.bin from http://arm.mini-box.com/releases/kernel_bootstrap/latest/BOOT.BIN weights 0 octets (but I've successfully compiled it from sources).
Mike

[ekrem_hb]

I am changed to new uImage for 2.3 stable 2 (ve for windows 7 adb
problem)

but touch calibration is not work always force close
what is the problem

On 18 Nisan, 20:17, Michaël Javault <michael.java...@gmail.com> wrote:
> Hi Nicu,
> I've replaced the uImage from the "2.3 stable 2 - based on kernel version

> 3.1" archive (http://arm.mini-box.com/releases/android-2.3-gingerbread-kernel-3.1-2...)
> with the latest precompiled fromhttp://arm.mini-box.com/releases/kernel_bootstrap/latest/uImageand it

> works (the device is recognized as an Android ADB interface).

> Oh, and just so you know, the BOOT.bin fromhttp://arm.mini-box.com/releases/kernel_bootstrap/latest/BOOT.BINweights 0