CN114995893B - Firmware management method, flash memory, host and storage medium - Google Patents

Abstract

The present disclosure relates to a firmware management method, a flash memory, a host, and a storage medium, the method including: acquiring an operation instruction for the firmware to be operated; determining partition information corresponding to the firmware to be operated according to the operation instruction; and executing the operation content in the operation instruction on the firmware to be operated according to the firmware information corresponding to the firmware to be operated. According to the embodiment of the disclosure, the firmware information of the firmware to be operated can be determined by the flash memory based on the partition information by acquiring the partition information corresponding to the firmware in the flash memory, so that the flash memory can be compatible with the firmware in different development environments. In addition, under the condition that the adapter comprising the flash memory is connected to the host, the host can also access the firmware to be operated through the partition information, and therefore the host can be compatible with the firmware under different development environments.

Description

Firmware management method, flash memory, host and storage medium

technical field

The present disclosure relates to the technical field of computers, and in particular to a firmware management method, a flash memory, a host and a storage medium.

Background technique

Hardware devices usually manage their corresponding firmware through flash memory. For example, firmware developed based on UEFI environment can access firmware information through the OPROM (Option Read-Only Memory) area stored on the flash memory. With the continuous development of hardware devices, hardware devices usually need to load multiple firmwares, so how to better manage firmware is a technical problem urgently needed to be solved by those skilled in the art.

Contents of the invention

The present disclosure proposes a firmware management technical solution.

According to one aspect of the present disclosure, a firmware management method is provided, which is applied to flash memory, and the management method includes: acquiring an operation instruction for the firmware to be operated; and determining a partition corresponding to the firmware to be operated according to the operation instruction information; wherein, the partition information includes: the firmware to be operated and the firmware information corresponding to the firmware to be operated; according to the firmware information corresponding to the firmware to be operated, execute the operation instruction on the firmware to be operated Action content.

In a possible implementation manner, the management method further includes: responding to the packaged configuration file sent by the host, parsing the packaged configuration file to obtain partition information corresponding to each firmware; saving the Describe the partition information corresponding to each firmware.

In a possible implementation manner, the parsing the packaged configuration file to obtain the partition information corresponding to each firmware includes: parsing the packaged configuration file to obtain the partition information corresponding to each firmware Partition information, corresponding partition flash memory address; wherein, the partition flash memory address is used to determine the storage location of the partition information in the flash memory; the storage of the partition information corresponding to each firmware includes: storing each The partition information corresponding to the firmware is stored in the partition flash memory address of the flash memory.

According to one aspect of the present disclosure, a firmware management method is provided, which is applied to a host connected to a flash memory, and the management method includes: generating or updating a configuration file according to initial firmware information corresponding to each firmware; wherein , the initial firmware information is used to represent the firmware information of each firmware in the initial development environment; the configuration file is packaged, and the packaged configuration file is sent to the flash memory.

In a possible implementation manner, the generating or updating the configuration file according to the initial firmware information corresponding to each firmware includes: signing each firmware, and generating a signature file corresponding to each firmware; according to the The initial firmware information corresponding to each firmware, the signature file corresponding to each firmware, and the configuration file is generated or updated.

In a possible implementation manner, the generating or updating the configuration file according to the initial firmware information corresponding to each firmware includes: determining the partition flash memory address corresponding to each firmware; the partition flash memory address is used to determine the The location where each firmware is loaded in the flash memory; according to the initial firmware information corresponding to each firmware and the partition flash memory address corresponding to each firmware, a configuration file is generated or updated.

In a possible implementation manner, the management method further includes: generating an operation instruction for the firmware to be operated according to the configuration file; wherein the operation instruction is used to update the partition of the firmware to be operated in the flash memory information; sending the operation instruction to the flash memory; generating prompt information corresponding to the firmware update information in response to the firmware update information sent by the flash memory.

According to an aspect of the present disclosure, there is provided a flash memory, the flash memory includes: an operation instruction acquisition module, used to acquire an operation instruction for the firmware to be operated; a partition information determination module, used to determine the Partition information corresponding to the firmware to be operated; wherein, the partition information includes: the firmware to be operated and firmware information corresponding to the firmware to be operated; the operation instruction execution module is used to, according to the firmware information corresponding to the firmware to be operated, Execute the operation content in the operation instruction on the firmware to be operated.

