CN111258617B - Electronic equipment - Google Patents
Electronic equipment Download PDFInfo
- Publication number
- CN111258617B CN111258617B CN201911425086.1A CN201911425086A CN111258617B CN 111258617 B CN111258617 B CN 111258617B CN 201911425086 A CN201911425086 A CN 201911425086A CN 111258617 B CN111258617 B CN 111258617B
- Authority
- CN
- China
- Prior art keywords
- file system
- storage space
- system driver
- fast file
- processor chip
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012360 testing method Methods 0.000 claims abstract description 49
- 238000000034 method Methods 0.000 claims description 48
- 230000008569 process Effects 0.000 claims description 44
- 238000012795 verification Methods 0.000 claims description 6
- 230000002093 peripheral effect Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 11
- 230000009471 action Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4411—Configuring for operating with peripheral devices; Loading of device drivers
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides an electronic device, which comprises a mainboard, a first storage device and a processor chip, wherein the first storage device and the processor chip are arranged on the mainboard; the first storage device at least comprises a first storage space and a second storage space, wherein the first storage space stores a power-on self-test application program for driving the processor chip to run, and the power-on self-test application program comprises an original rapid file system driving program; the second storage space is used for storing an updated fast file system driver, if the original fast file system driver in the power-on self-test application program is updated, and the updated fast file system driver is stored in the second storage space, only the fast file system driver can be updated when the program is updated, and the updated fast file system driver is stored in the second storage space, so that the whole update of the power-on self-test application program is not needed, and the program updating flow and time are reduced.
Description
Technical Field
The application belongs to the technical field of equipment safety, and particularly relates to an electronic device.
Background
The FFSdriver (fast file system driver) program is a driver program related to a BIOS (basic input output system) in an electronic device.
At present, the FFSdriver program in the electronic device is located in the power-on self-test application program and is updated along with the update of the power-on self-test application program, that is, if the FFSdriver program needs to be updated, the whole update of the power-on self-test application program needs to be performed.
Disclosure of Invention
In view of the above, an object of the present application is to provide an electronic device, including:
the system comprises a mainboard, a first storage device and a processor chip;
the first storage device and the processor chip are arranged on the mainboard;
the first storage device at least comprises a first storage space and a second storage space, the first storage space stores a power-on self-test application program for driving the processor chip to run, and the power-on self-test application program comprises an original rapid file system driving program;
the second storage space is used for storing an updated fast file system driver, and if the original fast file system driver in the power-on self-test application program is updated, the updated fast file system driver is stored in the second storage space.
Optionally, the first storage space and the second storage space are independent from each other, and address data of the first storage space and address data of the second storage space are different.
Optionally, the processor chip is configured to obtain a fast file system driver to be updated and address data of the second storage space, and write the obtained fast file system driver into the second storage space according to the address data of the second storage space.
Optionally, the processor chip is configured to verify integrity of the obtained fast file system driver, and if the verification is passed, replace the fast file system driver stored in the second storage space with the obtained fast file system driver.
Optionally, the method further includes: a second storage device; the processor chip has more access to the second memory means than to the first memory means.
Optionally, the second storage device is configured to store an updated fast file system driver.
Optionally, the processor chip is configured to call the fast file system driver in the second storage space of the first storage device if the call of the fast file system driver in the second storage device fails.
Optionally, the operation process of the processor chip includes a first type operation process and a second type operation process;
the processor chip is in the first type running process, and calls the original fast file system driver;
and the processor chip is in the second type operation process and calls the updated fast file system driving program.
Optionally, the first storage device is a serial peripheral interface read only memory.
Optionally, the second storage device is a hard disk storage.
According to the technical scheme, the first storage device at least comprises a first storage space and a second storage space, the first storage space stores a power-on self-test application program for driving the processor chip to run, and the power-on self-test application program comprises an original rapid file system driving program; the second storage space is used for storing an updated fast file system driver, if an original fast file system driver in the power-on self-test application program is updated, the updated fast file system driver is stored in the second storage space, so that the original fast file system driver and the updated fast file system driver can be stored in the first storage space and the second storage space respectively, if the fast file system driver needs to be updated, only the fast file system driver in the second storage space can be updated, the whole update of the self-test application program of the starting-up machine is not needed, the program updating process is simplified, and the updating time is shortened.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a block diagram of an electronic device according to an embodiment of the present disclosure;
FIG. 2 is a diagram illustrating a call to a fast file system driver according to an embodiment of the present application;
FIG. 3 is a diagram of another method for invoking a fast file system driver according to an embodiment of the present application;
fig. 4 is a block diagram of another electronic device provided in an embodiment of the present application;
fig. 5 is a schematic diagram of another fast file system driver invocation program provided in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that the electronic devices referred to in the embodiments of the present application are not limited to notebook computers, desktop computers, tablet computers, and the like, and the types of the electronic devices are not particularly limited.
Referring to fig. 1, a block diagram of an electronic device according to an embodiment of the present application is shown, where the electronic device at least includes: motherboard 100, first memory device 200, and processor chip 300.
The first storage device 200 and the processor chip 300 are disposed on the motherboard 100, and at least two storage spaces are disposed in the first storage device 200, for example, the first storage device includes at least a first storage space 201 and a second storage space 202. The first storage device 200 may be a memory capable of being disposed on a motherboard, for example, the first storage device may be a serial peripheral interface read only memory, and similarly, the first storage device 200 may also be another type of memory, which is not specifically limited in this embodiment of the application.
In the electronic device shown in fig. 1, the main board 100 of the electronic device includes a plurality of components, and not only the first storage device 200 and the processor chip 300, but also other components on the main board 100 are not listed here. Similarly, the storage space included in the first storage device 200 is not limited to the first storage space 201 and the second storage space 202.
In this embodiment, the first storage space 201 and the second storage space 202 store different types of data, and the first storage space 201 stores therein a power-on self-test application (FV _ MAIN) for driving the processor chip 300 to run, where the power-on self-test application includes an original fast file system driver (FFSdriver). The second storage space 202 stores the updated fast file system driver, and if the original fast file system driver in the power-on self-test application is updated, the updated fast file system driver is stored in the second storage space. For example: a secure region, named as OSR (odmsecurtyregion), is provided in the first storage device 202, and the OSR region serves as a second storage space for storing the updated fast file system driver.
Because the second storage space can store the updated fast file system driver, only the second storage space can be updated when the fast file system driver is updated, and the fast file system driver to be updated can be stored in the second storage space, and the power-on self-check application program does not need to be updated.
In this embodiment, the power on self test application functions as follows: when the electronic equipment is started, the power-on self-test application program is used for carrying out power-on self-test. The power-on self-test application program is a program in Firmware (FV), and the Firmware is a main part in a BIOS (basic input output system).
It can be understood that the original fast file system driver included in the power-on self-test application can be classified into the following two cases:
the first situation is as follows: the electronic equipment factory-leaving power-on self-test application program carries a rapid file system driver, and the original rapid file system driver is the rapid file system driver carried in the electronic equipment factory-leaving power-on self-test application program.
Case two: in the usage process of the electronic device, the processor chip 300 may upgrade the power-on self-test application, and when the power-on self-test application is upgraded, the fast file system driver in the power-on self-test application is also upgraded accordingly, in this case, the original fast file system driver is the fast file system driver in the upgraded power-on self-test application.
For the two situations, the updated fast file system driver stored in the second storage space is the updated fast file system driver stored in the second storage space and downloaded separately after the electronic device leaves the factory and the power-on self-test application program is not upgraded, or the fast file system driver in the second storage space is updated separately again after the power-on self-test application program is upgraded each time.
Therefore, the original quick file system driving program and the updated quick file system driving program can be stored in the first storage space and the second storage space respectively, if the quick file system driving program needs to be updated, the quick file system driving program in the second storage space can be updated only, the whole updating of the self-checking application program of the computer is not needed, the program updating process is simplified, and the updating time is shortened.
In this embodiment, in order not to interfere with each other when the first storage space and the second storage space are upgraded, the first storage space 201 and the second storage space 202 are independent of each other, for example, the storage areas occupied by the two storage spaces are independent of each other, and further, in the case where the first storage space 201 and the second storage space 202 are provided in the first storage device 200, the address data for accessing the first storage space 201 and the second storage space 202 are different, so that the first storage space 201 or the second storage space 202 can be operated independently, for example, a fast file system driver in the second storage space 202 can be updated independently.
The fast file system driver in the second storage space 202 is updated independently, and the fast file system driver stored before the second storage space can be replaced by the latest fast file system driver directly, or the latest fast file system driver is written into the second storage space and deleted after being successfully called
In this embodiment, the process of independently updating the fast file system driver in the second storage space is as follows:
the processor chip 300 obtains the fast file system driver to be updated and the address data of the second storage space 202, and the processor chip 300 writes the fast file system driver to be updated into the second storage space 202 according to the address data of the second storage space 202. Because the address data of the second storage space is different from that of the first storage space, the first storage space is not influenced in the process of updating the second storage space, and therefore the second storage space is independently updated.
It should be noted that before the processor chip 300 writes the fast file system driver to be updated into the second storage space 202, the processor chip 300 verifies the integrity of the obtained fast file system driver to be updated through a preset verification method. If the driver of the fast file system to be updated is determined to be complete (verified), the driver of the fast file system to be updated is written into the second storage space 202, for example, the driver of the fast file system stored in the second storage space 202 is replaced with the acquired driver of the fast file system.
For example: when the processor chip 300 obtains the fast file system driver to be updated, the signature verification and checksum (checksum) is performed on the fast file system driver to be updated, so as to ensure that the fast file system driver to be updated is correct and complete program data.
According to the above technical solution, the first storage space 201 and the second storage space 202 are independent from each other, and the address data of the first storage space is different from the address data of the second storage space, so that the processor chip 300 can independently upgrade the power-on self-test application program in the first storage space 201, and also independently write the fast file system driver to be updated into the second storage space 202, thereby independently upgrading the program in any storage space without mutual influence between the first storage space and the second storage space.
In one implementation, the processor chip 300 is running, and the running process types of the processor chip 300 include at least two types of running processes, for example, at least two running processes include: a first type of operation and a second type of operation.
The first type operation and the second type operation of the processor chip 300 in the present embodiment refer to: the processor chip 300 may be a process of a fast system driver invoked by the processor chip 300 during different types of operations. The first and second types of operation of processor chip 300 are described below.
The first type of operation of processor chip 300:
the processor chip 300 calls the original fast file system driver, i.e. the fast file system driver in the first memory space 201, while in the first type of operation.
The first type of operation process may be used to indicate that the electronic device is booted for the first time after leaving the factory, the fast file system driver is not stored in the second storage space 202 (the second storage space 202 is blank), or the power-on self-test application in the first storage space 201 is upgraded, and the version of the fast file system driver stored in the second storage space 202 is lower than the version of the fast file system driver in the first storage space 201.
For various situations of the first type operation process, the process of the processor chip 300 calling the fast file system driver in the first storage space 201 is described as an example in which the first type operation process and the second type operation process correspond to the booting of the electronic device, and the first type operation process and the second type operation process also correspond to applications other than the booting, which is not necessarily described in this embodiment.
Example one: after the electronic device leaves the factory (or after the factory setting is restored), when the electronic device is turned on for the first time, the processor chip 300 calls the original fast file system driver from the first storage space 201.
Example two: in the using process of the electronic device, the power-on self-test application program in the first storage space 201 may be upgraded, and as can be known from the foregoing, the power-on self-test application program also upgrades the fast file system driver in the power-on self-test application program at the same time, so that the version of the fast file system driver in the first storage space is higher than the version of the fast file system driver in the first storage space 201, and after the power-on self-test application program is upgraded, when the electronic device is powered on for the first time, the processor chip 300 calls the original fast file system driver from the first storage space 201.
Example three: the second storage space 202 stores the updated fast file system driver, but the second storage space 202 may not have the correct fast file system driver stored therein for a number of reasons. When the electronic device is powered on, the processor chip 300 calls the original fast file system driver from the first storage space 201 due to a driver error of the second storage space 202.
Example four: the second storage space 202 stores the updated fast file system driver, but the version of the fast file system driver in the second storage space 202 is lower than that of the fast file system driver in the first storage space 201 for various reasons, so that the processor chip 300 calls the original fast file system driver from the first storage space 201 when the electronic device is powered on.
It is understood that, in this embodiment, the processor chip 300 may obtain the first version number of the fast file system driver in the first storage space 201 and obtain the second version number of the fast file system driver in the second storage space 202 before calling the fast file system driver. The first version number and the second version number are compared to determine which storage space has the high version of the fast file system driver.
For better explanation, the case where the version of the fast file system driver in the second storage space 202 is lower than the version of the fast file system driver in the first storage space 201 is referred to in the fourth example above, and the following is given as an example.
In the using process of the electronic device, the power-on self-test application program in the first storage space 201 is upgraded, and after the power-on self-test application program is successfully upgraded, the version of the fast file system driver program in the first storage space 201 is higher than the version of the fast file system driver program in the second storage space 202.
According to the second example, when the electronic device is turned on next time (assuming that the electronic device is turned on for the n +1 th time, n is a positive integer), the processor chip 300 calls the original fast file system driver from the first storage space 201. At this time, the electronic device may not write the fast file system driver to be updated into the second storage space 202 during the use process.
That is, at this time, the version of the fast file system driver in the second storage space 202 is still lower than the version of the fast file system driver in the first storage space 201, and when the electronic device is booted at the n +2 th time, the processor chip 300 still calls the original fast file system driver from the first storage space 201.
The second type of operation of processor chip 300:
the processor chip 300 calls the updated fast file system driver, i.e. the fast file system driver in the second memory space 202, while in the second type of operation.
It can be understood that the first storage space 201 and the second storage space 202 are independent from each other, and the address data of the first storage space and the address data of the second storage space are different, so that in the process of using the electronic device, when the fast file system driver needs to be updated, the updated fast file system driver can be separately stored in the second storage space 202 without updating the power-on self-test application, and at this time, the version number of the fast file system driver in the second storage space 202 is higher than the version number of the fast file system driver in the first storage space 201. When the electronic device is powered on, the processor chip 300 calls the fast file system driver from the second storage space 202.
As can be seen from the above contents in the first type operation process and the second type operation process of the processor chip 300, when the fast file system driver is updated, the fast file system driver can be updated in a manner of upgrading the power-on self-test application, and the fast file system driver in the second storage space 202 can also be updated separately.
However, no matter which updating mode is adopted, even if the updating fails, the starting process of the electronic equipment cannot be influenced. That is, when the fast file system driver is updated by upgrading the power-on self-test application, if the update fails, the processor chip 300 may call the fast file system driver in the second storage space 202 during the power-on process of the electronic device, so as to ensure that the electronic device can be normally powered on.
When the fast file system driver in the second storage space 202 is updated separately, the processor chip 300 may call the fast file system driver in the first storage space 201 if the updated fast file system driver fails to be written into the second storage space 202.
It will be appreciated that the processor chip 300 may re-invoke the original fast file system driver in the first storage space 201 if the invocation fails while in the second type of operation, i.e. when the invocation fails to invoke the updated fast file system driver, i.e. the fast file system driver in the second storage space 202.
According to the above technical solution, when the processor chip 300 is in different operation process types, the called fast file system driver has different processes. When the processor chip 300 is in the first type of operation, the original fast file system driver in the first memory space 201 is called. When the processor chip 300 is in the second type of operation, the updated fast file system driver in the second storage space 202 is called, thereby ensuring that the electronic device can be normally powered on.
To better explain the process of the processor chip 300 calling the fast file system driver in the first type of running process and the second type of running process in the embodiment of the present application described above, a schematic diagram of calling the fast file system driver as shown in fig. 2 is provided, and it should be noted that fig. 2 is only illustrated by way of example in boot.
The schematic diagram of invoking the fast file system driver shown in fig. 2 is divided into the following three phases.
At the first stage, when the electronic device is booted (PowerOn) for the first time after leaving the factory (or after restoring factory settings), the processor chip 300 calls an original fast file system driver (FFS driver) from the power on self-test application (FV _ MAIN in fig. 2) stored in the first storage space 201, and completes the booting process of the electronic device.
In stage two, during the use of the electronic device, the processor chip 300 obtains the updated fast file system driver and verifies the driver. The verified updated fast file system driver is stored in the second storage space 202 (OSR in fig. 2) by the designated flush tool, the designated flush tool stores the updated fast file system driver in the second storage space 202 by acquiring the fast file system driver to be updated and acquiring address data of the second storage space 202, and the processor chip 300 writes the fast file system driver to be updated in the second storage space 202 according to the address data of the second storage space 202.
And step three, after the updated fast file system driver is stored in the OSR, when the electronic device is powered on again, the processor chip 300 calls the updated fast file system driver from the OSR to complete the power-on process of the electronic device.
Accordingly, to better explain the process of invoking the fast file system driver related to the processor chip 300 under different operation process types, another schematic diagram of invoking the fast file system driver as shown in fig. 3 is proposed, and it should be noted that fig. 3 is only used for illustration.
When the processor chip 300 is in the first type operation process, the processor chip 300 calls an original fast file system driver (FFSdriver) from FV _ MAIN (power on self test application) stored in the first storage space 201, so that the electronic device completes a corresponding application (e.g., the first application in fig. 3).
When the processor chip is in the second type of operation process, the processor chip calls the updated fast file system driver from the second storage space 202 (OSR in fig. 3) to make the electronic device complete the corresponding application (e.g., the first application in fig. 3).
The type of the first storage device 200 included in the electronic apparatus shown in fig. 1 includes, but is not limited to, a serial peripheral interface read only memory (spi rom), for which the speed of reading data is limited. The processor chip 300 may not call the fast file system driver from the first storage device 200 fast, reducing processing efficiency. To solve this problem, a block diagram of another electronic device shown in fig. 4 is proposed, where the electronic device shown in fig. 4 further includes: a second storage means 400. The second storage device 400 is externally connected to the motherboard, that is, the second storage device 400 is not disposed on the motherboard, but is plugged into the motherboard in some manner, for example, the motherboard 100 provides a plurality of joints for external devices, and the second storage device 400 is connected to the motherboard 100 through the joints provided by the motherboard 100.
In the embodiment, the path for accessing the second storage apparatus 400 is greater than the path for accessing the first storage apparatus 200, thereby illustrating that the access security performance of the second storage apparatus 400 is lower than that of the first storage apparatus 200.
In one implementation, the second storage 400 is also used to store the updated fast file system driver so as to backup the updated fast file system driver through the second storage space and the second storage 400.
In this embodiment, the processor chip 300 obtains the fast file system driver to be updated and verifies the obtained fast file system driver, that is, the processor chip 300 verifies the integrity of the obtained fast file system driver to be updated through a preset verification method. If the driver of the fast file system to be updated is determined to be complete (verified), the driver of the fast file system to be updated is written into the second storage device 400. The processor chip 300 may also write the fast file system driver to be updated, which passes the verification, into the second storage space 202, while writing the fast file system driver to be updated into the second storage 400.
It is understood that the second storage means 400 is a hard disk memory, such as: the second storage device 400 is a solid state disk memory having a fast read/write characteristic, so that although the security performance of the second storage device 400 is lower than that of the first storage device, the read/write rate is higher than that of the first storage device, and based on this, the processor chip 300 may also set the order of accessing the second storage device and the first storage space. If the read/write rate is the first priority, the processor chip 300 calls the fast file system driver in the second storage device 400 preferentially, and if the calling of the fast file system driver updated in the second storage device 400 fails, the processor chip 300 calls the fast file system driver in the first storage device 200.
When the processor chip 300 calls the fast file system driver in the first storage device 200, the processor chip 300 calls the fast file system driver in the second storage space 202 of the first storage device 200.
If the second storage space 202 does not contain the fast file system driver, or if the version of the fast file system driver in the second storage space 202 is lower than that of the fast file system driver in the first storage space 201, the processor chip 300 calls the fast file system driver in the first storage space 201 of the first storage device 200.
Also in the second storage means 400, there may be a case where the fast file system driver is not stored, and the processor chip 300 cannot call the fast file system driver in the second storage means 400. At this point the processor chip 300 calls the fast file system driver from the first storage means 200. The specific contents of the processor chip 300 calling the fast file system driver in the first storage device 200 can be referred to the related contents in the above embodiments, and are not described herein again.
If the processor chip 300 sets the order of accessing the second storage device and the first storage space to be the first of security performance, the fast file system driver of the second storage space is called preferentially, if the calling fails, the fast file system driver in any one of the second storage device and the first storage space can be called, and if the calling fails again, the fast file system driver in the remaining one of the second storage device and the first storage space can be called.
In addition, during the use of the electronic device, the power on self test application in the first storage space 201 may be upgraded, so that the original fast file system driver in the first storage space 201 may be updated along with the upgrade of the power on self test application. At this time, the version of the fast file system driver in the first storage space may be higher than the versions of the fast file system driver in the second storage space and the second storage device, and then when the next electronic device after the power-on self-test application is upgraded is powered on, the processor chip 300 first calls the original fast file system driver from the first storage space 201, and for the specific definition of the original fast file system driver, reference may be made to the related contents in fig. 1 of the embodiment of the present application, which is not described herein again.
As can be seen from the above technical solutions, the electronic device includes a main board 100, a first storage device 200, a processor chip 300 and a second storage device 400. When the electronic device is powered on, the processor chip 300 preferentially calls the fast file system driver from the second storage device 400, and if the call is successful, the processing efficiency is improved. If the fast file system driver is not called from the second storage device 400, the processor chip 300 also calls the fast file system driver from the first storage device 200 to ensure the normal operation of the electronic device.
To better explain the process of invoking the fast file system driver by the processor chip 300 in fig. 4 in the embodiment of the present application, a schematic diagram of invoking the fast file system driver is provided as shown in fig. 5, and it should be noted that fig. 5 is only used for illustration.
When the electronic device is powered on, the processor chip 300 preferably calls the updated fast file system driver in the second storage device 400. When the processor chip 300 calls the updated fast file system driver in the second storage device 400, if the updated fast file system driver in the second storage device 400 cannot be executed, or the fast file system driver does not exist in the second storage device 400, it may be determined that the call fails, and how to determine that the call of the updated fast file system driver in the second storage device 400 fails may refer to the related contents in fig. 4.
The processor chip 300 calls the fast file system driver from the first storage device 200 to ensure normal booting of the electronic device. For a specific process of the processor chip 300 invoking the fast file system driver from the first storage device 200, reference may be made to relevant contents in the above embodiments, and details are not described herein again.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a device that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such device. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of additional like elements in a device that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
The foregoing is merely an alternative embodiment of the present application and it should be noted that modifications and embellishments could be made by those skilled in the art without departing from the principle of the present application and should be considered as the scope of the present application.
Claims (10)
1. An electronic device, the electronic device comprising:
the system comprises a mainboard, a first storage device and a processor chip;
the first storage device and the processor chip are arranged on the mainboard;
the first storage device at least comprises a first storage space and a second storage space, the first storage space stores a power-on self-test application program for driving the processor chip to run, and the power-on self-test application program comprises an original rapid file system driving program;
the second storage space is used for storing an updated fast file system driver, and if the original fast file system driver in the power-on self-test application program is updated, the updated fast file system driver is stored in the second storage space.
2. The electronic device of claim 1, wherein the first storage space and the second storage space are independent of each other, and address data of the first storage space and the second storage space are different.
3. The electronic device of claim 1, wherein the processor chip is configured to obtain a fast file system driver to be updated and address data of the second storage space, and write the obtained fast file system driver into the second storage space according to the address data of the second storage space.
4. The electronic device of claim 3, wherein the processor chip is configured to verify the integrity of the obtained fast file system driver, and if the verification is passed, replace the fast file system driver stored in the second storage space with the obtained fast file system driver.
5. The electronic device of any of claims 1-4, further comprising: a second storage device; the processor chip has more access to the second memory means than to the first memory means.
6. The electronic device of claim 5, the second storage to store an updated fast file system driver.
7. The electronic device of claim 6, the processor chip to invoke the fast file system driver in the second storage space of the first storage device if the invocation of the fast file system driver in the second storage device fails.
8. The electronic device of any one of claims 1-4, wherein the processor chip operations include a first type of operation and a second type of operation;
the processor chip is in the first type running process, and calls the original fast file system driver;
and the processor chip is in the second type operation process and calls the updated fast file system driving program.
9. The electronic device of any one of claims 1-4, wherein the first storage is a serial peripheral interface read only memory.
10. The electronic device of any of claims 1-4, the second storage being a hard disk storage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911425086.1A CN111258617B (en) | 2019-12-31 | 2019-12-31 | Electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911425086.1A CN111258617B (en) | 2019-12-31 | 2019-12-31 | Electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111258617A CN111258617A (en) | 2020-06-09 |
| CN111258617B true CN111258617B (en) | 2022-03-25 |
Family
ID=70946776
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911425086.1A Active CN111258617B (en) | 2019-12-31 | 2019-12-31 | Electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111258617B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112099860B (en) * | 2020-09-15 | 2023-02-10 | 深圳忆联信息系统有限公司 | Automatic reconstruction grouping method and device of drive files, computer equipment and storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1049923A (en) * | 1989-08-25 | 1991-03-13 | 国际商业机器公司 | Device and method for preventing unauthorized access to a basic input output system |
| CN1371051A (en) * | 2001-02-20 | 2002-09-25 | 技嘉科技股份有限公司 | BIOS update method in computer system |
| CN101038555A (en) * | 2006-03-15 | 2007-09-19 | 戴尔产品有限公司 | A chipset-independent method for locally and remotely updating and configuring system bios |
| TW201335850A (en) * | 2013-04-30 | 2013-09-01 | Felicity Taiwan Corp | A computer system using a Disk-BIOS and the method thereof |
| CN103853566A (en) * | 2012-11-30 | 2014-06-11 | 鸿富锦精密工业（深圳）有限公司 | Basic input output system (BIOS) updating system and method |
| CN103914311A (en) * | 2012-12-31 | 2014-07-09 | 研祥智能科技股份有限公司 | Firmware management method and system |
| CN104516752A (en) * | 2013-09-26 | 2015-04-15 | 联想(北京)有限公司 | Information processing method and electronic equipment |
| CN104573529A (en) * | 2015-01-28 | 2015-04-29 | 加弘科技咨询(上海)有限公司 | BIOS firmware dividing and updating method and system |
| CN104636173A (en) * | 2015-03-11 | 2015-05-20 | 浪潮集团有限公司 | Fast BIOS configuration method |
| CN106528348A (en) * | 2016-11-18 | 2017-03-22 | 合肥联宝信息技术有限公司 | Method for constructing BIOS of intelligent terminal and BIOS component |
| CN107402772A (en) * | 2016-05-18 | 2017-11-28 | 深圳市祈飞科技有限公司 | A kind of method of upgrading BIOS |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN110515645A (en) * | 2019-07-31 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A method for realizing function update of BIOS and related device |
-
2019
- 2019-12-31 CN CN201911425086.1A patent/CN111258617B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1049923A (en) * | 1989-08-25 | 1991-03-13 | 国际商业机器公司 | Device and method for preventing unauthorized access to a basic input output system |
| CN1371051A (en) * | 2001-02-20 | 2002-09-25 | 技嘉科技股份有限公司 | BIOS update method in computer system |
| CN101038555A (en) * | 2006-03-15 | 2007-09-19 | 戴尔产品有限公司 | A chipset-independent method for locally and remotely updating and configuring system bios |
| CN103853566A (en) * | 2012-11-30 | 2014-06-11 | 鸿富锦精密工业（深圳）有限公司 | Basic input output system (BIOS) updating system and method |
| CN103914311A (en) * | 2012-12-31 | 2014-07-09 | 研祥智能科技股份有限公司 | Firmware management method and system |
| TW201335850A (en) * | 2013-04-30 | 2013-09-01 | Felicity Taiwan Corp | A computer system using a Disk-BIOS and the method thereof |
| CN104516752A (en) * | 2013-09-26 | 2015-04-15 | 联想(北京)有限公司 | Information processing method and electronic equipment |
| CN104573529A (en) * | 2015-01-28 | 2015-04-29 | 加弘科技咨询(上海)有限公司 | BIOS firmware dividing and updating method and system |
| CN104636173A (en) * | 2015-03-11 | 2015-05-20 | 浪潮集团有限公司 | Fast BIOS configuration method |
| CN107402772A (en) * | 2016-05-18 | 2017-11-28 | 深圳市祈飞科技有限公司 | A kind of method of upgrading BIOS |
| CN106528348A (en) * | 2016-11-18 | 2017-03-22 | 合肥联宝信息技术有限公司 | Method for constructing BIOS of intelligent terminal and BIOS component |
| CN109992517A (en) * | 2019-04-03 | 2019-07-09 | 中电科技（北京）有限公司 | Firmware module adjustment method and system based on UEFI |
| CN110515645A (en) * | 2019-07-31 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A method for realizing function update of BIOS and related device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111258617A (en) | 2020-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10613773B2 (en) | Backing up firmware during initialization of device | |
| US10437580B2 (en) | Software updating methods and systems | |
| US11144328B2 (en) | System method to update failover process by running basic input/output (BIOS) system boot code from non-volatile memory express device (NVME) | |
| US20040255106A1 (en) | Recovery of operating system configuration data by firmware of computer system | |
| US8539213B2 (en) | Manageability extension mechanism for system firmware | |
| US20100058314A1 (en) | Computer System and Related Method of Logging BIOS Update Operation | |
| US8788800B2 (en) | OS processing method, system and non-transitory computer readable storage medium thereof | |
| US20180052679A1 (en) | Method of Bootup and Installation, and Computer System thereof | |
| CN110737558A (en) | Method and device for automatically deploying efi shell system to execute test, computer equipment and storage medium | |
| US20130080751A1 (en) | Method and device for updating bios program for computer system | |
| CN114265603A (en) | System upgrade method, device and electronic device based on asymmetric partition | |
| CN102880478B (en) | Software update method | |
| US11106457B1 (en) | Updating firmware runtime components | |
| CN110515671B (en) | Initialization method, initialization device, terminal device and readable storage medium | |
| US20060190933A1 (en) | Method and apparatus for quickly developing an embedded operating system through utilizing an automated building framework | |
| CN111258617B (en) | Electronic equipment | |
| CN117687663B (en) | OTA-based partition dynamic adjustment method, device, equipment and storage medium | |
| CN115033267A (en) | Method for verifying equipment tree mirror image version and terminal equipment | |
| CN100476745C (en) | Method for realizing automatic fault tolerance of image file in Linux operating system boot process | |
| CN103106086B (en) | Operating system disposal route and system | |
| CN110286953B (en) | Method and device for starting embedded system, embedded device and storage medium | |
| JP2005149501A (en) | System and method for testing memory with expansion card using dma | |
| CN118210518A (en) | Method, device, processor and computer readable storage medium for realizing application cross-center independent deployment control for low-code platform | |
| CN113377425B (en) | Method and device for generating BMC firmware, method and device for starting BMC, and storage medium | |
| CN108052337A (en) | A kind of firmware upgrade method and device of eMMC production tools |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |