Method for making system files of ubi format into factory burn image files

Abstract

The invention discloses a method for making system files of ubi format into factory burn image files. The method includes the following steps that nandflash partition information of Linux embedded equipment is read from partition files; a uboot starting file is made through an mkimage tool; a kernel and a root file system are integrated into a mirror image file; the system files are converted; content in a spare region of the nandflash is appended, and ECC data of the files are calculated; the image files capable of being burned in a partition mode are made, and the image files comprise partition list files and combined files. According to the method, a burning tool is not needed, making cost is not needed, the time for making burnt images in a factory is short, manual participation is not needed, the totally correct image files can be automatically generated within several seconds, the burning time is shortened, and the efficiency of a production line of Linux embedded products is improved.

Description

technical field [0001] The invention relates to storage technology, in particular to a method for making a system file in ubi format into a factory burning image file used in a Linux embedded device. Background technique [0002] The nandflash structure can provide extremely high cell density, high storage density, fast writing and erasing speed, and low cost of storage media. It has gradually become the preferred storage device for embedded systems. However, considering cost and technology, nandflash allows the existence of A certain percentage of bad blocks. [0003] The lifespan of nandflash is limited. The number of erasing and writing times of a nandflash block is about 10^5-10^6 times. In order to keep the service life of nandflash long enough, it is necessary to avoid unbalanced areas of erasing and writing, otherwise the flash memory will be partially erased. The entire nandflash is scrapped due to the write limit, which is actually a waste, so Wear Balance technolo...

AI Technical Summary

Problems solved by technology

If you use a burner to directly burn and compile the original system files (bootstrap.bin, uboot.bin, uImage, rootfs), the system cannot run because there is no spare area information

[0005] Since nandflash has a certain probability of bad blocks when it leaves the factory, if you use a writer to directly burn the burning image with spare area information, the system still cannot run

Because, when the first partition of nandflash has 1 bad block, nandflash burns by skipping the bad block, and the burner will write the remaining data of the first partition to the first block of the second partition In the block, the data of the original second partition is burnt into the second block of the second partition, but the data is read from a fixed address when the system starts, that is, the system goes to the first Read data in a block, at this time, the first block of the second partition stores the remaining data of the first partition, and the system cannot run

[0006] There are two main methods for burning existing Linux embedded devices: one method is to use script commands to burn various system files (bootstrap, config, uboot1, uboot2, integrated image image1, integrated image image2), this method has two disadvantages Firstly, it needs to make the burning tooling, which requires a certain production cost; secondly, the time to burn the system files is long, and the production efficiency is low; another method is to manually make the partition table file partTable.bin and the merge file Merge.bin and burn To record the image, the programmer first manually enters commands to download each system file to the nandflash of the embedded device, removes the nandflash and reads out all the data with a burner, then saves the data of each partition of the nandflash, and then uses a third-party application software to manually create a partition table file partTable.bin and merged file Merge.bin, and finally use the burner to burn the created image file (partition table file partTable.bin and merged file Merge.bin). The disadvantage of this method is that there are many steps to make the image file, and the time Long, manual intervention, complex process, error-prone and other shortcomings

Images