According to an aspect of the present disclosure, a host is provided, the host is connected to the flash memory, and the host further includes: a configuration file update module, configured to generate or update a configuration file according to initial firmware information corresponding to each firmware ; Wherein, the initial firmware information is used to represent the firmware information of each firmware in the initial development environment; the configuration file sending module is used to package the configuration file, and send the packaged configuration file to the described flash memory.

According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored, and the above-mentioned management method is implemented when the computer program instructions are executed by a processor.

In the embodiment of the present disclosure, the operation instruction for the firmware to be operated can be obtained, and then according to the operation instruction, the partition information corresponding to the firmware to be operated is determined, and finally the firmware information corresponding to the firmware to be operated is determined for the The firmware to be operated executes the operation content in the operation instruction. In the embodiments of the present disclosure, by obtaining the partition information corresponding to the firmware in the flash memory, the flash memory can determine the firmware information of the firmware to be operated based on the partition information, thereby realizing that the flash memory is compatible with firmware in different development environments. In addition, when the adapter including the above-mentioned flash memory is connected to the host, the host can also access the firmware to be operated through the above-mentioned partition information, thereby realizing that the host is compatible with firmware in different development environments.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments with reference to the accompanying drawings.

Description of drawings

The accompanying drawings here are incorporated into the description and constitute a part of the present description. These drawings show embodiments consistent with the present disclosure, and are used together with the description to explain the technical solution of the present disclosure.

Fig. 1 shows a flowchart of a firmware management method provided according to an embodiment of the present disclosure.

Fig. 2 shows a flowchart of a firmware management method provided according to an embodiment of the present disclosure.

FIG. 3 shows a block diagram of a flash memory provided according to an embodiment of the present disclosure.

Fig. 4 shows a block diagram of a host provided according to an embodiment of the present disclosure.

Fig. 5 shows a block diagram of an electronic device 800 provided according to an embodiment of the present disclosure.

Detailed ways

Various exemplary embodiments, features, and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. The same reference numbers in the figures indicate functionally identical or similar elements. While various aspects of the embodiments are shown in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as superior or better than other embodiments.

The term "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations. In addition, the term "at least one" herein means any one of a variety or any combination of at least two of the more, for example, including at least one of A, B, and C, which may mean including from A, Any one or more elements selected from the set formed by B and C.

In addition, in order to better illustrate the present disclosure, numerous specific details are given in the following specific implementation manners. It will be understood by those skilled in the art that the present disclosure may be practiced without some of the specific details. In some instances, methods, means, components and circuits that are well known to those skilled in the art have not been described in detail so as to obscure the gist of the present disclosure.

In related technologies, most firmware is usually OPROM (Option Read-Only Memory, optional read-only memory) based on UEFI (Unified Extensible Firmware Interface, Unified Extensible Firmware Interface) environment, which is based on EDKII (a UEFI development software package), the SBIOS (System Basic Input Output System, system-level basic input and output system) in the motherboard can perform PCIE (Peripheral Component Interconnect Express , a high-speed serial computer expansion bus standard). However, for firmware in different application fields and different development environments, the motherboard is usually not compatible with it, for example: firmware developed based on Boot Loader (boot loader), RTOS (Real-Time Operating System, real-time operating system) The compatibility is poor.

In view of this, the embodiment of the present disclosure provides a firmware management method, which can obtain the operation instructions for the firmware to be operated, and then determine the partition information corresponding to the firmware to be operated according to the operation instructions, and finally according to the operation instructions Operate the firmware information corresponding to the firmware, and execute the operation content in the operation instruction on the firmware to be operated. In the embodiments of the present disclosure, by obtaining the partition information corresponding to the firmware in the flash memory, the flash memory can determine the firmware information of the firmware to be operated based on the partition information, thereby realizing that the flash memory is compatible with firmware in different development environments. In addition, when the adapter including the above-mentioned flash memory is connected to the host, the host can also access the firmware to be operated through the above-mentioned partition information, thereby realizing that the host is compatible with firmware in different development environments.

Referring to FIG. 1, FIG. 1 shows a flowchart of a firmware management method provided by an embodiment of the present disclosure. As shown in FIG. 1, the above-mentioned management method can be applied to flash memory. Technology Device, memory technology device, also known as storage technology device, hereinafter referred to as MTD), non-volatile flash memory (for example: Nandflash, Nor flash), etc. Embodiments of the present disclosure are not limited here. The management methods mentioned above include:

Step S100, acquiring an operation instruction for the firmware to be operated. Exemplarily, the operation instruction can be any instruction that can operate on the firmware. For specific instruction content, please refer to the operation content that can be executed by firmware in related technologies, such as: upgrade, downgrade, detect, disable and other operations for firmware , the embodiments of the present disclosure will not be described in detail here. In one example, the above operation instruction may include a unique serial number of the firmware to be operated, so that the flash memory determines the firmware to be operated among all the firmware.

Step S200, according to the operation instruction, determine partition information corresponding to the firmware to be operated. Wherein, the partition information includes: the firmware to be operated and firmware information corresponding to the firmware to be operated. Exemplarily, partition information corresponding to each firmware can be stored in the flash memory, that is, each firmware can run in the above-mentioned flash memory, and the flash memory can determine the firmware information of each firmware based on the above-mentioned partition information, so as to realize different development environments Unified management of firmware. For the above firmware information, reference may be made to related technologies. For example, the above firmware information may include: a unique number, version information, signature file, etc., which are not limited in this embodiment of the present disclosure.

Step S300, according to the firmware information corresponding to the firmware to be operated, execute the operation content in the operation instruction on the firmware to be operated. Exemplarily, the above-mentioned firmware information is used to provide parameter support for the above-mentioned operation content. For example, if the operation content is error correction and recovery of firmware, the flash memory can downgrade the version of the firmware to be operated to the rolled-back version in the firmware information. Another example: if the operation content is firmware upgrade, the flash memory can determine the patch package of the firmware to be operated according to the current version information and the pre-upgrade version information in the firmware information.

In a possible implementation manner, the above management method further includes: responding to the packaged configuration file sent by the host, parsing the packaged configuration file to obtain the partition information corresponding to each firmware; and then saving the Describe the partition information corresponding to each firmware. Exemplarily, the above-mentioned configuration file can be any file format, which can be read by the flash memory after being processed by the corresponding packaging tool in the related art and can load the recorded firmware information into the flash memory, for example: the above-mentioned configuration The file can be a JSON file. The above-mentioned JSON file can be packaged by the corresponding packaging tool in related technologies, and the firmware information recorded by the packaging tool will be configured into the flash memory. The file format of the configuration file can be set flexibly, which is not limited in this embodiment of the present disclosure. Exemplarily, the flash memory can load the firmware information in the configuration file into the space reserved for it in the flash memory, and run the firmware in this space, so that the flash memory can determine the firmware information, running conditions, etc. of each firmware, Furthermore, after the subsequent flash memory receives an operation instruction for the firmware to be operated, corresponding operations can be performed on the firmware to be operated. Combined with the actual application scenario, developers can modify the configuration file, and after the modified configuration file is packaged by the packaging tool in the related technology, it is sent to the flash memory, and the flash memory can save it to form the flash memory firmware in the development stage configuration. For example, the above-mentioned flash memory can be configured in the adapter, that is, the flash memory is used to store firmware information corresponding to each hardware in the adapter. Exemplarily, the above-mentioned configuration file can be visible to the user side, and the user side can modify the firmware information in the configuration file according to the actual running conditions of the host computer, so as to improve the freedom of firmware setting. After the modification of the configuration file is submitted on the user side, the flash memory can update the corresponding partition information in the flash memory according to the modified configuration file, thereby realizing the update of the firmware information on the user side. For the user side, the embodiment of the present disclosure provides a configuration file for the user to check the firmware information (for example, it can be displayed through a visual interface), and the user side itself does not need to care about the arrangement, generation and loading of the firmware, which is easy for the user side. Firmware management. For the development side, the embodiments of the present disclosure support the development side to configure firmware and firmware information into the configuration file, so that the flash memory can centrally manage multiple firmwares, and the firmware management on the development side is also facilitated.

In a possible implementation manner, the parsing the packaged configuration file to obtain the partition information corresponding to each firmware includes: parsing the packaged configuration file to obtain the partition information corresponding to each firmware Partition information, corresponding partition flash memory address; wherein, the partition flash memory address is used to determine the storage location of the partition information in the flash memory. In this case, the saving the partition information corresponding to each firmware includes: saving the partition information corresponding to each firmware to the partition flash memory address of the flash memory. Exemplarily, the address of the above-mentioned partition flash memory can be automatically allocated according to the size of the firmware information corresponding to each firmware, or a fixed flash memory size can be set for storage of partition information, or it can be set manually. The embodiment of the present disclosure No limitation is imposed here. In one example, the manufacturer can manually set the partition flash memory address corresponding to each firmware in the configuration file. For example, through the field corresponding to the partition flash memory address in the configuration file, a different location can be set for the partition information of each firmware. So that the partition information corresponding to different firmware can be queried in the flash memory. The above process of configuring the address of the partitioned flash memory can be executed in the host, which will be described in detail later.

