CN102830984B - Method, chip and the communication terminal that firmware updates - Google Patents

Abstract

Embodiments of the invention provide method, chip and the communication terminal that firmware updates, and wherein, the method that firmware updates includes: communication terminal knows that the second firmware needs to update；Communication terminal is downloaded the second firmware and is updated the more new data needed；Predetermined flag position is set to the second value by communication terminal；When communication terminal is again started up, the first firmware knows that predetermined flag position is after the second value, it is determined that more new data writing position in the second firmware, and the more new data that the second firmware updates needs writes this writing position, it is achieved the renewal of the second firmware；After second firmware is updated successfully, predetermined flag position is set to the first value by the first firmware；Wherein, the first firmware is firmware more new module, and the second firmware includes: operating system nucleus.Method, chip and the communication terminal that the firmware provided by the embodiment of the present invention is updated, it may be achieved directly completed the renewal of firmware by terminal.

Description

Firmware update method, chip and communication terminal

technical field

The invention relates to the communication field, in particular to a firmware update method, a chip and a communication terminal.

Background technique

With the development of science and technology, the intelligence of mobile terminals is getting higher and higher. With the continuous optimization of each version, most of the firmware in mobile terminals needs to be upgraded frequently. In addition to the completion on the mobile terminal, the rest of the firmware that needs to be updated, including the operating system kernel, can only be downloaded to a personal computer (PC) through the network first, and then use the PC to connect to the mobile terminal. renew.

Contents of the invention

In order to enable the terminal to directly update the firmware that needs to be upgraded, an embodiment of the present invention provides a firmware update method, which is suitable for communication terminals, and the method includes:

The communication terminal learns that the second firmware needs to be updated;

The communication terminal downloads the update data required for the second firmware update;

The communication terminal sets the predetermined flag bit as the second value;

When the communication terminal starts up again, after the first firmware learns that the predetermined flag is the second value, it determines the write position of the update data in the second firmware, and writes the update data needed for the second firmware update into the write position, realizing an update of the second firmware;

After the second firmware is successfully updated, the first firmware sets the predetermined flag to the first value;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

Preferably, the communication terminal downloading the update data required for the second firmware update includes: the communication terminal verifies the update data required for the second firmware update, and stores the verified update data in a predetermined location;

Writing the update data needed for the second firmware update into the writing location includes: obtaining the update data needed for the second firmware update from a predetermined location, and writing the update data needed for the second firmware update into the write location.

Preferably, the update data required for the communication terminal to download the second firmware update includes: the communication terminal downloads the differential packet required for the second firmware update;

Writing the update data required by the second firmware update to the write position by the first firmware includes: writing the differential packet into the write position by the first firmware using a predetermined algorithm.

Preferably, the communication terminal downloading the update data required for the second firmware update includes: the communication terminal verifies the update data required for the second firmware update, and stores the verified update data in a predetermined location;

Writing the update data needed for the second firmware update into the writing location includes: obtaining the update data needed for the second firmware update from a predetermined location, and writing the update data needed for the second firmware update into the write location.

Preferably, when the communication terminal starts up again, the first firmware knowing that the predetermined flag bit is the second value includes:

When the communication terminal starts up again, after the third firmware learns that the predetermined flag is set to the second value, the first firmware is loaded, so that the first firmware knows that the predetermined flag is the second value;

Wherein, the third firmware is the firmware directly loading the first firmware during the startup process of the communication terminal.

Further, the communication terminal includes a processor, the processor includes a first core and a second core, the first firmware is located in the second core, and the operating system kernel is located in the second core;

The second firmware further includes: firmware located on the first core.

Furthermore, the second value is used to indicate that the status of any firmware in the second firmware needs to be updated.

Preferably, after the second firmware is successfully updated, the first firmware sets the predetermined flag bit to the first value, specifically including:

After the second firmware update is successful, the predetermined flag is set to a third value;

The operating system kernel judges whether the operating system corresponding to the operating system kernel needs to be updated;

If an update is required, the operating system kernel updates the operating system, and notifies the first firmware after the update is successful;

The first firmware sets a predetermined flag bit to a first value.

More preferably, after setting the predetermined flag bit to the third value, before the first firmware sets the predetermined flag bit to the first value, the method further includes:

If the communication terminal starts up again, the second firmware learns that the predetermined flag bit is the third value, and returns to the step of updating the operating system.

Further, before the second firmware update is successful, after the first firmware determines the write location of the update data in the second firmware, the method further includes:

The update data required for updating the second firmware is written into the writing position to realize the update of the second firmware.

The embodiment of the present invention also provides another firmware update method, which is suitable for communication terminals, including:

The communication terminal learns that the fifth firmware needs to be updated;

The communication terminal downloads the update data required for the fifth firmware update;

The communication terminal sets the predetermined flag bit as the fourth value;

When the communication terminal starts again, after the fourth firmware learns that the predetermined flag is the fourth value, it forms the backup firmware of the fifth firmware, and determines the first write position of the update data required for the fifth firmware update in the backup firmware of the fifth firmware , and write the update data needed for the fifth firmware update into the first writing position, forming the backup update firmware of the fifth firmware;

The fourth firmware determines the second write location in the fifth firmware, and writes the backup of the fifth firmware to update the data in the firmware, and writes it into the second write location to realize the update of the fifth firmware;

After the fifth firmware is successfully updated, the fourth firmware sets the predetermined flag to the fifth value;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or the firmware that needs to be loaded before the fourth firmware can be loaded during the startup process of the communication terminal.

Preferably, the communication terminal downloads the update data required for the fifth firmware update specifically, the communication terminal verifies the update data required for the fifth firmware update, and stores the update data required for the fifth firmware update that has passed the verification into a predetermined location;

Writing the update data required for the fifth firmware update into the first writing location includes: obtaining the update data required for the fifth firmware update from a predetermined location, and writing the update data required for the fifth firmware update into the first write location.

Preferably, the update data required for the fifth firmware update is the differential packet required for the fifth firmware update;

Writing the update data required by the fifth firmware update into the first write location by the fourth firmware includes: the fourth firmware writes the differential packet required by the fifth firmware update into the first write location by using a predetermined algorithm.

Preferably, after the fourth firmware forms the backup firmware of the fifth firmware, the method further includes: the fourth firmware sets the predetermined flag bit to a sixth value;

Before the fifth firmware update is successful, the method further includes:

If the communication terminal starts up again, the fourth firmware learns that the predetermined flag is the sixth value, and returns to the step of determining the first write position of the update data needed for the fifth firmware update in the backup firmware of the fifth firmware.

Preferably, after the fourth firmware forms a backup of the fifth firmware to update the firmware, the method further includes: the fourth firmware sets the predetermined flag bit to the seventh value;

Before the fifth firmware update is successful, the method further includes:

If the fourth firmware learns that the predetermined flag bit is the seventh value when the communication terminal starts up again, return to the step of determining the second writing position in the fifth firmware.

More preferably, when the communication terminal starts up again, before the fourth firmware learns that the predetermined flag bit is the seventh value, it further includes:

After the sixth firmware learns that the predetermined flag bit is the seventh value, it replaces the loading of the fifth firmware with the loading of the backup update firmware of the fifth firmware.

Preferably, the method further includes:

The communication terminal learns that the seventh firmware needs to be updated;

The communication terminal downloads the update data required for the seventh firmware update;

The communication terminal sets the predetermined flag bit as the eighth value;

When the communication terminal starts again, after the fourth firmware learns that the predetermined flag is the eighth value, it determines the write position of the update data required by the seventh firmware update in the seventh firmware, and writes the update data required by the seventh firmware update The writing location realizes the updating of the seventh firmware;

After the seventh firmware is successfully updated, the fourth firmware sets the predetermined flag to the fifth value;

Wherein, the seventh firmware includes: an operating system kernel.

More preferably, the communication terminal includes a processor, the processor includes a third core and a fourth core, the fourth firmware is located in the fourth core, the operating system kernel is located in the fourth core, and the seventh firmware further includes: firmware located in the third core.

Preferably, after the seventh firmware update is successful, the fourth firmware sets the predetermined flag bit to the fifth value, specifically including:

After the seventh firmware update is successful, the predetermined flag is set to the ninth value;

The operating system kernel judges whether the operating system corresponding to the operating system kernel needs to be updated;

If an update is required, the operating system kernel updates the operating system, and notifies the fourth firmware after the update is successful;

The fourth firmware sets the predetermined flag bit to a fifth value.

More preferably, after the predetermined flag is set to the ninth value, before the fourth firmware sets the predetermined flag to the fifth value, the method further includes: if the communication terminal starts up again, the operating system kernel learns that the predetermined flag is The ninth value returns the step of updating the operating system.

Preferably, before the seventh firmware update is successful, after the fourth firmware determines the write position of the update data required for the seventh firmware update in the seventh firmware, the method further includes: writing the update data required for the seventh firmware update This write position realizes the update of the seventh firmware.

The embodiment of the present invention also provides a chip, which is applied to a communication terminal. The chip includes a first firmware and a second firmware, wherein the first firmware includes:

The predetermined flag reading module is used to learn that the second firmware needs to be updated after learning that the predetermined flag on the communication terminal is the second value;

The write position determination module is used to determine the write position of the update data required by the second firmware update in the second firmware after the predetermined flag reading module knows that the second firmware needs to be updated;

The update writing module is used to write the update data required by the second firmware update into the second firmware after the write position determination module determines the write position of the update data required by the second firmware update in the second firmware Location;

A predetermined flag bit setting module, configured to set the predetermined flag bit to a first value after the second firmware update is successful;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

Preferably, the chip includes a first core and a second core, and the first firmware and the operating system kernel are located in the second core;

The second firmware further includes: firmware located on the first core.

Preferably, the predetermined flag bit setting module is further used to set the predetermined flag bit to a third value after the second firmware update is successful, and notify the operating system kernel; and after receiving the operating system kernel update success notification, set The predetermined flag bit is set to the first value;

The operating system kernel is further used to determine whether the corresponding operating system needs to be updated, and if so, update the operating system, and send an update success notification to the first firmware after the update is successful.

The embodiment of the present invention also provides another chip, which is applied to a communication terminal. The chip includes fourth firmware and fifth firmware, and the fourth firmware includes:

The predetermined flag reading module is used to learn that the fifth firmware needs to be updated after knowing that the predetermined flag on the communication terminal is the fourth value;

