Starting method and related device

By dividing the target firmware into the first sub-firmware and the second sub-firmware and loading it in different memory, the failure or exception problem caused by insufficient storage space during the processor startup process is solved, and the normal startup and efficiency of the processor are achieved. Improve and ensure the security of the processor.

CN119065725APending Publication Date: 2024-12-03PHYTIUM TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411075678.6
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-06
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The processor startup process is complicated, especially due to startup failures or exception problems caused by storage space limitations of memory devices, which are particularly prominent in heterogeneous architecture processors.

Method used

By dividing the target firmware into a first sub-firmware and a second sub-firmware, and loading it in the second memory and the first memory, the second processor core can be enabled normally based on these firmware, avoiding startup caused by insufficient storage space. Failed or exception.

Benefits of technology

It effectively avoids processor startup failures or exceptions caused by insufficient storage space, simplifies the startup process, improves startup efficiency, and ensures the security of the second processor core.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065725A_ABST
    Figure CN119065725A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a starting method, which comprises the following steps of: responding to a starting operation through a first processor core, loading a first sub-firmware into a second memory, and loading a second sub-firmware into a first memory, the second processor core can be normally started based on the target firmware loaded in the second memory and the first memory, and the problem that the first processor core fails to start or is abnormal to start due to the fact that the storage space of the second memory is insufficient to load all the target firmware is avoided.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present specification relates to the field of computer application technology, specifically, to processor startup technology under the field of computer application technology, and more specifically, to a startup method and related devices. Background Art

[0002] System on Chip (SoC) is an advanced integrated circuit technology that integrates a complete electronic system on a single chip, including all or part of the necessary electronic circuits of the processor, memory, input / output interface, sensor, communication module, graphics processor (GPU), storage controller, power management unit, etc.

[0003] As the processor structure becomes more complex, the processor startup process also becomes more complicated. It is necessary to optimize the startup method for different types of processor architectures. Summary of the invention

[0004] The embodiments of the present specification provide a startup method and related devices to achieve the purpose of optimizing the startup process of a processor architecture of a heterogeneous architecture and avoid the problem of startup failure or startup abnormality caused by storage space limitations of a storage device.

[0005] To achieve the above technical objectives, the embodiments of this specification provide the following technical solutions:

[0006] In a first aspect, an implementation of the present specification provides a startup method, the startup method is applied to a processor architecture, the processor architecture includes a first processor, an input-output processor, and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, the startup method includes:

[0007] The first processor core obtains the target firmware in response to the startup operation to execute the startup process of the second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware;

[0008] The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory.

[0009] During the startup process, the first sub-firmware and the second sub-firmware are loaded into the second memory and the first memory respectively through the first processor core, so that the second processor core can be started based on the first sub-firmware loaded in the second memory and the second sub-firmware loaded in the first memory, avoiding the problem of the first processor core failing to start or starting abnormally due to insufficient storage space in the second memory to load all the target firmware.

[0010] In an optional embodiment, the second memory includes a firmware storage space for storing the first sub-firmware;

[0011] The startup process specifically includes:

[0012] When the size of the storage space required by the target firmware is larger than the size of the storage space corresponding to the firmware storage space, the first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory.

[0013] In this embodiment, a firmware storage space for storing the first sub-firmware is divided in the second memory. During the startup process, the first processor core can first determine the size relationship between the storage space required by the target firmware and the storage space corresponding to the firmware storage space. When the size of the storage space required by the target firmware is larger than the size of the storage space corresponding to the firmware storage space, the first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory. When the size of the storage space required by the target firmware is less than or equal to the size of the storage space corresponding to the firmware storage space, the target firmware can be loaded as a whole into the firmware storage space, which is beneficial to simplifying the startup process when the size of the storage space required by the target firmware is less than or equal to the size of the storage space corresponding to the firmware storage space, and is beneficial to improving the startup efficiency of the startup method.

[0014] In an optional implementation manner, loading the first sub-firmware into the firmware storage space and loading the second sub-firmware into the first memory includes:

[0015] According to the storage space size corresponding to the firmware storage space, the target firmware is divided into the first sub-firmware and the second sub-firmware, the size of the storage space required by the first sub-firmware being less than or equal to the size of the storage space corresponding to the firmware storage space;

[0016] The first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory.

[0017] In this embodiment, the first sub-firmware and the second sub-firmware are divided based on the storage space size corresponding to the firmware storage space, so that the storage space size required for the second sub-firmware obtained by the division can be more adapted to the storage space size corresponding to the firmware storage space, thereby avoiding the problem of wasting firmware storage space due to the storage space size required for the second sub-firmware being much smaller than the storage space size corresponding to the firmware storage space, and also avoiding the situation where the storage space size required for the second sub-firmware obtained by the division is larger than the storage space size corresponding to the firmware storage space, causing abnormal startup / failure of the second processor core.

[0018] In an optional embodiment, the second memory includes a firmware storage space for storing the first sub-firmware;

[0019] The input-output processor further includes: a firmware program register, wherein when the value of the firmware program register is a target value, the first processor core is prohibited from accessing the firmware storage space;

[0020] After the execution of the startup process, the following steps are also included:

[0021] The value of the firmware program register is set as the target value.

[0022] In this embodiment, the input-output processor also includes: a firmware program register. After the first processor core executes the startup process, the value of the firmware program register is set to a target value to prohibit the first processor core from accessing the firmware storage space, so as to avoid the first processor core and the second processor core simultaneously accessing the first sub-firmware loaded in the second memory during the startup and operation of the second processor core. The first processor core and the second processor core may cause anomalies. At the same time, it can also prevent attackers from maliciously accessing the first sub-firmware loaded in the firmware storage space through the first processor core, which is beneficial to ensuring the security of the target firmware loaded in the second memory after the second processor core is started.