The management method provided by the embodiments of the present disclosure can be applied to flash memory. By using partition information, flash memory can manage firmware in various development environments, which improves the compatibility of flash memory with firmware and is beneficial to development in various development environments. Firmware development.

Referring to FIG. 2, FIG. 2 shows a flowchart of a firmware management method provided by an embodiment of the present disclosure. As shown in FIG. 2, the above-mentioned management method can be applied to a host, for example, the above-mentioned host can be any A motherboard to which the above-mentioned flash memory can be connected or an electronic device equipped with the motherboard. The above-mentioned flash memory can be built into an external device relative to the host (for example: any kind of adapter) to manage firmware information corresponding to the hardware in the external device. The above-mentioned flash memory may also be directly connected to the host to manage firmware information corresponding to the hardware in the host, which is not limited in this embodiment of the present disclosure. For example: flash memory can be built into adapters such as graphics cards and network cards. In this case, the above-mentioned host may include an external device interface, that is, the flash memory may interact with the host through the interface of the adapter. As shown in Figure 2, the above management methods include:

Step S500, generating or updating a configuration file according to initial firmware information corresponding to each firmware. Wherein, the initial firmware information is used to represent the firmware information of each firmware in the initial development environment. The aforementioned initial development environment may be any firmware development environment, such as UEFI, Boot Loader, RTOS, etc. mentioned above. Exemplarily, the above-mentioned configuration file may also preset a fixed format, and the fixed format may include a fixed configuration field type (or a field representing a type of firmware information), if the host detects that the configuration field in the initial firmware information is consistent with If the configuration fields in the configuration file are the same, the value of the configuration field in the initial firmware information can also be automatically and directly assigned to the configuration field in the configuration file, so as to update the value of the configuration field in the configuration file. In an example, the developer may also manually create the configuration file, that is, the developer may manually fill in the configuration file with the values of each configuration field in the initial firmware information. Embodiments of the present disclosure are not limited here. Exemplarily, the above configuration files may include the size of firmware generated in respective development environments, the location of firmware information in the flash memory, firmware information of each firmware, etc., which are not limited in this embodiment of the present disclosure.

In a possible implementation manner, the above initial firmware information may correspond to a signature file. The above-mentioned signature file can be used to determine whether the firmware has been maliciously tampered with after the flash memory, the adapter configured with the flash memory, and the host connected to the flash memory leave the factory, so as to increase the security of the firmware.

On this basis, step S500 may include: signing each firmware, and generating a signature file corresponding to each firmware. Then generate or update the configuration file according to the initial firmware information corresponding to each firmware and the signature file corresponding to each firmware. In related technologies, manufacturers are limited by the low compatibility of the flash memory in the adapter and the flash memory in the host with the firmware development environment. Usually, manufacturers can only use a specific signature scheme, that is, the security management method for firmware is too single, which is not conducive to firmware development. It is also not conducive to the manufacturer's configuration. For example, the manufacturer can only encrypt the firmware based on PKCS (Public Key Cryptography Standards, public key encryption standard). In the embodiment of the present disclosure, since the signature file field can be saved in the configuration file, the firmware management method provided by the embodiment of the present disclosure can be compatible with using the same encryption standard for different firmware, and can also be compatible with different firmware Different encryption standards are used, which are not limited in the embodiments of the present disclosure. For example: Manufacturers can use private keys to sign firmware under different development environments to generate signature files, then save the signature files to the above configuration files, and send them to the flash memory after being packaged for subsequent motherboards or Host verification. In addition, the above-mentioned configuration files can also be set to be visible on the development side or the user side, so as to facilitate firmware management.

