i.MX ProcessorsのトピックRe: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Wed, 26 Feb 2014 07:58:06 GMT

By using "setenv bootcmd booti mmc2" followed by a successful "saveenv", we can boot the droid JB demo binary successful w/ the iMX6Q-SD board.

However, after doing "reset" or power on again, we found that the env variable "bootcmd" has been changed to some other value and device can't boot.

Here is the successful boot case:

Hit any key to stop autoboot: 0

MX6Q SABRESD U-Boot > setenv bootcmd booti mmc2

MX6Q SABRESD U-Boot > saveenv

Saving Environment to MMC...

Writing to MMC(2)... done

MX6Q SABRESD U-Boot > boot

kernel @ 10808000 (4724232)

Here is the env after "reset" or reboot, the boot will fail (w/ a droid icon with a !! mark shown on the screen):

MX6Q SABRESD U-Boot > printenv

...

bootcmd=run bootcmd_android_recovery

bootcmd_android_recovery=booti mmc2 recovery

It seems that the successful boot was from boot partition of mmc2 (SD3 on the board), but the changed value is from recovery partition.

Hope someone can give some pointers here about how to fix it.

I am using the following commands to prepare the 8GB SD card:

dd if=u-boot-6q.bin of=/dev/sdb bs=1K skip=1 seek=1

dd if=SD/boot.img of=/dev/sdb1;

dd if=SD/system.img of=/dev/sdb5;

dd if=SD/recovery.img of=/dev/sdb2;

The image I am using is "android_jb4.3_1.1.0-ga_image_6qsabresd.tgz"

Regards,

yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 27 Feb 2014 02:22:37 GMT

Hi Feng,

Can you attach your whole uboot environment? And how do you create your SD card partitions?

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 27 Feb 2014 02:56:48 GMT

Dan,

Here are the "printenv" dump, the boot log is also attached.

MX6Q 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

bootcmd_android_recovery=booti mmc2 recovery

ethact=FEC0

fastboot_dev=mmc2

bootargs=console=ttymxc0,115200 init=/init video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=28M androidboot.hardware=freescale androidboot.console=ttymxc0 vmalloc=400M no_console_suspend=1

stdin=serial

stdout=serial

stderr=serial

bootcmd=run bootcmd_android_recovery

As for the SD card partition, I did it using the "mksdcard-android.sh" tool within the MGFtools tarball got from freescale site.

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 27 Feb 2014 06:24:05 GMT

Hi Feng,

When you power on the board ,set the uboot environment the bootcmd should be set ''setenv bootcmd booti mmc2'. You can have a try~~

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 27 Feb 2014 06:31:01 GMT

Dan,

Yes I know that setenv thing, but my question was after using the "setenv bootargs ..." and "saveenv", the device can boot successfully once, then upon another reboot, the param changed back to the recovery I shared with you.

Do you have any hints about why the param changed to recovery mode?

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 27 Feb 2014 08:05:34 GMT

Hi Feng,

Bootargs env is an optional setting for booti. The boot.img includes a default bootargs, which will be used if there is no definition of the bootargs env.

To clear the bootargs env and set up

the booting from SD card in SD slot 3, you can use the following command:

U-Boot > setenv fastboot_dev mmc2 [eMMC as fastboot deivce]

U-Boot > setenv bootcmd booti mmc2 [Load the boot.img from SD card]

U-Boot > setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32

video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M

androidboot.console=ttymxc0 androidboot.hardware=freescale

U-Boot > saveenv

When you boot the board, the default environment in boot.img is booting from eMMC. So I suggest you to boot from eMMC first.

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 27 Feb 2014 08:09:31 GMT

Hi Feng,

I will try to the boot JB4.3 on the iMX6Q-SD board from SD card. Then I will give you reply.

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Tue, 04 Mar 2014 08:27:20 GMT

Hi Feng,

I have tested on my board with the same environment with you, It works OK. But I download the image to board by MFGTool not dd commends. I think the problem happened when you downloaded image to your board. When you download by dd commends, you missed sync. Maybe you can try the following to download again.

dd if=u-boot-6q.bin of=/dev/sdb bs=1K skip=1 seek=1; sync

dd if=SD/boot.img of=/dev/sdb1;sync

dd if=SD/system.img of=/dev/sdb5; sync