A firmware backup module, configured to form backup firmware of the fifth firmware after learning that the predetermined flag bit is a fourth value;

The first writing position determination module is used to determine the first writing position of the update data required for updating the fifth firmware in the backup firmware of the fifth firmware after forming the backup firmware of the fifth firmware;

The backup firmware update module is used to write the update data needed for the fifth firmware update into the first write position, forming the backup update firmware of the fifth firmware;

The second write position determination module is used to determine the second write position in the fifth firmware after the backup firmware update module forms the backup update firmware of the fifth firmware;

Backup update firmware write module, after the second write position is determined, the data in the backup update firmware of the fifth firmware is written into the second write position to realize the update of the fifth firmware;

A predetermined flag bit setting module, configured to set the predetermined flag bit to a fifth value after the fifth firmware update is successful;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or the firmware that needs to be loaded before the fourth firmware can be loaded during the startup process of the communication terminal.

More preferably, the predetermined flag bit setting module is further configured to set the predetermined flag bit to a sixth value after the firmware backup module forms the backup firmware of the fifth firmware;

The predetermined flag reading module is further configured to, when the communication terminal starts up again, notify the backup firmware update module to form the fifth firmware after knowing that the predetermined flag on the communication terminal is the sixth value. Backup and update firmware.

Preferably, the predetermined flag bit setting module is further used to set the predetermined flag bit to the seventh value after the backup firmware update module forms the backup update firmware of the fifth firmware;

The predetermined flag bit reading module is further used to notify the backup update firmware writing module to implement the fifth firmware update after knowing that the predetermined flag bit on the communication terminal is the seventh value when the communication terminal starts up again.

More preferably, the chip further includes sixth firmware, which is used to replace the loading of the fifth firmware with the loading of the backup update firmware of the fifth firmware after knowing that the predetermined flag bit is the seventh value when the communication terminal starts up again .

Preferably, the chip further includes the seventh firmware; the predetermined flag reading module is further used to know that the seventh firmware needs to be updated when the predetermined flag is set to the eighth value;

The fourth firmware further includes:

A writing location determination module, configured to determine the writing location of the update data required for updating the seventh firmware in the seventh firmware after the predetermined flag bit reading module learns that the seventh firmware needs to be updated; and

The update writing module is used for the write position determining module to write the update data required for the seventh firmware update after determining the write position of the update data required for the seventh firmware update in the seventh firmware Enter the write position in the seventh firmware to realize the update of the seventh firmware;

The predetermined flag bit setting module is further used to set the predetermined flag bit to a fifth value after the seventh firmware update is successful;

The seventh firmware includes: an operating system kernel.

The embodiment of the present invention also provides a communication terminal, including the first firmware and the second firmware, and the communication terminal further includes:

An update status learning module, configured to learn that the second firmware needs to be updated;

a download module, configured to download the update data required for the second firmware update; and

The flag bit setting module is used to set the predetermined flag bit to a second value after the update state acquisition module learns that the second firmware needs to be updated;

The first firmware is used for, when the communication terminal starts up again, after knowing that the predetermined flag bit is the second value, determine the write position of the update data in the second firmware, and write the update data required by the second firmware update into this Write the location to realize the update of the second firmware; and when the second firmware update is successful, set the predetermined flag bit to the first value;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

The embodiment of the present invention also provides another communication terminal, including fourth firmware and fifth firmware, and the communication terminal further includes:

An update status learning module, configured to learn that the fifth firmware needs to be updated;

A download module, configured to download update data needed for the fifth firmware update; and

The flag bit setting module is used to set the predetermined flag bit to the fourth value after the update state acquisition module learns that the fifth firmware needs to be updated;

The fourth firmware is used for, when the communication terminal is started again, after learning that the predetermined flag is the fourth value, the backup firmware of the fifth firmware is formed, and it is determined that the update data required for the fifth firmware update is in the backup firmware of the fifth firmware. The first write location, and the update data needed for the fifth firmware update is written into the first write location, forming the backup update firmware of the fifth firmware; then determine the second write location in the fifth firmware, and backup update firmware Write the data in the second write position to realize the update of the fifth firmware; when the fifth firmware update is successful, the predetermined flag is set to the fifth value;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or the firmware that needs to be loaded before the fourth firmware can be loaded during the startup process of the communication terminal.

The firmware update method, chip, and communication terminal provided by the embodiments of the present invention can enable the communication terminal to realize its own firmware update by relying on the interaction between itself and the network end, and get rid of the dependence of the firmware that needs to be upgraded in the terminal through the PC upgrade, and at the same time Increased security and reliability of updates or upgrades.

Description of drawings

Fig. 1 is the schematic flow chart of the method of an embodiment of the present invention;

Fig. 2 is a schematic diagram of a dual-core firmware framework according to an embodiment of the present invention;

Fig. 3 is a schematic flow chart of a method according to an embodiment of the present invention;

4 is a schematic diagram of a chip structure according to an embodiment of the present invention;

Fig. 5 is a schematic diagram of chip structure according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a chip structure according to an embodiment of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below in conjunction with the embodiments and the accompanying drawings. Here, the exemplary embodiments and descriptions of the present invention are used to explain the present invention, but not to limit the present invention.

The present invention mainly provides a method for upgrading the firmware of a communication terminal, especially an intelligent terminal, and a terminal using this method, which reduces the dependence on a personal computer for upgrading the firmware of an intelligent terminal, accelerates the adoption of new functions and services of the terminal, and improves maintenance efficiency. , service and troubleshooting efficiency, while prolonging the service life of the terminal and improving user satisfaction.

Referring to Fig. 1, the present invention provides a method implementation of firmware update, applicable to communication terminals, including:

The communication terminal learns that the second firmware needs to be updated;

The communication terminal downloads the update data required for the second firmware update;

The communication terminal sets the predetermined flag bit as the second value;

When the communication terminal starts up again, after the first firmware learns that the predetermined flag bit is the second value, it determines the write position of the update data in the second firmware, and writes the update data required by the second firmware update into the position to realize the second firmware update. update;

After the second firmware is successfully updated, the first firmware sets the predetermined flag to the first value;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

The following embodiments provided by the present invention will be described below by taking Qualcomm dual-processor chips QSD7xxx and QSD8xxx series chips adopted by smart mobile terminals as examples. The chip is a dual-processor (abbreviated as dual-core) chip, consisting of a baseband processor (Baseband Processor, BP) and an application processor (Application Processor, AP) dual processors. As shown in Figure 2, the chip is composed of two processors, ARM9 (BP) and ARM11 (AP), and the two processors interact through shared memory (SharedMemory). The ARM9 handles communication protocols, radio frequency, general-purpose input/output (GPIO), and more. ARM11 is responsible for common tasks, the running operating system kernel is Linux, which is loaded on the LINUX firmware of ARM11, and the operating system Android is called by the LINUX firmware and loaded on the ANDROID firmware. ARM11 is loaded by calling ARM9, and ARM9 is the main control chip in the usual sense. Referring to Figure 2 below, the main firmware of the Qualcomm QSD8 series chip is roughly introduced as follows:

PBL (Primary Boot Loader) is the basic boot loader: located in ARM9, in the onboard read-only memory (Read-Only Memory, ROM), which stores the initial code for terminal startup, responsible for loading the following DBL, and generally does not need to be updated.

DBL (DeviceBootLoader) is the device boot loader: located in ARM9, the following OSBL and FSBL are loaded into the random access memory (random access memory, RAM) by reading the flash memory flash, and the basic device configuration for terminal initialization is generally not required. renew.

FSBL (Fail-safeBootLoader) is the boot error recovery loader: located in ARM9, it is used to recover the error during terminal startup, and loads the following OSBL, generally no update is required. The processor chips of some manufacturers do not have a separate FSBL, and its functions are completed by the DBL.

OSBL (Operating System Boot Loader) is the operating system boot loader: located in ARM9, it is used to load the following ADSP, AMSS, APPSBL, and realize the SD card upgrade of the ARM9 processor side, verify the checksum and call the display of the boot logo, etc.

APPSBL (Applicationsystembootloader) application system boot loader: located in ARM11, it is the loader of the ARM11 processor, used to upgrade the SD card on the ARM11 processor side, and load the operating system kernel (KERNEL), etc. In this processor chip, the operating system kernel is LINUX.

ADSP: Located on the ARM9 side, it is a digital signal processor (Digital Signal Processing, DSP) on the ARM9 side, and is loaded by the above-mentioned OSBL when the terminal starts.

AMSS (Advanced Mobile Subscriber Software): Located on the ARM9 side, it is the operating system (Operating System, OS) of the processor ARM9, and is loaded by the above-mentioned OSBL when the terminal starts.

LINUX (linuxkernel): Located on the ARM11 side, it is the operating system kernel of the processor ARM11. When the terminal starts, it is loaded by the above APPSBL.

ANDROID (androidsystem): ARM11 core operating system, the terminal is loaded by the above-mentioned LINUX when it starts.

The call sequence of each firmware in the terminal startup process is shown by the arrow line in Figure 2. The OSBL on the baseband processor (BP) loads the ADSP and AMSS of the same core as it, and the APPSBL of the application processor (AP) to realize Cross-core (processor) loading.

Figure 2 also includes a firmware update module named Fota_ua, which is an update agent (updateagent) of firmware over-the-air (FOTA), which is located on the LINUX of the ARM11 side and used to update the firmware. When the terminal starts Subject to loading by APPSBL above. In the prior art, since the firmware update module itself is located on LINUX, it can only be updated by LINUX for the loaded ANDROID, and other firmware that needs to be updated, such as AMSS, ADSP, and firmware such as LINUX itself, are not provided by LINUX loads (LINUX also can't realize self-update, can only realize its update by means of PC), so then can't update it by LINUX, promptly can't realize directly completing the update of these firmwares by mobile terminal.

In one embodiment of the present invention, the firmware update module is used as a firmware alone to realize the update of other firmware, the first firmware is the firmware update module is Fota-ua (hereinafter referred to as Fota), and the operating system kernel is LINUX, which loads The firmware of the operating system is ANDROID (the corresponding operating system is the Android software system).

When the communication terminal learns that LINUX needs to be updated, it downloads the update data required for LINUX to be updated, and sets the predetermined flag bit to a specific value, which is used to indicate that LINUX needs to be updated. In the process of restarting the terminal, it is loaded to Fota, and Fota reads the value of the predetermined flag, and knows that LINUX needs to be updated, so it determines the writing position of the above-mentioned update data in LINUX, and writes the above-mentioned update data into this position. Implement updates to LINUX. If the writing is successful, Fota sets the predetermined flag bit to another specific value, indicating that the update of LINUX is successful.

The above-mentioned communication terminals know that LINUX needs to be updated. When LINUX has an updated version, the server side obtains the latest version and notifies all communication terminals in the form of wireless broadcast (if it is a communication terminal of a fixed connection mode, it is notified by a fixed network line) ) and learned. The server side can take the latest version of LINUX and the images or data of its previous versions respectively, use a predetermined algorithm to make a difference package of the images or data of the two versions, and save them.