In a possible implementation manner, step S500 may include: determining a partition flash memory address corresponding to each firmware. The address of the partition flash memory is used to determine the location where each firmware is loaded in the flash memory. Then generate or update the configuration file according to the initial firmware information corresponding to each firmware and the partition flash memory address corresponding to each firmware. Exemplarily, the address of the above-mentioned partition flash memory can be automatically allocated according to the size of the firmware information corresponding to each firmware, or a fixed flash memory size can be set for storage of partition information, or it can be set manually. The embodiment of the present disclosure No limitation is imposed here. In one example, the manufacturer can manually set the partition flash address corresponding to each firmware in the configuration file. For example, through the corresponding fields, different locations can be set for the partition information of each firmware, so that different firmware corresponds to All partition information can be queried in the flash memory. Exemplarily, the above-mentioned configuration file can be visible to the user side and the development side, that is, the user side or the development side can adjust various firmware information of the firmware through the above-mentioned configuration file when using the host computer, for example: it can be set on the host computer An operation interface set based on the above-mentioned configuration file, so that various firmware information in the above-mentioned configuration file can be explicitly consulted by the user side or the development side, and the firmware information adjusted by the user side or the development side on the operation interface is also It will be updated to the above configuration file accordingly, and then the flash memory can load the firmware information in the configuration file to the flash memory, which realizes the centralized management of different firmware in the flash memory by the host.

Continue to refer to FIG. 2, step S600, package the configuration file, and send the packaged configuration file to the flash memory. Exemplarily, the host may package the configuration file through a packaging tool in the related art, which will not be described in detail in this embodiment of the present disclosure, as long as the packaging tool is compatible with the file format of the configuration file.

In a possible implementation manner, the management method further includes: generating an operation instruction for the firmware to be operated according to the configuration file. Wherein, the operation instruction is used to update the partition information of the firmware to be operated in the flash memory. Exemplarily, the above operation instructions can be any instruction that can operate on firmware. For specific instruction content, please refer to the operation content that firmware can perform in related technologies, such as: upgrade, downgrade, detect, disable and other operations for firmware , the embodiments of the present disclosure will not be described in detail here. In one example, the operation instruction may include a unique serial number of the firmware to be operated, so that after the operation instruction is sent to the flash memory, the flash memory may update the firmware to be operated among all the firmware. Exemplarily, the host can call corresponding operation interfaces of firmware in different development environments according to the above configuration files, so as to realize compatibility of the host with firmware in different development environments. Then send the operation instruction to the flash memory. Finally, in response to the firmware update information sent by the flash memory, prompt information corresponding to the firmware update information is generated. Exemplarily, the above firmware update information may include: update success information, update failure information, etc., so that the host can visually convert the firmware update result into prompt information for the user to review. Exemplarily, the above-mentioned prompt information may be a voice prompt or a text prompt, and it only needs to be able to show the update result of the firmware, which is not limited in this embodiment of the present disclosure. Combined with actual application scenarios, the above steps can be applied to the user-side use stage, that is, the user can manage the firmware in the flash memory through the visualized management interface in the host, and the above-mentioned management interface can determine the operation interface with the flash memory according to the configuration file, so that The operation instructions can be correctly executed in the flash memory, thereby realizing the convenient management of the firmware in the flash memory at the user side.

The management method provided by the embodiments of the present disclosure can be applied to the host computer. By using the configuration file, the firmware information of each firmware can be changed according to the actual operating environment through the user side and the development side, thereby improving the actual performance of different firmware. processing effect.

It can be understood that the above-mentioned method embodiments mentioned in this disclosure can all be combined with each other to form a combined embodiment without violating the principle and logic. Due to space limitations, this disclosure will not repeat them. Those skilled in the art can understand that, in the above method in the specific implementation manner, the specific execution order of each step should be determined according to its function and possible internal logic.

FIG. 3 shows a block diagram of a flash memory provided according to an embodiment of the present disclosure. As shown in FIG. 3 , the flash memory 100 includes: an operation instruction acquisition module 110 for obtaining an operation instruction for the firmware to be operated; a partition information determination module 120 , used to determine partition information corresponding to the firmware to be operated according to the operation instruction; wherein, the partition information includes: the firmware to be operated and firmware information corresponding to the firmware to be operated; the operation instruction execution module 130, It is used for executing the operation content in the operation instruction on the firmware to be operated according to the firmware information corresponding to the firmware to be operated.

In a possible implementation manner, the flash memory further includes: a partition information processing module, configured to perform any of the following: responding to the packaged configuration file sent by the host, parsing the packaged configuration file , obtain the partition information corresponding to each firmware; save the partition information corresponding to each firmware.

In a possible implementation manner, the parsing the packaged configuration file to obtain the partition information corresponding to each firmware includes: parsing the packaged configuration file to obtain the partition information corresponding to each firmware Partition information, corresponding partition flash memory address; wherein, the partition flash memory address is used to determine the storage location of the partition information in the flash memory; the storage of the partition information corresponding to each firmware includes: storing each The partition information corresponding to the firmware is stored in the partition flash memory address of the flash memory.

