Firmware starting method, device, equipment and readable storage medium

Abstract

The application provides a firmware starting method, device and equipment and readable storage medium, the method comprises the following steps: obtaining user information input by a user, and judging whether the user information input by the user matches the user information pre-stored in the structure array; if the user information matches the pre-stored user information, determining the user type corresponding to the user information based on the correspondence between the pre-stored user information and the user type; and then using the firmware starting process corresponding to the user type to start the firmware. In the process of starting the firmware, the application adds the steps of comparing the user information and determining the user type; when the user information input by the user matches the pre-stored user information, the user type of the user is determined, and the firmware starting process corresponding to the user type is used to start the firmware, so that different user types of users have different device use permissions, thereby improving the security of the computer and ensuring the data security of the computer.

Description

Technical Field

[0001] This application relates to the field of computer data security technology, and in particular to a firmware boot method, apparatus, device and readable storage medium. Background Technology

[0002] Firmware is a set of programs embedded in the motherboard chipset of a computer. It includes the computer's most important basic input / output programs, power-on self-test (POST) programs, and / or system startup programs. When the computer is turned on, the firmware boots first, allowing the user to use the devices on the computer after startup.

[0003] Currently, in common solutions, any user can power on the computer, and the computer can boot from the preset firmware process. In other words, any user can use all devices on the computer after powering it on.

[0004] However, using the above method to boot the firmware will result in low computer security and cannot guarantee the security of the computer's data. Summary of the Invention

[0005] This application provides a firmware boot method, apparatus, device, and readable storage medium to improve computer security and thereby protect computer data security.

[0006] In a first aspect, embodiments of this application provide a firmware boot method, including:

[0007] Obtain user information input by the user, and determine whether the user information input by the user matches the user information pre-stored in the structure array;

[0008] If a match is found, the user type corresponding to the user information is determined based on the pre-stored correspondence between the user information and the user type.

[0009] Firmware boot is performed using a firmware boot process corresponding to the user type, wherein different user types correspond to different firmware boot processes.

[0010] Furthermore, in the method described above, the user type includes management type and normal type; the firmware booting process using the firmware boot procedure corresponding to the user type includes:

[0011] If the user type is management type, the first group of device controllers and devices are initialized, and a command array containing the first group of commands is obtained to realize firmware startup. The first group of device controllers and devices includes device controllers and devices with the function of interacting with external devices, and the first group of commands includes commands for modifying user information and device attributes.

[0012] If the user type is a normal type, the second group of device controllers and devices are initialized, and a command array containing the second group of commands is obtained to realize firmware startup. The second group of device controllers and devices does not include device controllers and devices with the function of interacting with external devices, and the second group of commands does not include commands for modifying user information and device attributes.

[0013] Furthermore, the method described above, after determining whether the user information input by the user matches the user information pre-stored in the structure array, further includes:

[0014] If the information does not match, a prompt message will be output, which will prompt the user to re-enter the user information.

[0015] The system detects whether the user has re-entered user information. If the user has re-entered user information, the system executes the steps of obtaining the user's input information and determining whether the user's input information matches the user information pre-stored in the structure array, as well as subsequent steps.

[0016] Furthermore, the method described above, when the user information input by the user does not match the user information pre-stored in the structure array, further includes:

[0017] Record the number of times the user information input by the user does not match the user information pre-stored in the structure array;

[0018] If the number of mismatches reaches a preset value, the firmware startup will stop and the system will enter an infinite loop.

[0019] Furthermore, the method described above, after stopping the firmware startup and entering an infinite loop, also includes:

[0020] Output an error message signal.

[0021] Furthermore, in the method described above, the user information input by the user includes a username; when the user information input by the user matches the user information pre-stored in the structure array, it further includes:

[0022] Create a structure array to record user login information;

[0023] The time when the user inputs user information and the username are obtained and stored in the structure array used to record user login information.

[0024] Furthermore, the method described above also includes:

[0025] The array of structures used to record user login information is stored in flash memory.

[0026] Secondly, embodiments of this application provide a firmware boot device, comprising:

[0027] The acquisition module is used to acquire user information input by the user and determine whether the user information input by the user matches the user information pre-stored in the structure array;

[0028] The determination module is used to determine the user type corresponding to the user information based on the pre-stored correspondence between the user information and the user type if a match is found.

[0029] The startup module is used to start the firmware using a firmware startup process corresponding to the user type, wherein different user types correspond to different firmware startup processes.

