topic Re: Having trouble with mfg-tool in i.MX Processors

Having trouble with mfg-tool

jsherman10 — Mon, 23 May 2016 07:16:42 GMT

Hello, I just purchased a imx6-qp and I'm trying to load Android 5.0.0 for a research project. I have downloaded the prebuilt core image and the mfg tool. I then extracted the images to the appropriate directory according to the quick start guide ( switched the board to download mode and connected the usb cable to the otg port). I'm trying to boot Android from the SD Card. I ran the correct .vbs file and it clicked on start and it seems to be stuck on loading u-boot. Any thoughts?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 08:39:49 GMT

Hi Jonathan,

there might be may cases why it don't work. Please check these:

- size of SD card

- lock switch on SD card

- change SD card

- correct slot for SD card

- newest version of MfgTool

- try to flash into NAND

Hope it helps.

Michal

Re: Having trouble with mfg-tool

jsherman10 — Mon, 23 May 2016 08:44:04 GMT

The size of the SD card is 32 GB. The lock switch is not set. The MFG tool I downloaded is android_ L5.0.0_1.0.0-ga_tools.tar.gz.

I'm running windows 8 and all of my USB slots are 3.0. Do you think that's what is causing the problem?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 08:54:04 GMT

Jonathan,

please try to use 4/8GB SD card. Make sure that SD card is formatted to 512Bytes per block.

Michal

Re: Having trouble with mfg-tool

jsherman10 — Mon, 23 May 2016 09:01:21 GMT

Alright, and sorry I'm new to this, how can I format the SD Card to 512Bytes per block?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 09:05:13 GMT

I'm using this tool SD Card Formatter - SD Association under windows. MfgTool formats SD card automatically when you loading new image but there might be problem with your 32GB SD card.

Michal

Re: Having trouble with mfg-tool

jsherman10 — Mon, 23 May 2016 09:08:16 GMT

Okay, I've also tried to partition the card using Linux and running the mksdcard-android sript, and I get the following error:

1+0 records in

1+0 records out

1024 bytes (1.0 kB) copied, 0.000261848 s, 3.9 MB/s

Checking that no-one is using this disk right now ...

BLKRRPART: Device or resource busy

This disk is currently in use - repartitioning is probably a bad idea.

Umount all file systems, and swapoff all swap partitions on this disk.

Use the --no-reread flag to suppress this check.

Disk /dev/sdc: 29476 cylinders, 64 heads, 32 sectors/track

sfdisk: ERROR: sector 0 does not have an msdos signature

/dev/sdc: unrecognized partition table type

Old situation:

No partitions found

Warning: given size (28412) exceeds max allowable size (28372)

New situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdc1 0+ 15 16- 16383+ 83 Linux

/dev/sdc2 16 23 8 8192 83 Linux

/dev/sdc3 24 1103 1080 1105920 5 Extended

/dev/sdc4 1104 29515 28412 29093888 83 Linux

/dev/sdc5 24+ 535 512- 524287+ 83 Linux

/dev/sdc6 536+ 1047 512- 524287+ 83 Linux

/dev/sdc7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdc8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdc9 1062+ 1063 2- 2047+ 83 Linux

Warning: partition 4 extends past end of disk

Successfully wrote the new partition table

Re-reading the partition table ...

BLKRRPART: Device or resource busy

The command to re-read the partition table failed.

Run partprobe(8), kpartx(8) or reboot your system now,

before using mkfs

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

Checking that no-one is using this disk right now ...

BLKRRPART: Device or resource busy

This disk is currently in use - repartitioning is probably a bad idea.

Umount all file systems, and swapoff all swap partitions on this disk.

Use the --no-reread flag to suppress this check.

Disk /dev/sdc: 29476 cylinders, 64 heads, 32 sectors/track

Old situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdc1 0+ 15 16- 16383+ 83 Linux

/dev/sdc2 16 23 8 8192 83 Linux

/dev/sdc3 24 1103 1080 1105920 5 Extended

/dev/sdc4 1104 29515 28412 29093888 83 Linux

/dev/sdc5 24+ 535 512- 524287+ 83 Linux

/dev/sdc6 536+ 1047 512- 524287+ 83 Linux

/dev/sdc7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdc8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdc9 1062+ 1063 2- 2047+ 83 Linux

New situation:

Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0

Device Boot Start End MiB #blocks Id System

/dev/sdc1 8 15 8 8192 83 Linux

/dev/sdc2 16 23 8 8192 83 Linux

/dev/sdc3 24 1103 1080 1105920 5 Extended

/dev/sdc4 1104 29515 28412 29093888 83 Linux

/dev/sdc5 24+ 535 512- 524287+ 83 Linux

/dev/sdc6 536+ 1047 512- 524287+ 83 Linux

/dev/sdc7 1048+ 1055 8- 8191+ 83 Linux

/dev/sdc8 1056+ 1061 6- 6143+ 83 Linux

/dev/sdc9 1062+ 1063 2- 2047+ 83 Linux

Warning: partition 4 extends past end of disk

Successfully wrote the new partition table

Re-reading the partition table ...

BLKRRPART: Device or resource busy

The command to re-read the partition table failed.

Run partprobe(8), kpartx(8) or reboot your system now,

before using mkfs

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

Do you think that could also because the SD Card could be potentially bad?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 09:12:20 GMT

If I see your log, there is 1024bytes per block. Please use another card.

Michal

Re: Having trouble with mfg-tool

jsherman10 — Mon, 23 May 2016 09:15:37 GMT

Okay, I also tried to use the MFG Tool to boot from EMMC as well, and I was still getting the same error. Does the SD Card need to be present on the board even if I download the images to EMMC?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 10:54:22 GMT

No, If you writing image to eMMC SD card does not need to be presented. And what about 8pin DIP switch configuration? Did you configure it correctly?

Re: Having trouble with mfg-tool

mike_susen — Mon, 23 May 2016 11:00:13 GMT

I have one another point. You are using Android 5.0.0 but this is not supported by Quad+ chip. i.MX6QP is supported since Android 6.0. So please use Android 6.0 Instead of 5.0.0.

Michal