Android Boot problem (SD card SABRE AI imx6q)

dmitriipetrov — Tue, 29 Sep 2015 16:56:09 GMT

I'm novice in setting boards, so please help

I have Ubuntu 14.04, and SABRE AI board (imx6 quad)

I have downloaded android_L5.0.0_1.0.0-ga_images_6qsabreauto.tar.gz

and followed instructions from document "Android User's Guide.pdf", but actually board wasn't loading.

I have created SD card, using "sudo mksdcard-android.sh /dev/sdb"

There wasn't no output from U_boot, so i changed image of uboot to one from mfgtools/Profiles/Linux/OS Firmware/firmware "u-boot-imx6qsabreauto_sd.imx"

Currently, i can't boot android, and i don't know why, because it seems, that i made SD card ok

I can enter uboot and i see "freescale" on my LCD

LOG SD:

sudo ./mksdcard-android.sh /dev/sdb

1+0 records in

1+0 records out

1024 bytes (1,0 kB) copied, 0,011853 s, 86,4 kB/s

Checking that no-one is using this disk right now ...

Disk /dev/sdb: 15193 cylinders, 64 heads, 32 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature

/dev/sdb: unrecognized partition table type

Old situation:

No partitions found

Warning: given size (14129) exceeds max allowable size (14089)

New situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdb1 0+ 15 16- 16383+ 83 Linux

/dev/sdb2 16 23 8 8192 83 Linux

/dev/sdb3 24 1103 1080 1105920 5 Extended

/dev/sdb4 1104 15232 14129 14468096 83 Linux

/dev/sdb5 24+ 535 512- 524287+ 83 Linux

/dev/sdb6 536+ 1047 512- 524287+ 83 Linux

/dev/sdb7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdb8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdb9 1062+ 1063 2- 2047+ 83 Linux

Warning: partition 4 extends past end of disk

Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

Checking that no-one is using this disk right now ...

BLKRRPART: Device or resource busy

This disk is currently in use - repartitioning is probably a bad idea.

Umount all file systems, and swapoff all swap partitions on this disk.

Use the --no-reread flag to suppress this check.

Disk /dev/sdb: 15193 cylinders, 64 heads, 32 sectors/track

Old situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdb1 0+ 15 16- 16383+ 83 Linux

/dev/sdb2 16 23 8 8192 83 Linux

/dev/sdb3 24 1103 1080 1105920 5 Extended

/dev/sdb4 1104 15232 14129 14468096 83 Linux

/dev/sdb5 24+ 535 512- 524287+ 83 Linux

/dev/sdb6 536+ 1047 512- 524287+ 83 Linux

/dev/sdb7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdb8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdb9 1062+ 1063 2- 2047+ 83 Linux

New situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdb1 8 15 8 8192 83 Linux

/dev/sdb2 16 23 8 8192 83 Linux

/dev/sdb3 24 1103 1080 1105920 5 Extended

/dev/sdb4 1104 15232 14129 14468096 83 Linux

/dev/sdb5 24+ 535 512- 524287+ 83 Linux

/dev/sdb6 536+ 1047 512- 524287+ 83 Linux

/dev/sdb7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdb8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdb9 1062+ 1063 2- 2047+ 83 Linux

Warning: partition 4 extends past end of disk

Successfully wrote the new partition table

Re-reading the partition table ...

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

dmitrii@dmitrii-Predator-G3-605:~/test/android_5_freescale/image_to_flash$ sudo dd if=u-boot-imx6qsabreauto_sd.imx of=/dev/sdb bs=1K seek=1; sync

407+0 records in

407+0 records out

416768 bytes (417 kB) copied, 0,816086 s, 511 kB/s

dmitrii@dmitrii-Predator-G3-605:~/test/android_5_freescale/image_to_flash$ sudo dd if=boot

boot.img boot-imx6q.img

dmitrii@dmitrii-Predator-G3-605:~/test/android_5_freescale/image_to_flash$ sudo dd if=boot-imx6q.img of=/dev/sdb1; sync

14844+1 records in

14844+1 records out

7600384 bytes (7,6 MB) copied, 1,79037 s, 4,2 MB/s

dmitrii@dmitrii-Predator-G3-605:~/test/android_5_freescale/image_to_flash$ sudo dd if=system.img of=/dev/sdb5; sync

737240+0 records in

737240+0 records out

377466880 bytes (377 MB) copied, 38,9548 s, 9,7 MB/s

dmitrii@dmitrii-Predator-G3-605:~/test/android_5_freescale/image_to_flash$ sudo dd if=recovery.img of=/dev/sdb2; sync

15916+1 records in

15916+1 records out

8149248 bytes (8,1 MB) copied, 2,66373 s, 3,1 MB/s

Although, 'boot' command isn't working

U-Boot 2014.04 (Jan 05 2015 - 14:55:34)

CPU: Freescale i.MX6Q rev1.2 at 792 MHz

CPU: Temperature 40 C, calibration data: 0x5824d47d

Reset cause: POR

Board: MX6-Sabreauto revA

I2C: ready

DRAM: 2 GiB

NAND: 0 MiB

MMC: FSL_SDHC: 0, FSL_SDHC: 1

No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In: serial

Out: serial

Ericeid=10,revid=11

mmc1 is current device

Net: FEC [PRIME]

Normal Boot

=> boot

Re: Android Boot problem (SD card SABRE AI imx6q)

Yuri — Mon, 05 Oct 2015 05:28:57 GMT

Hello,

Have You followed exactly instructions in section 4 (Working with the
i.MX 6Quad/6DualLite SABRE-AI Platform) of “Android_Quick_Start_Guide.pdf” ?

Is it possible to look at console log of the i.MX6 target during deploy process?

Have a great day,
Yuri

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

i.MX ProcessorsのトピックRe: Android Boot problem (SD card SABRE AI imx6q)

Android Boot problem (SD card SABRE AI imx6q)

Re: Android Boot problem (SD card SABRE AI imx6q)