i.MX ProcessorsのトピックRe: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Thu, 07 Sep 2017 07:35:08 GMT

Hi,

First, the mfg tool works well while the size of system.img less than 320MB.

But i want to put some prebuilt apk into system, the sparse system.img size grow to 327MB.

I have configured the BOARD_SYSTEMIMAGE_PARTITION_SIZE envrionment var in device/fsl/imx6/BoardConfigCommon.mk as 460MB、512MB and so on.I also even changed the

mksdcard-android.sh to change system partition size to 600MB、800MB、1GB and so on,the error always comes.

I think it is a bug of simg2img tool through the uart log.

I attach the picture, please analysis this problem.Thanks!

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Fri, 08 Sep 2017 03:33:36 GMT

anyone who care?

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Fri, 08 Sep 2017 09:30:57 GMT

anyone? you may try to reproduce this with sparse system image.

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Mon, 11 Sep 2017 01:12:13 GMT

Top of this discussion!

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

BiyongSUN — Mon, 11 Sep 2017 02:26:26 GMT

It should be the memory size issue on your board. It could not hold the system.img convert to ram on the board.

Try to convert the system image on your host. And burn the ram image.

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Mon, 11 Sep 2017 05:45:24 GMT

I have tried it, but after download done.

During bootup, init process can not mount the system partition.Maybe the dd command has broken the

ext4 super block(<CMD state="Updater" type="push" body="$ dd if=$FILE of=/dev/mmcblk%mmc%p5 bs=512">writting sparse system.img</CMD>).but i think the non sparse system.img is a formated image, i even can

mount the system.img on host.

Here is the android5.1 boot error log:

JBD2: no valid journal superblock found
EXT4-fs (mmcblk3p5): error loading journal
fs_mgr: __mount(source=/dev/block/mmcblk3p5,target=/system,type=ext4)=-1
fs_mgr: Failed to mount an un-encryptable or wiped partition on/dev/block/mmcblk3p5 at /system options: barrier=1 error: Invalid argument.

Do you kown why?

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Mon, 11 Sep 2017 06:03:13 GMT

I modified the ucl2.xml like this:

body="pipe dd of=/dev/mmcblk%mmc%p5 bs=512" file="../../../neo/system.img"

and it boot success now.

But is there any difference between the two commands?

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

houyong — Mon, 11 Sep 2017 08:27:36 GMT

Hi Biyong Sun,

I want to know about the difference between "pipe dd" and "dd", thank you!

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

BiyongSUN — Fri, 22 Sep 2017 05:11:36 GMT

The if pipe is not used, the whole file need to send to the memory, which is ramdisk.

That will consumer the lots of memory. Could be the problem for hardware design with small memory volume.

The pipe is as named, it will use the pipe. The entire file don't need to be sent.

The pipe command is filed in the mfg tool document.

Have you read that before you are alway asking here?

In the document, it uses the blod words. Do you notice that?

Document\V2\Manufacturing Tool V2 UCL User Guide.docx

pipe

string require file attribute

Execute shell command and read data from stdio pipe IN. mfg will send file to stdio pipe OUT. It is useful for big data transfer, more than physical memory size <CMD type="push" body="pipe tar -xv -C /mnt/ubi0" file="files/rootfs.tar"/> <CMD type="push" body="flush">Finish Flashing NAND</CMD>

Note: The above two commands must be combined to use

Recommend: Please add below command prior to pipe command to free some memory.

<CMD type="push" body="$ echo 3 > /proc/sys/vm/drop_caches">release memory</CMD>

Re: imx6q-sabresd program android5.1 system.img fail with mfgtool(2.3.3 & 2.6.2)

3401848300 — Wed, 13 Jun 2018 02:56:12 GMT

another example from IMX6_L5.1_2.1.0_MFG_TOOL:

<CMD state="Updater" type="push" body="pipe dd of=/dev/mmcblk%mmc%p5 bs=512" file="files/android/%folder%/system_raw.img">writting sparse system.img</CMD>