[0023] In an optional implementation, the processor architecture further includes: a third memory;

[0024] The obtaining of the target firmware comprises:

[0025] The target firmware is read from the third memory.

[0026] Before executing the startup process for the second processor core, the first processor core first reads the target firmware from the third processor, and utilizes the non-volatile property of the third processor when power is off to ensure the integrity of the target firmware.

[0027] In a second aspect, an implementation of the present specification provides a startup method, the startup method is applied to a processor architecture, the processor architecture includes a first processor, an input-output processor, and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, the startup method includes:

[0028] executing a startup process of a second processor core corresponding to a target firmware in response to the first processor core by the second processor core, based on the target firmware loaded in the second memory and the first memory; the target firmware includes a first sub-firmware and a second sub-firmware;

[0029] The boot process includes: the first processor core loads the first sub-firmware into the second memory, and loads the second sub-firmware into the first memory.

[0030] In this embodiment, the second processor core executes a startup process for the second processor core in response to the first processor core, and is started based on the target firmware loaded in the second memory and the first memory. In this way, the problem of startup failure or startup abnormality of the first processor core due to insufficient storage space in the second memory to load all the target firmware is avoided.

[0031] In an optional implementation, the second processor core is used to execute a first access request for a plurality of peripherals, the first access request comprising an access request for a peripheral sent by the first processor core;

[0032] The second memory comprises: a firmware storage space and a shared storage space, the firmware storage space is used to store the first sub-firmware, the shared storage space comprises a plurality of shared sub-spaces, the plurality of shared sub-spaces correspond to the plurality of peripherals one by one; the shared sub-space is used to store a first access request for the peripheral corresponding thereto;

[0033] After the target firmware loaded into the second memory and the first memory is started, the method further includes:

[0034] The shared storage space is re-divided according to the actual usage space of the multiple peripheral devices to update the storage space size of at least part of the shared subspaces in the multiple shared subspaces.

[0035] In this embodiment, the second processor core can be used to execute the first access request for multiple peripherals. In this way, the first access request for multiple peripherals that needs to be executed by the first processor core is handed over to the second processor core for execution, thereby reducing the resources consumed by the first processor core to access the peripherals, which is conducive to releasing the performance of the first processor core.

[0036] In addition, in addition to the firmware storage space for storing the first sub-firmware, the second memory also has multiple shared subspaces, which correspond one-to-one to multiple peripherals, so that the first access request of the corresponding peripheral can be stored in the corresponding shared subspace, which is beneficial for the second processor core to identify which peripheral the first access request is for. In some embodiments, corresponding security attributes can be set for different shared subspaces, so that when processing the first access request, the first access request can be filtered through the trusted domain controller, and only when the security attributes of the first access request are consistent with the security attributes of the shared subspace, the first access request is allowed to be sent to the shared subspace.

[0037] In an optional implementation, a first data path is established between the second processor core and the second memory, and a second data path is established between the second processor core and the first memory;

[0038] The starting based on the target firmware loaded in the second memory and the first memory includes:

[0039] Reading the first sub-firmware loaded in the second memory through the first data path, and reading the second sub-firmware loaded in the first memory through the second data path;

[0040] The system starts up based on the read first sub-firmware and second sub-firmware.

[0041] In this embodiment, a first data path is established between the second processor core and the second memory, and a second data path is established between the second processor core and the first memory. In this way, communication between the second processor core and the first memory and the second memory is achieved based on a dedicated data path, which is conducive to ensuring the stability of communication between the second processor core and the first memory and the second memory.

[0042] In a third aspect, an embodiment of this specification further provides a processor architecture, including:

[0043] An input-output processor, the input-output processor comprising a second processor core and a second memory;

[0044] A first processor core and a first memory; wherein,

[0045] The first processor core is configured to: in response to a startup operation, obtain a target firmware to execute a startup process of a second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware;

[0046] The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory;

[0047] The second processor core is configured to start based on the target firmware loaded in the second memory and the first memory in response to the first processor core executing a startup process of the second processor core corresponding to the target firmware.

[0048] In a fourth aspect, an embodiment of the present specification further provides a computing device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the startup method as described above when executing the computer program.

[0049] In a fifth aspect, an embodiment of the present specification further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the startup method as described above is implemented.

[0050] In a sixth aspect, an embodiment of the present specification provides a computer program product or a computer program, wherein the computer program product includes a computer program, and the computer program is stored in a computer-readable storage medium; the processor of the computer device reads the computer program from the computer-readable storage medium, and the processor implements the steps of the above-mentioned startup method when executing the computer program.

[0051] It can be seen from the above technical solution that the startup method provided in the embodiment of this specification responds to the startup operation through the first processor core, loads the first sub-firmware into the second memory, and loads the second sub-firmware into the first memory, so that the second processor core can be normally started based on the target firmware loaded in the second memory and the first memory, avoiding the problem of startup failure or startup abnormality of the first processor core due to insufficient storage space in the second memory to load all the target firmware. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0053] Figure 1 A schematic diagram of a processor architecture provided for one embodiment of this specification;

[0054] Figure 2 A schematic diagram of another processor architecture provided for one embodiment of this specification;

[0055] Figure 3 A schematic flow chart of a startup method provided for one embodiment of this specification;

[0056] Figure 4 A schematic diagram of a structure of another processor architecture provided for one embodiment of this specification;

[0057] Figure 5 A schematic flow chart of another startup method provided for one embodiment of this specification;

[0058] Figure 6 A schematic diagram of the structure of a computing device provided for one embodiment of the present specification. DETAILED DESCRIPTION

[0059] Unless otherwise defined, the technical terms or scientific terms used in the embodiments of this specification shall have the common meanings understood by persons with ordinary skills in the field to which this specification belongs. The words "first", "second" and similar words used in the embodiments of this specification do not indicate any order, quantity or importance, but are only used to avoid confusion of constituent elements.

[0060] Unless the context requires otherwise, throughout the specification, "plurality" means "at least two", and "including" is interpreted as an open, inclusive meaning, that is, "including, but not limited to". In the description of the specification, the terms "one embodiment", "some embodiments", "exemplary embodiments", "examples", "specific examples" or "some examples" are intended to indicate that a particular feature, structure, material or characteristic associated with the embodiment or example is included in at least one embodiment or example of the specification. The schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0061] The technical solutions in the embodiments of this specification will be described below in conjunction with the drawings in the embodiments of this specification. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this specification.

[0062] Overview

[0063] As processor performance improves and functions continue to increase, the complexity of processor architecture is also increasing. In related technologies, a multi-core processor architecture refers to a processor architecture that includes two or more processor cores. In a multi-core processor, these processor cores can independently execute different instructions to meet the needs of processing different tasks at the same time, significantly improving the computer's parallel processing capabilities and efficiency; these processor cores can also collaboratively execute the same instruction, based on the performance of multiple processor cores to collaboratively complete complex calculations and other tasks with high performance requirements. Multi-core processor architecture can effectively solve the limitations of single-core processors in improving performance.

[0064] In order to give full play to the advantages of each processor core in the multi-core processor architecture, the embodiments of this specification provide an innovative processor architecture. Figure 1 , the processor architecture includes:

[0065] The first processor 100 and the input output processor (IOP) 110 , in some implementations, the processor architecture may further include at least one peripheral controller 120 .

[0066] The first processor 100 is communicatively connected to the input / output processor 110 via an on-chip network 130 , and the input / output processor 110 is respectively connected to at least one peripheral controller 120 .

[0067] The on-chip network 130 is a communication network between various components within the entire processor architecture, and is used to provide communication links between various components within the processor architecture. Various types of buses, bus interfaces, etc. can be integrated in the on-chip network 130 to meet the communication requirements between the input and output processor 110 and various processor architecture components such as the first processor 100, the second processor, and the first memory 150 based on any type of bus.

[0068] Specifically, the input / output processor 110 includes at least one dedicated second processor core 111 , and the second processor core 111 can serve as an intermediate medium when the first processor 100 interacts with at least one peripheral controller 120 .

[0069] The above-mentioned first processor 100 is an application processor (AP) in the processor architecture, which may include a first processor core 101. The first processor core 101 can be used as an application processor core in the processor architecture. The application processor core is the operation and control center of the entire processor architecture and is used to execute instructions and operations.

[0070] At the same time, the application processor core can also be used to start and control other processor cores in the processor architecture, such as the second processor core 111 in the input-output processor 110. For example, before the second processor core 111 in the input-output processor 110 is started, the processor core of the first processor 100 copies the firmware program stored in the memory to the SRAM of the input-output processor 110, so that the second processor core 111 in the input-output processor 110 can load the firmware program from the SRAM to start running.

[0071] At least one peripheral controller 120 in the above-mentioned processor architecture may include any external device connected to the processor architecture or a controller corresponding to an external device interface, such as a UART (Universal Asynchronous Receiver / Transmitter) controller, an I2C (Inter-Integrated Circuit, serial communication bus) controller, an SPI (Serial Peripheral Interface, serial peripheral interface) controller, an SD (Secure Digital, SD card) controller, a GMAC controller (Gigabit Media Access Controller, Gigabit Media Access Controller), and the like. The peripheral controller may be used to control the peripheral according to the instructions or data sent by the input and output processor. In practical applications, the processor architecture may integrate different peripheral controllers according to actual functional requirements. These peripheral controllers may support the same protocol or different protocols. The specific selection and implementation of the peripheral controller may refer to the actual requirements of the processor architecture and the implementation of related technologies, and this specification does not specifically limit this. Each peripheral controller may directly interact with the input and output processor for data. In some embodiments, the above-mentioned peripheral controller 120 may include a controller for a low-speed peripheral. In this embodiment, the low-speed peripheral controller 120 is connected to the first processor 100 through the input-output processor 110. The low-speed peripheral controller is connected to the input-output processor 110, and the input-output processor 110 performs communication interaction with the low-speed peripherals, without the need for the first processor core to specifically execute access requests for the low-speed peripherals, which is conducive to releasing at least part of the resources of the first processor core.

[0072] As for the high-speed peripheral controller in the processor architecture, it can be directly connected to the first processor 100, so that the first processor 100 can execute access requests for high-speed peripherals, and high-speed peripherals usually interact with the first processor 100 for relatively more important services, so that the first processor 100 and the high-speed peripherals are directly connected and can ensure the smooth execution of high-speed services. However, in some embodiments, the high-speed peripheral controller can also be connected to the second processor core 111, and the first processor core 101 can hand over some access requests for the high-speed peripheral controller to the second processor core 111 for execution, so as to further reduce the computing pressure of the first processor core 101 when the peripherals are accessed. Optionally, the first processor core 101 can delegate low-speed access requests to the high-speed peripheral controller to the second processor core 111 for execution. The low-speed access requests to the high-speed peripheral controller have relatively low requirements for data transmission rate, etc., and the performance of the second processor core 111 can meet the access requirements. Therefore, the low-speed access requests to the high-speed peripheral controller are delegated to the second processor core 111 for execution. While meeting the access requirements, the computing pressure on the first processor core 101 is reduced, which is beneficial to releasing the performance of the first processor core 101.

[0073] The input-output processor 110 can be integrated into the processor architecture to share the pressure of the first processor and serve as an intermediate medium for data exchange between the first processor and the peripheral controller, so that the first processor can access each peripheral controller through the input-output processor, thereby realizing control of the peripherals connected to the peripheral controller. The input-output processor 110 includes at least one second processor core 111 for executing data communication operations between the first processor 100 and the peripheral controller 120.

[0074] In one embodiment of the present specification, the above-mentioned second processor core 111 may specifically include a RISC-V (Reduced Instruction Set Computer-Five, a fifth-generation reduced instruction set computer) core, that is, a processor core of the RISC-V instruction architecture, which can complete instruction access to modules with low real-time requirements such as low-speed peripherals.

[0075] Based on the above-mentioned input / output processor 110 and the second processor core 111 therein, the input / output processor 110 serves as a communication medium between the first processor 100 and each peripheral controller 120. The first processor 100 only needs to be connected to the input / output processor 110, and the input / output processor 110 is connected to each peripheral controller 120 respectively. In this way, there is no need for the first processor 100 to establish a communication link with each peripheral controller 120 separately.

[0076] At the same time, the second processor core 111 in the input-output processor 110 serves as an intermediate medium when the first processor 100 interacts with each peripheral controller 120. When the first processor 100 needs to access any target peripheral controller among the peripheral controllers, it only needs to send an access request for the target peripheral controller to the input-output processor 110. The second processor core 111 in the input-output processor 110 executes access to the target peripheral controller according to the access request sent by the first processor 100, and feeds back the access result to the first processor 100. In the above process, the first processor 100 only needs to send an access request for the target peripheral controller to the input-output processor 110. At this time, the first processor 100 can execute other operations without executing subsequent interactive operations with the target peripheral controller. Instead, the input-output processor 110 executes the actual access to the peripheral controller and feeds back the access result to the first processor 100. It can be seen that the above process greatly reduces the resource consumption when the first processor 100 interacts with the peripheral controller.

[0077] Furthermore, since the first processor 100 can delegate at least part of the interactive operations with the peripheral controller to the second processor core 111 for execution, the number of drivers for the peripheral controller installed in the first processor 100 can be reduced, and the operations of upgrading or updating the peripheral controller drivers can also be reduced, thereby further reducing the burden on the first processor 100 and reducing resource consumption.

[0078] In some optional embodiments, reference Figure 2 The processor architecture may further include a security processor 140 connected to the first processor 100 and connected to other parts of the processor architecture via an on-chip network 130 .

[0079] The security level of the security processor 140 may be higher than the security level of the first processor 100. Based on the high security level of the security processor 140, programs with high security level requirements may be run on the security processor 140, and a security measurement service module may be mounted in the security processor 140 to perform security measurement on other modules.

[0080] The security processor 140 can be used to perform security control on the processor architecture, for example, to actively perform security measurements on each module of the processor architecture or to perform security measurements on the corresponding modules in response to security measurement requests from each module, and to control at least some modules to operate when safety is confirmed through security measurements.

[0081] Still reference Figure 2Optionally, the input / output processor 110 may further include a second memory 112, a register array 113, a timer 114, a watchdog 115, a direct memory access 116, and a trusted domain controller 118. The second memory 112 may be used to store the target firmware corresponding to the second processor core, so that the second processor core can start and run based on the target firmware stored in the second memory 112 during operation. In addition, the second memory 112 may also provide a shared storage space, and both the first processor core 101 and the second processor core 111 have access rights to the shared storage space. The shared storage space may be used as an inter-core channel during the communication between the first processor core 101 and the second processor core 111, so as to meet the communication requirements between the first processor core 101 and the second processor core 111.

[0082] The register array 113 may be composed of a plurality of registers corresponding to different functions, such as a register for triggering an interrupt signal, a register for recording the data read and write status, a register for recording the number of data written, a register for recording the number of data read, a register for configuring the aforementioned inter-core channel capacity, and a register for recording the number of inter-core channels, etc. Of course, registers corresponding to other functions may also be set based on actual application requirements, which are not exhaustively listed in this specification. In addition, the register array 113 may also cooperate with the second memory 112 to construct an inter-core channel for realizing data exchange between the first processor core 101 and the second processor core 111. In one possible implementation, a shared storage space of a certain capacity in the second memory 112 and two registers of the register array can be used to cooperate in realizing data interaction between the first processor core 101 and the second processor core 111, wherein one of the registers is used to trigger an interrupt to the first processor core 101, so that the first processor core 101 responds to the interrupt to access the information stored in the second processor core 111 in the shared storage space, thereby realizing information transfer from the second processor core 111 to the first processor core 101, and the other register is used to trigger an interrupt to the second processor core 111, so that the second processor core 111 responds to the interrupt to access the information stored in the first processor core 101 in the shared storage space, thereby realizing information transfer from the first processor core 101 to the second processor core 111.

[0083] The role of the network interconnect 117 is similar to that of the on-chip network 130, and is also used as a data interaction path to realize data interaction between any two or more functional modules mounted on the network interconnect 117. For example, the data sent from the first processor core 101 to the second processor core 111 is sent to the shared memory space, the instructions of the second processor core 111 are transmitted to the second memory 112, and the instructions issued by the second processor core 111 are transmitted to the watchdog 115, the timer 114 and the peripheral controller 120, etc.

[0084] The role of the trusted domain controller 118 may include filtering requests issued by the first processor core 101. For example, in some embodiments, the trusted domain controller 118 may also filter requests issued by the first processor 100 according to the security attributes of the peripheral controller 120 after the second processor core 111 is started, so that the first processor core 101 can access the secure peripheral controller 120 by issuing a secure request; when the first processor core 101 requests to access the secure peripheral controller 120 by issuing an unsecure request, the request will be filtered by the trusted domain controller 118.