Compared with the previous version, the latest version may be an upgraded version, or it may be an old version that needs to be restored due to some errors in the previous version, so the above-mentioned update can be an upgrade or a restoration. The difference package of the two versions produced by a predetermined algorithm, that is, the incremental data, may be directly added data or data covering part of the original data, or both. The predetermined algorithm used for the above-mentioned different update situations can be any known incremental data algorithm or restoration algorithm, etc. For example, the server side can use the algorithm and tools provided by Redband to create a mirrored differential package.

The server side can also not make a differential packet, but directly save all the contents of the new version, so that the communication terminal can directly download all the data of the new version, determine the coverage position on the LINUX, and directly cover the data of the new version on the LINUX. However, this method causes a large amount of data downloaded by the terminal and a slow update speed. Especially for mobile terminals using wireless networks and terminals with small memory, it is more advantageous to use the differential packet writing method.

The above-mentioned communication terminal knows that LINUX needs to be updated, and the file system (FileSystem, FS) unit in the operating system firmware (ie ANDROID) detects that there is firmware (in this example, LINUX) that needs to be updated on the server side, and the FS unit then downloads the above-mentioned image difference package (in this example, take the mirrored differential package stored on the server side as an example), and store it in a predetermined area of the communication terminal, such as a specific partition of nand (a flash memory), or an emmc card (a type of memory Embedded memory, often used in mobile terminals). Alternatively, a software running on the ANDROID can also be used to detect whether there is a differential packet for firmware update on the server side, and after detecting a differential packet, notify the FS unit to download, or the software can be directly downloaded to the communication terminal.

After the FS unit downloads the image differential package required for LINUX update, write the logo that LINUX needs to update in a status information file, and then restart the terminal; Readable by DBL, FSBL (when this firmware exists), Fota and LINUX. The flag that LINUX needs to update is the above-mentioned second value, which is assumed to be 2 here (here is only an example, for example, it can be represented by the binary number 0010). The initial value of the flag bit FOTA_FLAG is assumed to be 1 (binary number 0001, that is, the above-mentioned first value), and the initial value indicates that each firmware in the terminal does not need to be updated.

During the restart process of the terminal, DBL reads the value of the flag bit FOTA_FLAG, and knows that the firmware to be updated is LINUX, so no special processing is required, and the basic device configuration is loaded, and the normal loading sequence is maintained, so that the terminal is gradually loaded to APPSBL . The value of the flag bit FOTA_FLAG read by the above DBL can also be performed by the FSBL, but because some chip products do not have a separate FSBL, only the DBL is used to read the value of the flag bit FOTA_FLAG for description. Since there is no need for special processing in the process of restarting the terminal, the reading of the flag bit FOTA_FLAG by DBL and FSBL is not a necessary step to update LINUX by Fota. After APPSBL loads Fota, Fota reads the value of the flag bit FOTA_FLAG, that is, it knows that LINUX needs to be updated, so first confirms the writing position of the data in the above mirror differential package in LINUX, and then uses the RedBend algorithm to write to this position to realize the LINUX update.

After the above writing is completed, that is, after the update is successful, Fota writes the completion flag in the flag bit FOTA_FLAG. The completion flag can specifically identify the success of the update to LINUX (that is, other firmware updates successfully use other values), or it can be directly restored to The initial value is 1 (the first value above), because the initial value indicates that there is no firmware to be updated, and the update of LINUX has been completed, and when no other firmware needs to be updated at the same time (generally, it is rare that several firmwares need to be updated at the same time), the Available initial values indicate that LINUX has been updated. Fota can not only update the firmware wirelessly, but Fota can also use the update method described in this application to update the firmware during wired update.

In a specific embodiment, the communication terminal downloading the update data required for the second firmware update includes: the communication terminal verifies the update data required for the second firmware update, and stores the verified update data in a predetermined location;

Writing the update data required for the second firmware update into the write location includes: obtaining the update data required for the second firmware update from the predetermined location, and writing the update data required for the second firmware update into the write location. into position.

After the FS unit on the terminal ANDROID downloads the image difference package, it can be directly stored in the predetermined area, or it can be cached and verified after downloading, such as identifying the server side, that is, the information publisher, whether it is a fake identity information publisher ( For example, the LINUX image differential package is not officially released). After the verification is passed, the mirror differential packet is written into the predetermined area. In the subsequent update steps, Fota will pass the verification and store the differential packets required for LINUX update in the predetermined area for reading and writing.

In another specific embodiment, after the FS unit writes the LINUX image difference package into the specific partition of nand, and sets the flag value that LINUX needs to update for FOTA_FLAG, it can directly guide the terminal to enter the restart state, or first display the prompt message, asking whether to restart the terminal, if the user chooses to skip the update link, the value of the flag bit FOTA_FLAG indicating that LINUX needs to be updated is kept as 2, and the image difference package required for LINUX update is also kept in the specific partition of nand, continue to use The current version of LINUX in the terminal will not be updated until Fota reads the flag when the terminal is started next time.

In another embodiment, Fota itself does not directly read the value of the flag bit FOTA_FLAG. After the above-mentioned FS downloads the differential package needed for LINUX update, and restarts the communication terminal, the first firmware learns that the predetermined flag bit is the second value including:

After the third firmware learns that the predetermined flag is set to the second value, the first firmware is called to make the first firmware know that the predetermined flag is the second value;

Wherein, the third firmware is firmware that directly loads the first firmware during the startup process of the communication terminal.

The above-mentioned third firmware is APPSBL, which loads Fota during terminal startup. After APPSBL is loaded, read the value of the flag FOTA_FLAG to 2, that is, it knows that LINUX needs to be updated, so when loading Fota, it notifies the value of the flag FOTA_FLAG to 2 (the comparison table between the value of the flag FOTA_FLAG and its identification content is stored in Fota) , or directly notify LINUX that it needs to be updated, so that Fota completes the update of LINUX by determining the location where LINUX update data is written and writing update data at this location.

In another embodiment, the communication terminal includes a processor including a first core and a second core, the first firmware is located in the second core, and the operating system kernel is located in the second core; and the second firmware further includes: a processor located in the first core firmware.

In this embodiment, the second firmware also contains ADSP and AMSS. The first firmware Fota and the operating system kernel LINUX are located in the second core, namely ARM11, and both ADSP and AMSS are located in the first core, namely ARM9. Fota can not only update the firmware LINUX with the same core (that is, located in the same processor, hereinafter referred to as the same core), but also update the firmware ADSP and AMSS in ARM9 across cores. Because the two cores interact through shared memory, the differential package required for ADSP or AMSS update downloaded by the FS unit of ANDROID (for the convenience of description, the following uses writing differential data as an example to realize firmware update) is stored in nand The specific partition can be used by Fota to write to ADSP or AMSS in a different core to achieve update. The specific partition of nand in this example and the specific partition of nand in the previous example can share the same specific partition. The identification information on the differential package can be used to distinguish which firmware the differential package in the partition belongs to, and it can also update LINUX, ADSP and AMSS The required differential packets are stored in specific partitions of different nands, and it can be identified which firmware the stored differential packets belong to from the location of the partitions. After Fota successfully writes the differential packet to the corresponding position of ADSP or AMSS, it will feed back to OSBL, so that OSBL will re-call the updated ADSP or AMSS to enter the memory.

The value of the flag bit FOTA_FLAG in the above-described embodiment is 2 and only indicates that LINUX needs to be updated (that is, a specific firmware needs to be updated), and the flag bit that ADSP and AMSS need to update can be set to other values (such as binary numbers 0011 and 0100), so that Fota When the flag bit FOTA_FLAG is read, it is known which specific firmware needs to be updated. In an alternative embodiment, the value of the flag bit FOTA_FLAG is 2, and any one or more firmwares in LINUX, ADSP or AMSS need to be updated, because the update methods of these several firmwares are roughly the same, and can be reset to one class firmware. Since the update data (differential packet) carries identification information of different firmware, Fota can determine which specific firmware needs to be updated according to the identification information in the update data after reading the flag bit FOTA_FLAG to know which type of firmware needs to be updated. Update, this makes the flag bit easier, for example, only 8-bit binary, that is, 1 Byte, is needed to set the length of the flag bit, and the subsequent embodiments of this paper are all described in this way. There are few scenarios where two or three firmwares in LINUX, ADSP, and AMSS need to be updated at the same time. Only after such firmwares of all the firmwares are successfully updated, Fota will set the value of the flag bit FOTA_FLAG to the first value (such as the initial value 1).

In another embodiment, after the above-mentioned second firmware update is successful, the first firmware setting the predetermined flag bit to the first value specifically includes:

After the second firmware update is successful, the predetermined flag is set to a third value;

The operating system kernel judges whether the operating system corresponding to the operating system kernel needs to be updated;

If an update is required, the operating system kernel updates the operating system, and notifies the first firmware after the update is successful;

The first firmware sets a predetermined flag bit to a first value.

In a specific embodiment, the firmware update data downloaded by the FS unit from the server includes differential packets required for updating LINUX, ADSP and/or AMSS, and differential packets required for updating ANDROID. Of course, there are very few scenarios where ADSP and/or AMSS and ANDROID need to be updated at the same time. Only in individual cases, LINUX and ANDROID need to be updated at the same time. In the case of only one flag FOTA_FLAG, the value of the flag FOTA_FLAG is set to 2, which is used to indicate that LINUX, ADSP and/or AMSS need to be updated. At this time, Fota cannot know whether ANDROID also needs to be updated. In this embodiment, after LINUX, ADSP and/or AMSS are successfully updated, Fota first changes the flag bit FOTA_FLAG from 2 to 3, and then notifies LINUX to determine whether ANDROID needs to be updated. If ANDROID does not need to be updated, LINUX will change the flag bit FOTA_FLAG to 1 (0001). 1 is the initial state, that is, no firmware needs to be updated or all firmware updates are successful. If the ANDROID needs to be updated, then LINUX determines the write position of the differential package in the ANDROID, and writes the differential package into this position to complete the update of the ANDROID.