dd if=SD/recovery.img of=/dev/sdb2;sync
By the way, I recommend you to use the MFGTool to download, I think it's more convenient. Which you can download from freescale for free, the link is SABRE Platform for Smart Devices Based on the i.MX 6 Series and it's under Programmers, the name is IMX_6DQ_MFG_TOOL.

Hope this can help you. If any question contact us~~

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Tue, 04 Mar 2014 13:35:18 GMT

Dan,

Thank you. I did use "sync" after each dd command but I didn’t put it on the ticket for simplicity.

I will retry later.

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 06 Mar 2014 02:07:18 GMT

Hi Feng,

Have you solved your problem?

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 06 Mar 2014 02:11:46 GMT

Dan,

Sorry I haven’t got a chance to try it again yet. I will update later when there is a chance for it.

Thank you for querying.

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 06 Mar 2014 04:09:09 GMT

Dan,

I found in my log that:

i2c: I2C3 SDA is low, start i2c recovery...

I2C3 Recovery success

Found PFUZE100! deviceid=10,revid=11

Recovery key pressed

Recovery command file founded!

recovery on bootdev: 6

setup env for recovery..

This probably tells that the boot loader detects that "recovery key pressed" thus it enters recovery mode. Maybe your device doesn’t have this behavior.

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 06 Mar 2014 05:45:20 GMT

Hi Feng,

Which board are you using? You designed?

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 06 Mar 2014 06:07:43 GMT

Dan,

The model is "MCIMX6Q-SDB", looks like a standard one from freescale. It has an on-board built-in SanDisk 8GB storage as mmc:0 but I am using a SD card which is mmc:2.

The boot DIP is set as 01000010 which means to boot from the SD.

I tried again with a newly prepared SD card, the situation is still the same. I guess somehow my card is entering "recovery" mode.

Regards,

Yanfeng

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 06 Mar 2014 06:23:48 GMT

Hi Feng,

It's strange, I can see that your setting is correct. Have you tried to download the android demo image to your board by MFGTool ?

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Thu, 06 Mar 2014 06:40:43 GMT

Dan,

Not yet. I though "dd" is direct and simple than such tools so I didn’t try it.

Is that MFGtool trying to download image files to the internal eMMC, or the SD card?

Should I adjust the boot DIP to something else?

Regards,

Yanfeng

Re: Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Thu, 06 Mar 2014 06:56:17 GMT

Hi Feng,

You can download image to both eMMC and SD card. It depends on your setting. It's easy and exact clearly to watch the download process.

When you want to download, you should change the SW6 to00001100 (from 1-8 bit) download mode. And when you want to boot, you have to change it to boot mode.

You can refer to the file I attached you.

Best Regards

Dan

Re: Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

martinhowell — Thu, 06 Mar 2014 16:55:11 GMT

If you are using the uboot that comes with the JB 4.2 you will find that it always overwrites the bootcmd with the string booti mmc3. I had to change uboot to stop this behavior. I dont know if this is the same in JB 4.3 or if there is a similar thing when booting in recovery mode.

Look in the file /bootable/bootloader/uboot-imx/board/freescale/mx6q_sabresd/mx6q_sabresd.c around line 1900, you can see it forces the env variable every board init.

int board_late_init(void)

{

int ret = 0;

#ifdef MX6Q_SABRESD_ANDROID_H

switch (get_boot_device()) {

case SD_BOOT:

setenv("fastboot_dev", "mmc2");

setenv("bootcmd", "booti mmc2");

break;

case MMC_BOOT:

setenv("fastboot_dev", "mmc3");

setenv("bootcmd", "booti mmc3");

break;

default:

printf("unsupported boot devices\n");

break;

}

#endif

#ifdef CONFIG_I2C_MXC

setup_i2c(CONFIG_SYS_I2C_PORT);

i2c_bus_recovery();

ret = setup_pmic_voltages();

if (ret)

return -1;

#endif

return 0;

}

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

Rita_Wang — Mon, 10 Mar 2014 05:48:36 GMT

Hi Feng,

Have you solved your problem now ?

Best Regards

Dan

Re: bootcmd env changed after a successful boot of JB4.3 demo binary w/ iMX6Q-SD board

yanfengliu — Mon, 10 Mar 2014 05:54:54 GMT

Dan

Unfortunately no.

We've given up this since it is only for a POC project.

Regards,

Yanfeng