[0085] The watchdog 115 may include a timer chip, whose functions may include monitoring whether the second processor core 111 is operating normally. If the second processor core 111 is operating abnormally, it may exceed a predetermined time without returning a heartbeat signal to the watchdog 111, and the watchdog 115 may time out. When the watchdog 115 times out, the watchdog 115 will reset the second processor core 111 to restore it to normal and restart operation.

[0086] The timer (Timer) 114 can be used for timing inside the input / output processor 110, and can also be used for reporting interrupts at a fixed time.

[0087] Understandably, Figure 2 As an example of a processor architecture only, in some embodiments, the processor architecture may include Figure 2 Some or all of the modules shown may even include Figure 2 Other modules other than the modules shown in the figure, similarly, the modules in the input and output processor 110 may also be compared Figure 2 The modules shown are more or less. The connection relationship and position between the modules can also be adaptively adjusted, for example, in Figure 2 In the illustrated embodiment, the peripheral controller 120 is disposed outside the input-output processor 110, and establishes a connection relationship with other modules of the input-output processor 110 through the interface of the input-output processor 110 and the network interconnection 117. In other embodiments, the peripheral controller 120 may also be integrated inside the input-output processor 110, that is, the peripheral controller 120 is encapsulated inside the input-output processor 110, so that the privatization of the peripheral controller 120 is realized, and the input-output processor 110 does not need to describe the relevant information of the peripheral controller to a third party during operation, which is conducive to improving the security of the input-output processor 110. This specification does not limit this, and it depends on the actual situation.

[0088] exist Figure 1 and Figure 2In the processor architecture shown, the second memory 112 may include high-speed memories such as SRAM (Static Random Access Memory). SRAM has the characteristics of fast access speed and short delay time, and is suitable for scenarios where data is quickly accessed. Therefore, in one embodiment, the second processor core can be started and run based on the target firmware loaded in the second memory, so as to utilize the fast access support of the second memory to improve the startup and operation performance of the second processor core. However, high-speed memories such as SRAM have the characteristic of being volatile when power is off, which requires that the first processor core 101 loads the target firmware for the second processor core 111 into the second memory 112 before the second processor core 111 is started. However, in some embodiments, the capacity of the storage space occupied by the target firmware may vary depending on the function of the second processor core 111. For example, in some embodiments, when the second processor core 111 needs to access a large number of types and / or quantities of peripheral controllers, the storage space occupied by the target firmware of the second processor core 111 may be correspondingly larger, and the second memory may not be able to load all the target firmware, resulting in abnormal startup / operation or failure of the second processor core 111. In order to solve this problem, the inventors found through further research that a first memory 150 can be set in the processor architecture to establish a data transmission path between the second processor core 111 and the first memory 150. Before the second processor core 111 is started, the first processor core 101 divides the target firmware for the second processor core 111 into a first sub-firmware and a second sub-firmware, and loads the first sub-firmware and the second sub-firmware into the second memory and the first memory respectively, so that the second processor core can be normally started based on the target firmware loaded in the second memory and the first memory, thereby avoiding the problem of startup failure or abnormal startup of the first processor core due to insufficient storage space in the second memory to load all the target firmware.

[0089] Based on the above concept, an implementation manner of the present specification provides a startup method. The startup method provided in the implementation manner of the present specification will be exemplarily described below in conjunction with the accompanying drawings.

[0090] Exemplary Methods

[0091] To be applied to Figure 1 and Figure 2The processor architecture shown in the figure is taken as an example, the processor architecture includes a first processor 100, an input-output processor 110 and a first memory 150; the first processor 100 includes a first processor core 101, and the input-output processor 110 includes a second processor core 111 and a second memory 112. In particular, taking the first processor core 101 applied to the processor architecture as an example, some embodiments of this specification exemplarily illustrate the startup method, such as Figure 3 As shown, the startup method includes:

[0092] S301: acquiring target firmware in response to a startup operation through the first processor core 101 to execute a startup process of a second processor core 111 corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware;

[0093] The booting process includes: loading the first sub-firmware into the second memory 112 , and loading the second sub-firmware into the first memory 150 .

[0094] The startup operation includes but is not limited to at least one of a power-on operation and a reset operation for the processor architecture. The target firmware can be used to drive the second processor core 111 to run. In some embodiments, the second processor core 111 can be used to process access requests for peripherals sent by the first processor core 101. The size of the storage space occupied by the target firmware may be related to the number and / or type of peripherals that the second processor core 111 can access. When the number and / or type of peripherals that the second processor core 111 can access is greater, the storage space occupied by the target firmware corresponding to the second processor core 111 may be larger.

[0095] The first sub-firmware and the second sub-firmware may be different parts of the target firmware, or in other words, the target firmware may be divided into the first sub-firmware and the second sub-firmware. In response to the startup operation, the first processor core 101 may first obtain the target firmware, and execute the startup process of the second processor core 111 corresponding to the target firmware based on the acquired target firmware. During the startup process, the first sub-firmware and the second sub-firmware are loaded into the second memory 112 and the first memory 150 respectively, so that the second processor core 111 can be started based on the first sub-firmware loaded in the second memory 112 and the second sub-firmware loaded in the first memory 150, thereby avoiding the problem of the first processor core 101 failing to start or abnormal startup due to insufficient storage space in the second memory 112 to load all the target firmware.

[0096] In one embodiment, the second memory 112 includes a firmware storage space for storing the first sub-firmware;

[0097] The startup process specifically includes:

[0098] When the size of the storage space required by the target firmware is larger than the size of the storage space corresponding to the firmware storage space, the first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory 150 .

[0099] In this embodiment, a firmware storage space for storing the first sub-firmware is divided in the second memory 112. During the startup process, the first processor core 101 can first determine the size relationship between the storage space required by the target firmware and the storage space corresponding to the firmware storage space. When the size of the storage space required by the target firmware is larger than the size of the storage space corresponding to the firmware storage space, the first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory 150. When the size of the storage space required by the target firmware is less than or equal to the size of the storage space corresponding to the firmware storage space, the target firmware can be loaded as a whole into the firmware storage space, which is beneficial to simplify the startup process when the size of the storage space required by the target firmware is less than or equal to the size of the storage space corresponding to the firmware storage space, and is beneficial to improving the startup efficiency of the startup method.

[0100] In order to make the division of the first sub-firmware and the second sub-firmware more reasonable, in one embodiment, the loading of the first sub-firmware into the firmware storage space and the loading of the second sub-firmware into the first memory 150 include:

[0101] According to the storage space size corresponding to the firmware storage space, the target firmware is divided into the first sub-firmware and the second sub-firmware, the size of the storage space required by the first sub-firmware being less than or equal to the size of the storage space corresponding to the firmware storage space;

[0102] The first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory 150 .

[0103] In this embodiment, the first sub-firmware and the second sub-firmware are divided based on the storage space size corresponding to the firmware storage space, so that the storage space size required for the first sub-firmware obtained by division can be more adapted to the storage space size corresponding to the firmware storage space, thereby avoiding the problem of wasting firmware storage space due to the storage space size required for the first sub-firmware being much smaller than the storage space size corresponding to the firmware storage space, and also avoiding the situation where the storage space size required for the first sub-firmware obtained by division is larger than the storage space size corresponding to the firmware storage space, causing the second processor core 111 to start abnormally / fail.

[0104] In order to ensure the security of the target firmware loaded in the second memory 112 after the second processor core 111 is started, and to avoid the abnormality that may be caused by the first processor core 101 and the second processor core 111 accessing the target firmware loaded in the second memory 112 at the same time during the startup and operation of the second processor core 111, the input and output processor 110 further includes: a firmware program register, when the value of the firmware program register is the target value, the first processor core 101 is prohibited from accessing the firmware storage space;

[0105] After the execution of the startup process, the following steps are also included:

[0106] The value of the firmware program register is set as the target value.

[0107] In this embodiment, the input / output processor 110 further includes a firmware program register, which may be Figure 2 A register in the register array shown in the figure, after the first processor core 101 executes the startup process, the value of the firmware program register is set to the target value to prohibit the first processor core 101 from accessing the firmware storage space, so as to avoid the abnormality that may be caused by the first processor core 101 and the second processor core 111 simultaneously accessing the first sub-firmware loaded in the second memory 112 during the startup and operation of the second processor core 111. At the same time, it can also prevent attackers from maliciously accessing the first sub-firmware loaded in the firmware storage space through the first processor core 101, which is beneficial to ensuring the security of the target firmware loaded in the second memory 112 after the second processor core 111 is started.

[0108] In one embodiment, reference Figure 4 , the processor architecture further includes: a third memory 160, and the third memory 160 can establish a communication connection with the first processor core 101 through an on-chip network. In an optional implementation, the third memory 160 can be used to store data such as target firmware, and the third memory 160 can be a non-volatile memory, which can be used to save data after the processor architecture is powered off, and the first memory 150 and the second memory 112 can both be volatile memories, which are mainly used for high-speed data access after the processor architecture is powered on.

[0109] In such Figure 4 In the processor architecture shown, obtaining the target firmware includes:

[0110] The target firmware is read from the third memory.

[0111] In this way, before executing the boot process for the second processor core 111, the first processor core 101 first reads the target firmware from the third processor, and utilizes the non-volatile property of the third processor when power is off to ensure the integrity of the target firmware.

[0112] To be applied to Figure 1 and Figure 2 The processor architecture shown in the figure is particularly applied to the second processor core 111 in the processor architecture as an example. The implementation mode of this specification also provides a startup method, such as Figure 5 As shown, including:

[0113] S501: executing, by the second processor core 111, a startup process of the second processor core 111 corresponding to the target firmware in response to the first processor core 101, based on the target firmware loaded in the second memory 112 and the first memory 150; the target firmware includes a first sub-firmware and a second sub-firmware;

[0114] The boot process includes: the first processor core 101 loads the first sub-firmware into the second memory 112 , and loads the second sub-firmware into the first memory 150 .

[0115] In this embodiment, the second processor core 111 executes a startup process for the second processor core 111 in response to the first processor core 101, and is started based on the target firmware loaded in the second memory 112 and the first memory 150. In this way, the problem of startup failure or startup abnormality of the first processor core 101 due to insufficient storage space of the second memory 112 to load all the target firmware is avoided.

[0116] For the relevant limitations on the first processor core 101 executing the boot process, please refer to the relevant description above, and this specification will not elaborate on it here.

[0117] In an optional implementation, the second processor core 111 is used to execute a first access request for multiple peripherals, where the first access request includes an access request for a peripheral sent by the first processor core 101;

[0118] The second memory 112 includes: a firmware storage space and a shared storage space, the firmware storage space is used to store the first sub-firmware, the shared storage space includes a plurality of shared sub-spaces, the plurality of shared sub-spaces correspond to the plurality of peripherals one by one; the shared sub-space is used to store a first access request for the peripheral corresponding thereto;

[0119] After the target firmware loaded in the second memory 112 and the first memory 150 is started, the method further includes:

[0120] The shared storage space is re-divided according to the actual usage space of the multiple peripheral devices to update the storage space size of at least part of the shared subspaces in the multiple shared subspaces.

[0121] In this embodiment, the second processor core 111 can be used to execute the first access request for multiple peripherals. In this way, the first access request for multiple peripherals that the first processor core 101 needs to execute is handed over to the second processor core 111 for execution, thereby reducing the resources consumed by the first processor core 101 to access the peripherals, which is beneficial to releasing the performance of the first processor core 101.

[0122] In addition, in addition to the firmware storage space for storing the first sub-firmware, the second memory 112 also has multiple shared subspaces, which correspond one-to-one to multiple peripherals, so that the first access request of the corresponding peripheral can be stored in the corresponding shared subspace, which is beneficial for the second processor core 111 to identify which peripheral the first access request is for. In some embodiments, corresponding security attributes can be set for different shared subspaces, so that when processing the first access request, the first access request can be filtered through the trusted domain controller 118. Only when the security attributes of the first access request are consistent with the security attributes of the shared subspace, the first access request is allowed to be sent to the shared subspace.

[0123] In one embodiment, a first data path is established between the second processor core 111 and the second memory 112, and a second data path is established between the second processor core 111 and the first memory 150;

[0124] The starting based on the target firmware loaded in the second memory 112 and the first memory 150 includes:

[0125] Reading the first sub-firmware loaded in the second memory 112 through the first data path, and reading the second sub-firmware loaded in the first memory 150 through the second data path;

[0126] The system starts up based on the read first sub-firmware and second sub-firmware.

[0127] In this embodiment, a first data path is established between the second processor core 111 and the second memory 112, and a second data path is established between the second processor core 111 and the first memory 150. In this way, communication between the second processor core 111 and the first memory 150 and the second memory 112 is achieved based on a dedicated data path, which is conducive to ensuring the stability of communication between the second processor core 111 and the first memory 150 and the second memory 112.

[0128] Exemplary Devices

[0129] In an exemplary embodiment of the present specification, a startup device is further provided, which is applied to a processor architecture, wherein the processor architecture includes a first processor, an input-output processor, and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, and the startup device includes:

[0130] A firmware loading module, configured to obtain a target firmware in response to a startup operation through the first processor core, so as to execute a startup process of a second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware;

[0131] The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory.

[0132] In an exemplary embodiment of the present specification, a startup device is further provided, which is applied to a processor architecture, wherein the processor architecture includes a first processor, an input-output processor, and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, and the startup device includes:

[0133] a startup module, configured to execute, by the second processor core, a startup process of the second processor core corresponding to the target firmware in response to the first processor core, and to start based on the target firmware loaded in the second memory and the first memory; the target firmware includes a first sub-firmware and a second sub-firmware;

[0134] The boot process includes: the first processor core loads the first sub-firmware into the second memory, and loads the second sub-firmware into the first memory.

[0135] For the specific definition of the startup device, please refer to the definition of the startup method above, which will not be repeated here. Each module in the above startup device can be implemented in whole or in part by software, hardware and a combination thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0136] Exemplary Computing Device and Processor Architectures

[0137] An embodiment of this specification also provides a processor architecture, referring to Figure 1 and Figure 2, the processor architecture comprises:

[0138] An input-output processor, the input-output processor comprising a second processor core and a second memory;

[0139] A first processor core and a first memory; wherein,

[0140] The first processor core is configured to: in response to a startup operation, obtain a target firmware to execute a startup process of a second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware;

[0141] The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory;

[0142] The second processor core is configured to start based on the target firmware loaded in the second memory and the first memory in response to the first processor core executing a startup process of the second processor core corresponding to the target firmware.

[0143] Regarding the limitations of the modules such as the first processor core, the first memory, the second processor core, and the second memory in the processor architecture, please refer to the above description of the startup method, and this specification will not elaborate on it here.

[0144] Another embodiment of this specification also provides a computing device, see Figure 6 As shown, an exemplary embodiment of the present specification also provides a computing device, including: a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the startup method according to various embodiments of the present specification described in the above embodiments of the present specification are executed.

[0145] The internal structure of the computing device can be as follows Figure 6 As shown, the computing device includes a processor, a memory, a network interface and an input device connected through a system bus. Among them, the processor of the computing device is used to provide computing and control capabilities. The memory of the computing device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computing device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the steps in the startup method according to various embodiments of the present specification described in the above embodiments of the present specification are performed.

[0146] The processor may include a main processor and may also include a baseband chip, a modem, etc.

[0147] The memory stores a program for executing the technical solution of the present invention, and may also store an operating system and other key services. Specifically, the program may include a program code, and the program code includes computer operation instructions. More specifically, the memory may include a read-only memory (ROM), other types of static storage devices that can store static information and instructions, a random access memory (RAM), other types of dynamic storage devices that can store information and instructions, a disk storage, a flash, and the like.

[0148] The processor may be a general-purpose processor, such as a general-purpose central processing unit (CPU), a microprocessor, etc., or an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the scheme of the present invention. It may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component.

[0149] The input device may include a device for receiving data and information input by a user, such as a keyboard, a mouse, a camera, a scanner, a light pen, a voice input device, a touch screen, a pedometer, or a gravity sensor.

[0150] Output devices may include means that allow information to be output to a user, such as display screens, printers, speakers, etc.

[0151] The communication interface may include using any transceiver or the like to communicate with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.

[0152] The processor executes the program stored in the memory and calls other devices, which can be used to implement each step of any one of the startup methods provided in the above embodiments of this specification.