FIG. 4 shows a block diagram of a host provided according to an embodiment of the present disclosure. As shown in FIG. 4 , the host is connected to the flash memory, and the host 200 includes: a configuration file update module 210 configured to correspond to each firmware The initial firmware information, generate or update the configuration file; Wherein, the initial firmware information is used to represent the firmware information of each firmware in the initial development environment; The configuration file sending module 220 is used to package the configuration file processing, sending the packaged configuration file to the flash memory.

In a possible implementation manner, the generating or updating the configuration file according to the initial firmware information corresponding to each firmware includes: signing each firmware, and generating a signature file corresponding to each firmware; according to the The initial firmware information corresponding to each firmware, the signature file corresponding to each firmware, and the configuration file is generated or updated.

In a possible implementation manner, the generating or updating the configuration file according to the initial firmware information corresponding to each firmware includes: determining the partition flash memory address corresponding to each firmware; the partition flash memory address is used to determine the The location where each firmware is loaded in the flash memory; according to the initial firmware information corresponding to each firmware and the partition flash memory address corresponding to each firmware, a configuration file is generated or updated.

In a possible implementation manner, the host further includes: a prompt information generation module, configured to perform any of the following: generate an operation instruction for the firmware to be operated according to the configuration file; wherein, the operation instruction uses to update the partition information of the firmware to be operated in the flash memory; send the operation instruction to the flash memory; and generate prompt information corresponding to the firmware update information in response to the firmware update information sent by the flash memory.

In some embodiments, the functions or modules included in the device provided by the embodiments of the present disclosure can be used to execute the methods described in the method embodiments above, and its specific implementation can refer to the description of the method embodiments above. For brevity, here No longer.

Embodiments of the present disclosure also provide a computer-readable storage medium, on which computer program instructions are stored, and the above-mentioned method is implemented when the computer program instructions are executed by a processor. Computer readable storage media may be volatile or nonvolatile computer readable storage media.

An embodiment of the present disclosure also proposes an electronic device, including: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to invoke the instructions stored in the memory to execute the above method.

An embodiment of the present disclosure also provides a computer program product, including computer-readable codes, or a non-volatile computer-readable storage medium carrying computer-readable codes, when the computer-readable codes are stored in a processor of an electronic device When running in the electronic device, the processor in the electronic device executes the above method.

The electronic device may be provided as a terminal or other forms of devices. Exemplarily, the above-mentioned host may be an electronic device including a flash memory interface.

Fig. 5 shows a block diagram of an electronic device 800 provided according to an embodiment of the present disclosure. For example, the electronic device 800 may be user equipment (User Equipment, UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, vehicle-mounted device, Terminal devices such as wearable devices.

5, electronic device 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input/output interface 812, sensor component 814, and communication component 816.

The processing component 802 generally controls the overall operations of the electronic device 800, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above method. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802 .

The memory 804 is configured to store various types of data to support operations at the electronic device 800 . Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 can be realized by any type of volatile or non-volatile storage device or their combination, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic Disk or Optical Disk.

The power supply component 806 provides power to various components of the electronic device 800 . Power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for electronic device 800 .

The multimedia component 808 includes a screen providing an output interface between the electronic device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the electronic device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a microphone (MIC), which is configured to receive an external audio signal when the electronic device 800 is in an operation mode, such as a call mode, a recording mode and a voice recognition mode. Received audio signals may be further stored in memory 804 or sent via communication component 816 . In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

The input/output interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of electronic device 800 . For example, the sensor component 814 can detect the open/closed state of the electronic device 800, the relative positioning of components, such as the display and the keypad of the electronic device 800, the sensor component 814 can also detect the electronic device 800 or a Changes in position of components, presence or absence of user contact with electronic device 800 , electronic device 800 orientation or acceleration/deceleration and temperature changes in electronic device 800 . Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. The sensor assembly 814 may also include an optical sensor, such as a complementary metal-oxide-semiconductor (CMOS) or charge-coupled device (CCD) image sensor, for use in imaging applications. In some embodiments, the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 can access wireless networks based on communication standards, such as wireless networks (Wi-Fi), second-generation mobile communication technologies (2G), third-generation mobile communication technologies (3G), fourth-generation mobile communication technologies (4G ), long-term evolution (LTE) of universal mobile communication technology, fifth generation mobile communication technology (5G) or their combination. In an exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, electronic device 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the method described above.

In an exemplary embodiment, there is also provided a non-volatile computer-readable storage medium, such as the memory 804 including computer program instructions, which can be executed by the processor 820 of the electronic device 800 to implement the above method.

The present disclosure can be a system, method and/or computer program product. A computer program product may include a computer readable storage medium having computer readable program instructions thereon for causing a processor to implement various aspects of the present disclosure.

A computer readable storage medium may be a tangible device that can retain and store instructions for use by an instruction execution device. A computer readable storage medium may be, for example, but is not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (non-exhaustive list) of computer-readable storage media include: portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or flash memory), static random access memory (SRAM), compact disc read only memory (CD-ROM), digital versatile disc (DVD), memory stick, floppy disk, mechanically encoded device, such as a printer with instructions stored thereon A hole card or a raised structure in a groove, and any suitable combination of the above. As used herein, computer-readable storage media are not to be construed as transient signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., pulses of light through fiber optic cables), or transmitted electrical signals.

Computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or downloaded to an external computer or external storage device over a network, such as the Internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers. A network adapter card or a network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in each computing/processing device .

Computer program instructions for performing the operations of the present disclosure may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or Source or object code written in any combination, including object-oriented programming languages—such as Smalltalk, C++, etc., and conventional procedural programming languages—such as the “C” language or similar programming languages. Computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server implement. In cases involving a remote computer, the remote computer can be connected to the user computer through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (such as through the Internet using an Internet service provider). connect). In some embodiments, electronic circuits, such as programmable logic circuits, field programmable gate arrays (FPGAs) or programmable logic arrays (PLAs), can be customized by utilizing state information of computer-readable program instructions, which can Various aspects of the present disclosure are implemented by executing computer readable program instructions.

Aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It should be understood that each block of the flowcharts and/or block diagrams, and combinations of blocks in the flowcharts and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that when executed by the processor of the computer or other programmable data processing apparatus , producing an apparatus for realizing the functions/actions specified in one or more blocks in the flowchart and/or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause computers, programmable data processing devices and/or other devices to work in a specific way, so that the computer-readable medium storing instructions includes An article of manufacture comprising instructions for implementing various aspects of the functions/acts specified in one or more blocks in flowcharts and/or block diagrams.

It is also possible to load computer-readable program instructions into a computer, other programmable data processing device, or other equipment, so that a series of operational steps are performed on the computer, other programmable data processing device, or other equipment to produce a computer-implemented process , so that instructions executed on computers, other programmable data processing devices, or other devices implement the functions/actions specified in one or more blocks in the flowcharts and/or block diagrams.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in a flowchart or block diagram may represent a module, a portion of a program segment, or an instruction that includes one or more Executable instructions. In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved. It should also be noted that each block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by a dedicated hardware-based system that performs the specified function or action , or may be implemented by a combination of dedicated hardware and computer instructions.

The computer program product can be specifically realized by means of hardware, software or a combination thereof. In an optional embodiment, the computer program product is embodied as a computer storage medium. In another optional embodiment, the computer program product is embodied as a software product, such as a software development kit (Software Development Kit, SDK), etc. Wait.

The above descriptions of the various embodiments tend to emphasize the differences between the various embodiments, the same or similar points can be referred to each other, and for the sake of brevity, details are not repeated herein.

Those skilled in the art can understand that in the above method of specific implementation, the writing order of each step does not mean a strict execution order and constitutes any limitation on the implementation process. The specific execution order of each step should be based on its function and possible The inner logic is OK.

If the technical solution of this application involves personal information, the product applying the technical solution of this application has clearly notified the personal information processing rules and obtained the individual's independent consent before processing personal information. If the technical solution of this application involves sensitive personal information, the products applying the technical solution of this application have obtained individual consent before processing sensitive personal information, and at the same time meet the requirements of "express consent". For example, at a personal information collection device such as a camera, a clear and prominent sign is set up to inform that it has entered the scope of personal information collection, and personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed to agree to the collection of his personal information; or On the personal information processing device, when the personal information processing rules are informed with obvious signs/information, personal authorization is obtained through pop-up information or by asking individuals to upload their personal information; among them, the personal information processing rules may include Information such as the information processor, the purpose of personal information processing, the method of processing, and the type of personal information processed.

Having described various embodiments of the present disclosure above, the foregoing description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and alterations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principle of each embodiment, practical application or improvement of technology in the market, or to enable other ordinary skilled in the art to understand each embodiment disclosed herein.

Claims (10)

1. A management method of firmware is applied to a flash memory, and is characterized in that the flash memory is configured in an adapter, and the management method comprises the following steps:

acquiring an operation instruction for the firmware to be operated; the firmware to be operated is firmware corresponding to hardware in the adapter;

determining partition information corresponding to the firmware to be operated according to the operation instruction; wherein the partition information includes: the firmware to be operated and the firmware information corresponding to the firmware to be operated; the partition information is obtained based on a packed configuration file sent by a host; the partition information corresponds to a partition flash memory address; the partition flash memory address is used for determining the storage position of the partition information in the flash memory;

and executing the operation content in the operation instruction on the firmware to be operated according to the firmware information corresponding to the firmware to be operated.

2. The management method according to claim 1, wherein the management method further comprises:

responding to a packed configuration file sent by a host, and analyzing the packed configuration file to obtain partition information corresponding to each firmware;

and saving the partition information corresponding to each firmware.

3. The method for managing according to claim 2, wherein the parsing the packaged configuration file to obtain partition information corresponding to each firmware includes:

analyzing the packed configuration file to obtain partition information corresponding to each firmware and a partition flash memory address corresponding to each firmware; the partition flash memory address is used for determining the storage position of the partition information in the flash memory;

the saving of the partition information corresponding to each firmware includes:

and storing the partition information corresponding to each firmware into the partition flash memory address of the flash memory.

4. A management method of firmware is applied to a host, and is characterized in that the host is connected with a flash memory in an adapter, and the management method comprises the following steps:

generating or updating a configuration file according to the initial firmware information corresponding to each firmware; the initial firmware information is used for representing the firmware information of each firmware in the initial development environment, and the firmware is the firmware corresponding to the hardware in the adapter; wherein the configuration file is used to determine partition information for each firmware; the partition information corresponds to a partition flash memory address; the partition flash memory address is used for determining the storage position of the partition information in the flash memory;

and packaging the configuration file, and sending the packaged configuration file to the flash memory.

5. The method for managing as set forth in claim 4, wherein the generating or updating the configuration file according to the initial firmware information corresponding to each firmware comprises:

signing each firmware to generate a signature file corresponding to each firmware;

and generating or updating a configuration file according to the initial firmware information corresponding to each firmware and the signature file corresponding to each firmware.

6. The method according to claim 4 or 5, wherein the generating or updating the configuration file according to the initial firmware information corresponding to each firmware comprises:

determining a partition flash memory address corresponding to each firmware; the partition flash memory address is used for determining the position of each firmware loaded in the flash memory;

and generating or updating a configuration file according to the initial firmware information corresponding to each firmware and the partition flash memory address corresponding to each firmware.

7. The management method according to any one of claims 4 or 5, characterized in that the management method further comprises:

generating an operation instruction for the firmware to be operated according to the configuration file; the operating instruction is used for updating the partition information of the firmware to be operated in the flash memory;

sending the operation instruction to the flash memory;

and generating prompt information corresponding to the firmware updating information in response to the firmware updating information sent by the flash memory.

8. A flash memory, wherein the flash memory is configured in an adapter, the flash memory comprising:

the operating instruction acquisition module is used for acquiring an operating instruction aiming at the firmware to be operated; the firmware to be operated is firmware corresponding to hardware in the adapter;

the partition information determining module is used for determining partition information corresponding to the firmware to be operated according to the operation instruction; wherein the partition information includes: the firmware to be operated and the firmware information corresponding to the firmware to be operated; the partition information is obtained based on a packed configuration file sent by a host; the partition information corresponds to a partition flash memory address; the partition flash memory address is used for determining the storage position of the partition information in the flash memory;

and the operating instruction executing module is used for executing the operating content in the operating instruction to the firmware to be operated according to the firmware information corresponding to the firmware to be operated.

9. A host, wherein the host is coupled to the flash memory of claim 8, the flash memory being configured in an adapter, the host further comprising:

the configuration file updating module is used for generating or updating a configuration file according to the initial firmware information corresponding to each firmware; the initial firmware information is used for representing the firmware information of each firmware in the initial development environment, and the firmware is the firmware corresponding to the hardware in the adapter; wherein the configuration file is used to determine partition information for each firmware; the partition information corresponds to a partition flash memory address; the partition flash memory address is used for determining the storage position of the partition information in the flash memory;

and the configuration file sending module is used for packaging the configuration files and sending the packaged configuration files to the flash memory.

10. A computer-readable storage medium on which computer program instructions are stored, which computer program instructions, when executed by a processor, implement the management method of any one of claims 1 to 7.

Images