[0030] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0031] The memory is used to store the executable instructions of the processor;

[0032] The processor is used to invoke program instructions in the memory to execute the firmware boot method as described in the first aspect.

[0033] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the firmware boot method as described in the first aspect.

[0034] This application provides a firmware booting method, apparatus, device, and readable storage medium. It acquires user-inputted user information and determines whether the user-inputted information matches user information pre-stored in a structure array. If a match is found, the user type is determined based on the pre-stored correspondence between user information and user types. Then, a firmware booting process corresponding to the user type is employed to boot the firmware. In other words, this application adds a user information comparison and user type determination step to the firmware booting process. When the user-inputted information matches the pre-stored user information, the user type is determined, and a firmware booting process corresponding to the user type is employed. This allows users of different user types to have different device access permissions, thereby improving computer security and protecting computer data security. Attached Figure Description

[0035] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0036] Figure 1 A schematic diagram illustrating the firmware boot process as an example of existing technology;

[0037] Figure 2 A flowchart of the firmware boot method provided in Embodiment 1 of this application;

[0038] Figure 3 A schematic diagram of the firmware boot process provided as an example of this application;

[0039] Figure 4 A flowchart of the firmware boot method provided in Embodiment 2 of this application;

[0040] Figure 5 This is a schematic diagram of the firmware boot device provided in the embodiments of this application;

[0041] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0042] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concepts of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0043] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0044] When a computer is turned on, it first performs a firmware boot. Figure 1 A schematic diagram illustrating the firmware boot process as an example of existing technology, such as... Figure 1 As shown, during firmware startup, CPU initialization 110, memory initialization 120, bridge chip initialization 130, video memory initialization 140, and initialization of all device controllers and devices 150 are performed, and all command arrays are obtained 160, so that the user can use all devices on the computer after booting up.

[0045] Currently, in common solutions, any user can power on the computer, and the computer can boot from the preset firmware process. This means that any user can use all devices on the computer after powering on. However, this method of firmware booting compromises computer security, as any user can export data from the computer using external devices, thus compromising data security.

[0046] The firmware boot method, apparatus, device, and readable storage medium provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0047] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will be described below with reference to the accompanying drawings.

[0048] Example 1

[0049] Figure 2 The flowchart of the firmware boot method provided in Embodiment 1 of this application is as follows: Figure 2 As shown, the firmware boot method provided in this embodiment includes the following steps:

[0050] Step 201: Obtain the user information input by the user and determine whether the user information input by the user matches the user information pre-stored in the structure array.

[0051] Step 202: If a match is found, the user type corresponding to the user information is determined based on the pre-stored correspondence between the user information and the user type.

[0052] Step 203: Start the firmware using the firmware startup process corresponding to the user type, wherein different user types correspond to different firmware startup processes.

[0053] It should be noted that the execution entity of the firmware boot method provided in this embodiment can be a firmware boot device. In practical applications, this firmware boot device can be implemented by a computer program, such as application software, or by a medium storing the relevant computer program, such as a USB flash drive or optical disc, or by a physical device integrating or installing the relevant computer program, such as a chip. The firmware may include a pmon.

[0054] In this embodiment, in order to improve computer security and ensure computer data security, different firmware boot processes can be used during firmware boot according to different user types, so that different users can have different device usage permissions.

[0055] Specifically, the firmware boot device first obtains the user information entered by the user and determines whether the entered user information matches the user information pre-stored in a structure array. The user information includes, but is not limited to, username and / or password.

[0056] In practical applications, administrators can pre-store the user information of users who are allowed to use the current computer and their corresponding user types in the computer's structure array. When the computer boots up and performs firmware startup, a prompt message similar to "Please enter user information" will be displayed on the screen. After the user completes the input, the firmware startup device can obtain the user information entered by the user and determine whether the user information entered by the user matches the user information pre-stored in the structure array.

[0057] If a match is found, it indicates that the user is permitted to use the current computer. The firmware boot device can determine the user type based on the pre-stored correspondence between user information and user type, and perform firmware boot using the firmware boot process corresponding to the user type.

[0058] Different user types correspond to different firmware boot processes, and different firmware boot processes can initialize different device controllers and devices, thus allowing different users to have different device usage permissions.

[0059] In one example, based on the above embodiment one, the user type may include management type and ordinary type.

[0060] Figure 3 A schematic diagram of the firmware boot process provided as an example in this application is shown below. Figure 3As shown, after the firmware boot device completes CPU initialization 310, memory initialization 320, bridge chip initialization 330, and video memory initialization 340, it will perform user information matching and determine the user type 350. If the user type is management type, the firmware boot device can initialize the first group of device controllers and devices 360 and obtain a command array 370 containing the first group of commands to achieve firmware boot. The first group of device controllers and devices includes device controllers and devices with external device interaction capabilities. Therefore, management type users have the permission to use interfaces for external device interaction, such as USB interfaces and / or network ports. Furthermore, the first group of commands includes commands for modifying user information and device attributes. Therefore, management type users can modify the computer's device attributes, such as network card MAC address, network card IP, and / or environment variables, and can also modify their own and / or ordinary type user's user information.

[0061] Accordingly, if the user type is normal, the firmware boot device can initialize the second group of device controllers and devices 380 and obtain a command array 390 containing the second group of commands to realize firmware boot. The second group of device controllers and devices does not include device controllers and devices with the function of interacting with external devices, and the second group of commands does not include commands for modifying user information and device attributes.

[0062] In other words, because the firmware boot process does not initialize the device controller and device with external interaction capabilities, ordinary users cannot use such devices, meaning they lack the permission to interact with the computer using external devices; for example, they cannot import data from the computer to a USB drive. Furthermore, because the firmware boot process does not include commands to modify user information and device attributes in its command array, ordinary users cannot modify the computer's device attributes and user information.

[0063] Based on the above embodiment one, in an optional implementation, the user information input by the user may include a username. If the user information input by the user matches the user information pre-stored in a structure array, the firmware boot device can create a structure array for recording user login information, and then obtain the time and username of the user input information and store them in the structure array for recording user login information, so that management users can read it. Specifically, a structure array can be created to record the username, login date, and time of each user login. This structure array for recording user login information is stored in a specified location in flash memory and will not be lost when power is off. A creation command is used to read the information recorded in this structure array for recording user login information. Management users can read the structure data stored in the flash memory through commands, and obtain the information recorded in the structure array for recording user login information through software parsing.

[0064] The firmware boot method provided in this embodiment obtains user information input by the user and determines whether the user information input by the user matches the user information pre-stored in a structure array. If they match, the user type corresponding to the user information is determined based on the pre-stored correspondence between user information and user type. Then, the firmware boot process corresponding to the user type is adopted to boot the firmware. In other words, in this embodiment, a user information comparison and user type determination step is added to the firmware boot process. When the user information input by the user matches the pre-stored user information, the user type of the user is determined, and the firmware boot process corresponding to the user type is adopted to boot the firmware. This allows users of different user types to have different device usage permissions, supports multi-user mode, and thus improves computer security and protects computer data security.

[0065] Example 2

[0066] Figure 4 The flowchart of the firmware boot method provided in Embodiment 2 of this application is as follows: Figure 4 As shown, based on the above embodiment one, in order to further illustrate the firmware boot method of this application, the firmware boot method provided in this embodiment includes the following steps:

[0067] In step S410, user information input by the user is obtained.

[0068] In step S420, it is determined whether the user information input by the user matches the user information pre-stored in the structure array; if they match, step S430 is executed, otherwise step S450 is executed.

[0069] In step S430, the time of the user's input information and the username in the user information are recorded.

[0070] In step S440, based on the pre-stored correspondence between the user information and the user type, the user type corresponding to the user information is determined; firmware startup is performed using a firmware startup process corresponding to the user type, wherein different user types correspond to different firmware startup processes.

[0071] In step S450, the number of iterations n is incremented by 1, where the initial value of n can be 0.

[0072] In step S460, it is determined whether the number of attempts n is greater than or equal to a preset value. If n is less than the preset value, step S470 is executed. If n is greater than or equal to the preset value, step S490 is executed. In step S490, an infinite loop is entered.

[0073] In this embodiment, the firmware boot device can record the number of times the user information entered by the user does not match the user information stored in the structure array, i.e., the number n mentioned above; if the number of mismatches reaches a preset value, such as 3 times, then the firmware boot will stop and enter an infinite loop.

[0074] In step S470, a prompt message is output, which prompts the user to re-enter user information.

[0075] In this embodiment, if the user information entered by the user does not match the user information pre-stored in the structure array, the firmware startup device can output a prompt message to prompt the user to re-enter the user information. For example, the prompt message can be output by displaying text on the screen, such as "User information error, please re-enter," so that the user can re-enter the user information according to the prompt message.

