MY-IMX6 MfgTool User Guide
目录
Identify the system you need
The main reason to confirm the system you need is to avoid downloading unnecessary files and waste time waiting to download.Currently, the total size of all file systems is over 5G, and we may only need one of them, usually no more than 400M.
Confirm your target system version according to the model of the evaluation board
For example, the development board is MY-IMX6-EK200 .In the system version supported in the following table, the target operating system version that needs to be burned isLinux-3.14.52.The next step is to determine the file system you want based on the system version.
| Evaluation board | Supported Linux versions | ||||
|---|---|---|---|---|---|
| Linux-3.0.35 | Linux-3.14.52 | Linux-4.1.15 | |||
| MY-IMX6-EK140 | √ | ||||
| MY-IMX6-EK140P | √ | ||||
| MY-IMX6-EK200 | √ | √ | √ | ||
| MY-IMX6-EK314 | √ | √ | √ | ||
| MY-IMX6-EK336 | √ | √ | |||
| Evaluation board | Supported Android versions | ||||
|---|---|---|---|---|---|
| Android-4.2.2 | Android-4.4.2 | Android-5.1.1 | |||
| MY-IMX6-EK140 | |||||
| MY-IMX6-EK140P | |||||
| MY-IMX6-EK200 | √ | √ | √ | ||
| MY-IMX6-EK314 | √ | √ | |||
| MY-IMX6-EK336 | √ | ||||
Select the corresponding file system of the system
For example, in the previous step, I chose Linux-3.14.52，In the table below, I found Linux-3.14.52，I chose the file system I needed and wrote down the file name of the file system.This file is the file that needs to be downloaded later in the network disk.
| Operating System | Corresponding file system support | ||
|---|---|---|---|
| File system description | File system file name | The size of file system | |
| Linux-3.0.35 | minuscule Linux | rootfs-linux-minimal.tar.bz2 | 6.9MB |
| Regular Linux | rootfs-linux.tar.bz2 | 64.4MB | |
| Linux + QT4.8.5 | rootfs-linux-qt4.tar.bz2 | 90.8MB | |
| Ubuntu 12.04 | ubuntu-12.04.tar.bz2 | 1.45GB | |
| Linux-3.14.52 | minuscule Linux | distro-core-image-base.tar.bz2 | 21.4MB |
| Regular Linux | distro-fsl-image.tar.bz2 | 227MB | |
| Linux + QT5.5.0 | distro-fsl-imx-fb-image-qt5.tar.bz2 | 304MB | |
| Ubuntu 16.04 无GUI | armhf-rootfs-ubuntu-xenial.tar.bz2 | 176MB | |
| Ubuntu 16.04 LXDE GUI | armhf-rootfs-ubuntu-xenial-lxde.tar.bz2 | 838MB | |
| Linux-4.1.15 | minuscule Linux (MYIMX6A9) | core-image-base-myimx6a9.tar.bz2 | 25.4MB |
| Regular Linux (MYIMX6A9) | fsl-image-linux-myimx6a9.tar.bz2 | 201MB | |
| Linux + QT5.6.1 (MYIMX6A9) | fsl-image-qt5-myimx6a9.tar.bz2 | 376MB | |
| minuscule Linux (MYIMX6A7) | core-image-base-myimx6a7.tar.bz2 | 24.3MB | |
| Regular Linux (MYIMX6A7) | fsl-image-linux-myimx6a7.tar.bz2 | 120MB | |
| Linux + QT5.6.1 (MYIMX6A7) | fsl-image-qt5-myimx6a7.tar.bz2 | 158MB | |
| Android-4.2.2 | Android 4.2.2 (MYIMX6EK200) | system-ard422-myimx6ek200.img | 280MB |
| Android-4.4.2 | Android 4.4.2 (MYIMX6EK200) | system-ard442-myimx6ek200.img | 360MB |
| Android 4.4.2 (MYIMX6EK314) | system-ard442-myimx6ek314.img | 360MB | |
| Android-5.1.1 | Android 5.1.1 | system-ard511.img | 303MB |
Prepare the burning tool
Open the network location
Open the network drive to the "MYZR-IMX6 > 4_ Burning Tool" location.
Download the main program
Download the main program of the burn tool,“my-imx6-mfgtool-lib262-<date>.rar”，and unzip it to the current Windows folder.
Download images outside the file system
Download "OS Firmware" and overwrite“my-imx6-mfgtool-v262\Profiles\Linux\OS Firmware”。
Download the file system file
Download the file system file we confirmed earlier.That is, find the file we selected under the directory "OS Firmware_rootfs" for the system version and download it in the directory corresponding to the Windows burn tool "my-imx6-mfgtool-v262\Profiles Linux\OS Firmware".
For example, if we choose distro-fsl-imx-fb-image-qt5.tar.bz2 of linux-3.14.52, then download the file in the image-linux-31452 of "OS Firmware_rootfs" on the network disk and put it in Windows "my-imx6-mfgtool-v262\Profiles Linux 385-firmware".
Configuration burning tool
- Run the programming tool configuration program "MfgConfig.exe".
- The Evaluation Kit is selected according to the main model of your development board.
- CPU Type is selected according to its own development board specifications.
- Memory Size is selected according to its own development board specifications.
- OS Select is based on the system version we confirmed earlier.
- Rootfs File is selected according to the File system File we confirmed and downloaded earlier.
- Click "Make", and the configuration tool will generate the configuration file "cfg.ini" used by the burn tool.
- Run the main program“MfgTool2.exe”，of the burn tool. If no error is reported, it means normal.If an error is reported, it is resolved according to the information in the mfgtools.log under the tool directory.
- At this point, the file required for the burning record is ready.
For the development of board burning system
Keep the development board in download mode
Find the two-bit dial code SWITCH indicated by "BOOTMODE" or "BOOT SWITCH" ON the development board, 1 ON and 2 OFF.
Connect the development board to the computer
- Connect the MiniUSB cable to the development board and computer.
- Connect the development board to the computer with the serial line and open the serial port software on the computer.
- Connect the power cord to the development board and power it on.
Burning system to development board
- Close the main program "MfgTool2.exe" of the burning tool and run it again.
[[File::MY_IMX6_MfgTool_3.3.0.1.jpg]]- If the main program starts incorrectly, close the "MfgTool" in the process list of the Windows task manager, and then run the main program.
- If the main program displays "No Device Connected", check the connection status of the MiniUSB cable and confirm whether the dial code of the development board is in download mode.
- Click the "Start" button on the main interface of the burn tool to Start the burn.
[[File::MY_IMX6_MfgTool_3.5.0.1.jpg]] - In the process of burning, PC opportunity assessment board recognition as a storage device, then whether you need the pop-up dialog prompt formatting, here "cancel" or ignore the dialog or close the dialog box. [[File::MY_IMX6_MfgTool_3.5.0.2.jpg]]
- When the burn is complete, the message bar prints "Done" and the status bar turns green.Click "Stop" to complete the burn.Click "Exit" to Exit MFG Tools. [[File::MY_IMX6_MfgTool_3.5.0.3.jpg]]
Burning error handling
- Observe and retain the information on the main program of the burning tool. This information will indicate the specific stage of the burning error.
- Observe and retain the last part of the computer serial terminal software, this information will indicate the specific cause of the burning error.
- If you don't understand it, you can send these two pieces of information to our email (service@myzr.com.cn) or forum (bbs.myzr.com.cn) for support.
Start the development board
- Power off the development board After the burning is completed, turn off the power of the development board, and prepare to change the boot mode of the development board.
- Change Boot mode to boot mode Find the two-digit DIP switch indicated by “BOOTMODE” or “BOOT SWITCH” on the development board, turn 1 to OFF and 2 to ON.
- For development of board power Power on the development board, and the serial terminal software will see the information about the system startup.
Production use of burning tools
Configure burn tool to burn multiple equipment at the same time
Our current burn tool can burn seven devices at the same time by:
- Open UICfg.ini in the burning tool and change "PortMgrDlg=1" to "PortMgrDlg=7". Then the computer connects seven devices through the USB HUB, then turn on the burning tool, and then burn according to the process.
Burn your own compiled Image
According to the following "system version and corresponding file relationship table", replace the file compiled by yourself with the corresponding file in the burning tool, and re-burn the system for the development board. For example, if the u-boot of the Linux-3.14.52 MY-IMX6-EK200-6Q-1G development board is compiled, then open the burn tool to the “image-linux-31452” directory and replace the compiled u-boot file with uboot-myimx6ek200-6q.imx.
Burn your own application
Package your application as "my-demo. Tar.bz2" and replace the "my-demo. Tar.bz2" in the burn tool and re-burn the system for the development board based on the later "system version and corresponding file relational table". Note: "my-demo.tar.bz2" will be burned to the "/home/root" directory of the development board.
Burn your own file system updates
According to the following "system version and corresponding file relationship table", package a self-updating package, replace the corresponding file in the burning tool, and re-burn the system for the development board. Note: the file system update package will be burned to the root of the development board.
Other instructions
- All the above points can be replaced before burning.
- In the process of production, if no changes are made to the configuration of the burn tool, there is no need to exit and run the burn tool repeatedly, or even click the STOP button of the main program of the burn tool.When a device is burned out, the power of the device can be cut off. After connecting to the new device, the recording tool will burn the device.
Attached Table
Table 1: system version and corresponding file relational table
| system version | file type | Location | corresponding file |
|---|---|---|---|
| Linux-3.0.35 | U-Boot file | image-linux-3035 | uboot-<ek name>-<ek spec>.bin |
| core files | uImage-myimx6 | ||
| Kernel module package | kernel-modules.tar.bz2 | ||
| File system update package | rootfs-update.tar.bz2 | ||
| MYZR Demo | my-demo.tar.bz2 | ||
| Linux-3.14.52 | U-Boot file | image-linux-31452 | uboot-<ek name>-<ek spec>.imx |
| core files | zImage-myimx6 | ||
| Kernel module package | kernel-modules-myimx6.tar.bz2 | ||
| Device tree file | <ek name>-<ek spec>.dtb | ||
| File system update package | l31452_rtfs_update.tar.bz2 | ||
| MYZR Demo | my-demo.tar.bz2 | ||
| Linux-4.1.15 | U-Boot file | image-linux-4115 | image-uboot / uboot-<ek name>-<ek spec>.imx |
| core files | image-kernel / zImage-myimx6[a7 | a9] | ||
| Kernel module package | image-kernel / kernel-modules-myimx6[a7 | a9].tar.bz2 | ||
| Device tree file | image-dtb / <ek name>-<ek spec>.dtb | ||
| File system update package | image-update / krogoth_rootfs_update.tar.bz2 | ||
| MYZR Demo | image-update / my-demo.tar.bz2 | ||
| Android-4.2.2 | U-Boot file | image-android-422 | uboot-ard422-<ek name>-<ek spec>.bin |
| Boot Image | boot-ard422-<ek name>.img | ||
| Recovery Image | recovery-ard422-<ek name>.img | ||
| System Image | system-ard422-<ek name>.img | ||
| Android-4.4.2 | U-Boot file | image-android-442 | uboot-ard442-<ek name>-<ek spec>.bin |
| Boot Image | boot-ard442-<ek name>.img | ||
| Recovery Image | recovery-ard442-<ek name>.img | ||
| System Image | system-ard442-<ek name>.img | ||
| Android-5.1.1 | U-Boot file | image-android-511 | uboot-ard511-<ek name>-<ek spec>.bin |
| Boot Image | boot-ard511-<ek name>.img | ||
| Recovery Image | recovery-ard511-<ek name>.img | ||
| System Image | system-ard511.img |
-------------------------------------------------------------------------------- * Looking forward to communicating with you for more functions and field applications. * ZhuHai MYZR Technology CO.,LTD. * Latest Update: 2018/07/04 * Supporter: Tang Bin, Lin Yuannan --------------------------------------------------------------------------------
