topic Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD. in i.MX Processors

mfgtool gets stuck while loading Android 5.0 onto imx6 board based on SabreSD.

jamespieterick — Tue, 10 Nov 2015 22:46:16 GMT

Hi Everyone,

I an working on loading android 5.0.0.1 Lollipop onto our custom board that is based upon the Sabresd reference design. One of the main differences between our design and the Sabre board is that we are using an Atmel maxTouch touchscreen controller connected through the host USB port instead of the max11801 touch sensor connected through i2c.

When I attempt to load android onto our board using mfgtool, the download process appears to progress normally until it starts looping writing the following message over and over:

max11801_ts 1-0048: FIFO_RD_AUX_MSB read fails

I looked through the Android source code and I believe that I found the place where this message originates: line 130 of file max11801_ts.c in directory .../kernel_imx/drivers/input/touchscreen. The above message appears to be printed when the max11801 touch screen fails to respond to an AUX_measurement command sent over the I2C bus. Since the max11801 is not present on our board it makes sense that there is no response. I have removed this file from my build but I am still seeing this problem. Obviously this message is coming from either somewhere else or from a file that I still need to rebuild.

What else might I need to be rebuild so that the code is no longer attempting to communicate with the max11801?

I have rebuilt and replaced all of the .img and .imx files tha are placed into the ...\Profiles\Linux\OS Firmware\files\android\sabresd folder in the folder where mfgtool is located.

I am using mfgtool2-android-mx6q-sabresd-emmc-1.2g.vbs to start mfgtool. and I am attempting to load into emmc.

I am attaching a file with the debug output as well as a copy of the mfgtool log.

Thanks,

Jim Pieterick

Original Attachment has been moved to: mfgtoolDebugOut.txt.zip

Original Attachment has been moved to: MfgTool.log.zip

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

igorpadykov — Wed, 11 Nov 2015 02:04:10 GMT

Hi James

mfg tools firmware is located in Linux\OS Firmware\firmware\

and these files should be rebuilt using description in attached

Yocto Guide sect.6.2 Manufacturing Tool, MFGTool.

Files in ...\Profiles\Linux\OS Firmware\files\android\sabresd

are for writing to media (like sd,emmc,nand).

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Wed, 11 Nov 2015 17:08:02 GMT

Hi Igor,

Are you saying that I need to set up the Yocto project build environment just to build mfgtool? You realize that I am working with Android 5.0 right? This seems like a really messy way to handle this. If this is true developers need to maintain two versions of the files that define the hardware configurations. One in the Yocto build environment and one in the Android build environment.

If I have to setup Yocto, I have a few questions:

- What version of the Yocto project is needed to build a version of the mfgtool that is compatible with Android 5.0 on my custom board?

- Is there a porting guide for Yocto to guide me through the modifications that are required for making mfgtool compatible with my board?

Also, I don't understand why mfgtool would even care about the touch screen on the target unit. It does not use it. The fact that mfgtool can get stuck when failing to communicate with a device it is not going to use is indicative of a bug in my opinion. Mfgtool simply has no reason to call that code.

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

igorpadykov — Thu, 12 Nov 2015 01:32:29 GMT

Hi James

1. version is described in p.3 Release Notes (attached), it is L3.10.53

Task #10 - How to create a custom layer

Best regards

igor

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Thu, 12 Nov 2015 18:13:40 GMT

James,

There are two kernels you need to replace. The mfgtool loads a stock kernel to the memory first. This stock kernel is used to write the real kernel to the flash device. It seems you only replaced the kernel that is to be written to the flash.

Moreover, the stock kernel needs to have the support for the protocol the MFGTOOL is using. No, you don't need yocto to build this. You just need a compiler. You can use the pre-built yocto toolchain for example.

The mfgtool's document folder has a "Manufacturing Tool V2 Linux or Android Firmware Development Guide V2.docx" file that explains the process.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Thu, 12 Nov 2015 22:11:29 GMT

Hi Kursad,

The documents folder that is associated with the version of mfgtool that I have to download android 5.0 does not have "Manufacturing Tool V2 Linux or Android Firmware Development Guide V2.docx" in it. I did find a copy in a documents folder associated with the mfgtool that came with android 4.4.2.1. The problem is that when I look for information about building the mfgtool kernel, I find the following information:

--------------------------------

How to Generate U-Boot and Kernel Image for MFG

Please refer to the BSP User Guide, chapter Build Manufacturing Firmware.

--------------------------------

Is this the wrong version of the document? If so where do I get a copy of the correct version?

With that said I still do not understand why I need to rebuild the mfgtool. The parts of my board that the mfgtool should care about are identical to the sabresd reference design. What's different is the touchscreen and the display.. Mfgtool uses neither of these. I have no trouble loading Android 4.4.2 onto my board with the version of mfgtool that comes with 4.4.2. When I attempt to load Android 5.0, the 5.0 version of mfgtool is attempting to communicate with the max11801 touch screen controller, failing and getting stuck in a apparent infinite loop. My opinion is that this is a bug. The mfgtool does not need the touchscreen to perform a download. It should not be trying to communicate with it and it definitely should not be getting stuck in an infinite loop when it can't communicate with the touchscreen controller. Is there a way for me to open a problem report against this tool?

