AnsweredAssumed Answered

could not update u-boot command line via mfgtool

Question asked by tsung li wang on Aug 30, 2018
Latest reply on Mar 14, 2019 by tsung li wang

Hi community,

I'm working on i.MX6 Quad sabre-SD platform and build Android 6 for my image.

Now I have faced strange phenomenon.

Here is the situation.


I update my image via mfgtool.

And below is my u-boot burning part in ucl2.xml.

<!-- burn uboot -->
<CMD state="Updater" type="push" body="$ dd if=/dev/zero of=/dev/mmcblk%mmc% bs=1k seek=768 conv=fsync count=512">clear u-boot arg</CMD>
<CMD state="Updater" type="push" body="$ echo 0 > /sys/block/mmcblk%mmc%boot0/force_ro">access boot partition 1</CMD>
<CMD state="Updater" type="push" body="send" file="files/android/%folder%/u-boot-imx%soc%%ldo%.imx" >Sending u-boot.bin</CMD>
<CMD state="Updater" type="push" body="$ dd if=$FILE of=/dev/mmcblk%mmc%boot0 bs=512 seek=2 ">write U-Boot to sd card</CMD>
<CMD state="Updater" type="push" body="$ echo 1 > /sys/block/mmcblk%mmc%boot0/force_ro"> re-enable read-only access </CMD>

After burning image, mfgtool would show green bar to be success.

So I booting my machine and get into u-boot environment console to check whether u-boot command line has been changed correctly or not.

But I find out that u-boot command line did not change to latest version.

But the time did update like below picture

If picture is too small, could see original picture attached below.


In the red block shows time that your u-boot updated.

And blue block shows my u-boot command line.


Red block did update time so I assume that my u-boot burned the image well.

But Blue block did not change to what I set in my source code.


How can I fix this problem?

How can I change my u-boot command line?


Thanks in Advanced!