[0153] The computing device may also include a display component and a voice component. The display component may be a liquid crystal display or an electronic ink display. The input device of the computing device may be a touch layer covered on the display component, or a button, trackball or touchpad provided on the housing of the computing device, or an external keyboard, touchpad or mouse.

[0154] Those skilled in the art will understand that Figure 6The structure shown in the figure is only a block diagram of a part of the structure related to the scheme of this specification, and does not constitute a limitation on the computing device to which the scheme of this specification is applied. The specific computing device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] Exemplary computer program products and storage media

[0156] In addition to the above-mentioned methods and devices, the startup method provided in the embodiments of this specification may also be a computer program product, which includes computer program instructions, which, when executed by a processor, enable the processor to execute the steps of the startup method according to various embodiments of this specification described in the above "Exemplary Method" section of this specification.

[0157] The computer program product may be implemented in hardware, software or a combination thereof. In one optional embodiment, the computer program product is implemented as a computer storage medium. In another optional embodiment, the computer program product is implemented as a software product, such as a software development kit (SDK).

[0158] The computer program product may be written in any combination of one or more programming languages ​​to write program code for performing the operations of the embodiments of the present specification, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0159] In addition, an embodiment of the present specification also provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to execute the steps of the startup method according to various embodiments of the present specification described in the above "Exemplary Method" section of the present specification.

[0160] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this specification can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0161] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0162] The above-mentioned embodiments only express several implementation methods of this specification, and the descriptions are relatively specific and detailed, but they cannot be understood as limiting the scope of the solutions provided by the embodiments of this specification. It should be pointed out that for ordinary technicians in this field, several modifications and improvements can be made without departing from the concept of this specification, which all belong to the protection scope of this specification. Therefore, the protection scope of the patent of this specification shall be based on the attached claims.

Claims

1. A startup method, It is characterized in that The startup method is applied to a processor architecture, the processor architecture includes a first processor, an input-output processor and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, and the startup method includes: The first processor core obtains the target firmware in response to the startup operation to execute the startup process of the second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware; The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory.

2. The method according to claim 1, It is characterized in that The second memory includes a firmware storage space for storing the first sub-firmware; The startup process specifically includes: When the size of the storage space required by the target firmware is larger than the size of the storage space corresponding to the firmware storage space, the first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory.

3. The method according to claim 2, It is characterized in that The step of loading the first sub-firmware into the firmware storage space and loading the second sub-firmware into the first memory includes: According to the storage space size corresponding to the firmware storage space, the target firmware is divided into the first sub-firmware and the second sub-firmware, the size of the storage space required by the first sub-firmware being less than or equal to the size of the storage space corresponding to the firmware storage space; The first sub-firmware is loaded into the firmware storage space, and the second sub-firmware is loaded into the first memory.

4. The method according to claim 1, It is characterized in that The second memory includes a firmware storage space for storing the first sub-firmware; The input-output processor further includes: a firmware program register, wherein when the value of the firmware program register is a target value, the first processor core is prohibited from accessing the firmware storage space; After the execution of the startup process, the following steps are also included: The value of the firmware program register is set as the target value.

5. The method according to any one of claims 1 to 4, It is characterized in that The processor architecture further includes: a third memory; The obtaining of the target firmware comprises: The target firmware is read from the third memory.

6. A method of starting, It is characterized in that The startup method is applied to a processor architecture, the processor architecture includes a first processor, an input-output processor and a first memory; the first processor includes a first processor core, the input-output processor includes a second processor core and a second memory, and the startup method includes: executing a startup process of a second processor core corresponding to a target firmware in response to the first processor core by the second processor core, based on the target firmware loaded in the second memory and the first memory; the target firmware includes a first sub-firmware and a second sub-firmware; The boot process includes: the first processor core loads the first sub-firmware into the second memory, and loads the second sub-firmware into the first memory.

7. The method according to claim 6, It is characterized in that The second processor core is used to execute a first access request for a plurality of peripheral devices, wherein the first access request comprises an access request for a peripheral device sent by the first processor core; The second memory includes: a firmware storage space and a shared storage space, the firmware storage space is used to store the first sub-firmware, the shared storage space includes a plurality of shared sub-spaces, the plurality of shared sub-spaces correspond to the plurality of peripherals one by one; the shared sub-space is used to store a first access request for the peripheral corresponding thereto; After the target firmware loaded into the second memory and the first memory is started, the method further includes: The shared storage space is re-divided according to the actual usage space of the multiple peripheral devices to update the storage space size of at least part of the shared subspaces in the multiple shared subspaces.

8. The method according to claim 6, It is characterized in that A first data path is established between the second processor core and the second memory, and a second data path is established between the second processor core and the first memory; The starting based on the target firmware loaded in the second memory and the first memory includes: Reading the first sub-firmware loaded in the second memory through the first data path, and reading the second sub-firmware loaded in the first memory through the second data path; The system starts up based on the read first sub-firmware and second sub-firmware.

9. A processor architecture, It is characterized in that include: An input-output processor, the input-output processor comprising a second processor core and a second memory; A first processor core and a first memory; wherein, The first processor core is configured to: in response to a startup operation, obtain a target firmware to execute a startup process of a second processor core corresponding to the target firmware; the target firmware includes a first sub-firmware and a second sub-firmware; The boot process includes: loading the first sub-firmware into the second memory, and loading the second sub-firmware into the first memory; The second processor core is configured to start based on the target firmware loaded in the second memory and the first memory in response to the first processor core executing a startup process of the second processor core corresponding to the target firmware.

10. A computing device, It is characterized in that The invention comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the startup method according to any one of claims 1 to 8 when executing the computer program.

11. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the startup method according to any one of claims 1 to 8 is implemented.