My next question is this: Would the version of mfgtool that came with Android 4.4.2 work to download the Android 5.0 files? I realize that instead of .bin files the 5.0 load has .imx files. Can I just change the associated ucl.xml file? It seems like that would be a lot easier that figuring out how to fix and then build the 5.0 mfgtool.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

igorpadykov — Fri, 13 Nov 2015 01:52:44 GMT

Hi James

yes in general mfgtool that came with Android 4.4.2 should be able

to program the Android 5.0 files, with necessary ucl.xml modifications.

~igor

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Fri, 13 Nov 2015 14:19:25 GMT

James,

The mfgtool does not try to communicate with the touch controller. It's the kernel that the mfgtool loads that does this. The mfgtool follows a two step process:

1. It first loads a minimal u-boot and kernel for your board. For SabreSD, our team has prepared a kernel for this purppose. For your board, you need to prepare one. This kernel can be mostly identical to your normal kernel, except it needs to include the FSL serial download protocol + initramfs.

2. This minimal kernel then downloads the Android images (which include the *real* kernel that will ultimately run on your board). The minimal kernel then uses commands like dd, cp, fdisk, etc. to write the images onto the flash device on your board.

As you can see the mfgtool does not and cannot have a universal minimal kernel that will work on every board. The minimal kernel for SabreSD likely is not optimized for non-touchscreen operation so that's why it fails to work on your board. That said, if the 4.4.2 minimal kernel is working for you, you should be able to replace it with the one that ships with 5.0.0. Or as you asked, you can do the opposite. You can use the 4.4.2 downloader to download the 5.0.0 images.

The first way (using 5.0.0 downloader) :

You can find these minimal kernel/device tree/u-boot files in the Profiles\Linux\OS Firmware\firmware directory. zImage is the kernel file. The device tree file depends on the board and the configuration you are using. For example, zImage--3.10.53-r0-imx6q-sabresd-20150105054653.dtb is the device tree for the quad/dual version of imx6, running on SabreSD. Please see the BootStrap section of the profile you are using in ucl2.xml file for the file names.

The second way (using the 4.4.2 downloader) :

In this case, I am pretty sure you really don't have to replace the u-boot.bin files to u-boot.imx files. All you need to replace is boot-*.img, system.img and recovery-*.img files. You can compare the "Updater" section of the profile you are using in ucl2.xml and see if any of the images are written differently, but I wouldn't expect so.

In the long run, you have a couple of options:

1. Keep using mfgtool, and create your own minimal kernel etc.

2. There is also an open source third party tool called imx_usb_loader if you are more comfortable with linux than Windows. This is not as comprehensive as the mfgtool, but the idea is the same. You load a binary (in their case, u-boot) to the memory using the download protocol. Then you use this binary to write the real images on to the flash.

Let me know if this helps.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Sat, 14 Nov 2015 00:38:10 GMT

Hi All,

I tried option 2 and I could not get it to work. I get as far as the following:

UTP: received command '$ echo 1 > /sys/block/mmcblk3boot0/force_ro'

UTP: executing "echo 1 > /sys/block/mmcblk3boot0/force_ro"

sh: can't create /sys/block/mmcblk3boot0/force_ro: nonexistent directory

UTP: sending Non-success to kernel for command $ echo 1 > /sys/block/mmcblk3boot0/force_ro.

utp_poll: exit with status 256

I am not sure what the issue is with this; I tried adding some mkdir commands to create /sys/block/mmcblk3boot0 but the system would not let me create it. I am not sure what the issue is here. An ideas?

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Sat, 14 Nov 2015 21:22:57 GMT

James,

You cannot create directories in the /sys folder. This is a special filesystem that holds information exported by the kernel. Here is one document that talks about it:

https://www.kernel.org/pub/linux/kernel/people/mochel/doc/papers/ols-2005/mochel.pdf

What is your boot device? If it's not mmcblk3, then you need to modify the ucl2.xml file to reflect the boot device you are using.

However, if you just replaced the boot/system/recover img files, and if you are normally able to use the 4.4.2 mfgtool, this should not have happened. Either you inadvertently replaced another file or something on your board has changed. Can you try this:

1. Start with a vanilla 4.4.2 mfgtool and load android 4.4.2 on your board. Make sure this works.

2. Still using the 4.4.2 mfgtool, replace the 3 img files in the Profiles\Linux\OS Firmware\files\android\<board name> folder with the 5.0.0 versions for your board. Also replace u-boot-<board>.imx with the u-boot for your board. Make sure to save the originals, and the new ones are named exactly the same as the old ones.

Let me know if this doesn't work and where it fails.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 00:15:56 GMT

Kursad,

I was able to do step 1 without a problem. Mfgtool is able to load Android Kitkat onto my board successfully.