In a preferred embodiment based on the above embodiments, after the predetermined flag bit is set to the third value, before the first firmware sets the predetermined flag bit to the first value, the firmware update method further includes:

If the communication terminal starts up again, the second firmware learns that the predetermined flag bit is the third value, and returns to the step of updating the operating system.

The flag bit FOTA_FLAG is used to know which or which type of firmware of the terminal needs to be updated. If the current update fails, the firmware that needs to be updated can be quickly located during the next startup process and the firmware can be updated again.

In the above-mentioned embodiments, when Fota updates LINUX, ADSP or AMSS, after Fota determines the write position of the differential package in LINUX, ADSP or AMSS, a failure occurs when the differential package is written in this position (including The terminal is powered off), causing the terminal to start again. Since the value of the flag bit FOTA_FLAG is still 2, during the restart process of the terminal, Fota learns from the value of the flag bit FOTA_FLAG that the firmware of LINUX, ADSP or AMSS needs to be updated, and will update the In the write position of the LINUX, ADSP or AMSS update data determined in the second update process, write the corresponding update data again to realize the update of LINUX, ADSP or AMSS. After the update is successful, Fota will set the value of the flag bit FOTA_FLAG back to the initial value. If this update still encounters failures, continue the above-mentioned update of LINUX, ADSP or AMSS during the next startup process.

After the above-mentioned Fota sets the flag bit FOTA_FLAG to 3, if LINUX judges that ANDROID needs to be updated, then update ANDROID. When the update process of LINUX to ANDROID fails, so LINUX has not set the value of the flag FOTA_FLAG to 1, and the terminal restarts due to the update failure, the value of the flag FOTA_FLAG is kept as 3. In the process of restarting, Fota reads that the value of the flag FOTA_FLAG is 3, and then knows that ANDROID needs to be updated, so it directly notifies LINUX to update ANDROID. After LINUX updates ANDROID successfully, the value of flag FOTA_FLAG is set to 1. If LINUX fails to update ANDROID again, the above terminal will continue to restart, and Fota reads the value of flag FOTA_FLAG as 3, and notifies LINUX Steps to update ANDROID.

As mentioned in the previous description, the firmware that needs to be updated by the communication terminal also includes OSBL, APPSBL, and Fota itself. When OSBL, APPSBL, and Fota need to be updated, if only the method in the above-mentioned embodiment is used to implement the terminal itself. Update, in the process of updating OSBL and APPSBL by Fota, if a fault occurs that causes damage to OSBL and APPSBL, Fota can only be loaded after OSBL and APPSBL are successfully loaded, so the OSBL or APPSBL cannot be restored when the terminal restarts, and Fota cannot be loaded to Continue the last incomplete update. In addition, Fota cannot update itself. As shown in Figure 3, the embodiment of the present invention uses the following method to update the firmware:

The communication terminal learns that the fifth firmware needs to be updated;

The communication terminal downloads the update data required for the fifth firmware update;

The communication terminal sets the predetermined flag bit as the fourth value;

When the communication terminal starts up again, after the fourth firmware learns that the predetermined flag is the third value, it forms the backup firmware of the fifth firmware, and determines the first write position of the update data needed for the fifth firmware update in the backup firmware of the fifth firmware , and write the update data needed for the fifth firmware update into the first writing position, forming the backup update firmware of the fifth firmware;

The fourth firmware determines the second write location in the fifth firmware, and writes the data in the backup update firmware to the second write location to realize the update of the fifth firmware;

After the fifth firmware is successfully updated, the fourth firmware sets the predetermined flag to the fifth value;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or the firmware that is called earlier than the fourth firmware during the startup process of the communication terminal.

The above-mentioned fifth firmware includes OSBL, APPSBL and Fota itself, and of course ADSP, AMSS and LINUX can also be included, but the update of the latter three can be realized by using the various embodiments mentioned above, so only OSBL, APPSBL and Fota's own update method. The following still takes the server side as an example to make a mirror image or a differential packet of data and broadcast to notify the communication terminal as an example.

In a specific embodiment, the communication terminal runs a detection software on the FS unit or the ANDROID and learns that OSBL, that is, the above-mentioned fifth firmware needs to be upgraded (this example takes firmware upgrade as an example), and the FS unit or the detection software (hereinafter taking the FS unit as an example) ) Download the differential package required for OSBL update to the emmc card (of course, it can also be stored in a specific partition of nand), and set the value of the predetermined flag bit (the flag bit FOTA_FLAG is described below as an example) to 2 (here only for For example, for example, 2 is the binary number 0010, indicating that the OSBL needs to be updated), which is the fourth value above.

When the terminal starts up again, the above-mentioned fourth firmware, that is, Fota, knows that the fifth firmware (OSBL) needs to be updated by reading the value of the flag FOTA_FLAG to 2, and then forms a backup firmware of OSBL in a predetermined area of the terminal (such as in RAM) , and then determine the write position of the differential package required by the OSBL update on the backup firmware of the OSBL, i.e. the first write position, and write the differential package required by the OSBL update into the first write position, so as to upgrade the backup firmware of the OSBL. After the upgrade is successful, the OSBL backup will be generated to update the firmware.

At this time, Fota first determines the second writing position of the OSBL, and writes the backup update firmware of the OSBL into the second writing position. Generally speaking, writing in the second location is an overwriting of the original version of the OSBL, and when the overwriting succeeds, an update of the OSBL is realized. After overwriting is successful, Fota restores the value of the flag bit FOTA_FLAG to 1 (initial value), that is, no firmware needs to be updated. Since the OSBL has been successfully updated, "no firmware needs to be updated" can also be used to indicate that the OSBL has been successfully updated.

In another embodiment, the communication terminal knows that Fota itself needs to be updated, and downloads the differential package needed for Fota update to the emmc card in the above-mentioned FS unit, and sets the flag bit FOTA_FLAG to 2, and 2 identifies OSBL, APPSBL and Firmware such as Fota needs to be updated, and which firmware needs to be updated can be known from the identification information on the differential package. After the terminal restarts, Fota learns that it needs to update itself from the flag bit FOTA_FLAG, then forms Fota's backup firmware in a predetermined area (such as in RAM), and then determines the writing position of the differential package required for Fota update on Fota's backup firmware That is, the first writing location, and write the differential packet needed for Fota update into the first writing location, upgrade the backup firmware of Fota, and generate the backup update firmware of Fota. Then, Fota determines its own second writing location, so that Fota's backup update firmware is written into the second writing location. After the writing is successful, Fota restores the value of the flag bit FOTA_FLAG to the initial value 1.

In a preferred embodiment, the above-mentioned communication terminal downloading the update data required for the fifth firmware update specifically includes: the communication terminal verifies the update data required for the fifth firmware update, and updates the update data required for the fifth firmware update that has passed the verification deposit into a predetermined location;

Writing the update data required for the fifth firmware update into the first writing location includes: obtaining the update data required for the fifth firmware update from a predetermined location, and writing the update data required for the fifth firmware update into the first write location.

