V1.4.0 Notes:
Important considerations have carefully collected in “USBBurnTool_ V1.4.0_User_Notes. doc”of USBBurnTool-V1.4.0.rar. Make sure you have read the document before use.
For NAND burn, burn tool needs Kernel support. The operation must follow following rules:
1. Use the Burn tool need updated kernel to certain release versions or later (refer to the R&D news about the Android / Linux released). USBBurnTool V1.4.0 is not forward compatible with previous version of the kernel. Burning previous kernel version will cause system abnormal boot.
2. When first burning, the NANDflash need be full erased, and the kernel version are required be the latest version, otherwise, it will cause the system boot fail.
3. Except the first burning operation, each of partitions can be burned separately. Only kernel need be the certain version or later, the other images are no limited.
The source version addition to a version of the kernel requirements, no other mirrored version requirements
(The kernel of recovery.cpio.img has the same requirements).
The issue is due to NAND module improvement. Have no essential unrelated to burn tool. SD / MM burn is unaffected.
V1.4.0 Primary update:
1. Fix mark nand bad blocks unsuccessfully when write fail;
2. Update libnm.a, synchronize the libnm.a in kernel;
3. Add configure DDR frequency manually in the platform tab;
4. Add a “Flag” group in the NV tab,which is used for the factories batch or model of product. The flag can be set in default setting file text, or manually configure its length, offset and the burning times in UI.
5. Add the window functions can be maximized and restored.
6. Add a switching function between English and Chinese.
7. Add support for 64-bit drivers,but not get a digital certificate yet.
Known issues
1. Tools crash, but no machine can reproduce yet.
2. The driver can’t install in certainPC. The issue cannot solve by software.
This problem occurs because that one defect in chip bootrom code causes flow disorder after the treatment of some unsupported desc.
3.64bit driver has not been get a PC digital verification, is a business issue.
4. Sometimes unplug usb cable during burn, the results still show "Successful". It is the thread return value problem. It can be solved in the next version.
Downloads:
Support and Feedback:
Feel free to contact support@ingenic.cn