CN106569854B - Method and system for setting equipment firmware and realizing factory test - Google Patents
Method and system for setting equipment firmware and realizing factory test Download PDFInfo
- Publication number
- CN106569854B CN106569854B CN201610950294.3A CN201610950294A CN106569854B CN 106569854 B CN106569854 B CN 106569854B CN 201610950294 A CN201610950294 A CN 201610950294A CN 106569854 B CN106569854 B CN 106569854B
- Authority
- CN
- China
- Prior art keywords
- firmware
- factory test
- starting
- fusion
- formal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44552—Conflict resolution, i.e. enabling coexistence of conflicting executables
Abstract
The invention discloses a method for setting equipment firmware, wherein the method comprises the following steps: generating fusion firmware which comprises a data part, a starting part and a system part of factory test firmware, and a starting part and a system part of formal firmware; and placing the fusion firmware into equipment, and modifying a boot loader in the equipment so that the GPT partition table points to a boot part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a boot part and a system part of formal firmware in the fusion firmware after the plant test is finished. By the aid of the method, after factory test is finished, operation of downloading formal firmware can be reduced, and working efficiency is improved.
Description
Technical Field
The invention relates to the technical field of electronic products, in particular to a method and a system for setting equipment firmware and realizing factory test.
Background
With the increasing maturity and popularization of intelligent equipment, the intelligent equipment is widely applied. Before shipping the device, the developer typically needs to prepare two different device firmware, one being the factory test firmware for factory testing and the other being the official firmware for release to the end user.
Because only one firmware file can be installed on the equipment, when the factory test is finished, the factory test firmware is deleted, and the formal firmware is downloaded again, so that the workload of a factory is increased.
Disclosure of Invention
The invention mainly solves the technical problem of providing a method and a system for setting equipment firmware and realizing factory test, which can reduce the operation of downloading formal firmware and improve the working efficiency after the factory test is finished.
In order to solve the technical problems, the invention adopts a technical scheme that: there is provided a method of setting device firmware, the method comprising: generating fusion firmware which comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of the formal firmware; and placing the fusion firmware into the equipment, and modifying a boot loader in the equipment so that the GPT partition table points to a boot part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a boot part and a system part of formal firmware in the fusion firmware after the plant test is finished.
The system comprises a start part and a system part of formal firmware in fusion firmware, a data part and a data part, wherein the start part and the system part of the formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed.
The method comprises the following steps that a start part of a data part of fused firmware is established into two partitions, and a starting part and a system part of factory test firmware are respectively arranged; after the factory test is completed, at least the beginning of the factory test firmware is deleted to format the data portion on the next reboot.
Wherein after factory testing is completed, the factory test firmware is completely deleted to format the data portion at the next reboot.
In order to solve the technical problem, the invention adopts another technical scheme that: a method for realizing factory test is provided, which comprises the following steps: starting the device to load a boot loader; the method comprises the steps that a boot loader obtains a boot part of factory test firmware in fusion firmware by reading a GPT partition table, and then guides a Linux kernel to conduct factory test, wherein the fusion firmware comprises a data part, a boot part and a system part of the factory test firmware, and a boot part and a system part of formal firmware; after the factory test is finished, restarting the equipment to load and start the loader; the boot loader modifies the GPT partition table to point the GPT partition table to a boot portion and a system portion of the formal firmware in the converged firmware.
The system comprises a start part and a system part of formal firmware in fusion firmware, a data part and a data part, wherein the start part and the system part of the formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, so that the GPT partition table points to the starting part and the system part of the formal firmware in the fused firmware.
Wherein, after completing the factory test, restarting the equipment to load the boot loader comprises: setting mark data converted into formal firmware; before the boot loader modifies the GPT partition table, the method comprises the following steps: and judging whether the equipment comprises the mark data or not, if so, executing the step of starting a loader to modify the GPT partition table, and otherwise, not executing.
The method comprises the following steps that a start part of a data part of fused firmware is established into two partitions, and a starting part and a system part of factory test firmware are respectively arranged; after the factory test is completed, the factory test firmware is completely deleted to format the data portion on the next reboot.
In order to solve the technical problem, the invention adopts another technical scheme that: there is provided a system for setting device firmware, comprising: the generating module is used for generating fusion firmware which comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of the formal firmware; the device comprises a setting module and a processing module, wherein the setting module is used for placing the fusion firmware into the device and modifying a start loader in the device so that the GPT partition table points to a start part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a start part and a system part of formal firmware in the fusion firmware after the plant test is completed.
In order to solve the technical problem, the invention adopts another technical scheme that: a system for realizing factory test is provided, which comprises: the first starting module is used for starting the equipment to load the starting loader; the acquisition module is used for acquiring a starting part of the factory test firmware in the fusion firmware by reading the GPT partition table according to the starting loader, and further guiding a Linux kernel to carry out factory test, wherein the fusion firmware comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of formal firmware; the second starting module is used for restarting the equipment to load and start the loader after the factory test is finished; and the modification module is used for modifying the GPT partition table by the boot loader so as to point the GPT partition table to the boot part and the system part of formal firmware in the fusion firmware.
The invention has the beneficial effects that: the factory test firmware and the formal firmware are fused, the GPT partition table points to a starting part and a system part of the factory test firmware in the fused firmware in factory test, and after the factory test is finished, the GPT partition table points to the starting part and the system part of the formal firmware in the fused firmware by modifying a starting loader in equipment, so that the requirements of using the factory test and the formal version are met, the operation of downloading the formal firmware can be reduced, and the working efficiency is improved.
Drawings
FIG. 1 is a flow chart illustrating an embodiment of a method for setting firmware of a device according to the present invention;
FIG. 2 is a schematic flow chart diagram illustrating an embodiment of a factory testing method according to the present invention;
FIG. 3 is a schematic flow chart of another embodiment of a plant testing method according to the present invention;
FIG. 4 is a block diagram of an embodiment of a firmware system for a configuration device according to the present invention;
FIG. 5 is a schematic structural diagram of an embodiment of a plant measurement system according to the present invention;
FIG. 6 is a block diagram of another embodiment of a setup device firmware system of the present invention;
fig. 7 is a structural diagram of another embodiment of the plant testing system according to the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
FIG. 1 is a flowchart illustrating a method for setting firmware of a device according to an embodiment of the present invention. It should be noted that the method of the present invention is not limited to the flow sequence shown in fig. 1 if the results are substantially the same. As shown in fig. 1, the method comprises the steps of:
s11: and generating fusion firmware which comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of the formal firmware.
The device firmware is the software that the most basic, lowest level of the terminal works on. For independently operable end products, device firmware generally refers to an operating system, such as: smart phones, routers or MP4, etc.; for dependent end products, the device firmware is the lowest layer of program code for supporting device operations, such as: hard disk, optical drive or U disk. Therefore, before the user uses the terminal product, the device firmware is written into the hardware system corresponding to the terminal product by other tools or software, and when the terminal is powered on, the device firmware directly drives and calls the system hardware, so that the terminal normally works.
The device firmware generally includes a boot portion, a system portion, and a data portion. Taking an Android system as an example, the equipment firmware mainly comprises a boot partition, a system partition and a data partition, wherein the boot partition comprises a Linux kernel and a start script of the Android system; the system partition mainly comprises an Android system core component, a configuration file and a preset APP program; and the data partition is a storage space inside the device for storing user data, such as pictures, videos, etc. taken. In this embodiment, the factory test firmware includes part of test software, and before shipment of the device, the factory will first install the factory test firmware for testing basic functions, parameters, and the like of the product hardware, and after the test is completed, the factory test version is deleted and then the formal firmware for shipment is installed. The formal firmware is the formal version that is ultimately released for use by the end user. The converged firmware integrates factory test firmware for testing and formal firmware for formal publishing.
Optionally, the boot portion and the system portion of the formal firmware in the fusion firmware are located before the boot portion and the system portion of the plant test firmware, and the data portion is located after the boot portion and the system portion of the plant test firmware. Because the data part of the firmware has large capacity, in the specific implementation, the starting part and the system part of the factory test firmware are stored in the data partition of the formal firmware. Therefore, two partitions are established by fusing the beginning parts of the data parts of the firmware, the starting part and the system part of the factory test firmware are respectively arranged, and after the factory test is finished, at least the beginning parts of the factory test firmware are deleted so as to format the data parts when the factory test firmware is restarted next time.
S12: and placing the fusion firmware into the equipment, and modifying a boot loader in the equipment so that the GPT partition table points to a boot part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a boot part and a system part of formal firmware in the fusion firmware after the plant test is finished.
The boot loader is used for initializing the memory device and further guiding the system kernel. Taking Android as an example, a GPT partition table is adopted in the existing Android system for setting names of the partitions, the names of the partitions in the GPT partition table are read by starting a loader, and then a specific position of a boot partition is obtained, so that a Linux kernel is guided, the Linux kernel obtains the position of a system partition by reading the GPT partition table, and finally, each component of the Android system is loaded.
In this embodiment, the fused firmware is placed in the device, before the factory test, the names of the boot part and the system part of the factory test firmware are set as default names of the system by modifying the GPT partition table, and the names of the boot part and the system part of the formal firmware in the GPT partition table are set as temporary names, so that when the system runs, the GPT partition table points to the boot part of the factory test firmware in the fused firmware, thereby guiding the system kernel, and the system kernel finally obtains the system part by reading the GPT partition table, and then loads each component of the system, thereby completing the factory test. After the factory test is finished, the GPT partition table is modified through the boot loader, the names of the boot part and the system part of the formal firmware are set as default names of the system, so that when the system runs, the GPT partition table points to the boot part and the system part of the formal firmware in the fusion firmware, and finally when the system leaves a factory, the equipment runs as the formal firmware. Meanwhile, after the factory test is completed, the factory test firmware is completely deleted to format the data portion at the next restart. Taking the Android system as an example, in the starting process of the Android system, if the header of the data partition is detected not to contain valid EXT4 file data, the system automatically reformats the data partition into an EXT4 file system.
By the mode, the operation of downloading formal firmware after factory test is finished can be reduced, and the working efficiency is improved.
Referring to fig. 2, fig. 2 is a schematic flow chart of an embodiment of a factory test implementation method of the present invention, in this embodiment, the factory test implementation method includes the following steps:
s21: the device is booted to load the boot loader.
S22: and the boot loader acquires a boot part of the factory test firmware in the fusion firmware by reading the GPT partition table, and further guides the Linux kernel to perform factory test, wherein the fusion firmware comprises a data part, a boot part and a system part of the factory test firmware, and a boot part and a system part of the formal firmware.
The system comprises a start part and a system part of formal firmware in fusion firmware, a data part and a data part, wherein the start part and the system part of the formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, so that the GPT partition table points to the starting part and the system part of the formal firmware in the fused firmware.
S23: after the factory test is completed, the equipment is restarted to load the boot loader.
Optionally, after the factory test is completed, before the device is restarted to load the boot loader, a flag bit "convert to formal firmware" may be added on the graphical interface where the fused firmware runs or in the program where the system runs, and when the factory tester restarts the device, the system detects the flag "convert to formal firmware", the process automatically proceeds to step S24 to complete the conversion from the fused firmware to the formal firmware, otherwise, the process is not executed. In other embodiments, a firmware conversion start button may also be provided on the graphical interface where the firmware is run, and when the tester completes the test, the tester clicks the button, and the device is restarted and automatically enters the firmware conversion process.
S24: the boot loader modifies the GPT partition table to point the GPT partition table to a boot portion and a system portion of the formal firmware in the converged firmware.
The method comprises the steps of integrating the initial part of the data part of the firmware, establishing two partitions, respectively setting the starting part and the system part of the factory test firmware, and completely deleting the factory test firmware after the factory test is finished so as to format the data part when the firmware is restarted next time.
By the method, the starting part and the system part of the factory test firmware are stored in the data partition of the formal firmware, the specific position of the starting part of the factory test firmware is obtained by modifying the file name of the GPT partition table, so that the factory test process is completed, the process of downloading the firmware again is reduced, and the working efficiency is improved.
FIG. 3 is a schematic flow chart of another embodiment of a plant testing method according to the present invention. The following description will be made in detail by taking the Android system as an example with reference to fig. 2 and 3.
The formal firmware 31 includes: a boot partition, a system partition and a data partition; the factory test firmware 32 includes: boot partitions, system partitions, and data partitions. Before the factory test, the factory test firmware and the formal firmware are fused into the GPT partition table, in this embodiment, the start part and the system part of the factory test firmware are stored in the data partition of the formal firmware, and the fused firmware is downloaded to the device. In order to distinguish factory test firmware, a starting part and a system part of formal firmware, a boot partition of the formal firmware is renamed to a boot X partition, a system partition of the formal firmware is renamed to a system X partition by modifying a GPT partition table, and names of the boot partition and the system partition of the factory test firmware in the firmware are fused and unchanged. As shown, the fusion firmware 33 includes: a boot partition, a system X partition, a boot partition, a system partition, and a data partition. When the Linux is started, the GPT partition table points to a boot partition of the factory test firmware by default, and then the Linux kernel is guided to complete the factory test operation.
After the factory test is completed, at least the initial part of the factory test firmware is deleted, in other embodiments, all boot partitions and system partitions of the factory test part can be deleted, only a small initial part can be deleted, when the system is restarted, it is detected that the data partition header does not contain valid EXT4 file data, and the system automatically reformats the data partition into an EXT4 file system. Meanwhile, starting a loader, reading the GPT partition table by the loader, and changing the names of the boot partition and the system partition of the formal firmware back to the boot partition and the system partition to finally obtain a new fused firmware 34, including: and the boot partition, the system partition and the data partition convert the fusion firmware into formal firmware and release the formal firmware to an end user.
By the method, after the factory testing part is finished, the data part is formatted, the firmware file which is the same as the formal firmware is finally obtained, the re-downloading process is reduced, and the working efficiency is improved.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an embodiment of a firmware system of a setting device according to the present invention, where the setting device firmware includes: a generation module 41 and a setting module 42.
The generating module 41 is configured to generate a fusion firmware, where the fusion firmware includes a data portion, a start portion and a system portion of the factory test firmware, and a start portion and a system portion of the formal firmware.
Optionally, the start part and the system part of the formal firmware in the fusion firmware are located before the start part and the system part of the plant test firmware, and the data part is located after the start part and the system part of the plant test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed.
The setting module 42 is configured to place the fusion firmware into the device, and modify a boot loader in the device, so that the GPT partition table points to a boot portion and a system portion of the plant test firmware in the fusion firmware when performing the plant test, and the GPT partition table points to a boot portion and a system portion of a formal firmware in the fusion firmware after the plant test is completed.
Optionally, two partitions are established at the beginning of the data part of the fused firmware, and a start part and a system part of the factory test firmware are respectively set; after the factory test is completed, at least the beginning of the factory test firmware is deleted to format the data portion on the next reboot.
Optionally, after the factory test is completed, the factory test firmware is completely deleted to format the data portion at the next restart.
Fig. 5 is a schematic structural diagram of an embodiment of a factory test system implemented by the present invention, where the setting device firmware includes: a first starting module 51, an obtaining module 52, a second starting module 53 and a modifying module 54.
A first boot module 51 for booting the device to load the boot loader.
The obtaining module 52 is configured to obtain a boot portion of the factory test firmware in the fusion firmware by reading the GPT partition table according to the boot loader, and further boot the Linux kernel to perform factory test, where the fusion firmware includes a data portion, a boot portion and a system portion of the factory test firmware, and a boot portion and a system portion of the formal firmware.
Optionally, the start part and the system part of the formal firmware in the fusion firmware are located before the start part and the system part of the plant test firmware, and the data part is located after the start part and the system part of the plant test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, so that the GPT partition table points to the starting part and the system part of the formal firmware in the fused firmware.
And a second starting module 53, configured to restart the device to load the boot loader after the factory test is completed.
Optionally, after the factory test is completed, before restarting the device to load the boot loader, the method includes: setting mark data converted into formal firmware; before the boot loader modifies the GPT partition table, the method comprises the following steps: and judging whether the equipment comprises the mark data or not, if so, executing the step of starting a loader to modify the GPT partition table, and otherwise, not executing.
And a modification module 54, configured to modify the GPT partition table by the boot loader to point the GPT partition table to a boot portion and a system portion of formal firmware in the converged firmware.
Optionally, two partitions are established at the beginning of the data part of the fused firmware, and a start part and a system part of the factory test firmware are respectively set; after the factory test is completed, the factory test firmware is completely deleted to format the data portion on the next reboot.
Each module and unit in the above embodiments may respectively execute the corresponding steps in the above method embodiments, so that details of each module are not described herein, and please refer to the description of the corresponding steps above in detail.
FIG. 6 is a block diagram of another embodiment of a setup device firmware system of the present invention, the system comprising: a processor 61, and a memory 62 coupled to the processor 61.
The processor 61 is used for generating fusion firmware, wherein the fusion firmware comprises a data part, a starting part and a system part of factory test firmware, and a starting part and a system part of formal firmware; and placing the fusion firmware into the equipment, and modifying a boot loader in the equipment so that the GPT partition table points to a boot part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a boot part and a system part of formal firmware in the fusion firmware after the plant test is finished.
The system comprises a start part and a system part of formal firmware in fusion firmware, a data part and a data part, wherein the start part and the system part of the formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware; the processor 61 is configured to modify the names of the start part and the system part of the formal firmware into the default names of the system after the factory test is completed.
Optionally, the processor 61 is configured to establish two partitions at the beginning of the data portion of the fused firmware, and respectively set the start portion and the system portion of the factory test firmware; after the factory test is completed, at least the beginning of the factory test firmware is deleted to format the data portion on the next reboot.
Optionally, the processor 61 is configured to delete the factory test firmware completely after the factory test is completed, so as to format the data portion at the next restart.
Referring to fig. 7, fig. 7 is a structural diagram of another embodiment of the plant testing system implemented by the present invention, and the system includes: a processor 71, and a memory 72 coupled to the processor 71.
The processor 71 is used to boot the device to load the boot loader; the method comprises the steps that a boot loader obtains a boot part of factory test firmware in fusion firmware by reading a GPT partition table, and then guides a Linux kernel to conduct factory test, wherein the fusion firmware comprises a data part, a boot part and a system part of the factory test firmware, and a boot part and a system part of formal firmware; after the factory test is finished, restarting the equipment to load and start the loader; the boot loader modifies the GPT partition table to point the GPT partition table to a boot portion and a system portion of the formal firmware in the converged firmware.
The system comprises a start part and a system part of formal firmware in fusion firmware, a data part and a data part, wherein the start part and the system part of the formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware; the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, and the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, so that the GPT partition table points to the starting part and the system part of the formal firmware in the fused firmware.
Optionally, the processor 71 is configured to, after the factory test is completed, restart the device to load the boot loader, and before the restart includes: setting mark data converted into formal firmware; before the boot loader modifies the GPT partition table, the method comprises the following steps: and judging whether the equipment comprises the mark data or not, if so, executing the step of starting a loader to modify the GPT partition table, and otherwise, not executing.
Optionally, the processor 71 is configured to establish two partitions at the beginning of the data portion of the fused firmware, and respectively set the start portion and the system portion of the factory test firmware; after the factory test is completed, the factory test firmware is completely deleted to format the data portion on the next reboot.
In the several embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes performed by the present specification and drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method of setting up device firmware, comprising the steps of:
generating fusion firmware which comprises a data part, a starting part and a system part of factory test firmware, and a starting part and a system part of formal firmware;
and placing the fusion firmware into equipment, and modifying a boot loader in the equipment so that the GPT partition table points to a boot part and a system part of the plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a boot part and a system part of formal firmware in the fusion firmware after the plant test is finished.
2. The method of claim 1,
the start part and the system part of formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware, and the data part is positioned behind the start part and the system part of the factory test firmware;
the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, and the starting part, the system part and the names of the factory test firmware are completely deleted after the factory test is completed.
3. The method of claim 1,
establishing two partitions at the beginning part of the data part of the fusion firmware, and respectively setting a starting part and a system part of the factory test firmware;
upon completion of the factory test, at least the boot portion and/or the system portion of the factory test firmware is deleted to format the data portion on the next reboot.
4. The method of claim 3, wherein after completion of factory test, the factory test firmware is completely deleted to format the data portion on the next reboot.
5. A method for realizing factory test is characterized by comprising the following steps:
starting the device to load a boot loader;
the method comprises the steps that a boot loader obtains a boot part of factory test firmware in fusion firmware by reading a GPT partition table, and then guides a Linux kernel to perform factory test, wherein the fusion firmware comprises a data part, a boot part and a system part of the factory test firmware, and a boot part and a system part of formal firmware;
after the factory test is completed, restarting the equipment to load a start loader;
the boot loader modifies the GPT partition table to point the GPT partition table to a boot portion and a system portion of formal firmware in the converged firmware.
6. The method of claim 5,
the start part and the system part of formal firmware in the fusion firmware are positioned in front of the start part and the system part of the factory test firmware, and the data part is positioned behind the start part and the system part of the factory test firmware;
the names of the starting part and the system part of the formal firmware are temporary names, the names of the starting part and the system part of the factory test firmware are system default names, the names of the starting part and the system part of the formal firmware are modified into the system default names after the factory test is completed, and the starting part, the system part and the names of the factory test firmware are completely deleted after the factory test is completed, so that the GPT partition table points to the starting part and the system part of the formal firmware in the fusion firmware.
7. The method of claim 6,
after the factory test is completed, before restarting the equipment to load the boot loader, the method includes:
setting mark data converted into formal firmware;
before the boot loader modifies the GPT partition table, the method includes:
and judging whether the equipment comprises the mark data or not, if so, executing the step of modifying the GPT partition table by the boot loader, and otherwise, not executing.
8. The method of claim 5,
establishing two partitions at the beginning part of the data part of the fusion firmware, and respectively setting a starting part and a system part of the factory test firmware;
after factory testing is completed, the factory test firmware is completely deleted to format the data portion on the next reboot.
9. A system for setting up device firmware, comprising:
the generating module is used for generating fusion firmware which comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of the formal firmware;
and the setting module is used for placing the fusion firmware into equipment and modifying a start loader in the equipment so that the GPT partition table points to a start part and a system part of plant test firmware in the fusion firmware during plant test, and the GPT partition table points to a start part and a system part of formal firmware in the fusion firmware after the plant test is finished.
10. A system for performing factory testing, the system comprising:
the first starting module is used for starting the equipment to load the starting loader;
the acquisition module is used for acquiring a starting part of the factory test firmware in the fusion firmware by reading the GPT partition table according to the starting loader, and further guiding a Linux kernel to carry out factory test, wherein the fusion firmware comprises a data part, a starting part and a system part of the factory test firmware, and a starting part and a system part of formal firmware;
the second starting module is used for restarting the equipment to load the starting loader after the factory test is finished;
and the modification module is used for modifying the GPT partition table by the boot loader so as to point the GPT partition table to a boot part and a system part of formal firmware in the fusion firmware.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610950294.3A CN106569854B (en) | 2016-11-02 | 2016-11-02 | Method and system for setting equipment firmware and realizing factory test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610950294.3A CN106569854B (en) | 2016-11-02 | 2016-11-02 | Method and system for setting equipment firmware and realizing factory test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106569854A CN106569854A (en) | 2017-04-19 |
| CN106569854B true CN106569854B (en) | 2020-05-19 |
Family
ID=58534973
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610950294.3A Active CN106569854B (en) | 2016-11-02 | 2016-11-02 | Method and system for setting equipment firmware and realizing factory test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106569854B (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108235095B (en) * | 2018-01-17 | 2020-12-08 | 深圳创维数字技术有限公司 | Set top box starting/debugging method based on disk medium, set top box and storage medium |
| CN109274807B (en) * | 2018-11-21 | 2021-06-22 | Oppo（重庆）智能科技有限公司 | Test method, device and system |
| CN109710192B (en) * | 2018-12-27 | 2022-04-05 | 公安部物证鉴定中心 | Data erasing method for firmware area used by Western digital hard disk |
| CN111176665B (en) * | 2019-12-26 | 2024-02-09 | 晶晨半导体（深圳）有限公司 | High-capacity emmc mirror image manufacturing method and device |
| CN113821434A (en) * | 2021-09-09 | 2021-12-21 | 摩拜(北京)信息技术有限公司 | Firmware upgrade test method and device, electronic equipment and readable storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103777981A (en) * | 2014-01-13 | 2014-05-07 | 中南大学 | Multi-operation-system remote loading implementation method suitable for X86 framework |
| CN104133706A (en) * | 2014-08-01 | 2014-11-05 | 珠海全志科技股份有限公司 | Firmware modifying method and device |
| CN105204876A (en) * | 2014-06-12 | 2015-12-30 | 联想(北京)有限公司 | System starting method and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7769478B2 (en) * | 2006-06-09 | 2010-08-03 | Lionel L.L.C. | Sound system and method for electric model trains |
-
2016
- 2016-11-02 CN CN201610950294.3A patent/CN106569854B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103777981A (en) * | 2014-01-13 | 2014-05-07 | 中南大学 | Multi-operation-system remote loading implementation method suitable for X86 framework |
| CN105204876A (en) * | 2014-06-12 | 2015-12-30 | 联想(北京)有限公司 | System starting method and electronic equipment |
| CN104133706A (en) * | 2014-08-01 | 2014-11-05 | 珠海全志科技股份有限公司 | Firmware modifying method and device |
Non-Patent Citations (1)
| Title |
|---|
| 基于ARM和Android的智能电视系统研发;张保伟;《中国优秀硕士学位论文全文数据库 信息科技辑》;20121015(第10期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106569854A (en) | 2017-04-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106569854B (en) | Method and system for setting equipment firmware and realizing factory test | |
| CN104615462B (en) | Cross-platform Mobile solution generation service end and system | |
| CN106610839B (en) | Method for issuing upgrade package, lightweight upgrade method, device and system | |
| CN103853586A (en) | Method of realizing wireless card driver in UEFI (unified extensible firmware interface) layer | |
| CN104978271A (en) | Automatic upgrade pressure measurement method and system for Android system | |
| WO2016078263A1 (en) | Upgrading control device and terminal, terminal upgrading method and system, and storage medium | |
| US7293168B2 (en) | System and method for initially configuring and booting a device using a device identifier | |
| CN110221840B (en) | Function implementation method and device of application program, equipment and storage medium | |
| CN115291946A (en) | Hongmong system transplanting method, device, electronic equipment and readable medium | |
| CN105468420B (en) | Operating system update method and apparatus | |
| CN105094911B (en) | A key upgrade method and a key upgrading tool for wireless communication module | |
| CN111930395B (en) | Program downloading method of intelligent terminal and intelligent terminal | |
| CN113254045A (en) | Software initialization method, system and computer readable storage medium | |
| CN105791514B (en) | Application starting monitoring method and device | |
| CN113360161A (en) | Resource upgrading method and related product | |
| CN106445504A (en) | Update method and system of mobile terminal device driver | |
| WO2023060893A1 (en) | Storage space management method and apparatus, and device and storage medium | |
| CN111475347B (en) | Method, device, equipment and medium for supporting hot plug and unplug function of camera | |
| CN111142954B (en) | Startup control method and device and computer readable storage medium | |
| CN108052337A (en) | A kind of firmware upgrade method and device of eMMC production tools | |
| CN103488503B (en) | Oftware updating method and device | |
| CN110750579A (en) | Efficient memory distribution method and system for cloud database Redis | |
| CN107832090B (en) | Method for improving starting speed of man-machine interaction module of fault information processing device | |
| WO2016192296A1 (en) | Method for testing terminal performance, terminal, and storage medium | |
| CN106775798A (en) | A kind of installation method of operating system and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230721 Address after: 361000 room 4101, No. 131, xinjingdongli, Haicang District, Xiamen City, Fujian Province Patentee after: Xiamen Jiupin sesame Information Technology Co.,Ltd. Address before: 518063 16 floor, block B, North TCL building, Nanshan District science and technology south ten road, Shenzhen, Guangdong. Patentee before: JRD COMMUNICATION (SHENZHEN) Ltd. |
|
| TR01 | Transfer of patent right |