I then removed everythingt from ucl2.xml that did not appear to be involved in loading android onto the board. I reran mfgtool to verify that I did not break the download. Andoid 4.4 downloaded and ran successfully.

I trimmed down the Android 5.0 version of the ucl2.xml file. I verified that I can use it to successfully download to the Sabre board. I am attaching both ucl2.xml files. I have been using a vbscript to call the mfgtool for 5.0 I am also attaching that file.

When I attempted step 2 I did the following:

- I replace files boot.mg, ramdisk.img, recovery.img and system.img with the files from my 5.0 build.

- I replaced uboot-6q.bin with u-boot-imx6q.imx.

- I modified ucl2.xml so that the reference to uboot-6q.bin is replaced with a reference to uboot-imx6.imx.

Mfgtool appears to run successfully with this setup but when I try to actually run Android on my board it does not even start printing on the debug port. I suspect that the problem is related to the fact that the ucl2.xml file for Lollipop used mccblk3 and my modified one uses mmcblk0. I tried replacing all of the references to mccblk0 with references to mmcblk3 as well as replacing references to mmc0 with mmc3 but that did not help. I am not sure at this point what I should try next. Do you have any suggestions?

Thanks,

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Tue, 17 Nov 2015 16:08:56 GMT

James,

mmcblk number is just how the kernel iterates the interfaces. If you have a single MMC/SD device, then only writing to only one will work. If you have multiple, you need to choose the correct one obviously. Do you have more than one?

If you have only a single interface and the mfgtool succeeded, the problem is with the u-boot image you are writing.

I'm guessing you did this, but please don't forget to set the boot mode back to emmc from serial download mode. If you have done this, can you attach the USB cable to the OTG port and see if the unit goes back into the serial download mode even if it's set to "boot from emmc?" If that's the case, that means the bootrom couldn't find a valid boot image or device. If not, it was able to locate u-boot on the correct device, but u-boot is faulty.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 16:25:06 GMT

Hi Kursad,

I am seeing the symptom that you describe where the mfgtool sees the unit as an HID-compliant device when the boot switches are set to eMMC boot mode.. So it looks like the bootrom couldn't find a valid image. My suspicion is that I am downloading the boot image to the wrong location. Do you have any suggestions as to how I correct this?

Thanks,

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Tue, 17 Nov 2015 16:37:09 GMT

Can you re-run the process using the 4.4.2 mfgtool + 5.0 images and send me these two files:

* The board's console log during the whole process.

* mfgtool.log file that's generated in the mfgtool's root directory.

I can look at these and see if I can spot anything.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 16:59:32 GMT

Hi Krysad,

Here are the logs that you've asked for.

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 17:20:10 GMT

Hi Kursad,

I just performed the same exercise with the 5.0 version of Mfgtool and the Sabre board. In this case I am using the ucl2.xml file that I attached above as ucl2-Lollipop.xml. I am attaching the the log files.

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 17:23:47 GMT

Hi Kursad,

I also noticed that I did not attach the ucl2.xml file that I am using with the 4.4.2 mfgtool. I thought that I had done that previously. I am attaching it now.

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Tue, 17 Nov 2015 18:58:23 GMT

James,

The logs look OK. Your board has only one mmc device, so all mmc writes are correct. There are some differences in the partition map of 4.4.2 and 5.0, but these shouldn't cause a boot failure as far as I can tell.

Let's try the following. I'm attaching a boot tester program. After you flash your 5.0 image with the 4.4.2 tool, set the boot mode to eMMC and connect the USB cable to your PC. As you said it won't boot and will go to the serial download mode. Do not launch the mfgtool. Instead, using the utility attached, from a DOS window, type:

Boot_Tester.exe -t mx6x -df test.inc

This will connect to the board and will read the boot log. It should tell us which device it's trying to boot from and why the boot process failed. Please copy paste that output and attach it here.

Meanwhile I'll look into the logs you attached some more and see if I can see any issues.

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

jamespieterick — Tue, 17 Nov 2015 20:52:09 GMT

Hi Kursad,

When I ran the tool this is what was printed to the command prompt window:

Microsoft Windows [Version 6.1.7601]

C:\Users\admin>cd C:\Users\admin\Desktop\chess\Mfgtools-Rel-13.01.00_ER_MX6Q_UPD

ATER_test3\Boot Tester

C:\Users\admin\Desktop\chess\Mfgtools-Rel-13.01.00_ER_MX6Q_UPDATER_test3\Boot Te

ster>Boot_Tester.exe -t mx6x -df test.inc

MX6DQ opened.

HAB_TYPE: DEVELOP

Image loading...

download Image to IRAM OK

Re-open MX6x device.

Running BOOT DEBUG., press "ESC" key to exit.

Jim Pieterick

Re: mfgtool gets stuck while loading Android 5.0 onto imx6 board base on SabreSD.

KursadOney — Tue, 17 Nov 2015 21:38:48 GMT

It doesn't show the boot log. Can you put the board in serial download mode and see if you can see the boot log that way?

You should see something like this: