Burn a system image on the MarS board, marsboard

Burn a system image on the MarS board, marsboard

MarS Board is an evaluation Board based on The Freescale Semiconductor I. MX 6 Dual processor. I. MX 6 Dual Processor integrates ARM Cortex up to 1 GHz™-A9 kernel, 2D and 3D graphics processor, and 3D 1080 p video processor.
The MarS Board evaluation Board has a variety of interfaces, including HDMI interface, LVDS interface, Mini usb otg interface, Mini USB Debug interface, RJ45 interface, USB Host interface, TF card interface, and LCD display interface, it can help developers develop in various fields such as the Internet, desktop, high-end mobile internet devices, high-end handheld computers, high-end portable media players, game machines, and portable navigation devices.

 

This Board is the domestic design of the English site, the online can directly find the information is very little, the official burning write tool is Mfgtools-Rel-12.04.01_ER_MX6Q_UPDATER, but there are compatibility problems, does not support XP and USB

My system is win 8.1 pro, so I can only find another tool, eventually I am using a Mfgtools-Rel-4.1.0_130816_MX6Q_UPDATER, can be compatible with win 8.1, but still need a USB HUB to convert USB 2.0

Use the Mfgtools-Rel-4.1.0_130816_MX6Q_UPDATER to note that there must be an image file under the Profiles \ MX6Q Linux Update \ OS Firmware directory, otherwise the burning tool cannot open

This burning tool is roughly the same as the official method of use. The pre-configuration to be burned in cfg. ini is as follows:

1 [profiles]2 chip = MX6Q Linux Update3 4 [platform]5 board = MarS Board6 7 [LIST]8 name = Ubuntu-Marsboard-eMMC

 

I chose Ubuntu-Marsboard-eMMC as the configuration. If you want to modify the configuration, the Ubuntu-Marsboard-eMMC configuration is recorded in ucl2.xml under the Profiles \ MX6Q Linux Update \ OS Firmware directory.

 1 <LIST name="ubuntu-Marsboard-eMMC" desc="Choose eMMC as media"> 2     <CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot.bin" >Loading U-boot</CMD> 3     <CMD state="BootStrap" type="load" file="uImage" address="0x10800000" 4         loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >Loading Kernel.</CMD> 5     <CMD state="BootStrap" type="load" file="initramfs.cpio.gz.uboot" address="0x10C00000" 6         loadSection="OTH" setSection="OTH" HasFlashHeader="FALSE" >Loading Initramfs.</CMD> 7     <CMD state="BootStrap" type="jump" > Jumping to OS image. </CMD> 8      9     <CMD state="Updater" type="push" body="$ flash_eraseall /dev/mtd0">Erasing Boot partition</CMD>10     <CMD state="Updater" type="push" body="send" file="files/u-boot.bin">Sending U-Boot</CMD>11     <CMD state="Updater" type="push" body="$ dd if=$FILE of=/dev/mtd0 bs=512">write U-Boot to SPI-NOR</CMD>12     <CMD state="Updater" type="push" body="$ flash_eraseall /dev/mtd1">Clear Params</CMD>13 14     <CMD state="Updater" type="push" body="send" file="files/uImage">Sending kernel uImage</CMD>15     <CMD state="Updater" type="push" body="$ dd if=$FILE of=/dev/mmcblk0 bs=1M seek=1 conv=fsync">write kernel image to sd card</CMD>16     17     <CMD state="Updater" type="push" body="send" file="mksdcard.sh.tar">Sending partition shell</CMD>18     <CMD state="Updater" type="push" body="$ tar xf $FILE "> Partitioning...</CMD>19     <CMD state="Updater" type="push" body="$ sh mksdcard.sh /dev/mmcblk0"> Partitioning...</CMD>20 21     <CMD state="Updater" type="push" body="$ mkfs.ext3 -j /dev/mmcblk0p1">Formatting rootfs partition</CMD>22     <CMD state="Updater" type="push" body="$ mkdir -p /mnt/mmcblk0p1"/> 23     <CMD state="Updater" type="push" body="$ mount -t ext3 /dev/mmcblk0p1 /mnt/mmcblk0p1"/>24     <CMD state="Updater" type="push" body="pipe tar --numeric-owner -zxv -C /mnt/mmcblk0p1" file="files/oneiric.tgz">Sending and writting rootfs</CMD>25     <CMD state="Updater" type="push" body="frf">Finishing rootfs write</CMD>26     <CMD state="Updater" type="push" body="$ umount /mnt/mmcblk0p1">Unmounting rootfs partition</CMD>27     <CMD state="Updater" type="push" body="$ echo Update Complete!">Done</CMD>28   </LIST>

The 24 rows configured above

<CMD state="Updater" type="push" body="pipe tar --numeric-owner -zxv -C /mnt/mmcblk0p1" file="files/oneiric.tgz">Sending and writting rootfs</CMD>

Here, the system file image used for writing is set to files/oneiric. tgz, that is, the \ Profiles \ MX6Q Linux Update \ OS Firmware \ files \ oneiric. tgz file is used.

Note that this burning method is significantly different from Raspberry Pi's burning method. Raspberry Pi's image file only has one imgfile, but it is divided into three, u-boot.bin, uImage, and oneiric. tgz

The u-boot.bin is the image that records the boot area, the uImage is the Linux kernel image, and the oneiric. tgz is the file system image.

The official cross-compilation tool and source code, you can also use the BSP provided by Freescale, You can streamline the compilation of your own kernel, generate u-boot.bin and uImage files

Oneiric. the tgz file determines the system version number. The MarS Board uses the derivative Ubuntu version Linaro, which is the official oneiric. the tgz version is 11.10. You can download the latest version of the image from the official website of Linaro and use a later version of the image.

If you want to use a system of version 14.04 or later, the u-boot.bin file needs to download the latest source code compilation generation, otherwise the boot will not work properly.

Note that the kernel and kernel dynamic module are not compiled together (the kernel is in uImage, and the kernel dynamic module is in oneiric. tgz), so some functions (such as iptables) cannot be used)

 

Prepare u-boot.bin, uImage, and oneiric. the three tgz files can be burned out. The burning tool will first load the Kernel File and boot file, and then automatically restart the device (the USB will be disconnected for a short while and will be automatically connected) start burning

How to burn a system image to a disk

Open NERO StartSmart, select "copy and backup", click "burn the image to the CD", select the image file you want to burn, put it on a blank disc, and select "write speed ", it seems that 24 * is better.

You can simply burn a file on a CD rather than an image.

In the rain forest system, there is a hard disk installer in it. You can click the installer to directly install it.

Auto read ???
Why do you want to read data automatically?
Taking into account a lot of things, the system does not automatically read because the system has disabled automatic reading to Prevent automatic playback of the autorun virus.

I can't read it. It may be due to the quality of the CD, or the optical drive. I also have a CD, which cannot be read in the system, but can be started from the optical drive, but the system can be installed. Depressed!

How can I burn an image file into a USB flash drive?

1. You have copied ghost.exe and WinxpSP3.gho files on the USB flash drive. the ghost file downloads a Ghost version of XP from the internet. I personally recommend that the computer company sp3 V9.1 use the perfect version. This system is absolutely clean, non-toxic, and non-malicious plug-in. The system is stable and the xp patch is hit in March June.
Official Website: (select "Thunder download ")
Down.dhghost.cn/
◆ The downloaded file is an ISO compressed file, which can be carved into a CD. Of course, you can also directly decompress the WinxpSP2.gho file. (Note: To make a good choice for this file under the Dos ghost, it is best to extract it to a folder named in English)
2. USB flash drive tool: ephemeral.
3. Press Del To Go To The CMOS settings, and then select "First Boot Device" under "Advance Bios Features ", press the Page Down button to select the USB-ZIP or USB-FDD so that you can start from the U disk.
4. Run the ghost program when starting the system to DOS, select Local-Partition-From Image as prompted, select the WinxpSP2.gho file after decompression, and then yes, after 100%, all subsequent installation is automated. OK