[0076] Step S480: Detect whether the user has re-entered user information. If the user has re-entered user information, return to step S410; otherwise, return to step S470.

[0077] In this embodiment, the firmware boot device can detect whether the user has re-entered user information. If the user re-enters user information, the device can again execute the steps of obtaining the user-entered user information and determining whether the user-entered user information matches the user information pre-stored in the structure array.

[0078] Furthermore, in one example, after the firmware boot device stops firmware booting and enters an infinite loop, an error message signal can also be output. Specifically, the error message signal can be continuously output, and the error message signal can be an audible signal, such as a "beep beep beep" sound.

[0079] The firmware startup method provided in this embodiment can record the number of times the user information entered by the user does not match the user information stored in the pre-stored structure array. When the number of mismatches reaches a preset value, it enters an infinite loop and outputs a prompt signal, thereby further improving the security of the computer.

[0080] Example 3

[0081] Figure 5 This is a schematic diagram of the firmware boot device provided in the embodiments of this application, as shown below. Figure 5 As shown, the firmware boot device provided in this embodiment includes: an acquisition module 61, a determination module 62, and a boot module 63. The acquisition module 61 is used to acquire user information input by the user and determine whether the user information input by the user matches user information pre-stored in a structure array. The determination module 62 is used to determine the user type corresponding to the user information based on the pre-stored correspondence between the user information and user types if a match is found. The boot module 63 is used to perform firmware boot using a firmware boot process corresponding to the user type, wherein different user types correspond to different firmware boot processes.

[0082] The firmware boot device provided in this embodiment acquires user information input by the user and determines whether the user information input by the user matches the user information pre-stored in a structure array. If they match, the user type corresponding to the user information is determined based on the pre-stored correspondence between user information and user type. Then, a firmware boot process corresponding to the user type is used to boot the firmware. In other words, in this embodiment, a user information comparison and user type determination step is added to the firmware boot process. When the user information input by the user matches the pre-stored user information, the user type of the user is determined, and a firmware boot process corresponding to the user type is used to boot the firmware. This allows users of different user types to have different device usage permissions, thereby improving computer security and ensuring computer data security.

[0083] In an optional implementation, the user type includes a management type and a normal type. The startup module 63 is further configured to initialize the first group of device controllers and devices and obtain a command array containing a first set of commands when the user type is a management type, thereby enabling firmware startup. The first group of device controllers and devices includes device controllers and devices with external device interaction capabilities, and the first set of commands includes commands for modifying user information and device attributes. When the user type is a normal type, the module initializes the second group of device controllers and devices and obtains a command array containing a second set of commands, thereby enabling firmware startup. The second group of device controllers and devices does not include device controllers and devices with external device interaction capabilities, and the second set of commands does not include commands for modifying user information and device attributes.

[0084] In an optional embodiment, the firmware boot device further includes an output module and a detection module. The output module outputs a prompt message when the user-inputted information does not match the user information pre-stored in a structure array, prompting the user to re-enter the user information. The detection module detects whether the user has re-entered the user information. If re-entry is detected, the steps of obtaining the user-inputted information and determining whether it matches the pre-stored user information in the structure array, as well as subsequent steps, are executed again.

[0085] In an optional embodiment, the firmware boot device further includes a recording module and a stopping module. The recording module records the number of times the user-inputted information does not match the user information pre-stored in a structure array. The stopping module stops firmware boot and enters an infinite loop if the number of mismatches reaches a preset value.

[0086] In an optional embodiment, the output module is further configured to output an error message signal after stopping firmware startup and entering an infinite loop.

[0087] In an optional embodiment, the firmware boot device further includes a creation module and a storage module. The creation module creates a structure array for recording user login information. The storage module acquires the time the user inputs user information and the username, and stores them in the structure array for recording user login information.

[0088] In an optional embodiment, the storage module is further configured to store an array of structures used to record user login information into flash memory.

[0089] It should be noted that the technical solution and effects of the firmware boot device provided in this embodiment can be found in the relevant content of the foregoing method embodiments, and will not be repeated here.

[0090] Example 4

[0091] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application, such as... Figure 6 As shown, this application also provides an electronic device 700, including: a memory 701 and a processor 702.

[0092] Memory 701 is used to store programs. Specifically, the program may include program code, which includes computer-executable instructions. Memory 701 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0093] The processor 702 is used to execute the program stored in the memory 701.

