iMX6Q SABRE SD: can't boot from eMMC with default images from freescale

[floriang]

Hi

     I am not able to boot to android using the image provided on freescale website for eMMC:

Below are my steps:

1. Copy the following files in release_package/image_*/sabresd_6dq to your MFGTool-Dir/Profiles/MX6Q Linux

Update/OS Firmware/files/android/ directory.

  eMMC/boot.img

  u-boot-6q.bin and renamed it to u-boot.bin

  eMMC/system.bin

  eMMC/recovery.bin

2. Change the SABRE SD SW6 (boot) to 00001100 (from 1-8 bit) to enter download mode.

3. And download the images by MFGTool

4. Download sucessful.

5.Change Boot Switch (SW6) to 11010110 (from 1-8 bit) to switch the board back to eMMC boot mode.

6. Reset

7. Tried to set/change environment variables according to the Android_User_Manual.pdf

Please help,

thanks.

Attached is the log messages

Original Attachment has been moved to: putty.log.zip

[jeffreyhsu]

Dear floriang,

I have same problem,

Are you into Android shell now? 

How do you slove this probem?

Is modify "u-boot commands" ? 

I check JB422_110 FAQ , and fill the u-boot commands :

setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0

video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x17b00000

gpumem=96M vmalloc=400M androidboot.console=ttymxc0

but the problem is exist.

What are you change?

Could you kindly tell me? 

Thanks a lot.

[floriang]

Hello Jeffrey,

Depending on the board the image may not work. I was successful using Sabre "Platform (the ones with the LCD attached), but I have only one Sabre Board, working correctly with Jellybean image
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=RDIMX6SABREBRD&fpsp=1&tab=Design_Tool...

(android_jb4.2.2_1.1.0-ga_image_bundle.tar.gz)

I suggest you try the android images of the link above with a Sabre "Platform" if you didn't try yet, and try starting another thread if you still have troubles.

[jeffreyhsu]

Dear Floriang,

Thanks your quick respond.

I am devlopment on our board similar with SABRE board.

I base on the android_jb4.2.2_1.1.0-ga_image_bundle.tar.gz to devlopment.

But our board only 512MB.

so I set my u-boot command line as below:

MX6SDL SABRESD U-Boot > printenv

bootdelay=3

baudrate=115200

ipaddr=192.168.1.103

serverip=192.168.1.101

netmask=255.255.255.0

loadaddr=0x10800000

rd_loadaddr=0x11000000

netdev=eth0

ethprime=FEC0

splashimage=0x30000000

splashpos=m,m

lvds_num=1

ethact=FEC0

bootargs=console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x17b00000 gpumem=96M vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale ldb=sin0

stdin=serial

stdout=serial

stderr=serial

fastboot_dev=mmc2

bootcmd=booti mmc2

You seem OK on JB422_110, but I am failure.

Do you use same u-boot command line?

(PS: our display is output to LVDS0, so I set ldb=sin0)

Below is stop debug message of my image:

ehci_fsl_bus_suspend begins, Host 1

ehci_fsl_bus_suspend ends, Host 1

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

request_suspend_state: wakeup (3->0) at 20502714005 (1970-01-02 00:00:08.690542668 UTC)

eth0: no PHY, assuming direct connection to switch

PHY 0:00 not found

eth0: could not attach to PHY

acc_open

acc_release <

[floriang]

Hi!

I was not able to get anything working with ICS, so I gave a try to jellybean.

Jellybean woks fine, and I was able to compile an engineering build of android and write to the eMMC by following the user guide.

I think ICS is broken.

[LeonardoSandova · Accepted solution]

The first line of your log has weird characters but I was able to read it with vim. the eMMC image should work out of the box. Just to make sure, what are the u-boot commands you executed? There is a newer version of JB422_110, try it also.

Leo

[floriang]

Edit2:

Using exactly the same steps and the jellybean images (4.2.2) from freescale, I can write successfully to eMMC or SD card, and everything seems to work fine.

Is the ICS image from freescale broken?

I will try to compile my own image to see if it changes anything...

Edit:

I am using the r13.4.1 image (with ICS).

Also I tried to write to the SD card with the manufacturing tools without success.

From the sd card, I am able to boot to the OS sometimes, but the OS freezes after 1-2minute.

When the OS freeze, I get the kind of messages below:

binder: release 2506:2506 transaction 20667 out, still active

binder: 2387:2667 transaction failed 29189, size 584-8

binder: 2988:2999 transaction failed 29189, size 292-0

binder: release 2988:2988 transaction 21177 out, still active

request_suspend_state: sleep (0->3) at 163926767689 (1970-01-02 00:02:16.179447349 UTC)

stop_drawing_early_suspend: timeout waiting for userspace to stop drawing

binder: release 2387:2665 transaction 21178 out, still active

binder: release 2387:2665 transaction 21177 in, still active

binder: release 2387:2666 transaction 21224 in, still active

binder: send failed reply for transaction 21224 to 2837:2858

binder: release 2387:3009 transaction 21208 in, still active

binder: send failed reply for transaction 21208 to 3011:3011

binder: 2837:2858 transaction failed 29189, size 532-0

alarm_release: clear alarm, pending 0

alarm_release: clear alarm, pending 0

alarm_release: clear alarm, pending 0

request_suspend_state: wakeup (3->0) at 171893651356 (1970-01-02 00:02:24.146329683 UTC)

binder: release 2272:2272 transaction 20667 in, still active

binder: send failed reply for transaction 20667, target dead

binder: release 2272:2372 transaction 21178 in, still active

init: untracked pid 2269 exited

init: untracked pid 2272 exited

....

init: untracked pid 2596 exited

request_suspend_state: wakeup (0->0) at 178214894357 (1970-01-02 00:02:30.467573685 UTC)

acc_open

acc_release