Applicable scope evaluation board corresponding to the operating system support
Evaluation board model
(Evaluation board)
Linux system version support (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 model
(Evaluation board)
Android system version support (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
√
File system support for the operating system
Since the relationship between the Linux system and the file system is one-to-many, the same Linux system can support different file systems. Here, the corresponding relationship is listed as follows:
In addition, the file system is relatively large, the smallest file is only a few MB, but the largest file system has more than 1GB. In order to save everyone's download time, you first pre-select the file system you need according to the following table. You can download only the file system you need when you download the file system.
operating system
(operating system)
File system support
(file system)
File system file name
(the name of file system) file system file size
(the size of file system)
(the note of file system)
Linux-3.0.35
Rootfs-linux-minimal.tar.bz2 6.9MB the smallest (thin) Linux file system
(the simple Linux file system)
Rootfs-linux.tar.bz2 64.4MB regular Linux file system
(the common Linux file system)
Rootfs-linux-qt4.tar.bz2 90.8MB Linux QT4 file system
(Linux QT4 file system)
Ubuntu-12.04.tar.bz2 1.45GB Ubuntu 12.04 file system
(Ubuntu 12.04 file system)
Linux-3.14.52
Distro-core-image-base.tar.bz2 21.4MB The smallest (thin) Linux file system
(the simple Linux file system)
Distro-fsl-image.tar.bz2 227MB regular Linux file system
(the common Linux file system)
Distro-fsl-imx-fb-image-qt5.tar.bz2 304MB Linux-QT5 file system
(Linux QT5 file system)
Distro-fsl-image-6ul.tar.bz2 99.7MB 6UL (EK140) Linux file system
(6UL-EK140 Linux file system)
Armhf-rootfs-ubuntu-xenial.tar.bz2 176MB Ubuntu 16.04 file system (no GUI)
(Ubuntu 16.04 file system and no GUI)
Armhf-rootfs-ubuntu-xenial-lxde.tar.bz2 838MB Ubuntu 16.04 file system with GUI LXDE
(Ubuntu 16.04 file system and GUI is LXDE)
Linux-4.1.15
Core-image-base-myimx6a9.tar.bz2 25.4MB The smallest (thin) Linux file system for the MYIMX6A9 series
(the simple Linux file system)
Fsl-image-linux-myimx6a9.tar.bz2 201MB MYIMX6A9 Series General Linux File System
(the common Linux file system)
Fsl-image-qt5-myimx6a9.tar.bz2 376MB MYIMX6A9 series Linux-QT5.6.1 file system
(Linux QT5 file system)
Core-image-base-myimx6a7.tar.bz2 24.3MB MYIMX6A7 series smallest (thin) Linux file system
(the simple Linux file system)
Fsl-image-linux-myimx6a7.tar.bz2 120MB MYIMX6A7 series regular Linux file system
(the common Linux file system)
Fsl-image-qt5-myimx6a7.tar.bz2 158MB MYIMX6A7 Series Linux-QT5.6.1 File System
(Linux QT5 file system)
Android-4.2.2
System-ard422-myimx6ek200.img 280MB Android 4.2.2 system files for MYIMX6EK200
(Android 4.2.2 file system for MYIMX6EK200)
Android-4.4.2
System-ard442-myimx6ek200.img 360MB MYIMX6EK200 Android 4.4.2 system files
(Android 4.4.2 file system for MYIMX6EK200)
System-ard442-myimx6ek314.img 360MB MYIMX6EK314 for Android 4.4.2 system files
(Android 4.4.2 file system for MYIMX6EK314)
Android-5.1.1
System-ard511.img 303MB Android 5.1.1 system files
(Android 5.1.1 file system)
Note: The Ubuntu 16 GUI (armhf-rootfs-ubuntu-xenial-lxde.tar.bz2) file system takes a few minutes to enter the graphical interface for the first time, and then each time you log in to the graphical interface, it's faster.
Prepare the directory and file description of the burning tool burning tool
Here is a complete description of the complete burning tool directory and file structure, and a brief description of the directory and files, to facilitate understanding of the burning tools.
/
|-> Profiles
| |-> Linux
| |-> OS Firmware
| |-> firmware-3035: firmware used by the burning tool (the firmware of MFG Tool)
| |-> firmware-31452: firmware used by the burning tool (the firmware of MFG Tool)
| |-> image-android-422: Target burning file (Android-4.2.2) (target of burn files (Android-4.2.2)
| |-> image-android-442: Target burning file (Android-4.4.2) (target of burn files (Android-4.4.2)
| |-> image-android-511: Target burning file (Android-5.1.1) (target of burn files (Android-5.1.1)
| |-> image-linux-3035: Target burning file (Linux-3.0.35) (target of burn filesLinux-3.0.35)
| |-> image-linux-31452: Target burning file (Linux-3.14.52) (target of burn files (Linux-3.14.52)
| |-> ucl2.xml: Burning rules
|
|-> cfg.ini: Configuration of MFG Tool
|
|-> MfgTool2.exe: Main program of the burning tool (Main program)
|
|-> MfgToolLib.dll: Dynamic link database of MFG Tool
|
|-> UICfg.ini: The UI configuration of MFG Tool
Burning tool main package
The main burning package includes: MfgTool2.exe, MfgToolLib.dll, UICfg.ini, and an empty "Profiles/Linux/OS Firmware" directory.
Download the main program compression package "MY-IMX6-MfgTool.rar" in the network disk and extract it to the Windows system.
Note: The currently used burning tool compression package is "my-imx6-mfgtool-lib262-final.rar"
Burning tool configuration file
Download the programming tool configuration file "cfg.ini" on the network disk and place "cfg.ini" in the burning tool directory, which is in the same directory as "MfgTool2.exe".
System firmware (required file)
The "OS Firmware" directory in the network disk includes some files of ucl2.xml, firmware-3035, firmware-31452, image-*, most of which are necessary, and the entire directory is not large, in order to avoid unnecessary errors. It is recommended to download the entire "OS Firmware" directory and place the "OS Firmware" directory in the "Profiles/Linux/" directory of the burning tool.
System firmware (file system)
According to the file system file name selected in the previous "File System Support for Operating System" table, find the corresponding file in the "OS Firmware_rootfs" directory and download it to the burning tool "Profiles/Linux/OS Firmware/ "The corresponding directory.
Such as (Eg):
Need the QT4 file system of Linux-3.0.35, then download "OS Firmware_rootfs/image-linux-3035/rootfs-linux-qt4.tar.bz2" in the network disk and put "rootfs-linux-qt4.tar.bz2" "Place it in the "Profiles/Linux/OS Firmware/image-linux-3035/" directory of the burning tool.
Need Linux-3.14.52 Linux minimum file system, then download "OS Firmware_rootfs/image-linux-31452/distro-core-image-base.tar.bz2" in the network disk, and put "distro-core-image- Base.tar.bz2" is placed in the "Profiles/Linux/OS Firmware/image-linux-31452/" directory of the burning tool.
Configure the burning tool configuration description configuration file (cfg.ini)
The configuration file is located in the MY-IMX6-MfgTool directory and the file name is cfg.ini. Open cfg.ini to see that there are several configuration items in the file.
Target burning system and items that need to be configured
The relationship between the target burning system and the configuration items in the configuration file (cfg.ini) is shown in the following table:
Target system
(Target system)
The target system corresponds to the item to be configured in the cfg.ini file.
(Red is must configurate)
Name ek_name ek_spec rootfs_l3035_file rootfs_l31452_file rootfs_l4115_file
Linux-3.0.35 √ √ √ √ Ignore (ignore) Ignore (ignore)
Linux-3.14.52 √ √ √ Ignore (ignore) √ Ignore (ignore)
Linux-4.1.15 √ √ √ Ignore (ignore) Ignore (ignore) √
Android-4.2.2 √ √ √ Ignore (ignore) Ignore (ignore) Ignore (ignore)
Android-4.4.2 √ √ √ Ignore (ignore) Ignore (ignore) Ignore (ignore)
Android-5.1.1 √ √ √ Ignore (ignore) Ignore (ignore) Ignore (ignore)
Note:
The dark blue background indicates the type of system that the burning tool supports for burning.
The yellow background indicates the items that can be configured in the programming file (cfg.ini) of the burning tool.
The red background indicates the items that must be configured corresponding to the target burning system.
A white background indicates a configuration item that is independent of the target system, that is, an item that can be ignored or not configured corresponding to the target system.
Start to configure the burning item name item configuration (name item)
The name item is configured for the target burning system. If you need to burn the Linux-3.0.35 system, configure name = Linux-3.0.35 and make sure the other "name" lines are preceded by a "#".
Configuration item
(Configuring item)
Target value
(Target)
Description
(Note)
Name Linux-3.0.35 configuration target burning system is Linux-3.0.35
(Burning system is Linux-3.0.35)
Linux-3.14.52 configuration target burning system is Linux-3.14.52
(Burning system is Linux-3.14.52)
Android-4.2.2 configuration target burning system for Android-4.2.2
(Burning system is Android-4.2.2)
Android-4.4.2 configure target burning system for Android-4.4.2
(Burning system is Android-4.4.2)
Android-5.1.1 configuration target burning system for Android-5.1.1
(Burning system is Android-5.1.1)
Configuration example (Eg
Name = Linux-3.0.35
#name = Linux-3.14.52
#name = Android-4.2.2
#name = Android-4.4.2
#name = Android-5.1.1
Ek_name item configuration
The ek_name entry is configured for the main model of the evaluation board. This corresponds to the main model of the evaluation board. If you need to burn the system to MY-IMX6-EK200, configure ek_name = myimx6ek200 and make sure the other "ek_name" lines are preceded by a "#".
Configuration item
(Configuring item)
Target value
(Target)
Description
(Note)
Ek_name myimx6ek140 The evaluation board for the target burning is MY-IMX6-EK140
(configuring board is MY-IMX6-EK140)
Myimx6ek200 configuration target burning evaluation board model is MY-IMX6-EK200
(configuring board is MY-IMX6-EK200)
Myimx6ek314 configuration target burning evaluation board model is MY-IMX6-EK314
(configuring board is MY-IMX6-EK314)
Myimx6ek336 The target evaluation board is MY-IMX6-EK336
(configuring board is MY-IMX6-EK336)
Configuration example: (Eg
#ek_name = myimx6ek140
Ek_name = myimx6ek200
#ek_name = myimx6ek314
#ek_name = myimx6ek336
Ek_spec item configuration
The ek_spec item is configured to the specifications of the evaluation board, which corresponds to the specifications of the evaluation board. If the target evaluation board's CPU is quad-core and memory is standard, configure ek_spec = 6q and ensure that the other "ek_spec" lines are preceded by a "#".
Configuration item
(Configuring item)
Target value
(Target)
Description
(Note)
The ek_spec 6qp target evaluation board is configured as: i.MX 6QuadPlus CPU with standard memory (1G)
(evaluation board: CPU=I.MX6 QuadPlus, RAM=1GB)
The 6qp-2g target evaluation board is configured as: i.MX 6QuadPlus CPU, 2G memory
(evaluation board: CPU=I.MX6 QuadPlus, RAM=2GB)
The 6q target evaluation board is configured as: i.MX 6Quad ​​CPU with standard memory (1G)
(evaluation board: CPU=I.MX6 Quad, RAM=1GB)
The 6q-2g target evaluation board is configured as: i.MX 6Quad ​​CPU, memory 2G
(evaluation board: CPU=I.MX6 Quad, RAM=2GB)
The 6u target evaluation board is configured as: i.MX 6DualLite CPU with standard memory (1G)
(evaluation board: CPU=I.MX6 DualLite, RAM=1GB)
The 6s target evaluation board is configured as: i.MX6Solo CPU with standard memory (512M)
(evaluation board: CPU=I.MX6 Solo, RAM=512MB)
The configuration of the 6s-1g target evaluation board is: i.MX6Solo CPU, memory 1G
(evaluation board: CPU=I.MX6 Solo, RAM=1GB)
The 6g target evaluation board is configured as: i.MX6UL CPU with standard memory (256M)
(evaluation board: CPU=I.MX6 UltraLite, RAM=256MB)
The 6g-512m target evaluation board is configured as: i.MX6UL CPU, memory 512M
(evaluation board: CPU=I.MX6 UltraLite, RAM=512MB)
Configuration example: (Eg
#ek_spec = 6qp
#ek_spec = 6qp-2g
Ek_spec = 6q
#ek_spec = 6q-2g
#ek_spec = 6u
#ek_spec = 6s
#ek_spec = 6s-1g
#ek_spec = 6g
#ek_spec = 6g-512m
Rootfs_l3035_file configuration
The rootfs_l3035_file entry is a file system configured for Linux-3.0.35. If you need to burn the rootfs-linux.tar.bz2 system, configure rootfs_l3035_file = rootfs-linux.tar.bz2 and make sure that the other rootfs_l3035_file lines have a "#" in front of it. If the name is not Linux-3.0.35, you can Skip the rootfs_l3035_file configuration because it will be ignored by the burning tool.
Configuration item
(configuration item)
Target value
(target value )
Description
(instruction)
Rootfs_l3035_file rootfs-linux-minimal.tar.bz2 corresponds to the smallest Linux file system
Rootfs-linux.tar.bz2 corresponds to the regular Linux file system
Rootfs-linux-qt4.tar.bz2 corresponds to the Linux QT file system
Ubuntu-12.04.tar.bz2 corresponds to the Ubuntu 12.04 file system
Configuration example
#rootfs_l3035_file = rootfs-linux-minimal.tar.bz2
Rootfs_l3035_file = rootfs-linux.tar.bz2
#rootfs_l3035_file = rootfs-linux-qt4.tar.bz2
#rootfs_l3035_file = ubuntu-12.04.tar.bz2
Rootfs_l31452_file configuration (rootfs_l31452_file item configuration)
The rootfs_l31452_file entry is a file system configured for Linux-3.14.52. If you need to burn the distro-fsl-image.tar.bz2 system, configure rootfs_l3035_file = distro-fsl-image.tar.bz2 and make sure that the other rootfs_l31452_file line has a "#" in front of it.
If the name entry is not configured for Linux-3.14.52, you can skip the Linux-3.14.52 configuration because it will be ignored by the burning tool.
Configuration item
(configuration item)
Target value
(target value)
Description
(instruction)
Rootfs_l31452_file distro-core-image-base.tar.bz2 corresponds to the smallest Linux file system
(corresponding to minumal Linux file system)
Distro-fsl-image.tar.bz2 corresponds to the regular Linux file system
(corresponding to conventional Linux file system)
Distro-fsl-image-qt5.tar.bz2 corresponds to the Linux-QT5 file system
(corresponding to Linux-QT5 file system)
Distro-fsl-image-6ul.tar.bz2 Corresponds to 6UL (EK140) Linux file system (no GPU)
(corresponding to Linux file system(without GPU) of 6UL(EK140))
Armhf-rootfs-ubuntu-xenial.tar.bz2 corresponds to Ubuntu 16.04 file system (no GUI)
(corresponding to Ubuntu 16.04 file system(without GUI))
Armhf-rootfs-ubuntu-xenial-lxde.tar.bz2 corresponds to Ubuntu 16.04 file system, GUI is LXDE
(corresponding to Ubuntu 16.04 file system, GUI is LXDE)
Configuration example
#rootfs_l31452_file = distro-core-image-base.tar.bz2
Rootfs_l31452_file = distro-fsl-image.tar.bz2
#rootfs_l31452_file = distro-fsl-image-qt5.tar.bz2
#rootfs_l31452_file = distro-fsl-image-6ul.tar.bz2
#rootfs_l31452_file = armhf-rootfs-ubuntu-xenial.tar.bz2
#rootfs_l31452_file = armhf-rootfs-ubuntu-xenial-lxde.tar.bz2
Check configuration
Check each configuration item in the configuration file to ensure that each configuration item is not configured twice. The line capital of the other line of the configuration item has the "#" character.
Burn connection evaluation board and PC
Refer to "Connecting Devices" in the MY-IMX6-EKxxx Quick Start Guide.
Configure the download mode of the evaluation board
Download mode description
The way the MY-IMX6 series evaluation board enters the download mode is:
Evaluation board model
(Evaluation board model)
How the MY-IMX6 series evaluation board supports the download mode
(Ways to enter download mode supported by MY-IMX6 series of evaluation board)
Two-digit hardware dialing method
(Two bit hardware dialing mode) hardware BOOT button
( hardware BOOT button)
MYIMX6EK140
YES
NO
MYIMX6EK200
YES
YES
MYIMX6EK314
YES
NO
MYIMX6EK336
YES
NO
Hardware dialing into download mode
Tip: The two-digit DIP switch of MYIMX6EK200 is on the core board; the two-digit DIP switch of MYIMX6EK140, MYIMX6EK314 and MYIMX6EK336 is on the bottom plate.
Since the two-digit dial switch of the EK200 is on the core board, it is relatively troublesome to use the hardware dialing code. Therefore, the core board of the EK200 has been modified in V2.1.1, and can support the "hardware BOOT button" mode to enter the download mode. For details, please refer to the next section "Hardware BOOT button to enter the download mode".
1) Power off the evaluation board.
2) Find the two-digit DIP switch of the evaluation board
3) Turn 1 of the two-position dial switch to “ON†and 2 to “OFFâ€.
4) Re-power the evaluation board
Reference picture with two-digit dial switch
Hardware BOOT button enters download mode
Note: This mode is supported by the MYIMX6EK200. This method is not supported by MYIMX6EK140, MYIMX6EK314, and MYIMX6EK336.
Method of operation
Press and hold "BOOT SW1" on the EV kit's backplane to reset or re-power the EV kit hardware, then release "BOOT SW1".
Tip: The BOOT button is next to the power connector of the EV kit.
Start MFG Tools
Important: Before starting MFG Tools, please make sure that the corresponding file has been downloaded and exists in the corresponding folder of MFG Tools.
Double-click "MfgTool2.exe" and the software will recognize the HID device.
MFG Tools startup error handling
1) Read the information on the error prompt window carefully
2) Look carefully at running the LOG file
To achieve these two, MFG Tools can basically solve the problem when it starts.
Start burning
1) Click “Start†of MFG Tools to start burning.
2) Burning information
During the programming process, the information bar of the MFG Tools will display the progress and status information of the burning.
3) Processing of the burning process
During the burning process, the PC will recognize the evaluation board as a storage device, and a dialog box will pop up to indicate whether formatting is required. Click “Cancel†or ignore the dialog box or close the dialog box.
4) Burning completed processing
Tip: After the burning is completed, the information bar will output “Done†and the status bar will turn green.
Click "Stop" to complete the programming.
Click "Exit" to exit MFG Tools.
MFG burning error handling
1) Carefully view the running LOG file
2) Carefully read the information output when the serial terminal is programmed to abort.
Burn the last job
If you use the dialing mode to enter the download mode and burn it, you need to turn "1" of the DIP switch back to OFF and "2" to turn back to ON.
Start a new system
Restart the evaluation board to start the new system.
Advanced programming of the burning tool to burn your own compiled firmware (program firmware compiled by yourself)
Here we need to figure out the dependencies of the target system and files. Then replace the file you compiled with the corresponding file, close it and re-open the burning tool to burn it.
Target system and associated files are shown in the table below.
Target system
(target system)
Associated file
(relevant file)
Linux-3.0.35
Image-linux-3035/uboot-${ek_name}-${ek_spec}.bin
Image-linux-3035/uImage-myimx6
Image-linux-3035/kernel-modules.tar.bz2
Linux-3.14.52
Image-linux-31452/uboot-${ek_name}-${ek_spec}.imx
Image-linux-31452/zImage-myimx6
Note: EK140 is zImage-myimx6g
(Attention: EK140 is zImage-myimx6g)
Image-linux-31452/kernel-modules.tar.bz2
Note: EK140 is kernel-modules-myimx6g.tar.bz2
(Attention: EK140 is kernel-modules-myimx6g.tar.bz2)
Android-4.2.2
Image-android-422/uboot-ard422-${ek_name}-${ek_spec}.bin
Image-android-422/boot-ard422-${ek_name}.img
Image-android-422/recovery-ard422-${ek_name}.img
Image-android-422/system-ard422-${ek_name}.img
Android-4.4.2
Image-android-442/uboot-ard442-${ek_name}-${ek_spec}.bin
Image-android-442/boot-ard442-${ek_name}.img
Image-android-442/recovery-ard442-${ek_name}.img
Image-android-442/system-ard442-${ek_name}.img
Android-5.1.1
Image-android-511/uboot-ard511-${ek_name}-${ek_spec}.bin
Image-android-511/boot-ard511-${ek_name}-${ek_spec}.img
Image-android-511/recovery-ard511-${ek_name}-${ek_spec}.img
Image-android-511/system-ard511.img
Description: "${*}" indicates a reference. For example, uboot-(Instruction: "${*}" means quoting.example uboot-)${ek_name}-${ek_spec}.bin, assuming "ek_name = myimx6ek200", "ek_spec = 6q". Then uboot-${ek_name}-${ek_spec}.bin is uboot-myimx6ek200-6q.bin.
Program renewed file system
The burning tool in the current network disk supports the update of the target system burning file system of Linux-3.0.35 and Linux-3.14.52 to the device. It is no longer necessary to unpack the file system and then add the file and package it to avoid errors. Opportunity.
The principle is that the burning tool will burn a specified file into the file system of the device (burn to the root directory of the file system).
The specific method is as follows:
If the target system is Linux-3.0.35, copy the rootfs-update.tar.bz2 to the Linux development host and unzip it to a directory A in the image-linux-3035 directory of the burning tool, and add or update it. The file is placed under directory A (note: the relative path of the new file is absolutely the same as the target file system). Then the file under the package directory A is rootfs-update.tar.bz2 (here is the file under the package directory A, not the entire directory), then replace the rootfs-update.tar.bz2 with the same name under the image-linux-3035 directory. file.
If the target system is Linux-3.14.52, the method is the same as that of Linux-3.0.35, but the file is image-linux-31452/l31452_rtfs_update.tar.bz2.
Burn your own app
The burning tool in the current network disk supports the target system of Linux-3.0.35 and Linux-3.14.52 to burn the application package to the device. It is no longer necessary to unpack the file system and then add the file and package it to avoid the error. opportunity.
The principle is similar to the burn file system update. The target system Linux-3.0.35 will be burned to the device's /root directory; the target system Linux-3.14.52 will be burned to the device's /home/root directory.
The specific method is as follows:
Copy image-linux-3035/my-demo.tar.bz2 or image-linux-31452/my-demo.tar.bz2 to the Linux development host and extract it, then add, delete, change, and complete the my-demo directory. Then package the my-demo directory to my-demo.tar.bz2, and then replace my-demo.tar.bz2 with the corresponding file under the burning tool.
Production method
In a production environment, using a burning tool to burn a single device is a cumbersome task. However, our current burning tool can burn seven devices at the same time, which greatly reduces the workload during production.
The specific method is as follows:
Tip: If you don't make changes to the burning tool, you don't need to repeatedly exit and run the burning tool, or even click the STOP button of the burning tool main program. When a device is burned, the device can be powered off, and then connected to a new device, the burning tool will burn the device.
Litecoin (LTC) is a cryptocurrency created as a fork of Bitcoin in 2011. It uses a hashing algorithm called Scrypt that requires specifically designed mining software and hardware. It is minable, and continues to rank in the top cryptocurrencies for value and trading volume.
Litecoin mining is the process of validating transactions in the blockchain, closing the block, and opening a new one. Litecoin uses the proof-of-work consensus mechanism, which uses computational power to solve the nonce, which is part of the hash, that secures the block. The hash is the alphanumeric sequence of numbers that is encrypted by the hashing algorithm. When the nonce is solved, Litecoin is rewarded.
Litecoin mining became popular in 2011 when Charlie Lee, a software engineer at Google, announced its creation as a Bitcoin fork with modifications intended to help it scale more effectively.
Just like Bitcoin, it can be mined on computers using central processing units and graphics processing units. However, it isn't as profitable or competitive as purchasing an application-specific integrated circuit (ASIC) and joining a mining pool.
Ltc Asic Miner,Antminer L3 Plus Plus,Bitmain Antminer L3 Plus,Bitmain L3 Plus
Shenzhen YLHM Technology Co., Ltd. , https://www.hkcryptominer.com