[0094] The computer program is stored in memory 701 and configured to be executed by processor 702 to implement the firmware boot method provided in any embodiment of this application. Related descriptions can be understood by referring to the relevant descriptions and effects corresponding to the steps in the accompanying drawings, and will not be elaborated upon here.

[0095] In this embodiment, the memory 701 and the processor 702 are connected via a bus. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0096] Example 5

[0097] This application also provides a computer-readable storage medium storing a computer program thereon, which is executed by a processor to implement the firmware boot method provided in any embodiment of this application.

[0098] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0099] The modules described as separate components may or may not be physically separate. Similarly, the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0100] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated module can be implemented in hardware or in a combination of hardware and software functional modules.

[0101] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to the processor or controller of a general-purpose computer, special-purpose computer, or other programmable firmware boot device, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on the machine, partially on the machine, or as a standalone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0102] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0103] Furthermore, although the operations are described in a specific order, this should be understood as requiring that such operations be performed in the specific order shown or in sequential order, or requiring that all illustrated operations be performed to achieve the desired result. In certain environments, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this application. Certain features described in the context of individual embodiments may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented individually or in any suitable sub-combination in multiple implementations.

[0104] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0105] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A firmware boot method, characterized in that, include: Obtain user information input by the user, and determine whether the user information input by the user matches the user information pre-stored in the structure array; If a match is found, the user type corresponding to the user information is determined based on the pre-stored correspondence between the user information and the user type. The user type is either a management type or a normal type. Firmware boot is performed using a firmware boot process corresponding to the user type, wherein different user types correspond to different firmware boot processes; The step of booting the firmware using a firmware boot process corresponding to the user type includes: If the user type is management type, the first group of device controllers and devices are initialized, and a command array containing the first group of commands is obtained to realize firmware startup. The first group of device controllers and devices includes device controllers and devices with the function of interacting with external devices, and the first group of commands includes commands for modifying user information and device attributes. If the user type is a normal type, the second group of device controllers and devices are initialized, and a command array containing the second group of commands is obtained to realize firmware startup. The second group of device controllers and devices does not include device controllers and devices with the function of interacting with external devices, and the second group of commands does not include commands for modifying user information and device attributes.

2. The method according to claim 1, characterized in that, After determining whether the user information input by the user matches the user information pre-stored in the structure array, the method further includes: If the information does not match, a prompt message will be output, which will prompt the user to re-enter the user information. The system detects whether the user has re-entered user information. If the user has re-entered user information, the system executes the steps of obtaining the user's input information and determining whether the user's input information matches the user information pre-stored in the structure array, as well as subsequent steps.

3. The method according to claim 2, characterized in that, When the user information input by the user does not match the user information pre-stored in the structure array, the method further includes: Record the number of times the user information input by the user does not match the user information pre-stored in the structure array; If the number of mismatches reaches a preset value, the firmware startup will stop and the system will enter an infinite loop.

4. The method according to claim 3, characterized in that, After stopping the firmware startup and entering an infinite loop, the method also includes: outputting an error message signal.

5. The method according to claim 1, characterized in that, The user information input by the user includes a username; when the user information input by the user matches the user information pre-stored in a structure array, it also includes: Create a structure array to record user login information; The time when the user inputs user information and the username are obtained and stored in the structure array used to record user login information.

6. The method according to claim 5, characterized in that, Also includes: The array of structures used to record user login information is stored in flash memory.

7. A firmware boot device, characterized in that, include: The acquisition module is used to acquire user information input by the user and determine whether the user information input by the user matches the user information pre-stored in the structure array; The determination module is used to determine the user type corresponding to the user information based on the pre-stored correspondence between the user information and the user type if a match is found. The user type is either a management type or a normal type. The startup module is used to initialize the first group of device controllers and devices and obtain a command array containing the first group of commands if the user type is management type, so as to realize firmware startup. The first group of device controllers and devices includes device controllers and devices with the function of interacting with external devices, and the first group of commands includes commands for modifying user information and device attributes. If the user type is a normal type, the second group of device controllers and devices are initialized, and a command array containing the second group of commands is obtained to enable firmware startup. The second group of device controllers and devices does not include device controllers and devices with the function of interacting with external devices, and the second group of commands does not include commands for modifying user information and device attributes.

8. An electronic device, characterized in that, include: Memory and processor; The memory is used to store the executable instructions of the processor; The processor is used to invoke program instructions in the memory to execute the firmware boot method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the firmware boot method as described in any one of claims 1-6.

Images