First, the development environment
Computer: win10 64 Wei
putty：putty0.71
usb_otg_driver：android_drv_90000_64.exe
ADB：platform-tools
Two, fastboot command programming
(1) would need to be written to the mirror copy "USB_fastboot_tool" -> "platform-tools" folder.
(2) development board starts to enter Uboot mode.
(3) create eMMC partition and format.
If the original has already done this step may be skipped are not necessarily partitioned and formatted before each write.
In HyperTerminal, enter the following partition and formatting commands:
fdisk -c 0
fatformat mmc 0:1
ext3format mmc 0:2
ext3format mmc 0:3
ext3format mmc 0:4
In HyperTerminal, enter the following command:
fastboot
Note: fastboot command need to use USB_fastboot_tool tools on PC support.
---------------------- dividing line, both on the top uboot completed below finished on ADB ------------ -----------------------------
(4) running ADB environment.
Running on a PC "USB_fastboot_tool" -> "platform-tools" folder in the file "cmd.exe"
(5) In the Windows command line, enter the following command:
fastboot.exe flash bootloader u-boot-iTOP-4412.bin
Reminded not recommended to program the "u-boot-iTOP-4412.bin" this file, you can skip this step, because the factory had burned written this image files.
fastboot.exe flash kernel zImage
fastboot.exe flash ramdisk ramdisk-uboot.img
fastboot.exe flash system system.img
fastboot -w
Above fastboot.exe flash command can be performed separately, program only the single mirror.
6) In the Windows command line, enter the command to restart the development board:
fastboot reboot
Third, the problems encountered
1. The handset is in uboot command line mode, type fastboot, computer equipment manager does not appear "Androd ADB Interface"!
Through the investigation, an unknown phone devices in Device Manager, by reloading the ADB drivers, computer equipment appeared "Androd ADB Interface".
2. Writing system.img failure phenomenon as follows:
C:\Users\snaking616\Desktop\ADB>fastboot.exe flash system system.img
sending 'system' (257620 KB)...
OKAY [ 39.877s]
writing 'system'...
FAILED (status malformed (0 bytes))
finished. total time: 74.996sSolution: There are problems in the CD-ROM system the two dates, the programming of the system is above the mirror 20,170,517 of the 20,151,120 mirror mirror system is replaced, the command "fastboot.exe flash system system.img" programming success.
Facts have proved that you can use on win10 programming to use fastboot successful Android system image!
Fourth, Reference:
[1] iTOP-4412 Development Board mirror programmer - blog Park - Self_made
https://www.cnblogs.com/liming1593/p/5196538.html