After the FS unit on the communication terminal ANDROID downloads the mirror image or data differential package of the fifth firmware, it can be directly stored in the predetermined area, or it can be cached and verified after downloading, such as identifying the server, that is, the information publisher, whether it is Information publishers who forge their identities (for example, OSBL's mirror image or data differential package is not officially released). After the verification is passed, the above-mentioned image or data differential package is written into the predetermined area. In the subsequent update step, Fota will pass the verification and read and write the differential package required for updating the fifth firmware (such as OSBL) stored in the predetermined area.

In a specific embodiment, after setting the flag bit FOTA_FLAG, the FS unit can guide the terminal to enter the restart state, or first ask whether to restart the terminal by displaying a prompt message. If the user chooses to skip the update link, the flag bit FOTA_FLAG The value of the flag is reserved as 2, and the image or data differential package required for OSBL update is also retained on the emmc card until the next startup of the terminal, when Fota reads the value of this flag as 2, and then upgrades the OSBL.

In another embodiment, the above-mentioned update data required for the fifth firmware update is a differential packet required for the fifth firmware update;

Writing the update data required by the fifth firmware update into the first write location by the fourth firmware includes: the fourth firmware writes the differential packet required by the fifth firmware update into the first write location by using a predetermined algorithm.

In a specific embodiment, the update data is the image differential package of the old and new versions of the fifth firmware (such as APPSBL) (hereinafter referred to as the differential package). After the FS unit in the operating system stores the differential package into a predetermined area of the terminal, Fota, that is, the fourth firmware, first forms the backup firmware of the APPSBL, and uses a predetermined algorithm to determine the first write position of the firmware required by the APPSBL update on the backup firmware of the APPSBL, to write the differential packet, and form the backup update firmware of the APPSBL. The predetermined algorithm can be any known incremental data and corresponding incremental data restoration algorithm, such as using the algorithm and tools provided by Redband.

An alternative embodiment may also be that the terminal directly downloads all the contents of the latest version of the APPSBL, and when updating the backup firmware of the APPSBL, it is enough to completely cover the latest version on the old version, that is, there is no need to use a differential algorithm to Determine the write location of the differential packet and perform differential write.

In the above update process, the fifth firmware has gone through the links of backup-update-overwrite, and if any link fails, the flag bit FOTA_FLAG can be used to indicate the status of the firmware update, so that it can be quickly updated in the next startup process. Locate the link where the failure occurred for connection processing. That is, if there is any failure or power failure during the update (mostly upgrade), Fota can know what state the terminal stopped in the last update process according to FOTA_FLAG.

In another specific embodiment, after the fourth firmware forms the backup firmware of the fifth firmware, the following steps are further included: the fourth firmware sets the predetermined flag bit to the sixth value;

Before the fifth firmware update is successful, the method further includes:

If the communication terminal starts up again, the fourth firmware learns that the predetermined flag is the sixth value, and returns to the step of determining the first write position of the update data needed for the fifth firmware update in the backup firmware of the fifth firmware.

Still taking OSBL to be updated as an example, after the fourth firmware Fota forms the backup firmware of the fifth firmware OSBL, Fota records the predetermined flag bit, the flag bit FOTA_FLAG, as the above-mentioned sixth value, such as 3 (downloading and updating the differential package in this example Afterwards, the value of the flag bit is still set to 2), so the upgrade of the backup firmware of the OSBL is carried out. If the upgrade of the backup firmware of the OSBL fails and restarts again, Fota can know that the backup firmware of the OSBL has been formed from the value of the FOTA_FLAG flag bit of 3, and the upgrade of the backup firmware of the OSBL has not been completed (that is, the backup of the OSBL The update firmware has not been successfully generated), so Fota can directly write the differential package required for OSBL update on the OSBL backup firmware at the first write position determined in the last update, and can also re-determine the first write Enter the location, and then update the backup firmware of OSBL.

On the basis of the above embodiments, or in another separate embodiment, after the fourth firmware forms a backup of the fifth firmware and updates the firmware, the method further includes: the fourth firmware sets the predetermined flag bit to a seventh value;

Before the fifth firmware update is successful, the method further includes:

If the fourth firmware learns that the predetermined flag bit is the seventh value when the communication terminal starts up again, return to the step of determining the second writing position in the fifth firmware.

In a specific embodiment, if the upgrade of the backup firmware of the OSBL is successful, Fota sets the value of the flag bit FOTA_FLAG to the seventh value (such as 4), and then continues to overwrite the original OSBL with the backup firmware of the OSBL. Before the value of FOTA_FLAG is set to 4, its value can be 3, indicating that the backup firmware of OSBL has been formed but the backup update firmware of OSBL has not been generated, or it can be 2, which only indicates that OSBL needs to be updated, but not in OSBL. Adjust the value of the flag bit FOTA_FLAG when the backup firmware has been formed. In the latter case, if the overwriting fails, the terminal will not be able to know that the OSBL backup firmware has been formed during the restart process of the terminal, and Fota needs to generate the OSBL backup firmware again.

On the basis of the above two embodiments, or in another separate embodiment, after the fourth firmware forms a backup of the fifth firmware and updates the firmware, the method further includes: the fourth firmware sets the predetermined flag bit to a seventh value ;

Before the fifth firmware update is successful, the method further includes:

If the fourth firmware learns that the predetermined flag bit is the seventh value when the communication terminal starts up again, return to the step of determining the second writing position in the fifth firmware.

In a specific embodiment, if the backup update firmware of the OSBL successfully covers the OSBL, Fota sets the value of the flag FOTA_FLAG (from 4, following the above embodiment) to the initial value 1 again, indicating that the OSBL update is complete. If the overwriting process fails, the value of the flag FOTA_FLAG remains at 4. When the terminal restarts to Fota, Fota reads the value of FOTA_FLAG as 4, knowing that the OSBL backup update firmware has been generated, and because the overwriting process fails, then Fota directly makes the backup update firmware of the OSBL overwrite the second writing position on the OSBL, or re-determines the second writing position, and then overwrites the OSBL.

Due to failures in the overwriting process of OSBL, APPSBL or Fota backup update firmware on the original firmware, Fota may not be loaded normally when the terminal restarts, so the sixth firmware (including DBL or FSBL) will also be read when the terminal restarts. The value of the flag bit FOTA_FLAG. This example takes DBL as an example. When DBL reads the value of the flag bit FOTA_FLAG as 4, it will change the loading sequence of the firmware. In this example, the value of the flag FOTA_FLAG is 4, which only indicates that there is a problem with the coverage link in the update of firmware such as OSBL, APPSBL, or Fota, but does not specifically indicate which firmware is being updated. There is a problem with the coverage of the firmware, so when DBL reads the value of the flag FOTA_FLAG as 4, it needs to combine the identification information on the differential packet required for firmware update to confirm which specific firmware.

For example, when the value of the flag bit FOTA_FLAG is 4, DBL judges that OSBL is faulty in the overwriting process of backup and update firmware, then DBL changes the firmware loading sequence from FSBL-OSBL-APPSBL to FSBL-OSBL'APPSBL, OSBL' is OSBL backup to update the firmware. When loading to Fota, Fota knows that the value of the flag bit FOTA_FLAG is 4, and also knows from the identification information on the differential package that it is a fault that occurs during the update process of OSBL, then the second write of the OSBL backup update firmware on OSBL The location is covered.

When DBL judges that it is APPSBL that fails in the overwriting process of backup and update firmware, the loading sequence is changed from FSBL-OSBL-APPSBL to FSBL-OSBL-APPSBL', APPSBL' is the backup update firmware of APPSBL. When DBL judges that Fota is faulty in the overwriting process of backup and update firmware, it changes the loading sequence from OSBL-APPSBL-Fota to OSBL-APPSBL-Fota', Fota' is Fota's backup update firmware.

It should be noted that DBL will read the value of the flag bit FOTA_FLAG during each startup of the terminal. When it is not necessary to change the firmware loading sequence, it will be loaded to Fota in the normal order, and Fota will read the value of the flag bit FOTA_FLAG To determine the current update status of the terminal, and then continue the corresponding processing; and when it is necessary to change the firmware loading sequence, adjust the loading sequence, so as to avoid the above-mentioned situation that cannot be restarted.

The above-mentioned situations that do not need to change the firmware loading sequence include: the firmware (such as OSBL, APPSBL) that needs to be loaded before Fota can be loaded, or when Fota itself needs to be updated, and the terminal needs to be restarted due to a fault in the coverage of the backup update firmware; And earlier than, later than or loaded simultaneously with Fota, but whether it is successfully loaded will not affect the situation when the loaded firmware (such as ADSP, AMSS, LINUX and ANDROID) of Fota needs to be updated.

In a specific embodiment, the firmware update method further includes:

The communication terminal learns that the seventh firmware needs to be updated;

The communication terminal downloads the update data required for the seventh firmware update;

The communication terminal sets the predetermined flag bit as the eighth value;

When the communication terminal starts again, after the fourth firmware learns that the predetermined flag is the eighth value, it determines the write position of the update data required by the seventh firmware update in the seventh firmware, and writes the update data required by the seventh firmware update The writing location realizes the updating of the seventh firmware;

After the seventh firmware update is successful, the fourth firmware sets the predetermined flag to the first value;

Wherein, the seventh firmware includes: an operating system kernel.

The above-mentioned seventh firmware includes LINUX. When the communication terminal learns that LINUX needs to be updated through the FS unit, the FS unit rewrites the flag bit FOTA_FLAG to the eighth value (for example, 5) after downloading the differential package, and guides the terminal to start up again. During the restart process of the terminal, after Fota reads the value of the flag FOTA_FLAG to 5, there is no need to generate LINUX backup firmware, so directly determine the write location of the LINUX update data, and write the above-mentioned differential package.

In another embodiment, the communication terminal includes a processor, the processor includes a third core and a fourth core, the fourth firmware is located in the fourth core, the operating system kernel is located in the fourth core, and the seventh firmware further includes: located in the third core firmware.

In a specific embodiment, the processor used by the terminal is a dual-core baseband processor (BP) and an application processor (AP), the third core is the BP, and the fourth core is the AP. Fota and LINUX are located on the AP, and the seventh firmware further includes ADSP or AMSS located on the BP. The two cores interact through shared memory, so the differential packets required for ADSP or AMSS updates downloaded by the FS unit of ANDROID are stored in a predetermined area, and can be used by Fota to write to ADSP or AMSS in different cores. Into the implementation of the update.

On the basis of the above embodiments, after the seventh firmware update is successful, the fourth firmware setting the predetermined flag bit to the fifth value specifically includes:

After the seventh firmware update is successful, the predetermined flag is set to the ninth value;

The operating system kernel judges whether the operating system corresponding to the operating system kernel needs to be updated;

If an update is required, the operating system kernel updates the operating system, and notifies the fourth firmware after the update is successful;

The fourth firmware sets the predetermined flag bit to a fifth value.

After successfully updating the seventh firmware, Fota sets the flag bit FOTA_FLAG to the ninth value (for example, 6), and notifies LINUX to judge whether it is necessary to update ANDROID. If the judgment result is that ANDROID does not need to be updated, then LINUX will flag The bit FOTA_FLAG is set to the fifth value, which is 1 (binary number 0001), or LINUX notifies Fota, and the flag bit FOTA_FLAG is set to 1 by Fota. If the judging result is that the ANDROID needs to be updated, then LINUX determines the writing position of the differential packet in the ANDROID, and writes the differential packet into this position, so as to realize the updating of the ANDROID. It should be noted that if only ANDROID needs to be updated during the entire update process, FS will set the flag bit FOTA_FLAG to 6 at the beginning, and Fota can directly call LINUX to update ANDROID after obtaining the value of the flag bit FOTA_FLAG, so the above update methods are mostly LINUX and It is recommended when ANDROID releases a new version at the same time and needs to be updated at the same time.

Further, after the predetermined flag is set to the ninth value, before the fourth firmware sets the predetermined flag to the fifth value, the method further includes: if the communication terminal starts up again, the operating system kernel learns that the predetermined flag is The ninth value returns to the step of updating the operating system.

Specifically, if LINUX breaks down during the update process of ANDROID and causes the update to fail (such as a power failure during the update process), the value of the flag bit FOTA_FLAG remains at 6 (ninth value), and in the next startup process of the terminal , Fota recognizes that the flag FOTA_FLAG is 6, then informs LINUX to update ANDROID, until after the ANDROID update is successful, LINUX notifies Fota, and Fota sets the flag FOTA_FLAG to the fifth value (ie, the initial value 1), and completes the entire update process.

In one embodiment, before the seventh firmware update is successful, after the fourth firmware determines the write position of the update data required for the seventh firmware update in the seventh firmware, the method further includes: updating the update data required for the seventh firmware update Data is written into the writing location to realize updating of the seventh firmware.

If the seventh firmware (such as ADSP) breaks down during the update process, causing the terminal to start again, and when Fota is loaded, it is recognized that the seventh firmware needs to be updated from the eighth value (5) of the flag FOTA_FLAG, then the The differential packet required for ADSP update is written to the write position on the ADSP determined in the last update process, so as to realize the update of ADSP.

The present invention also provides a chip, as shown in FIG. 4, which is applied to a communication terminal. The chip includes a first firmware and a second firmware, wherein the first firmware includes:

The predetermined flag reading module is used to learn that the second firmware needs to be updated after learning that the predetermined flag on the communication terminal is the second value;

A writing location determination module, configured to determine the writing location of the update data required for the second firmware update in the second firmware after the predetermined flag bit reading module learns that the second firmware needs to be updated;

The update writing module is used for the write position determining module to write the update data required for the second firmware update after determining the write position of the update data required for the second firmware update in the second firmware into the write location in the second firmware;

A predetermined flag bit setting module, configured to set the predetermined flag bit to a first value after the second firmware update is successful;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

The above-mentioned first firmware and the operating system kernel correspond to the first firmware (Fota) and the operating system kernel (LINUX) in the above-mentioned method embodiment respectively, and are included in the chip provided above. After the scheduled flag reading module is informed that the predetermined flag on the communication terminal is the second value (such as 2), the flag FOTA_FLAG knows that LINUX needs to be updated; After the update, determine the write position of the update data required by the LINUX update in LINUX; after the write position determination module determines the write position of the update data required by the LINUX update in LINUX, update the required update data of the LINUX update Data is written into this writing location; After the LINUX update is successful, the predetermined flag bit setting module sets the flag bit FOTA_FLAG to the first value (such as initial value 1, which is used to identify the current state as no firmware needs to be updated, which also indicates that this updated successfully).

Further, the above-mentioned chip includes a first core and a second core, and the first firmware and the operating system kernel are located in the second core;

The second firmware further includes: firmware located on the first core.

See the above method embodiment, for the dual-core chip, Fota and LINUX are located on the second core (ARM11 or AP), ADSP and AMSS are located on the first core (ARM9 or BP), Fota can also pass the above modules To realize the cross-core update of ADSP and AMSS.

Further, the above-mentioned predetermined flag bit setting module is further configured to, after the second firmware update is successful, set the predetermined flag bit to a third value, and notify the operating system kernel; After the update of the kernel is successfully notified, the predetermined flag is set to the first value;

The operating system kernel is further used to judge whether its corresponding operating system needs to be updated, and if it needs to be updated, update the operating system, and send the update success notification to the first firmware after the update is successful.

In the case that the flag bit FOTA_FLAG can only set one value at a time, there may be scenarios where LINUX and ANDROID need to be updated at the same time (ADSP, AMSS, and ANDROID need to be updated at the same time, almost never), so if LINUX and ANDROID need to be updated at the same time In the scenario, the flag bit FOTA_FLAG will be set to the second value by the FS unit of ANDROID, which means that LINUX needs to be updated. When the LINUX update is successful, LINUX (or it notifies Fota, and Fota) will set the flag bit FOTA_FLAG to the third value. (such as 3), and then LINUX will judge whether ANDROID needs to be updated. If LINUX judges that ANDROID needs to be updated, then LINUX updates ANDROID, and after the update is successful (or it notifies Fota, by Fota) the flag bit FOTA_FLAG is set back to the initial value (1); if LINUX judges that ANDROID does not need to be updated, Then (or it notifies Fota, Fota) sets the flag bit FOTA_FLAG back to the initial value (1).

Similarly, if a failure occurs during the update of LINUX, ADSP or AMSS, when the terminal starts up again, the flag bit FOTA_FLAG remains at 2, and when Fota reads the value of the flag bit FOTA_FLAG, it can know that it is LINUX, ADSP Or there is a failure in the update process of AMSS, so continue to update LINUX, ADSP or AMSS.

At the same time, the present invention also provides a chip, which is applied in a communication terminal, and the chip includes fourth firmware and fifth firmware, wherein the fourth firmware includes:

The predetermined flag reading module is used to learn that the fifth firmware needs to be updated after knowing that the predetermined flag on the communication terminal is the fourth value;

A firmware backup module, configured to form backup firmware of the fifth firmware after learning that the predetermined flag bit is a fourth value;

The first writing location determination module is configured to determine the first writing location of the update data required for updating the fifth firmware in the backup firmware of the fifth firmware after forming the backup firmware of the fifth firmware;

A backup firmware update module, configured to write the update data needed for the fifth firmware update into the first write location, to form a backup update firmware of the fifth firmware;

The second write location determination module is used to determine the second write location in the fifth firmware after the backup firmware update module forms the backup update firmware of the fifth firmware;

The backup and update firmware writing module is used to write the data in the backup and update firmware of the fifth firmware into the second write position after the second write position is determined, so as to implement the fifth firmware. renew;

A predetermined flag bit setting module, configured to set the predetermined flag bit to a fifth value after the fifth firmware update is successful;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or firmware that needs to be loaded before the fourth firmware can be loaded during the startup process of the communication terminal.

The above-mentioned fourth firmware and the operating system kernel correspond to the fourth firmware (Fota) and the fifth firmware (which may include OSBL, APPSBL, and Fota itself) in the above-mentioned method embodiment respectively, and are included in the chip provided above. After knowing that the predetermined flag on the communication terminal, that is, the flag FOTA_FLAG, is the fourth value (such as 2), the predetermined flag read module knows that the fifth firmware (such as OSBL) needs to be updated; the firmware backup module learns that the predetermined flag After being 2, form the backup firmware of OSBL; After the backup firmware of OSBL is formed by the first write position determination module, determine the first write position of the update data that OSBL updates needs in the backup firmware of OSBL; Backup firmware The update module then writes the update data required by the OSBL update into the first write position to form the backup update firmware of the OSBL; the second write position determination module determines the first in the OSBL after the backup firmware update module forms the backup update firmware of the OSBL Two writing positions; after the backup update firmware writing module is determined in the second writing position, the data in the backup update firmware of OSBL is written into the second writing position to realize the update of OSBL; the predetermined flag bit setting module is in the OSBL After the update is successful, the predetermined flag bit, ie, the flag bit FOTA_FLAG, is set to the fifth value (such as an initial value of 1, which is used to indicate that the current state is that there is no firmware to be updated, which indicates that the update is successful).

Further, the predetermined flag bit setting module is further configured to set the predetermined flag bit to a sixth value after the firmware backup module forms the backup firmware of the fifth firmware;

The predetermined flag reading module is further configured to, when the communication terminal starts up again, notify the backup firmware update module to form the fifth firmware after knowing that the predetermined flag on the communication terminal is the sixth value. Backup and update firmware.

After the firmware backup module in Fota forms the backup firmware of OSBL, the predetermined flag bit setting module in Fota is set to the sixth value (such as 3) with flag bit FOTA_FLAG, like this, when the backup firmware of OSBL is carried out in the next update link When a fault occurs during updating, when the communication terminal starts again, the predetermined flag reading module in Fota learns that the flag FOTA_FLAG is 3, and then notifies the backup firmware update module to form a backup update firmware of OSBL.

Further, the predetermined flag bit setting module is further configured to set the predetermined flag bit to a seventh value after the backup firmware update module forms the backup update firmware of the fifth firmware;

The predetermined flag reading module is further used to notify the backup update firmware writing module to implement the fifth value after learning that the predetermined flag on the communication terminal is the seventh value when the communication terminal starts up again. Firmware update.

After the backup update firmware of OSBL is formed by the predetermined flag bit setting module, the flag bit FOTA_FLAG is set to the seventh value (such as 4) after the backup firmware update module forms the OSBL; After the flag bit FOTA_FLAG is 4, notify the backup update firmware write module to implement OSBL update.

Further, the chip further includes sixth firmware, which is used to replace the loading of the fifth firmware with the backup of the fifth firmware after knowing that the predetermined flag bit is the seventh value when the communication terminal restarts Loading of updated firmware.

The safer mode is that the sixth firmware (DBL or FSBL) will read the value of the flag bit FOTA_FLAG every time the terminal is started. When there is a fault in the content, the value of the flag FOTA_FLAG will be retained as 4, which is the seventh value, in the next startup of the terminal. When DBL or FSBL reads the value of the flag FOTA_FLAG as 4, the loading sequence of the firmware on the chip will be changed. Still taking OSBL update as an example, DBL or FSBL combined with the identification information on the differential package knows that the firmware that fails when writing the corresponding backup update firmware content in the second write location is OSBL, then the firmware loading sequence is changed from FSBL-OSBL -APPSBL is adjusted to FSBL-OSBL'APPSBL', OSBL' is the backup update firmware of OSBL.

As mentioned above, when the backup firmware is successfully formed and the backup update firmware is successfully formed, Fota will set the value of the flag FOTA_FLAG to identify the current link of the update process, so as to quickly locate the link where the fault occurs when the terminal restarts. The structure diagram is shown in Figure 6, the backup firmware update module and the backup update firmware write module are respectively connected with the predetermined flag bit reading module and the predetermined flag bit setting module, so as to quickly deliver status information.

Further, the chip further includes seventh firmware; the predetermined flag bit reading module is further configured to, when the predetermined flag bit is set to an eighth value, learn that the seventh firmware needs to be updated;

The fourth firmware further includes:

A writing location determination module, configured to determine the writing location of the update data required for updating the seventh firmware in the seventh firmware after the predetermined flag bit reading module learns that the seventh firmware needs to be updated; and

The update writing module is used for the write position determining module to write the update data required for the seventh firmware update after determining the write position of the update data required for the seventh firmware update in the seventh firmware Enter the write location in the seventh firmware to realize the update of the seventh firmware;

The predetermined flag bit setting module is further configured to set the predetermined flag bit to a fifth value after the seventh firmware update is successful;

The seventh firmware includes: an operating system kernel.

The seventh firmware includes LINUX, and may also include OSBL and APPSBL which are not in the same core as the fourth firmware Fota and LINUX. In the embodiment of above-mentioned chip, Fota can realize the update to LINUX, ADSP and AMSS on the function that realizes above-mentioned OSBL, APPSBL and Fota self renewal simultaneously, the module that it comprises and the function of execution, and the present invention provides The modules and functions in the foregoing chip embodiments are similar, and will not be repeated here. In the same way, Fota implements the update of the operating system ANDROID through LINUX as mentioned above.

The present invention also provides a communication terminal, including first firmware and second firmware, and the communication terminal further includes:

An update status learning module, configured to learn that the second firmware needs to be updated;

a download module, configured to download update data required for the second firmware update; and

The flag bit setting module is used for setting the predetermined flag bit to a second value after the update state obtaining module learns that the second firmware needs to be updated;

The first firmware is used to determine the write position of the update data in the second firmware after learning that the predetermined flag bit is the second value when the communication terminal starts up again, and store the updated data in the second firmware. The update data required for the second firmware update is written into the write location to realize the update of the second firmware; and when the second firmware update is successful, the predetermined flag is set to a first value;

Wherein, the first firmware is a firmware update module, and the second firmware includes: an operating system kernel.

The above-mentioned first firmware and the operating system kernel correspond to the first firmware (Fota) and the operating system kernel (LINUX) in the above-mentioned method embodiment respectively, and are included in the chip provided above. When the update status learning module learns that LINUX needs to be updated, the download module downloads and saves the update data required by the LINUX update; the flag bit setting module, after the update status learning module knows that LINUX needs to be updated, the predetermined flag bit FOTA_FLAG is set to the second value (such as 2); when the communication terminal started again, the first firmware Fota determined the write position of the update data needed for LINUX update in LINUX after learning that the flag bit FOTA_FLAG was 2, and wrote the update data needed for LINUX update Enter the write location to realize the update of LINUX; after the LINUX update is successful, Fota sets the flag bit FOTA_FLAG to the first value (such as 1).

The various optimized embodiments mentioned in the above method, such as using the form of differential packets, do differential writing to the updated firmware, such as the second firmware also includes ADSP and/or AMSS (both in different cores from Fota above), Fota can use the same method as above to realize the cross-core update of the two, and another example is to set the third value of the flag bit FOTA_FLAG (such as 3) to indicate that the operating system ANDROID corresponding to LINUX needs to be updated. If any firmware fails during the update process, Fota can read the value of the flag bit FOTA_FLAG to understand the current status of the update, so as to quickly locate the corresponding firmware and the corresponding status before the failure, and realize the update of the firmware. I won't repeat them here.

The embodiment of the present invention also provides another communication terminal, including the fourth firmware and the fifth firmware, and the communication terminal further includes:

An update status learning module, configured to learn that the fifth firmware needs to be updated;

A download module, configured to download update data needed for the fifth firmware update; and

The flag bit setting module is used for setting the predetermined flag bit to a fourth value after the update state obtaining module learns that the fifth firmware needs to be updated;

The fourth firmware is used to, when the communication terminal starts up again, form the backup firmware of the fifth firmware after learning that the predetermined flag bit is the fourth value, and determine the update required for the fifth firmware update Data is in the first write location in the backup firmware of the fifth firmware, and the update data required for updating the fifth firmware is written into the first write location to form the backup update firmware of the fifth firmware Then determine the second write position in the fifth firmware, write the data in the backup update firmware to the second write position, and realize the update of the fifth firmware; when the fifth After the firmware update is successful, the predetermined flag is set to the fifth value;

Wherein, the fourth firmware is a firmware update module, the fifth firmware is the fourth firmware, and/or firmware that needs to be loaded before the fourth firmware can be loaded during the startup process of the communication terminal.

The above-mentioned fourth firmware and the operating system kernel correspond to the fourth firmware (Fota) and the fifth firmware (which may include OSBL, APPSBL and Fota) in the above-mentioned method embodiment respectively, and are included in the chip provided above. When the update status acquisition module learns that the fifth firmware such as OSBL needs to be updated, the update data required by the OSBL update is downloaded and saved by the download module; after the update status acquisition module learns that the OSBL needs to be updated, the predetermined flag bit FOTA_FLAG is set to The fourth value (such as 2); when the communication terminal starts again, the fourth firmware Fota forms the backup firmware of OSBL after learning that the flag FOTA_FLAG is 2, and then determines that the update data needed for OSBL update is in the backup firmware of OSBL. One write position, and write the update data needed by OSBL update into described first write position, form the backup update firmware of OSBL; Then, Fota determines the second write position in OSBL, the backup update firmware of OSBL The data is written into the second writing position to realize the update of OSBL; when the OSBL is updated successfully, Fota sets the flag bit FOTA_FLAG to the fifth value (such as the initial value 1, indicating that there is no firmware to be updated at present).

The various optimized embodiments mentioned in the above methods, for example, use the form of differential packets to perform differential writing to the updated firmware, such as asking whether to restart immediately for updating when it is known that there is firmware that needs to be updated. For another example, when obtaining the backup firmware that needs to be updated, the value of the flag FOTA_FLAG is set to identify this state, such as after the backup firmware is successfully updated to form a backup update firmware, the value of the flag FOTA_FLAG is set to identify this state, and then When the backup update firmware is successfully written into the corresponding original firmware to be updated, set the value of the flag bit FOTA_FLAG back to the initial state to indicate that the update has been successful, and record by setting the value of the flag bit FOTA_FLAG in each link during the update process , so that when the update process fails and the terminal restarts, Fota can read the value of the flag bit FOTA_FLAG to understand the current status of the update, so as to quickly locate the corresponding firmware and the corresponding state before the failure, and realize the update of the firmware , and will not be repeated here.

It should also be noted that, in a single-core chip (such as a single-core chip shipped by Samsung), or in a multi-core (such as an existing quad-core chip), the Fota disclosed by the present invention can be used to realize the existing What cannot be realized in the technology is to update the firmware other than the ANDROID directly through the communication terminal itself, which will not be repeated here.

The above is only a preferred embodiment of the present invention, it should be pointed out that, for those of ordinary skill in the art, without departing from the principle of the present invention, some improvements and modifications can also be made, and these improvements and modifications can also be made. It should be regarded as the protection scope of the present invention.

Claims (28)

1. the method that a firmware updates, it is adaptable to communication terminal, it is characterised in that described method includes:

Described communication terminal knows that the second firmware needs to update；

Described communication terminal is downloaded described second firmware and is updated the more new data needed；

Predetermined flag position is set to the second value by described communication terminal；

When described communication terminal is again started up, first firmware knows that described predetermined flag position is after the second value, more new data writing position in described second firmware described in determining, and described second firmware is updated the more new data write said write position needed, realize the renewal of described second firmware, wherein, described first firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described second firmware includes operating system nucleus, the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that described file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal；

After described second firmware is updated successfully, described predetermined flag position is set to the first value by described first firmware.

2. the method that firmware as claimed in claim 1 updates, it is characterized in that, described communication terminal download described second firmware update need more new data packets draw together: described communication terminal to described second firmware update need more new data be verified, and by pass through checking described in more new data be stored in precalculated position；

The described more new data write said write position needed that updated by described second firmware includes: obtains described second firmware from described precalculated position and updates the more new data of needs, and described second firmware updates the more new data write said write position needed.

3. the method that firmware as claimed in claim 1 updates, it is characterised in that the more new data packets that described communication terminal is downloaded described second firmware renewal and needed is drawn together: described communication terminal is downloaded described second firmware and updated the difference bag needed；

Described second firmware is updated the more new data write said write position needed and includes by described first firmware: described first firmware uses pre-defined algorithm that described difference bag is write said write position.

4. the method that firmware as claimed in claim 1 updates, it is characterised in that when described communication terminal is again started up, the first firmware knows that described predetermined flag position is that the second value includes:

When described communication terminal is again started up, the 3rd firmware after knowing that predetermined flag position is set to the second value, loading described first firmware, described predetermined flag position is the second value to make described first firmware know；

Wherein, described 3rd firmware is, in described communication terminal start-up course, is loaded directly into the firmware of described first firmware.

5. the method that the firmware as according to any one of Claims 1 to 4 updates, it is characterized in that, described communication terminal includes processor, and described processor includes the first core and the second core, described first firmware is positioned at described second core, and described operating system nucleus is positioned at described second core；

Described second firmware farther includes: be positioned at the firmware that need not load in advance before the first firmware loads of described first core.

6. the method that firmware as claimed in claim 5 updates, it is characterised in that described second value, for indicating the state of any one firmware in described second firmware to update for needs.

7. the method that firmware as claimed in claim 1 updates, it is characterised in that after described second firmware is updated successfully, described predetermined flag position is set to the first value and specifically includes by described first firmware:

After described second firmware is updated successfully, described predetermined flag position is set to the 3rd value；

Described operating system nucleus judges that operating system that operating system nucleus is corresponding is the need of renewal；

If needing to update, described operating system is updated by described operating system nucleus, after being updated successfully, notifies described first firmware；

Described predetermined flag position is set to the first value by described first firmware.

8. the method that firmware as claimed in claim 7 updates, it is characterised in that described described predetermined flag position is set to the 3rd value after, before described predetermined flag position is set to the first value by described first firmware, described method farther includes:

If described communication terminal is again started up, described second firmware knows that described predetermined flag position is the 3rd value, returns the described step that described operating system is updated.

9. the method that a firmware updates, it is adaptable to communication terminal, it is characterised in that described method includes:

Described communication terminal knows that the 5th firmware needs to update；

Described communication terminal is downloaded described 5th firmware and is updated the more new data needed；

Predetermined flag position is set to the 4th value by described communication terminal；

When described communication terminal is again started up, 4th firmware knows that described predetermined flag position is after the 4th value, form the backup firmware of described 5th firmware, determine that described 5th firmware updates the more new data needed the first writing position in the backup firmware of described 5th firmware, and described 5th firmware is updated more new data described first writing position of write needed, form the backup updating firmware of described 5th firmware；Wherein, described 4th firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described 5th firmware is described 4th firmware, and/or in described communication terminal start-up course, need leading loading just can make the firmware of the 4th firmware loads, the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal；

The second writing position in described 5th firmware determined by described 4th firmware, by the data in the backup updating firmware of described 5th firmware, writes described second writing position, it is achieved the renewal of described 5th firmware；

After described 5th firmware is updated successfully, described predetermined flag position is set to the 5th value by described 4th firmware.

10. the method that firmware as claimed in claim 9 updates, it is characterized in that, the more new data that described communication terminal is downloaded described 5th firmware renewal and needed is specially, described 5th firmware is updated the more new data needed and is verified by described communication terminal, and the more new data that described 5th firmware by verifying updates needs is stored in precalculated position；

More new data described first writing position of write that being updated by described 5th firmware needs includes: obtains described 5th firmware from described precalculated position and updates the more new data of needs, and the more new data that described 5th firmware renewal needs is write described first writing position.

11. the method that firmware as claimed in claim 9 updates, it is characterised in that it is that described 5th firmware updates the difference bag needed that described 5th firmware updates the more new data needed；

Described 5th firmware is updated more new data described first writing position of write needed and includes by described 4th firmware: described 4th firmware uses pre-defined algorithm that the difference bag that described 5th firmware updates needs is write described first writing position.

12. the method that firmware as claimed in claim 9 updates, it is characterised in that after described 4th firmware forms the backup firmware of described 5th firmware, described method farther includes: described predetermined flag position is set to the 6th value by described 4th firmware；

Before described 5th firmware is updated successfully, described method farther includes:

If described communication terminal is again started up, described 4th firmware knows that described predetermined flag position is the 6th value, returns the described step determining that described 5th firmware updates the more new data needed the first writing position in the backup firmware of described 5th firmware.

13. the method that firmware as claimed in claim 9 updates, it is characterised in that after described 4th firmware forms the backup updating firmware of described 5th firmware, described method farther includes: described predetermined flag position is set to the 7th value by described 4th firmware；

Before described 5th firmware is updated successfully, described method farther includes:

If described communication terminal is again started up, described 4th firmware knows that described predetermined flag position is the 7th value, then return the step of described the second writing position determined in described 5th firmware.

14. the method that firmware as claimed in claim 13 updates, it is characterised in that when described communication terminal is again started up, know that described predetermined flag position farther includes before being the 7th value at described 4th firmware:

6th firmware knows that described predetermined flag position is after the 7th value, the loading of described 5th firmware will replace with the loading of the backup updating firmware to described 5th firmware.

15. the method that firmware as claimed in claim 9 updates, it is characterised in that described method farther includes:

Described communication terminal knows that the 7th firmware needs to update；

Described communication terminal is downloaded described 7th firmware and is updated the more new data needed；

Predetermined flag position is set to the 8th value by described communication terminal；

When described communication terminal is again started up, 4th firmware knows that described predetermined flag position is after the 8th value, determine that described 7th firmware updates the more new data needed writing position in described 7th firmware, and described 7th firmware is updated the more new data write said write position needed, it is achieved the renewal of described 7th firmware；

After described 7th firmware is updated successfully, described predetermined flag position is set to the 5th value by described 4th firmware；

Wherein, described 7th firmware includes: operating system nucleus.

16. the method that firmware as claimed in claim 15 updates, it is characterized in that, described communication terminal includes processor, described processor includes the 3rd core and the 4th core, described 4th firmware is positioned at described 4th core, described operating system nucleus is positioned at described 4th core, and described 7th firmware farther includes: be positioned at the firmware that need not load in advance before the 4th firmware loads of described 3rd core.

17. the method that firmware as claimed in claim 15 updates, it is characterised in that after described 7th firmware is updated successfully, described predetermined flag position is set to the 5th value and specifically includes by described 4th firmware:

After described 7th firmware is updated successfully, described predetermined flag position is set to the 9th value；

Described operating system nucleus judges that operating system that operating system nucleus is corresponding is the need of renewal；

If needing to update, described operating system is updated by described operating system nucleus, after being updated successfully, notifies described 4th firmware；

Described predetermined flag position is set to the 5th value by described 4th firmware.

18. the method that firmware as claimed in claim 17 updates, it is characterized in that, described described predetermined flag position is set to the 9th value after, before described predetermined flag position is set to the 5th value by described 4th firmware, described method farther includes: if described communication terminal is again started up, described operating system nucleus knows that described predetermined flag position is the 9th value, returns the described step that described operating system is updated.

19. a chip, it is applied in communication terminal, it is characterised in that described chip comprises the first firmware and the second firmware, and described first firmware comprises:

Predetermined flag position read module, after knowing that the predetermined flag position on communication terminal is the second value, knows that the second firmware needs to update；

Writing position determines module, after knowing that described second firmware needs renewal for described predetermined flag position read module, it is determined that described second firmware updates the more new data needed writing position in described second firmware；

Update writing module, after determining that described second firmware updates the more new data needed writing position in described second firmware for said write position determination module, described second firmware is updated the more new data needed and writes the writing position in described second firmware；Wherein, described first firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described second firmware includes operating system nucleus, and the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal；

Predetermined flag position arranges module, for, after described second firmware is updated successfully, described predetermined flag position being set to the first value.

20. chip according to claim 19, it is characterised in that described chip includes the first core and the second core, and described first firmware and described operating system nucleus are positioned at described second core；

Described second firmware farther includes: be positioned at the firmware that need not load in advance before the first firmware loads of described first core.

21. the chip according to claim 19 or 20, it is characterised in that described predetermined flag position arranges module and is further used for, after described second firmware is updated successfully, described predetermined flag position is set to the 3rd value, and notifies described operating system nucleus；And receive described operating system nucleus be updated successfully notice after, described predetermined flag position is set to the first value；

Described operating system nucleus is further used for, it is judged that described operating system, the need of renewal, if needing to update, is then updated by the operating system of self correspondence, and is updated successfully notice to described in described first firmware transmission after being updated successfully.

22. a chip, it is applied in communication terminal, it is characterised in that described chip comprises the 4th firmware and the 5th firmware, and described 4th firmware comprises:

Predetermined flag position read module, after knowing that the predetermined flag position on communication terminal is the 4th value, knows that the 5th firmware needs to update；

Firmware backup module, is used for knowing that described predetermined flag position is after the 4th value, forms the backup firmware of described 5th firmware；

First writing position determines module, after forming the backup firmware of described 5th firmware, it is determined that described 5th firmware updates the more new data needed the first writing position in the backup firmware of described 5th firmware；

Backup firmware is new module more, writes described first writing position for described 5th firmware is updated the more new data needed, forms the backup updating firmware of described 5th firmware；

Second writing position determines module, form the backup updating firmware of described 5th firmware for backup firmware more new module after, it is determined that the second writing position in described 5th firmware；

Backup updating firmware writing module, after determining for described second writing position, by the data in the backup updating firmware of described 5th firmware, writes described second writing position, it is achieved the renewal of described 5th firmware；Wherein, described 4th firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described 5th firmware is described 4th firmware, and/or in described communication terminal start-up course, need leading loading just can make the firmware of the 4th firmware loads, the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal；

Predetermined flag position arranges module, for, after described 5th firmware is updated successfully, described predetermined flag position being set to the 5th value.

23. chip according to claim 22, it is characterised in that described predetermined flag position arranges module and is further used for, after described firmware backup module forms the backup firmware of described 5th firmware, described predetermined flag position is set to the 6th value；

Described predetermined flag position read module is further used for, and when described communication terminal is again started up, after the predetermined flag position known on communication terminal is the 6th value, notifies that described backup firmware more new module forms the backup updating firmware of described 5th firmware.

24. chip according to claim 22, it is characterised in that described predetermined flag position arranges module and is further used for, after described backup firmware more new module forms the backup updating firmware of described 5th firmware, described predetermined flag position is set to the 7th value；

Described predetermined flag position read module is further used for, and when described communication terminal is again started up, after the predetermined flag position known on communication terminal is the 7th value, notifies that described backup updating firmware writing module realizes the renewal of described 5th firmware.

25. chip according to claim 24, it is characterized in that, described chip comprises the 6th firmware further, for when described communication terminal is again started up, after knowing that described predetermined flag position is the 7th value, the loading of described 5th firmware will be replaced with the loading of the backup updating firmware to described 5th firmware.

26. chip according to claim 22, it is characterised in that described chip comprises the 7th firmware further；Described predetermined flag position read module is further used for, and when described predetermined flag position is set to eight values, knows that described 7th firmware needs to update；

Described 4th firmware comprises further:

Writing position determines module, after knowing that described 7th firmware needs renewal for described predetermined flag position read module, it is determined that described 7th firmware updates the more new data needed writing position in described 7th firmware；And

Update writing module, after determining that described 7th firmware updates the more new data needed writing position in described 7th firmware for said write position determination module, described 7th firmware is updated the more new data needed and writes the writing position in described 7th firmware, it is achieved the renewal of described 7th firmware；

Described predetermined flag position arranges module and is further used for, and after described 7th firmware is updated successfully, described predetermined flag position is set to the 5th value；

Described 7th firmware includes: operating system nucleus.

27. a communication terminal, it is characterised in that comprising the first firmware and the second firmware, described communication terminal comprises further:

More new state knows module, is used for knowing that described second firmware needs to update；

Download module, updates, for downloading described second firmware, the more new data needed；And

Flag bit arranges module, after knowing that module knows that described second firmware needs renewal for described more new state, predetermined flag position is set to the second value；

Described first firmware is used for, when described communication terminal is again started up, after knowing that described predetermined flag position is the second value, more new data writing position in described second firmware described in determining, and described second firmware is updated the more new data write said write position needed, it is achieved the renewal of described second firmware；And after described second firmware is updated successfully, described predetermined flag position is set to the first value；Wherein, described first firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described second firmware includes operating system nucleus, and the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal.

28. a communication terminal, it is characterised in that comprising the 4th firmware and the 5th firmware, described communication terminal comprises further:

More new state knows module, is used for knowing that described 5th firmware needs to update；

Download module, updates, for downloading described 5th firmware, the more new data needed；And

Flag bit arranges module, after knowing that module knows that described 5th firmware needs renewal for described more new state, predetermined flag position is set to the 4th value；

Described 4th firmware is used for, when described communication terminal is again started up, after knowing that described predetermined flag position is the 4th value, form the backup firmware of described 5th firmware, determine that described 5th firmware updates the more new data needed the first writing position in the backup firmware of described 5th firmware, and described 5th firmware is updated more new data described first writing position of write needed, form the backup updating firmware of described 5th firmware；It is then determined that the second writing position in described 5th firmware, by the data in described backup updating firmware, write described second writing position, it is achieved the renewal of described 5th firmware；After described 5th firmware is updated successfully, described predetermined flag position is set to the 5th value；Wherein, described 4th firmware is firmware more new module, it is positioned on the LINUX of ARM11 end, for firmware is updated, when communication terminal starts by the loading of APPSBL, described 5th firmware is described 4th firmware, and/or in described communication terminal start-up course, need leading loading just can make the firmware of the 4th firmware loads, the file system elements that firmware more new module is operated by system firmware detects that server end has firmware to need to update, the more new data that file system elements then down loading updating needs, and be deposited in the presumptive area of communication terminal.