Electronic device including controller for system startup and method of operating same
By comparing the first firmware and the second firmware in an electronic device to enable the first controller, the problem of the electronic device not being able to recognize and verify the integrity of the firmware and BIOS is solved, ensuring stability at startup of the system and providing Configurations of different security levels.
Patent Information
- Application Number
- CN202380029410.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-25
- Filing Date
- 2023-03-15
- Publication Date
- 2024-11-15
AI Technical Summary
Electronic devices cannot recognize and verify the integrity of the firmware and BIOS stored in memory before the system starts up, resulting in problems that may not operate properly.
An electronic device is designed, including a first controller, a first memory, a second memory and a second controller. The second controller compares the first firmware and the second firmware when the electronic device is powered on, and turns on the first firmware based on the comparison result. A controller to ensure the integrity of firmware and BIOS when the system is started.
Implements the identification and verification of firmware and BIOS integrity before system startup, prevent system problems due to damage or manipulation, and provides different levels of security to configure according to the purpose of use.
Smart Images

Figure CN118974700A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to an electronic device including a controller for system booting, and a method of booting a system by using an additional controller included in the electronic device. Background Art
[0002] An electronic device may include a central processing unit (CPU), a memory, and a system for input / output. The memory of an electronic device may store various data for performing the functions of the electronic device. For example, the memory may store a basic input / output system (BIOS). The BIOS may include software for controlling and testing the electronic device input / output system. For example, the BIOS may include a program for performing a test (verification) process to identify whether the electronic device input / output system operates correctly when power is supplied to the computer.
[0003] When power is supplied, the electronic device may perform a startup operation. For example, a system embedded controller (EC) included in the electronic device may detect the input of a startup command and control a central processing unit (CPU) to perform a startup operation. When the startup operation is performed, the electronic device may perform a test operation of the electronic device by using a BIOS stored in a memory. For example, the CPU may load the BIOS into the CPU and execute the BIOS to perform the startup operation. When the startup operation is performed, the user of the electronic device may use the electronic device at an appropriate level (e.g., a window level).
[0004] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above information might be applicable as prior art with respect to the present disclosure. Summary of the invention
[0005] [Technical issues]
[0006] An electronic device may store firmware for the operation of various controllers (e.g., system embedded controllers) included in the electronic device in a memory. In addition, the electronic device may store a BIOS for controlling a basic input / output system of the electronic device in a memory. However, due to the process of using the electronic device or for specific reasons, the firmware and BIOS stored in the memory may be manipulated and / or damaged. When the electronic device performs various functions of the electronic device by using the damaged firmware and BIOS, the problem that the electronic device cannot operate normally may occur. In addition, the electronic device cannot recognize the manipulation and / or damage of the firmware and BIOS before the system is started.
[0007] Furthermore, to solve the above-mentioned problems, simply merging an existing controller with a controller configured to verify the integrity of firmware and / or BIOS stored in a memory may cause system efficiency to deteriorate due to excessive firmware for the operation of the merging controller.
[0008] An aspect of the present disclosure is to solve at least the above problems and / or disadvantages and provide at least the advantages described below. Therefore, one aspect of the present disclosure is to provide an electronic device that can verify firmware and BIOS for a controller stored in a memory before a system of the electronic device is started.
[0009] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.
[0010] [Technical solution]
[0011] According to one aspect of the present disclosure, an electronic device is provided. The electronic device includes a first controller; a first memory configured to: store a first basic input output system (BIOS) and a first firmware for controlling the first controller, and functionally connected to the first controller; a second memory configured to store a second firmware corresponding to the first firmware and a second BIOS corresponding to the first BIOS; and a second controller functionally connected to the first memory, the second memory and the first controller, wherein the second controller is configured to compare the first firmware and the second firmware during power-on when the electronic device is powered on, and to start the first controller based on at least the result of the comparison, and wherein the first controller is configured to respond to being turned on by the second controller, and the system for controlling the electronic device is started.
[0012] According to another aspect of the present disclosure, a method for operating an electronic device is provided, the electronic device comprising a first memory, a second memory, a first controller, and a second controller. The method comprises: comparing, by the second controller, a first firmware stored in the first memory and configured to control the first controller with a second firmware stored in the second memory and corresponding to the first firmware; based at least on the result of the comparison, turning on the first controller by the second controller; and in response to the first controller being turned on by the second controller, a system controlling the electronic device by the first controller is booted.
[0013] [Beneficial Effects of the Invention]
[0014] The electronic device according to various embodiments disclosed in this document can identify the manipulation and / or destruction of the firmware and / or BIOS stored in the memory and configured to control the controller before the system starts. For example, the electronic device can protect the integrity by verifying the firmware stored in the memory and configured to control the system embedded controller before the system starts. In addition, for example, the electronic device can ensure the integrity by verifying the BIOS stored in the memory before the system starts. Therefore, the electronic device can prevent problems caused by the damage of the firmware and / or BIOS after the system starts in advance.
[0015] Furthermore, according to various embodiments of the present disclosure, the electronic device may identify firmware and / or BIOS for controlling a system embedded controller before booting the system, and reconstruct the firmware and / or BIOS when the firmware and / or BIOS are manipulated or damaged.
[0016] Furthermore, according to various embodiments, the electronic device may provide different security levels according to the purpose of use of the electronic device (eg, business to business (B2B), business to consumer (B2C)).
[0017] In addition, various effects directly or indirectly recognized by this file can be provided.
[0018] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:
[0020] Figure 1 is a block diagram of an electronic device according to an embodiment of the present disclosure;
[0021] Figure 2 The figure illustrates the connection relationship between the elements of the electronic device according to the embodiment of the present disclosure;
[0022] Figure 3 is a flowchart illustrating a firmware verification and recovery operation of an electronic device according to an embodiment of the present disclosure;
[0023] Figure 4 is a flowchart illustrating a BIOS verification and recovery operation of an electronic device according to an embodiment of the present disclosure;
[0024] Figure 5 is a flowchart illustrating a firmware verification operation of an electronic device according to an embodiment of the present disclosure;
[0025] Figure 6 is a flowchart illustrating a system startup operation of an electronic device according to power application according to an embodiment of the present disclosure;
[0026] Figure 7 is a flowchart illustrating a system startup operation of an electronic device according to an embodiment of the present disclosure; and
[0027] Figure 8 An electronic device in a network environment according to an embodiment of the present disclosure is illustrated.
[0028] Throughout the drawings, it should be noted that like reference numbers are used to depict the same or similar elements, features, and structures. DETAILED DESCRIPTION
[0029] Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that the various embodiments of the present disclosure are not intended to limit the present disclosure to the specified embodiments, but include various modifications, equivalents and / or substitutions thereof.
[0030] Figure 1 is a block diagram of an electronic device according to an embodiment of the present disclosure.
[0031] Reference Figure 1 , the electronic device 100 may include a first controller 110, a second controller 120, a first memory 130, a second memory 140 and / or a central processing unit (CPU) 150. The above-listed elements may be operably connected or electrically connected to each other. As an example, the following may be modified, deleted or added: Figure 1 Some components of the electronic device 100 are shown. According to an embodiment of the present disclosure, in addition to Figure 1 In addition to the elements shown, other common elements may also be included.
[0032] The electronic device 100 may include a CPU 150 and an input / output device (not shown), and may be various types of devices. For example, the electronic device 100 may include a computer device, a portable multimedia device, a notebook computer, a laptop computer, a portable communication device (e.g., a smart phone), or a home appliance. The electronic device 100 according to the embodiment of this document is not limited to the above devices.
[0033] The first controller 110 may be a controller configured to perform system management of the electronic device 100 and may include a system embedded controller. The first controller 110 may control an operation for system startup of the electronic device 100. For example, the first controller 110 may load a program stored in the first memory 130 and perform an operation for system startup.
[0034] The first controller 110 may be connected to the first memory 130, the CPU 150, and the second controller 120. The first controller 110 may control the CPU 150 by executing instructions stored in the first memory 130. For example, the first controller 110 may acquire a boot request and send a system boot command to the CPU 150 in response to the boot request.
[0035] The second controller 120 may be a controller different from the first controller 110, and may control an authentication operation of the electronic device 100 during a power-on period in which the electronic device 100 is powered on. The second controller 120 may be connected to the first memory 130, the second memory 140, and the first controller 110. The second controller 120 may identify whether instructions stored in the first memory 130 and the second memory 140 are manipulated and / or damaged, and may turn on or off the first controller 110 for starting a system of the electronic device 100.
[0036] The first memory 130 and the second memory 140 may store various types of data. According to an embodiment, the first memory 130 and the second memory 140 may be configured by various types of memories. For example, the first memory 130 and the second memory 140 may be configured by a read-only memory (ROM) (e.g., a single program launcher ROM (SPI ROM)). However, it is not limited to the above example, and the first memory 130 and the second memory 140 may be configured by one of various non-volatile memories.
[0037] The first memory 130 may store a first basic input output system (BIOS). The first BIOS may include a program configured to be automatically executed when the electronic device 100 is turned on, the program being used to check the state of the electronic device 100, perform tasks for system initialization, and identify which peripheral devices are connected to the electronic device 100 during the initialization task.
[0038] The first memory 130 may store first firmware including a program for controlling the first controller 110. The first controller 110 may load the first firmware and perform various operations based on at least the first firmware.
[0039] The second memory 140 may store data for restoring the first memory 130. For example, the second memory may store backup (or restoration) data related to the data stored in the first memory 130. In another example, the second memory 140 may store a second BIOS corresponding to the first BIOS. The second BIOS may include a program configured to be automatically executed when the electronic device 100 is turned on, the program for checking the state of the electronic device 100, performing tasks for system initialization, and identifying which peripheral devices are connected to the electronic device 100 during the initialization task.
[0040] The first BIOS that is not manipulated and the second BIOS may be the same. The second memory 140 may store a second firmware corresponding to the first firmware including a program for controlling the first controller 110. The first firmware that is not manipulated and / or damaged may be the same as the second firmware. The second memory 140 may store a third firmware (not shown) including a program for controlling the second controller 120. The second controller 120 may load the third firmware and perform various operations based on at least the third firmware.
[0041] According to an embodiment of the present disclosure, the CPU 150 may be represented as an application processor according to the form of the electronic device 100. However, the CPU 150 is not limited to the above example, and the CPU 150 may be represented as a main processor.
[0042] According to an embodiment of the present disclosure, the electronic device 100 may include a main processor (e.g., a central processing unit or an application processor) or an auxiliary processor (e.g., a graphics processing unit, a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor) that can operate independently of the main processor or together with the main processor.
[0043] The CPU 150 may upload the operating system stored in the first memory 130 to a memory (not shown) included in the CPU 150 to start the operating system. In addition, the CPU 150 may execute the first BIOS stored in the first memory 130 to normally start the system of the electronic device 100. The CPU 150 may be electrically connected or operably connected to various elements included in the electronic device 100. In addition, the CPU 150 may perform calculations or data processing related to the control and / or communication of at least one other element of the electronic device 100 by using instructions stored in at least one memory of the electronic device 100. The at least one memory may store instructions that, when executed, cause the CPU 150 to process data of the electronic device 100 or control elements to perform operations of the electronic device 100.
[0044] During the power-on period when the electronic device 100 is powered on, the second controller 120 may verify whether the data stored in the first memory 130 and the second memory 140 are manipulated and / or damaged. For example, during the power-on period when the electronic device 100 is powered on, the second controller 120 may compare the first firmware for controlling the first controller 110 with the second firmware corresponding to the first firmware. The second controller 120 may be configured to load at least a portion of the first firmware and the second firmware from the first memory 130 and the second memory 140, respectively, to compare the first firmware and the second firmware. The second controller 120 may compare the loaded first firmware and the second firmware to verify the first firmware.
[0045] During a power-on period in which the electronic device is powered on, the second controller 120 may transmit a first control signal including a standby signal to the first controller in order to ensure the right to control the electronic device.
[0046] The second controller 120 may turn on the first controller 110 based at least on the result of the comparison. For example, when the first firmware and the second firmware are identical according to the comparison result, the second controller 120 may determine that the first firmware is not manipulated and / or damaged, and turn on the first controller 110. For example, the second controller 120 may send a second control signal including a turn-on signal to the first controller 110.
[0047] In response to the first controller 110 being turned on, the first controller may load the first firmware stored in the first memory 130. The first controller 110 may perform an operation by loading the first firmware into a first buffer memory included in the first controller 110 and executing the loaded first firmware.
[0048] The first controller 110 may control the electronic device 100 system to start up in response to being turned on by the second controller 120. For example, the first controller 110 may obtain a start-up request related to the system start-up of the electronic device 100. In addition, the first controller 110 may send a system start-up command to the CPU 150 based on the obtained start-up request.
[0049] Based on the received system boot command, the CPU 150 may perform a system boot operation by executing the first BIOS stored in the first memory 130. For example, the CPU 150 may load the first BIOS into a third buffer memory (not shown) included in the CPU 150 and execute the loaded first BIOS to boot the system.
[0050] The second controller 120 may verify the first firmware before booting the system, and may verify the first BIOS to prevent problems caused by program manipulation during booting the system.
[0051] Figure 2A connection relationship 200 between elements of an electronic device according to an embodiment of the present disclosure is illustrated.
[0052] Reference Figure 2 , which shows the connection relationship between the elements of the electronic device 100. The electronic device 100 may include a first controller 110, a second controller 120, a first memory 130, a second memory 140, a central processing unit 150 and a trusted platform module (TPM) 160, and / or a multiplexer 170 configured to perform connections between the elements. According to an embodiment of the present disclosure, the above elements may be operably connected or electrically connected to each other. As an example, the above elements may be modified, deleted or added. Figure 2 Some components of the electronic device 100 are shown. According to an embodiment of the present disclosure, in addition to Figure 2 In addition to the components shown, other common components may also be included. The components included in the electronic device 100 may be directly or indirectly connected by various methods, not limited to Figure 2 The connection relationship 200 shown in FIG. Figure 1 The content described is the same as the content.
[0053] The electronic device 100 may include a first controller 110, a second controller 120, a first memory 130, a second memory 140, a central processing unit 150, a trusted platform module (TPM) 160, and / or a multiplexer 170 configured to perform connections between elements. The electronic device 100 is not limited to Figure 2 The example shown in , and may include multiple multiplexers for connection relationships between elements.
[0054] The first memory 130 may store a first firmware 131 including a program for controlling the first controller 110, and a first BIOS 133. The second memory 140 may store a second firmware 141 corresponding to the first firmware 131 and used to restore (or back up) data stored in the first memory 130, and a second BIOS 143 corresponding to the first BIOS 133. When the first memory 130 is not manipulated or damaged, the first firmware 131 and the second firmware 141 may be the same, and the first BIOS 133 and the second BIOS 143 may be the same. The second memory 140 may store a third firmware (not shown) including a program for controlling the second controller 120.
[0055] Each of the first controller 110, the second controller 120 and / or the CPU 150 may include a buffer memory for temporarily storing data when performing an operation. For example, the first controller 110 may include a first buffer memory 111, the second controller 120 may include a second buffer memory 121, and / or the CPU 150 may include a third buffer memory (not shown).
[0056] The TPM 160 is a module for identifying the system security of the electronic device 100, and can store security keys. When the operating system is uploaded to the memory of the CPU 150 according to the system startup of the electronic device 100, the TPM 160 can perform operations related to security. For example, when the startup of the system is performed, the electronic device 100 can verify the integrity of the electronic device 100 by using the security key stored in the second controller 120, the security key stored in the CPU 150, and the security key included in the TPM 160. According to various embodiments of the present disclosure, the TPM 160 can be used to perform various operations for maintaining the security of the electronic device 100.
[0057] The first controller 110 may be connected to the second controller 120 , the first memory 130 , and the CPU 150 directly or by using the multiplexer 170 .
[0058] The first controller 110 may be connected to the second controller 120 to send or receive various control signals. For example, when the first controller 110 obtains a system boot request of the electronic device 100 in the turned-on state, the first controller 110 may send the boot request to the second controller 120. The second controller 120 may perform an operation of verifying the first BIOS based on the boot request obtained from the first controller 110. Figures 4 to 7 An operation of verifying the first BIOS by the first controller 110 is described in detail.
[0059] The first controller 110 may receive a control signal including various signals from the second controller 120. For example, the first controller 110 may be connected to the second controller 120 to send a start signal, a standby signal and / or a start signal. For example, during the power-on period at power-on, the second controller 120 may send a first control signal including a standby signal to the first controller 110 to ensure the right to control the electronic device 100. Even if powered on, the first controller 110 may not operate based on the first control signal. In addition, when the verification operation of the first firmware to be executed by the first controller 110 is completed, the second controller 120 may send a second control signal including a start signal to the first controller 110. The first controller 110 may be turned on based on the second control signal. The second controller 120 may perform a verification operation on the first BIOS in response to a start request sent from the first controller 110, and may send a start signal to the first controller 110 based at least on the result of the verification operation.
[0060] The first controller 110 may include a first buffer memory 111 to store and use various data. For example, the first controller 110 may load various programs including instructions from the first memory 130 into the first buffer memory 111. For example, when turned on, the first controller 110 may load the first firmware 131 including a program for controlling the first controller 110 stored in the first memory 130 into the first buffer memory 111. When turned on, the first controller 110 may operate by executing the first firmware 131 loaded into the first buffer memory 111.
[0061] The second controller 120 may be directly or indirectly connected to the second memory 140, the first memory 130, the first controller 110, and / or the TPM 160. For example, the second controller 120 may be indirectly connected to the first memory 130 and / or the first controller 110 through the multiplexer 170. According to an embodiment of the present disclosure, the second controller 120, the second memory 140, and / or the multiplexer 170 may be configured as a first module 201. According to another embodiment of the present disclosure, the second controller 120 and the second memory 140 may be configured as a single chip. Therefore, when the connection between the elements of the electronic device 100 is changed due to a change in the security level according to the purpose of use of the electronic device 100, the electronic device 100 may be configured to omit the first module 201. For example, when the purpose of use of the electronic device 100 corresponds to B2C instead of B2B, the electronic device 100 may be configured not to include the first module 201 and to omit the use of the first module 201 to perform operations.
[0062] During a power-on period when the electronic device 100 is powered on, the second controller 120 may perform a verification operation on the first firmware 131 stored in the first memory 130. For example, the second controller 120 is connected to the first memory 130 and the second memory 140, and may load at least a portion of the first firmware 131 and the second firmware 141 from the first memory 130 and the second memory 140, respectively. The second controller 120 may temporarily store the loaded first firmware 131 and the second firmware 141 in the second buffer memory 121 to verify the first firmware 131, and may compare the first firmware 131 and the second firmware 141 to perform a verification operation on the first firmware 131.
[0063] When a boot request is transferred from the first controller 110, the second controller 120 may perform a verification operation on the first BIOS 133 stored in the first memory 130. For example, the second controller 120 is connected to the first memory 130 and the second memory 140, and may load at least a portion of the first BIOS 133 and the second BIOS 143 from the first memory 130 and the second memory 140, respectively. The second controller 120 may temporarily store the loaded first BIOS 133 and the second BIOS 143 in the second buffer memory 121 to verify the first BIOS 133, and may compare the first BIOS 133 and the second BIOS 143 to perform a verification operation on the first BIOS 133.
[0064] The second memory 140 may include a third firmware (not shown) for controlling the second controller 120. The second controller 120 may operate by loading the third firmware into the second buffer memory 121 using a connection with the second memory 140 and executing the third firmware.
[0065] The first controller 110 may be indirectly connected to the CPU 150 through the multiplexer 170. However, when the connection between the elements of the electronic device 100 is changed according to the purpose of use of the electronic device 100, the first controller 110 may be directly connected to the CPU 150. The first controller 110 may be connected to the CPU 150 to send a system startup command. The first controller 110 may send a startup command to the CPU 150 in response to acquiring a system startup request. The CPU 150 may execute the system startup command in response to the acquired startup command.
[0066] The CPU 150 may be directly or indirectly connected to the TPM 160, the first memory 130, and the first controller 110. In response to a boot command acquired from the first controller 110, the CPU 150 may upload the first BIOS 133 stored in the first memory 130 to a third buffer memory (not shown) included in the CPU 150. The CPU 150 may perform a system boot operation by executing the loaded first BIOS 133.
[0067] Figure 3 3 is a flowchart 300 for explaining a firmware verification and recovery operation of an electronic device according to an embodiment of the present disclosure.
[0068] Reference Figure 3 , the electronic device 100 may include a second memory 140, a first memory 130, a second controller 120, a first controller 110 and / or a central processing unit 150. These elements may represent similar Figure 1 and Figure 2 Therefore, the configuration of the electronic device 100 described in the reference may be omitted. Figure 1 and Figure 2 Describes the same or similar content.
[0069] In operation 301, during a power-on period when the electronic device 100 is powered on, the second controller 120 may send a first control signal to the first controller 110. The first control signal may include a standby command signal by which the second controller 120 can control the electronic device 100 even during the power-on period. In operation 302, in response to the first control signal, the first controller 110 may maintain a standby state without being turned on.
[0070] In operation 303, the second controller 120 may load the first firmware (e.g., the first firmware 131) stored in the first memory 130, and in operation 305, the second controller 120 may load the second firmware (e.g., the second firmware 141) stored in the second memory 140. The second controller 120 may perform operations 303 and 305 to verify the first firmware before the first controller 110 is turned on.
[0071] In operation 307, the second controller 120 may compare the first firmware and the second firmware. For example, since the second firmware is identical to the first firmware, the second controller 120 may verify that the first firmware is not manipulated or damaged. When the first firmware and the second firmware are not identical as a result of the comparison, the second controller 120 may determine that the first firmware is manipulated or damaged.
[0072] When the first firmware and the second firmware are not identical, the second controller 120 may rewrite the first firmware stored in the first memory 130 with the second firmware in operation 309. For example, the second controller 120 may rewrite the first firmware with the second firmware that has not been manipulated. In operation 307, in response to the rewriting, the second controller 120 may verify the first firmware again by performing a comparison operation between the first firmware and the second firmware again.
[0073] When it is determined as a comparison result therebetween that the first and second firmware are identical, the second controller 120 may transmit a second control signal including a turn-on command to the first controller 110 in operation 311. Upon receiving the second control signal including the turn-on command, the first controller 110 may be turned on in operation 312.
[0074] When the first controller 110 is turned on by the second controller 120, the first controller may load the first firmware stored in the first memory 130 in operation 313. For example, the first controller 110 may copy an image of the first firmware to a first buffer memory (e.g., the first buffer memory 111) included in the first controller 110. According to an embodiment of the present disclosure, the first controller 110 may perform an operation by executing the loaded first firmware.
[0075] In operation 315 , the first controller 110 and the CPU 150 may perform an operation for booting a system of the electronic device 100 .
[0076] Figure 4 is a flow chart 400 illustrating BIOS verification and recovery operations of an electronic device according to an embodiment of the present disclosure.
[0077] Reference Figure 4 , the electronic device 100 may include a second memory 140, a first memory 130, a second controller 120, a first controller 110 and / or a central processing unit 150. These elements may represent similar Figure 1 and Figure 2 Therefore, the configuration of the electronic device 100 described in the reference is omitted. Figure 1 and Figure 2 The elements described are similar to the description of the elements.
[0078] When the electronic device 100 is in the terminated state and powered on, in operation 401, the first controller 110 may obtain a startup command of the electronic device. For example, the turned-on first controller 110 may obtain input related to system startup (e.g., startup request) (obtained from a user of the electronic device 100 through a physical key (e.g., power button) included in the electronic device 100). According to various embodiments of the present disclosure, the first controller 110 may obtain the startup request through the user or various methods including generating a preconfigured event.
[0079] In response to acquiring the start command, the first controller 110 may transfer the start command to the second controller 120 in operation 403. The first controller 110 may transfer the start command, and the second controller 120 may ensure the right to control the electronic device 100 after receiving the start command.
[0080] In response to acquiring the boot command, the second controller 120 may load the first BIOS (e.g., first BIOS 133) stored in the first memory 130 in operation 405, and may load the second BIOS (e.g., second BIOS 143) stored in the second memory 140 in operation 407. The second controller 120 may perform operations 405 and 407 to verify the first BIOS before the system of the electronic device 100 is booted.
[0081] In operation 409, the second controller 120 may compare the first BIOS and the second BIOS. For example, when the second BIOS and the first BIOS are identical, the second controller 120 may verify that the first BIOS is not manipulated or damaged. When the first BIOS and the second BIOS are not identical as a result of the comparison, the second controller 120 may determine that the first BIOS is manipulated or damaged.
[0082] When the first BIOS and the second BIOS are not identical, the second controller 120 may rewrite the first BIOS stored in the first memory 130 with the second BIOS in operation 411. For example, the second controller 120 may rewrite the first BIOS with the unmanipulated second BIOS. In operation 411, in response to the rewriting, the second controller 120 may re-verify the first BIOS by performing a comparison operation between the first BIOS and the second BIOS again.
[0083] When it is determined that the first BIOS and the second BIOS are identical as a result of comparing the first BIOS and the second BIOS, the second controller 120 may transmit a control signal including a boot command to the first controller 110 in operation 413 .
[0084] When receiving the control signal including the boot command, the first controller 110 may send a system boot command to the CPU 150 in operation 415 .
[0085] In response to receiving a system boot command from the first controller 110 , the CPU 150 may load the first BIOS stored in the first memory 130 in operation 417 .
[0086] The CPU 150 may load the first BIOS and execute the loaded first BIOS in operation 419 to perform a boot operation of the system.
[0087] According to an embodiment of the present disclosure, the electronic device 100 can identify whether the first BIOS and the first firmware used to control the first controller (e.g., a system embedded controller) are manipulated or damaged before starting the system, and, when the first BIOS and the first firmware are manipulated or damaged, the electronic device can restore the manipulated or damaged first BIOS and the first firmware to start the system.
[0088] Figure 5 5 is a flowchart 500 for describing a firmware verification operation of an electronic device according to an embodiment of the present disclosure.
[0089] Reference Figure 5 , in operation 501, during power-on when the electronic device 100 is powered on, the second controller 120 may compare the first firmware 131 and the second firmware 141. For example, the second controller 120 may compare the first firmware 131 stored in the first memory 130 and configured to control the first controller 110 and the second firmware 141 stored in the second memory 140 and corresponding to the first firmware 131. The second firmware 141 may include a backup firmware for the first firmware 131 for restoring the first firmware 131. The second controller 120 may compare the first firmware 131 and the second firmware 141 to determine whether the first firmware 131 has been manipulated and / or damaged.
[0090] In operation 503, the second controller 120 may turn on the first controller 110 based at least on the result of the comparison. For example, when the first firmware 131 for controlling the first controller 110 matches the second firmware 141, the second controller 120 may turn on the first controller 110. In order to turn on the first controller 110, the second controller 120 may send a control signal requesting turning on to the first controller 110.
[0091] In operation 505, the first controller 110 may control system startup of the electronic device 100 in response to being turned on by the second controller 120. For example, the first controller 110 may send a system startup command to the CPU 150 in response to being turned on. According to an embodiment, the CPU 150 may start the system by executing the first BIOS 133 based at least on the received system startup command.
[0092] Figure 6 600 is a flowchart for describing a system startup operation of an electronic device according to power application according to an embodiment of the present disclosure.
[0093] Reference Figure 6 In operation 601, the electronic device 100 may be powered on. For example, the electronic device 100 that has all power removed may recognize that power has been turned on. For example, the first controller 110 or the second controller 120 included in the electronic device 100 may recognize that the electronic device 100 is powered on.
[0094] In response to power being applied to the electronic device 100, the second controller 120 may control execution of functions of the electronic device 100. For example, in response to power being applied to the electronic device 100, the second controller 120 may send a control signal to the first controller 110, commanding the first controller 110 to standby.
[0095] In operation 603, the second controller 120 may compare the first firmware (e.g., the first firmware 131) and the second firmware (e.g., the second firmware 141). For example, the second controller 120 may load the first firmware 131 (e.g., the system embedded controller firmware (system EC FW)) for controlling the first controller 110 stored in the first memory 130. In addition, the second controller 120 may load the second firmware 141 corresponding to the first firmware 131. The second firmware 141 may include a backup firmware for the first firmware 131 for restoring the first firmware 131.
[0096] The second controller 120 may compare the loaded first firmware 131 and the second firmware 141. For example, the second controller 120 may compare the first firmware 131 and the second firmware 141 to determine whether the first firmware 131 has been manipulated and / or damaged. When the first firmware 131 has not been manipulated or damaged, the first firmware 131 may include the same code as the second firmware 141. However, when the first firmware 131 has been manipulated, the first firmware 131 may include a code different from the second firmware 141. The second controller 120 may verify the first firmware 131 by comparing the first firmware 131 and the second firmware 141.
[0097] In response to the first firmware 131 and the second firmware 141 being the same, the second controller 120 may turn on the first controller 110 in operation 605. For example, the second controller 120 may send a control signal for turning on to the first controller 110. The first controller 110, which has received the control signal from the second controller 120, may be turned on in response to the control signal. The turned-on first controller 110 may execute the first firmware 131 to perform operations related to system startup.
[0098] In response to the first firmware 131 and the second firmware 141 being different, the second controller 120 may restore the first firmware 131 by using the second firmware 141 in operation 607. For example, when the first firmware 131 and the second firmware 141 are different as a result of the comparison, the second controller 120 may recognize that the first firmware 131 has been manipulated. Therefore, the second controller 120 may rewrite the first firmware 131 with the second firmware 141 to restore the first firmware 131. According to an embodiment of the present disclosure, the second controller 120 may perform operation 605 in response to restoring the first firmware 131.
[0099] The second controller 120 may perform operation 607, and may verify the first firmware 131 and the second firmware 141 by performing another comparison. For example, the second controller 120 may rewrite the first firmware 131 with the second firmware 141, and may compare the first firmware 131 and the second firmware 141 again to identify whether the restoration of the first firmware 131 has been correctly performed. When the first firmware 131 and the second firmware 141 are identical at least based on the comparison result, the second controller 120 may perform operation 605.
[0100] The electronic device 100 may perform a verification operation on the first firmware 131 , which is firmware for controlling the operation of the first controller 110 , before the first controller 110 is turned on, thereby operating the first controller 110 in a state in which integrity of the first firmware 131 , which is firmware for controlling the operation of the first controller 110 , is verified.
[0101] In operation 609, the second controller 120 may compare the first BIOS 133 and the second BIOS 143. For example, the second controller 120 may load the first BIOS 133 stored in the first memory 130 and configured for basic operations of the system of the electronic device 100. In addition, the second controller 120 may load the second BIOS 143 corresponding to the first BIOS 133. According to an embodiment of the present disclosure, the second BIOS 143 may include a backup BIOS related to the first BIOS 133 for restoring the first BIOS 133.
[0102] The second controller 120 may compare the loaded first BIOS 133 and the second BIOS 143. For example, the second controller 120 may compare the first BIOS 133 and the second BIOS 143 to determine whether the first BIOS 133 is manipulated and / or damaged. When the first BIOS 133 is not manipulated, the first BIOS 133 may include the same code as the second BIOS 143. On the other hand, when the first BIOS 133 is manipulated, the first BIOS 133 may include a code different from the second BIOS 143. In an embodiment, the second controller 120 may verify the first BIOS 133 by comparing the first BIOS 133 and the second BIOS 143.
[0103] In response to obtaining a boot request command from the first controller 110, the second controller 120 may compare the first BIOS 133 and the second BIOS 143 in operation 609. For example, the turned-on first controller 110 may obtain input related to system startup (e.g., a boot request) (obtained from a user of the electronic device 100 through a physical key (e.g., a power button) included in the electronic device 100). The first controller 110 may obtain the boot request through a user or various methods including generating a preconfigured event. In response to obtaining the boot command, the first controller 110 may pass the boot command to the second controller 120. In addition, in response to obtaining the boot request, the first controller 110 may pass the right to control the execution of the function of the electronic device 100 to the second controller 120. Therefore, the second controller 120 may compare the first BIOS 133 and the second BIOS 143.
[0104] In response to the first BIOS 133 and the second BIOS 143 being the same, the first controller 110 may perform a system boot operation in operation 611. For example, when the first BIOS 133 and the second BIOS 143 are the same, in operation 611, the second controller 120 may transmit a signal related to performing a boot operation to the first controller 110. For example, the second controller 120 may compare the first BIOS 133 and the second BIOS 143, and may transmit a signal related to performing a boot operation (e.g., a verification completion signal for the first BIOS 133) to the first controller 110 based at least on a result of the comparison. The first controller 110 may control the electronic device 100 to boot the system based on the signal. For example, the first controller 110 may transmit a boot command to the CPU 150. According to an embodiment, the CPU 150, which has acquired the boot command from the first controller 110, may execute the first BIOS 133 to perform a boot operation of the system.
[0105] In response to the first BIOS 133 and the second BIOS 143 being different, the second controller 120 may restore the first BIOS 133 by using the second BIOS 143 in operation 613. For example, the second controller 120 may compare the first BIOS 133 and the second BIOS 143. In addition, when the first BIOS 133 and the second BIOS 143 are different, the first BIOS 133 may be recognized as being manipulated. Therefore, the second controller 120 may restore the first BIOS 133 by rewriting the first BIOS 133 with the second BIOS 143. In response to restoring the first BIOS 133, the second controller 120 may send a verification result of the first BIOS 133 to the first controller 110.
[0106] The second controller 120 may perform operation 613, and may verify the first BIOS 133 and the second BIOS 143 by performing another comparison. For example, the second controller 120 may rewrite the first BIOS 133 with the second BIOS 143, and may compare the first BIOS 133 and the second BIOS 143 again to identify whether the first BIOS 133 is properly restored. When the first BIOS 133 and the second BIOS 143 are identical at least based on the comparison result, the second controller 120 may transmit a signal related to performing a boot operation (e.g., a verification completion signal for the first BIOS 133) to the first controller 110. When the signal is sent to the first controller 110, the first controller 110 may have the right to control the execution of the function of the electronic device 100. In operation 611, the first controller 110, which has acquired the signal, may perform a system boot operation.
[0107] According to an embodiment of the present disclosure, a verification operation on the first BIOS 133 may be performed before the electronic device 100 performs a system startup operation, and thus the electronic device 100 may perform a system startup operation in a state where the integrity of the first BIOS 133 is verified before the system of the electronic device 100 is started.
[0108] Figure 7 700 is a flowchart for describing a system startup operation of an electronic device according to an embodiment of the present disclosure.
[0109] Reference Figure 7In operation 701, the first controller 110 may obtain a startup request for the electronic device 100. The electronic device 100 may be in a state where the user terminates the electronic device 100 without completely removing power from the electronic device 100. The electronic device 100 may obtain a startup request while the power supply to the electronic device is maintained and the electronic device is in a terminated state. For example, the first controller 110 may obtain a startup request for the electronic device. For example, the turned-on first controller 110 may obtain input related to system startup (e.g., startup request) (obtained from the user of the electronic device 100 through a physical key (e.g., a power button) included in the electronic device 100). The first controller 110 may obtain the startup request through the user or various methods including generating a preconfigured event.
[0110] In response to acquiring the startup request in operation 701, the first controller 110 may perform operation 609. For example, the first controller 110 may transfer the startup request to the second controller 120. In addition, the first controller 110 may transfer the right to control the execution of the function of the electronic device 100 to the second controller 120 in response to acquiring the startup request. The electronic device 100 may then perform operations 609 to 613.
[0111] According to an embodiment of the present disclosure, the electronic device 100 may perform operations 601 to 613 when power is removed and then applied. For example, when power is not removed and the electronic device 100 is in a terminated state, the electronic device 100 may perform operations 701 and operations 609 to 613. Therefore, compared with operation 609, operation 603 may be performed less frequently.
[0112] As described above, according to an embodiment of the present disclosure, an electronic device (eg, Figure 1 The electronic device 100 may include a first controller (eg, Figure 2 The first controller 110 is configured to store a first basic input and output system (BIOS) (eg, Figure 2 A first BIOS 133) and a first firmware for controlling the first controller (eg, Figure 2 The first firmware 131 of the first controller is functionally connected to the first memory (eg, Figure 2 The first memory 130 is configured to store the second firmware corresponding to the first firmware (eg, Figure 2 The second firmware 141) and the second BIOS corresponding to the first BIOS (eg, Figure 2 The second memory of the second BIOS 143 (for example, Figure 2 A second memory 140 of the first controller) and a second controller (e.g., Figure 2 The second controller 120 is configured to compare the first firmware and the second firmware during power-on when the electronic device is powered on, and to start the first controller based on at least a result of the comparison, and the first controller is configured to control the startup of the electronic device system in response to being turned on by the second controller.
[0113] The second controller may be configured to, in a case where the first firmware and the second firmware do not match as a result of the comparison, rewrite the first firmware with the second firmware, and compare and verify the first firmware and the second firmware.
[0114] The second controller may be configured to send a first control signal including a standby signal to the first controller during power-on for controlling the electronic device by the second controller.
[0115] The first controller may be configured to obtain a boot request for the electronic device, and in response to obtaining the boot request, send the boot request to the second controller, the second controller being configured to compare the first BIOS and the second BIOS in response to the sent boot request, and at least based on a result of the comparison, send a second control signal for starting the system to the first controller, and the first controller being configured to send a system boot command to a central processing unit (CPU) included in the electronic device based on the second control signal.
[0116] The second controller may be configured to rewrite the first BIOS with the second BIOS based on a comparison result that the first BIOS does not match the second BIOS, and to compare and verify the first BIOS with the second BIOS.
[0117] The CPU may be configured to execute the first BIOS according to the system startup command so as to perform system startup.
[0118] The second controller and the second memory may be configured as a single chip.
[0119] The first controller may include a first buffer memory, and be configured to load first firmware stored in the first memory into the first buffer memory in response to being turned on by the second controller, and operate by executing the loaded first firmware.
[0120] The second memory may be configured to store third firmware for controlling the second controller, and the second controller may include a second buffer memory and be configured to load the third firmware into the second buffer memory and operate by executing the loaded third firmware.
[0121] The CPU may include a third buffer memory, and be configured to load the first BIOS into the third buffer memory in response to a boot request of the system acquired from the first controller, and perform system boot by executing the loaded first BIOS.
[0122] The electronic device may further include a trusted platform module configured to store a security key for the electronic device, wherein the electronic device is configured to verify the integrity of the electronic device during startup of the execution system by using the security key, the security key stored in the CPU, and the security key stored in the second controller.
[0123] The boot request may include input related to system booting, which is obtained from a user of the electronic device through a physical key included in the electronic device.
[0124] As described above, according to an embodiment of the present disclosure, a method for operating a first memory (eg, Figure 2 A first memory 130), a second memory (eg, Figure 2 a second memory 140), a first controller (eg, Figure 2 110) and a second controller (eg, Figure 2 A method for an electronic device having a second controller 120) may include: comparing a first firmware stored in a first memory and configured to control the first controller and a second firmware stored in a second memory and corresponding to the first firmware, and, based at least on a result of the comparison, turning on the first controller by the second controller, and in response to the first controller being turned on by the second controller, a system for controlling the electronic device by the first controller is started.
[0125] The comparing of the first firmware and the second firmware may include, in response to a comparison result that the first firmware and the second firmware do not match, rewriting the first firmware with the second firmware, and comparing and verifying the first firmware and the second firmware.
[0126] The method may also include: obtaining, by the first controller, a startup request for the electronic device; in response to obtaining the startup request, sending, by the first controller, a startup request to the second controller; in response to the sent startup request, comparing, by the second controller, a first BIOS stored in a first memory and a second BIOS stored in a second memory; based at least on the comparison result, sending a signal for starting the system to the first controller; and based on the signal for starting the system, sending, by the first controller, a system startup command to a central processing unit (CPU) included in the electronic device.
[0127] The comparing of the first BIOS and the second BIOS may include, in response to a comparison result that the first BIOS and the second BIOS do not match, rewriting the first BIOS with the second BIOS, and comparing and verifying the first BIOS and the second BIOS.
[0128] The CPU may be configured to execute the first BIOS according to the system startup command so as to perform system startup.
[0129] The acquiring of the startup request may include acquiring, by the first controller, an input related to the startup system from a user of the electronic device through a physical key included in the electronic device.
[0130] The first controller and the second controller may include a first buffer memory and a second buffer memory, respectively, and the method may also include the first controller loading the first firmware into the first buffer memory and executing the loaded first firmware, and the second controller loading the third firmware stored in the second memory for executing the second controller into the second buffer memory and executing the third firmware.
[0131] The CPU may include a third buffer memory, and the method may further include loading, by the CPU, the first BIOS into the third buffer memory in response to a system boot command acquired from the first controller, and executing, by the CPU, the loaded first BIOS to perform system boot.
[0132] Figure 8 8 is a block diagram showing an electronic device 801 in a network environment 800 according to various embodiments of the present disclosure. Figure 8, the electronic device 801 in the network environment 800 may communicate with the electronic device 802 via the first network 898 (e.g., a short-range wireless communication network), or communicate with at least one of the electronic device 804 or the server 808 via the second network 899 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 801 may communicate with the electronic device 804 via the server 808. According to an embodiment, the electronic device 801 may include a processor 820, a memory 830, an input module 850, a sound output module 855, a display module 860, an audio module 870, a sensor module 876, an interface 877, a connection terminal 878, a haptic module 879, a camera module 880, a power management module 888, a battery 889, a communication module 890, a user identification module (SIM) 896, or an antenna module 897. In some embodiments, at least one of the above components (e.g., the connection terminal 878) may be omitted from the electronic device 801, or one or more other components may be added to the electronic device 801. In some embodiments, some of the above-described components (eg, sensor module 876, camera module 880, or antenna module 897) may be implemented as a single integrated component (eg, display module 860).
[0133] The processor 820 may run, for example, software (e.g., program 840) to control at least one other component (e.g., hardware component or software component) of the electronic device 801 connected to the processor 820, and may perform various data processing or calculations. According to one embodiment, as at least part of the data processing or calculation, the processor 820 may store a command or data received from another component (e.g., sensor module 876 or communication module 890) in a volatile memory 832, process the command or data stored in the volatile memory 832, and store the result data in a non-volatile memory 834. According to an embodiment, the processor 820 may include a main processor 821 (e.g., a central processing unit (CPU) or an application processor (AP)) or an auxiliary processor 823 (e.g., a graphics processing unit (GPU), a neural processing unit (NPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is independent of or combined with the main processor 821 in operation. For example, when the electronic device 801 includes a main processor 821 and an auxiliary processor 823, the auxiliary processor 823 may be adapted to consume less power than the main processor 821, or adapted to be dedicated to a specific function. The auxiliary processor 823 may be implemented as a separate part from the main processor 821, or as part of the main processor 821.
[0134] When the main processor 821 is in an inactive (e.g., sleep) state, the auxiliary processor 823 (rather than the main processor 821) may control at least some of the functions or states related to at least one component among the components of the electronic device 801 (e.g., display module 860, sensor module 876, or communication module 890), or when the main processor 821 is in an active state (e.g., running an application), the auxiliary processor 823 may control at least some of the functions or states related to at least one component among the components of the electronic device 801 (e.g., display module 860, sensor module 876, or communication module 890) together with the main processor 821. According to an embodiment, the auxiliary processor 823 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 880 or a communication module 890) that is functionally related to the auxiliary processor 823. According to an embodiment, the auxiliary processor 823 (e.g., a neural processing unit) may include a hardware structure dedicated to artificial intelligence model processing. The artificial intelligence model may be generated by machine learning. For example, such learning may be performed by the electronic device 801 where the artificial intelligence is executed or via a separate server (e.g., server 808). The learning algorithm may include, but is not limited to, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, for example. The artificial intelligence model may include multiple artificial neural network layers. The artificial neural network may be a deep neural network (DNN), a convolutional neural network (CNN), a recurrent neural network (RNN), a restricted Boltzmann machine (RBM), a deep belief network (DBN), a bidirectional recurrent deep neural network (BRDNN), or a deep Q network or a combination of two or more thereof, but is not limited thereto. Additionally or alternatively, the artificial intelligence model may include a software structure in addition to a hardware structure.
[0135] The memory 830 may store various data used by at least one component of the electronic device 801 (e.g., the processor 820 or the sensor module 876). The various data may include, for example, software (e.g., the program 840) and input data or output data for commands related thereto. The memory 830 may include a volatile memory 832 or a non-volatile memory 834.
[0136] The program 840 may be stored as software in the memory 830 , and may include, for example, an operating system (OS) 842 , middleware 844 , or an application 846 .
[0137] The input module 850 may receive commands or data to be used by other components (e.g., the processor 820) of the electronic device 801 from outside (e.g., a user) of the electronic device 801. The input module 850 may include, for example, a microphone, a mouse, a keyboard, a key (e.g., a button), or a digital pen (e.g., a stylus).
[0138] The sound output module 855 can output sound signals to the outside of the electronic device 801. The sound output module 855 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or playing records. The receiver can be used to receive incoming calls. Depending on the embodiment, the receiver can be implemented as a separate part from the speaker, or as part of the speaker.
[0139] The display module 860 may visually provide information to the outside (e.g., user) of the electronic device 801. The display device 860 may include, for example, a display, a holographic device, or a projector, and a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. According to an embodiment, the display module 860 may include a touch sensor adapted to detect a touch or a pressure sensor adapted to measure the strength of a force caused by a touch.
[0140] The audio module 870 can convert sound into an electrical signal, or vice versa. According to an embodiment, the audio module 870 can obtain sound via the input module 850, or output sound via the sound output module 855 or an earphone of an external electronic device (e.g., electronic device 802) directly (e.g., wired) or wirelessly connected to the electronic device 801.
[0141] The sensor module 876 may detect an operating state (e.g., power or temperature) of the electronic device 801 or an environmental state (e.g., a state of a user) outside the electronic device 801, and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 876 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illumination sensor.
[0142] The interface 877 may support one or more specific protocols to be used to connect the electronic device 801 directly (e.g., wired) or wirelessly to an external electronic device (e.g., the electronic device 802). According to an embodiment, the interface 877 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.
[0143] The connection end 878 may include a connector, wherein the electronic device 801 can be physically connected to an external electronic device (e.g., the electronic device 802) via the connector. According to an embodiment, the connection end 878 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).
[0144] The haptic module 879 may convert the electrical signal into mechanical stimulation (eg, vibration or motion) or electrical stimulation that can be recognized by the user via his sense of touch or kinesthetic sense. According to an embodiment, the haptic module 879 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.
[0145] The camera module 880 may capture a still image or a moving image. According to an embodiment, the camera module 880 may include one or more lenses, an image sensor, an image signal processor, or a flash.
[0146] The power management module 888 may manage power supply to the electronic device 801. According to an embodiment, the power management module 888 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).
[0147] The battery 889 may power at least one component of the electronic device 801. According to an embodiment, the battery 889 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.
[0148] The communication module 890 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 801 and an external electronic device (e.g., electronic device 802, electronic device 804, or server 808), and perform communication via the established communication channel. The communication module 890 may include one or more communication processors capable of operating independently from the processor 820 (e.g., an application processor (AP)) and supporting direct (e.g., wired) communication or wireless communication. According to an embodiment, the communication module 890 may include a wireless communication module 892 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 894 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 898 (e.g., a short-range communication network such as Bluetooth, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA)) or a second network 899 (e.g., a long-range communication network such as a traditional cellular network, a fifth generation (5G) network, a next-generation communication network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single chip), or these various types of communication modules can be implemented as multiple components separated from each other (e.g., multiple chips). The wireless communication module 892 can identify and authenticate the electronic device 801 in a communication network (such as the first network 898 or the second network 899) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 896.
[0149] The wireless communication module 892 can support 5G networks after the fourth generation (4G) network and next generation communication technologies (e.g., new radio (NR) access technology). NR access technology can support enhanced mobile broadband (eMBB), massive machine type communication (mMTC), or ultra-reliable low latency communication (URLLC). The wireless communication module 892 can support high frequency bands (e.g., millimeter wave (mmWave) bands) to achieve, for example, high data transmission rates. The wireless communication module 892 can support various technologies for ensuring performance on high frequency bands, such as, for example, beamforming, massive multiple input multiple output (massive MIMO), full dimensional MIMO (FD-MIMO), array antennas, analog beamforming, or massive antennas. The wireless communication module 892 can support various requirements specified in the electronic device 801, an external electronic device (e.g., electronic device 804), or a network system (e.g., a second network 899). According to an embodiment, the wireless communication module 892 may support a peak data rate for implementing eMBB (e.g., 20 Gbps or greater), loss coverage for implementing mMTC (e.g., 164 dB or less), or U-plane delay for implementing URLLC (e.g., 0.5 ms or less for each of the downlink (DL) and uplink (UL), or 1 ms or less round trip).
[0150] The antenna module 897 may transmit a signal or power to the outside of the electronic device 801 (e.g., an external electronic device) or receive a signal or power from the outside of the electronic device 801 (e.g., an external electronic device). According to an embodiment, the antenna module 897 may include an antenna including a radiating element, and the radiating element is formed of a conductive material or a conductive pattern formed in a substrate (e.g., a printed circuit board (PCB)) or formed on a substrate. According to an embodiment, the antenna module 897 may include a plurality of antennas (e.g., an array antenna). In this case, at least one antenna suitable for a communication scheme used in a communication network (such as the first network 898 or the second network 899) may be selected from the plurality of antennas by, for example, the communication module 890 (e.g., the wireless communication module 892). Subsequently, a signal or power may be transmitted or received between the communication module 890 and the external electronic device via the selected at least one antenna. According to an embodiment, another component (e.g., a radio frequency integrated circuit (RFIC)) other than the radiating element may be additionally formed as a part of the antenna module 897.
[0151] According to various embodiments, the antenna module 897 may form a millimeter wave antenna module. According to an embodiment, the millimeter wave antenna module may include a printed circuit board, a radio frequency integrated circuit (RFIC), and a plurality of antennas (e.g., array antennas), wherein the RFIC is disposed on a first surface (e.g., bottom surface) of the printed circuit board, or adjacent to the first surface and capable of supporting a specified high frequency band (e.g., millimeter wave band), and the plurality of antennas are disposed on a second surface (e.g., top surface or side surface) of the printed circuit board, or adjacent to the second surface and capable of transmitting or receiving signals of the specified high frequency band.
[0152] At least some of the above components may be connected to each other via an inter-peripheral communication scheme (e.g., a bus, a general purpose input output (GPIO), a serial peripheral interface (SPI), or a mobile industry processor interface (MIPI)) and communicatively transmit signals (e.g., commands or data) therebetween.
[0153] According to an embodiment, a command or data may be sent or received between the electronic device 801 and the external electronic device 804 via the server 808 connected to the second network 899. Each of the electronic device 802 or the electronic device 804 may be a device of the same type as the electronic device 801, or a device of a different type from the electronic device 801. According to an embodiment, all or some operations to be executed in the electronic device 801 may be executed in one or more of the external electronic device 802, the external electronic device 804, or the server 808. For example, if the electronic device 801 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 801 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 801 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices receiving the request may execute at least part of the function or service requested, or execute another function or another service related to the request, and transmit the result of the execution to the electronic device 801. The electronic device 801 may provide the result as at least a partial reply to the request in the case of further processing the result or in the case of not further processing the result. To this end, cloud computing technology, distributed computing technology, mobile edge computing (MEC) technology or client-server computing technology, for example, may be used. The electronic device 801 may use, for example, distributed computing or mobile edge computing to provide ultra-low latency services. In another embodiment, the external electronic device 804 may include an Internet of Things (IoT) device. The server 808 may be an intelligent server using machine learning and / or neural networks. According to an embodiment, the external electronic device 804 or the server 808 may be included in the second network 899. The electronic device 801 may be applied to intelligent services (e.g., smart homes, smart cities, smart cars or health care) based on 5G communication technology or IoT-related technologies.
[0154] The electronic device according to various embodiments may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to an embodiment of the present disclosure, the electronic device is not limited to those electronic devices described above.
[0155] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but include various changes, equivalent forms or alternative forms for corresponding embodiments. For the description of the accompanying drawings, similar reference numerals may be used to refer to similar or related elements. It will be understood that the nouns in the singular form corresponding to the term may include one or more things unless the relevant context clearly indicates otherwise. As used herein, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C" and "at least one of A, B or C" may include any one or all possible combinations of the items listed together with the corresponding one of the multiple phrases. As used herein, terms such as "1st" and "2nd" or "first" and "second" may be used to simply distinguish the corresponding component from another component, and do not limit the component in other aspects (e.g., importance or order). It will be understood that if an element (e.g., a first element) is referred to as being “combined with another element (e.g., the second element)”, “combined to another element (e.g., the second element)”, “connected with another element (e.g., the second element)”, or “connected to another element (e.g., the second element)” when the terms “operably” or “communicatively” are used or when the terms “operably” or “communicatively” are not used, it means that the element may be directly (e.g., wired) connected to the other element, wirelessly connected to the other element, or connected to the other element via a third element.
[0156] As used in connection with various embodiments of the present disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuit"). A module may be a single integrated component adapted to perform one or more functions or a minimum unit or portion of the single integrated component. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).
[0157] The various embodiments described herein may be implemented as software (e.g., program 840) including one or more instructions stored in a storage medium (e.g., internal memory 836 or external memory 838) that can be read by a machine (e.g., electronic device 801). For example, under the control of a processor, a processor (e.g., processor 820) of the machine (e.g., electronic device 801) may call at least one of the one or more instructions stored in the storage medium and execute the at least one instruction with or without the use of one or more other components. This enables the machine to operate to perform at least one function according to the at least one instruction called. The one or more instructions may include code generated by a compiler or code that can be run by an interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. Among them, the term "non-transitory" only means that the storage medium is a tangible device and does not include a signal (e.g., an electromagnetic wave), but the term does not distinguish between data being semi-permanently stored in a storage medium and data being temporarily stored in a storage medium.
[0158] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be published in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or may be published online (e.g., downloaded or uploaded) via an application store (e.g., Play StoreTM), or may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smart phones). If published online, at least part of the computer program product may be temporarily generated, or at least part of the computer program product may be at least temporarily stored in a machine-readable storage medium (such as a manufacturer's server, an application store's server, or a memory of a forwarding server).
[0159] According to various embodiments, each component (e.g., module or program) in the above-mentioned components may include a single entity or multiple entities, and some entities in the multiple entities may be separately arranged in different components. According to various embodiments, one or more components in the above-mentioned components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., module or program) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform the one or more functions of each component in the multiple components in the same or similar manner as the corresponding one component in the multiple components before integration. According to various embodiments, the operations performed by a module, program or another component may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in the operations may be run or omitted in different orders, or one or more other operations may be added.
Claims
1. An electronic device, include: a first controller; A first memory configured to: store a first basic input and output system BIOS and a first firmware for controlling the first controller, and functionally connected to the first controller; A second memory is configured to: store a second firmware corresponding to the first firmware and a second BIOS corresponding to the first BIOS; as well as a second controller functionally connected to the first memory, the second memory and the first controller, Wherein, the second controller is configured as: comparing the first firmware and the second firmware during power-on when the electronic device is powered on, and enabling the first controller based at least on the compared result, and The first controller is configured to: in response to being turned on by the second controller, a system for controlling the electronic device is started.
2. The electronic device according to claim 1, in, The second controller is further configured to: if the first firmware and the second firmware do not match as a result of the comparison: rewriting the first firmware with the second firmware, and The first firmware and the second firmware are compared and verified.
3. The electronic device according to claim 1, in, The second controller is further configured to: During the power-on period, a first control signal including a standby signal is sent to the first controller, and the standby signal is used for the second controller to control the electronic device.
4. The electronic device according to claim 1, in, The first controller is further configured to: obtain a start-up request for the electronic device, and in response to obtaining the start-up request, send the start-up request to the second controller, The second controller is further configured to: compare the first BIOS with the second BIOS in response to the sent boot request, and send a second control signal for booting the system to the first controller based at least on the comparison result, and The first controller is further configured to send a system startup command to a central processing unit CPU included in the electronic device based on the second control signal.
5. The electronic device according to claim 4, in, The second controller is further configured to: rewriting the first BIOS with the second BIOS based on a comparison result that the first BIOS and the second BIOS do not match, and The first BIOS and the second BIOS are compared and verified.
6. The electronic device according to claim 4, in, The CPU is configured to execute the first BIOS according to the system startup command, thereby starting the system.
7. The electronic device according to claim 1, in, The second controller and the second memory are configured as a single chip.
8. The electronic device according to claim 1, in, The first controller includes a first buffer memory and is configured to: In response to the first controller being turned on by the second controller, loading the first firmware stored in the first memory into the first buffer memory, and The operation is performed by executing the loaded first firmware.
9. The electronic device according to claim 1, in, The second memory is configured to store third firmware for controlling the second controller, and Wherein, the second controller comprises a second buffer memory and is further configured to: loading the third firmware into the second buffer memory, and The operation is performed by executing the loaded third firmware.
10. The electronic device according to claim 4, in, The CPU includes a third buffer memory and is configured to: loading the first BIOS into the third buffer memory in response to a boot request of the system obtained from the first controller, and System startup is performed by executing the loaded first BIOS.
11. The electronic device according to claim 4, further comprising: include: a trusted platform module configured to store a security key for the electronic device, The electronic device is configured to verify the integrity of the electronic device by using the security key, the security key stored in the CPU, and the security key stored in the second controller during execution of startup of the system.
12. The electronic device according to claim 4, in, The activation request includes an input related to activation of the system, the input being acquired from a user of the electronic device through a physical key included in the electronic device.
13. A method for operating an electronic device, the electronic device comprising a first memory, a second memory, a first controller and a second controller, the method include: comparing, by the second controller, first firmware stored in the first memory and configured to control the first controller with second firmware stored in the second memory and corresponding to the first firmware; The second controller starts the first controller based on at least the compared result; as well as In response to the first controller being turned on by the second controller, a system in which the electronic device is controlled by the first controller is started.
14. The method according to claim 13, in, Comparing the first firmware and the second firmware includes: In response to a comparison result that the first firmware does not match the second firmware, overwriting the first firmware with the second firmware; and The first firmware and the second firmware are compared and verified.
15. The method according to claim 13, further comprising: include: The first controller obtains a start-up request for the electronic device; In response to obtaining the start request, the first controller sends the start request to the second controller; In response to the sent boot request, the second controller compares a first basic input and output system BIOS stored in the first memory with a second BIOS stored in the second memory; sending a signal for activating the system to the first controller based at least on the compared result; as well as Based on the signal for starting the system, the first controller sends a system start command to a central processing unit included in the electronic device.
