android booting problem with binder issue on imx6 sabrelite

[sasidhars]

Hi,

        I am trying to boot android jelly bean on imx6 sabrelite board but the problem is can not able to get desktop environment. Its struck over android splash screen and below is the error displayed. Please help me how to fix this issue.

warning: `zygote' uses 32-bit capabilities (legacy support in use)

request_suspend_state: wakeup (3->0) at 20573687338 (2014-01-07 13:14:31.619795003 UTC)

eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=1:06, irq=284)

ADDRCONF(NETDEV_UP): eth0: link is not ready

acc_open

acc_release

PHY: 1:06 - Link is Up - 100/Full

ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

binder: release 2680:2692 transaction 5952 in, still active

binder: send failed reply for transaction 5952 to 2782:2782

binder: release 2680:2914 transaction 5955 in, still active

binder: send failed reply for transaction 5955 to 2809:2863

binder: release 2680:3013 transaction 5904 out, still active

binder: send failed reply for transaction 6012 to 2998:2998

binder: send failed reply for transaction 6023 to 2915:2962

binder: 2915:2962 transaction failed 29189, size 240-0

binder: 2998:2998 transaction failed 29189, size 2788-4

request_suspend_state: wakeup (0->0) at 30898374005 (2014-01-07 13:14:41.944479003 UTC)

alarm_release: clear alarm, pending 0

binder: release 2884:2972 transaction 4582 out, still active

alarm_release: clear alarm, pending 0

init: untracked pid 2400 exited

binder: release 2405:2405 transaction 5904 in, still active

binder: send failed reply for transaction 5904, target dead

binder: release 2782:2943 transaction 4617 out, still active

init: untracked pid 2927 exited

init: untracked pid 2884 exited

init: untracked pid 3017 exited

init: untracked pid 2782 exited

init: untracked pid 2809 exited

init: untracked pid 2864 exited

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

ERROR: v4l2 capture: slave not found!

binder: release 2946:2958 transaction 4582 in, still active

binder: send failed reply for transaction 4582, target dead

binder: release 2946:2977 transaction 4617 in, still active

binder: send failed reply for transaction 4617, target dead

init: untracked pid 2946 exited

init: untracked pid 2915 exited

init: untracked pid 2680 exited

request_suspend_state: wakeup (0->0) at 35482847340 (2014-01-07 13:14:46.528955005 UTC)

init: untracked pid 3015 exited

acc_open

acc_release

init: untracked pid 2405 exited

binder: release 3358:3507 transaction 9596 out, still active

binder: release 3517:3531 transaction 9596 in, still active

binder: send failed reply for transaction 9596, target dead

binder: release 3517:3555 transaction 9752 in, still active

binder: send failed reply for transaction 9752 to 3455:3547

binder: release 3258:3269 transaction 10337 in, still active

binder: send failed reply for transaction 10337 to 3481:3481

binder: 3481:3481 transaction failed 29189, size 208-0

binder: 3481:3481 transaction failed 29189, size 4324-4

alarm_release: clear alarm, pending 0

alarm_release: clear alarm, pending 0

request_suspend_state: wakeup (0->0) at 43142007674 (2014-01-07 13:14:54.188115006 UTC)

init: untracked pid 3038 exited

init: untracked pid 3037 exited

init: untracked pid 3502 exited

init: untracked pid 3432 exited

init: untracked pid 3417 exited

Thanks & Regards,

sasidhar

[chandrasekharma]

I got one issue regarding booting of android - 5.0.2 lollipop in sabresd-imx6q board.

init: cannot expand '$ro.product.manufacturer' while writing to '/sys/class/android_usb/android0/iManufac'

init: using deprecated syntax for specifying property 'ro.product.model', use ${name} instead

init: property 'ro.product.model' doesn't exist while expanding '$ro.product.model'

init: cannot expand '$ro.product.model' while writing to '/sys/class/android_usb/android0/iProduct'

android_usb: already disabled

read descriptors

read strings

mtp_bind_config

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

binder: 147:147 transaction failed 29189, size 0-0

This binder: 147:147 transaction failed 29189, size 0-0 message keep on occur in my serial terminal but in sabresd board dispaly i didn't get anything...

help me to solve this one thanks in advance

[sasidhars]

Hi Eric,

                  Thanks for your suggestions, Now i can able to boot android. But the problem is adb is not detecting the imx6 sabrelite board. And the output of adb is as follows :

$ adb devices

List of devices attached

0123456789ABCDEF offline

I went through the link https://community.freescale.com/thread/256677 and followed the steps

For Linux PC：

• ADB function
  • Download the Android SDK.
  • Update the adb configuration to scan for freescale's pid:
    • Run the SDK's tools to generate a configure file:

android-sdk-linux_86/tools/android update adb

• Modify the files:~/.android/adb_usb.ini, to add freescale vendor id:

# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x15a2

• Create a new udev rule file under the PC's /etc/udev/rules.d/ named: imx-android.rules. And fill in the following line into the file:

SUBSYSTEM=="usb", SYSFS{idVendor}=="15a2", MODE="0666"

• Change the new udev rule file's permission:

chmod a+r /etc/udev/rules.d/imx-android.rules

• Connect the Android Device
• Restart the adb server
  • adb kill-server
  • adb start-server

i followed the above steps but still iam facing the same issue, Please guide me to fix this issue

Thanks & Regards,

Sasidhar.

[EricNelson]

Hi Sasidhar,

You should see a prompt on your display to authorize your PC to run ADB. The "offline" message seems to indicate "unauthorized".

There's also a way to place a file in the /data partition, but I can't recall off-hand where the file is or where to get the data to place in the file.

[sasidhars]

Hi Eric,

                  I had enabled "USB DEBUGGING" in developer options. When i connect IMX6 board to PC i can see a prompt on display "usb Debugging connected", but still i am getting unauthorized output for adb in PC.

$ adb devices

List of devices attached

0123456789ABCDEF unauthorized

Thanks & Regards,

Sasidhar.

[EricNelson]

Hi Sasidhar,

As an alternative to using the on-screen prompt for authorization, you can also place your public key into /data/misc/adb/adb_keys as described here:

        http://stackoverflow.com/questions/15746917/adb-over-network-without-previous-usb-pairing

Essentially, on your PC:

        ~/$ cat $HOME/.android/adbkey.pub

Then paste the key into /data/misc/adb/adb_keys on the Android machine.

[EricNelson]

Hi Sasidhar,

Have you tried running adb server as root? I typically use this command-line to start ADB on my PC:

     ~/$ sudo `which adb` devices

This is mainly to save on edits to the files in /etc/udev/.

[EricNelson]

Hello Sasidhar,

This type of error normally occurs if the filesystems (esp system) didn't mount properly, and might indicate a problem when creating your SD card or SATA image.

Are you using our (Boundary Devices) Android?

We added code to allow booting to either SD card, so you'll need to ensure that a kernel command-line parameter points at your boot device.

See http://boundarydevices.com/android-jellybean-on-i-mx6-with-no-disclaimers/#sata for details and this section of the boot script for an example:

     android_device_boundary/nitrogen6x/6x_bootscript_jb.txt at boundary-imx_jb4.3_1.0.0-ga · boundarydev...

[sasidhars]

HI Eric,

                            Thanks for your suggestion. I am using imx6-jb-sdcard-20130628.img.gz downloaded from the link http://boundarydevices.com/android-jellybean-on-i-mx6-with-no-disclaimers/#sata and i am flashing it onto the sdcard using the command zcat /home/sasi/android_jb/imx6-jb-sdcard-20130628.img.gz | sudo dd of=/dev/sdb. still i'm facing the same issue (binder issue). The android_log.txt file has been attached for your reference. Waiting for your valuable suggestions.

Thanks & Regards,

Sasidhar

[EricNelson]

Hi Sasidhar,

Using the .img file should configure the filesystem properly, and will include our boot script.

The log you uploaded seems to cut off the end of some long lines, so I can't see the entire kernel command line:

>> Kernel command line: enable_wait_mode=off console=ttymxc1,115200 vmalloc=400M consoleblank=0 video=mxcfb0:dev=hdmi,bpp=32,1280x720M@60,if=RGB24 3

This does appear to be generated using the stock boot script though:

     android_device_boundary/nitrogen6x/6x_bootscript_jb.txt at boundary-imx_jb4.3_1.0.0-beta · boundaryd...

If you put the SD card in your PC, do you see all of the partitions? Does your system auto-mount /system?

Also, can you run "mount" from the shell when trying to boot Android?

What I'm getting at here is that the problem is most likely the SD card image, and specifically the /system partition (P5).

I can see it mount though:

>> EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)

Finally, can you run this command and capture the output for a minute or so?

     # logcat V:* &

This will produce a lot of output, and will likely repeat as Android attempts to re-start, but 60 seconds or so should give an idea of what is crashing.

[sasidhars]

HI Eric,

                  Thanks for your suggestions, My system is auto-mount, when i put SD card in my PC i can able to see all the partitions. And even i can able to run mount from the shell when Android is booting. when i run

# logcat V:* &

Each time i reboot IMX6 sabrelite board, i am getting different errors like

> Process com.android.launcher (pid 4815) has died.

> W/ActivityManager( 3816): Process com.android.phone has crashed too many times: killing!

I searched for NFS boot i got this below link

http://boundarydevices.com/android-r13-4-ga-for-i-mx6-in-stages-stage-1-booting-over-nfs/

but it is mentioned as android_kernel boot but not entire rootfs. Is there any chance to boot android rootfs through NFS.

The logcat ouput file has been attached for your reference. Please help me out in this issue.

[EricNelson]

Did you forget the attachment?

[sasidhars]

Hi Eric,

                   I had attached the document in the previous reply. I am attaching it again for your reference.

Thanks & Regards,

Sasidhar

[EricNelson]

Hello Sasidhar,

I'm not sure why I didn't see the attachment previously. Perhaps there's a delay on the Community site while the scanner runs.

Can you forward the output from "print" at the U-Boot prompt and "netcfg" from the Android shell?

I'm suspicious about this bit from the boot loader:

U-Boot 2013.04-00316-g1903727 (Jul 23 2013 - 11:01:29)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz
Reset cause: POR
Board: SABRE Lite
DRAM:  2 GiB

We don't sell 2GiB versions of SABRE Lite.

Are you sure that you have a 2GiB board?

Can you upload a photo?

[sasidhars]

Hi Eric,

                    I am using IMX6 sabrelite board with DDR 1GB only. And Below mentioned details are the output from "print" at the U-Boot prompt and "netcfg" from the Android shell. I had attached images of IMX6 Sabrelite board which i am using for your reference.

U-Boot > print

baudrate=115200

bootcmd=for dtype in sata mmc ; do for disk in 0 1 ; do ${dtype} dev ${disk} ;for fs in fat ext2 ; do ${fs}load ${dtype} ${disk}:1 10008000 /6x_bootscript&& source 10008000 ; done ; done ; done; setenv stdout serial,vga ; echo ; echo 6x_bootscript not found ; echo ; echo serial console at 115200, 8N1 ; echo ; echo details at http://boundarydevices.com/6q_bootscript ; usb start; setenv stdin serial,usbkbd

bootdelay=1

clearenv=if sf probe || sf probe || sf probe 1 ; then sf erase 0xc0000 0x2000 && echo restored environment to factory default ; fi

console=ttymxc1

ethact=FEC

ethaddr=00:19:b8:01:1d:41

ethprime=FEC

loadaddr=0x12000000

loadsplash=if sf probe ; then sf read ${splashimage} c2000 ${splashsize} ; fi

upgradeu=for dtype in sata mmc ; do for disk in 0 1 ; do ${dtype} dev ${disk} ;for fs in fat ext2 ; do ${fs}load ${dtype} ${disk}:1 10008000 /6x_upgrade && source 10008000 ; done ; done ; done

root@android:/ # netcfg

lo       UP                                   127.0.0.1/8   0x00000049 00:00:00:00:00:00

can0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00

eth0     UP                                192.168.1.32/24  0x00001043 00:19:b8:01:1d:41

tunl0    DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00

sit0     DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00

ip6tnl0  DOWN                                   0.0.0.0/0   0x00000080 00:00:00:00:00:00

root@android:/ # init: untracked pid 2873 exited

request_suspend_state: wakeup (0->0) at 73434213011 (2014-01-11 06:45:39.070027002 UTC)

Thanks & Regards,

Sasidhar.

[EricNelson · Accepted solution]

Hi Sasidhar,

This explains a lot. You're running software for a 2GiB board on a machine with only 1GiB of DDR.

Please use our latest U-Boot package from http://boundarydevices.com/u-boot-2013-10-release/ to re-program things using u-boot.nitrogen6q to fix that.

After fixing this, I suspect things will start working.