i.MX50 software update by recovery mode in Android

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.MX50 software update by recovery mode in Android

1,274 Views
PeterChan
NXP Employee
NXP Employee

Hello All,

 

I am working on a i.MX508 EVK board and trying to boot it into recovery mode for software update. My u-boot parameters is listed below:

bootargs=console=ttymxc0 init=/init androidboot.console=ttymxc0 keypad video=mxc_elcdif_fb:off no_console_suspend

bootargs_recovery=setenv bootargs ${bootargs} root=/dev/mmcblk0p4 rootfs=ext4

bootcmd=run bootcmd_recovery

Kernel command line:

console=ttymxc0 init=/init androidboot.console=ttymxc0 keypad video=mxc_elcdif_fb:off no_console_suspend root=/dev/mmcblk0p4 rootfs=ext4

 

However, the recovery mode always run into this error and no software update can be performed.

mxc_rtc mxc_rtc.0: setting system clock to 1970-01-01 00:23:57 UTC (1437)
EXT4-fs (mmcblk0p4): recovery complete
EXT4-fs (mmcblk0p4): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext2 filesystem) on device 179:4.
Freeing init memory: 196K
init: cannot open '/initlogo.rle'
init: Unable to open persistent property directory /data/property errno: 2
enabling adb
mxc_epdc_fb mxc_epdc_fb: Flush updates timeout! ret = 0x0
mxc_epdc_fb mxc_epdc_fb: Flush updates timeout! ret = 0x0
EXT4-fs (mmcblk0p6): recovery complete
EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts:

 

Has anyone met this problem before? Any clue about this error? I am using i.MX Android R10.3 release.

 

Thanks,

Peter

Labels (1)
0 Kudos
1 Reply

542 Views
PeterChan
NXP Employee
NXP Employee

I am able to get rid of the "Unable to open persistent property directory /data/property errno: 2" by mounting the recovery.img as loop device and create the /data/property directory to recovery.img. However, recovery mode still does not boot. The "exclamation" image is still showing on the eink panel. I tested i.MX50 eink prebuild image and it also get the same error. Have I made something wrong with the boot parameters in recovery mode?

Thanks,

Peter

0 Kudos