topic Enter Android recovery mode use external sdcard %>_<% in i.MX Processors

Enter Android recovery mode use external sdcard %>_<%

JayZhang — Tue, 08 May 2012 05:18:23 GMT

Hi all,

I want to go to android recovery mode on our mx53 board, the recovery.img is flashed into mmcblk1p4 partition, then I set the uboot environment as below:

setenv bootargs 'console=ttymxc0 init=/init root=/dev/mmcblk1p4 rootfs=ext4 video=mxcdi1fb:RGB666,XGA ldb=di1 di1_primary'

Flash image cmd as below:

mkfs.ext4 /dev/sdb4 -O ^extent -L recovery
dd if=/home/jay/Desktop/mx53_img/image/recovery.img of=/dev/sdb4; sync

But I get the error message:

regulator_init_complete: incomplete constraints, leaving DA9052_LDO3 on
regulator_init_complete: incomplete constraints, leaving DA9052_LDO1 on
mxc_rtc mxc_rtc.0: setting system clock to 1970-01-02 02:02:40 UTC (93760)
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mmcblk1p4" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
b300 3866624 mmcblk0 driver: mmcblk
b301 3866616 mmcblk0p1
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<8004f58c>] (unwind_backtrace+0x0/0xf0) from [<80489cfc>] (panic+0x6c/0xe0)
[<80489cfc>] (panic+0x6c/0xe0) from [<80008e34>] (mount_block_root+0x1cc/0x20c)
[<80008e34>] (mount_block_root+0x1cc/0x20c) from [<8000908c>] (prepare_namespace+0x128/0x180)
[<8000908c>] (prepare_namespace+0x128/0x180) from [<80008484>] (kernel_init+0x124/0x16c)
[<80008484>] (kernel_init+0x124/0x16c) from [<8004b9e0>] (kernel_thread_exit+0x0/0x8)
mmc1: Timeout waiting for hardware interrupt.
mxsdhci: ============== REGISTER DUMP ==============
mxsdhci: Sys addr: 0x00000000 | Version: 0x00001201
mxsdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001
mxsdhci: Argument: 0x00000000 | Trn mode: 0x00000000
mxsdhci: Present: 0xff880008 | Host ctl: 0x00000121
mxsdhci: Clock: 0x000010ff
mxsdhci: Int stat: 0x00000000
mxsdhci: Int enab: 0x117f010f | Sig enab: 0x117f000f
mxsdhci: Caps: 0x07f30000
mxsdhci: ===========================================
android_usb gadget: high speed config #1: android
android_usb gadget: high speed config #1: android
android_usb gadget: high speed config #1: android

I think my action is right, anyone help me?

Sorry for my poor English...

Thanks...

Re: Enter Android recovery mode use external sdcard %>_<%

JayZhang — Wed, 09 May 2012 02:53:11 GMT

Anyone had the same problem...

>.<

Re: Enter Android recovery mode use external sdcard %>_<%

charleschang — Fri, 11 May 2012 07:51:52 GMT

from these msg:

VFS: Cannot open root device "mmcblk1p4" or unknown-block(2,0)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<8004f58c>] (unwind_backtrace+0x0/0xf0) from [<80489cfc>] (panic+0x6c/0xe0)
[<80489cfc>] (panic+0x6c/0xe0) from [<80008e34>] (mount_block_root+0x1cc/0x20c)
[<80008e34>] (mount_block_root+0x1cc/0x20c) from [<8000908c>] (prepare_namespace+0x128/0x180)
[<8000908c>] (prepare_namespace+0x128/0x180) from [<80008484>] (kernel_init+0x124/0x16c)
[<80008484>] (kernel_init+0x124/0x16c) from [<8004b9e0>] (kernel_thread_exit+0x0/0x8)
mmc1: Timeout waiting for hardware interrupt.
mxsdhci: ============== REGISTER DUMP ==============
mxsdhci: Sys addr: 0x00000000 | Version: 0x00001201
mxsdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001
mxsdhci: Argument: 0x00000000 | Trn mode: 0x00000000
mxsdhci: Present: 0xff880008 | Host ctl: 0x00000121
mxsdhci: Clock: 0x000010ff
mxsdhci: Int stat: 0x00000000
mxsdhci: Int enab: 0x117f010f | Sig enab: 0x117f000f
mxsdhci: Caps: 0x07f30000
mxsdhci: ===========================================

I guess the card cannot be mount correctly....

change another may be OK.

Re: Enter Android recovery mode use external sdcard %>_<%

JayZhang — Sun, 13 May 2012 11:51:40 GMT

Dear Charles,

I have changed another one, I flashed the recovery.img into mmc0blk4, it works, but I just want to use the mmcblk1p4 partition, where I can config this?

Thanks for your rep and sorry for my poor English...

charles chang said:

from these msg:
VFS: Cannot open root device "mmcblk1p4" or unknown-block(2,0)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<8004f58c>] (unwind_backtrace+0x0/0xf0) from [<80489cfc>] (panic+0x6c/0xe0)
[<80489cfc>] (panic+0x6c/0xe0) from [<80008e34>] (mount_block_root+0x1cc/0x20c)
[<80008e34>] (mount_block_root+0x1cc/0x20c) from [<8000908c>] (prepare_namespace+0x128/0x180)
[<8000908c>] (prepare_namespace+0x128/0x180) from [<80008484>] (kernel_init+0x124/0x16c)
[<80008484>] (kernel_init+0x124/0x16c) from [<8004b9e0>] (kernel_thread_exit+0x0/0x8)
mmc1: Timeout waiting for hardware interrupt.
mxsdhci: ============== REGISTER DUMP ==============
mxsdhci: Sys addr: 0x00000000 | Version: 0x00001201
mxsdhci: Blk size: 0x00000000 | Blk cnt: 0x00000001
mxsdhci: Argument: 0x00000000 | Trn mode: 0x00000000
mxsdhci: Present: 0xff880008 | Host ctl: 0x00000121
mxsdhci: Clock: 0x000010ff
mxsdhci: Int stat: 0x00000000
mxsdhci: Int enab: 0x117f010f | Sig enab: 0x117f000f
mxsdhci: Caps: 0x07f30000
mxsdhci: ===========================================

I guess the card cannot be mount correctly....

change another may be OK.