Method and system for dynamically adjusting hardware core during boot process

Abstract

A kind of processing system and method of dynamically adjusting hardware core in booting process, and the configuration of the peripheral element to be tested is dynamically adjusted when electronic equipment is booted.The processing method of dynamically adjusting hardware core in booting process includes that boot program loads core device tree source file from memory;Flag identification program obtains element flag information of the peripheral element to be tested;Flag identification program reads the core device tree source file of memory, obtains the element environment parameter of element flag information from the core device tree source file;Flag identification program selects one of element environment parameter as target environment parameter;Boot program carries out environment test to the peripheral element to be tested with target environment parameter, obtains the evaluation result generated by environment test;Boot program generates running environment information according to the evaluation result of target environment parameter.

Description

Technical Field

[0001] This disclosure relates to a processing system and method for a computer hardware core, and more particularly to a processing system and method for dynamically adjusting the hardware core during the boot process. Background Technology

[0002] For computer devices, configuring the hardware environment is a crucial issue. With the diversification of hardware components, computer devices also require timely updates to the kernel configuration settings. When a computer device boots up, the bootloader calls the aforementioned configuration file.

[0003] Configuration files record relevant environmental parameters from the CPU, bus, and peripheral components. To facilitate the creation of configuration files, developers have introduced a hardware configuration development mechanism using a core device tree source. Developers can use the addition, modification, or deletion of core device tree source files to determine the purpose of adding, changing, or removing peripheral components. Due to the increasing number and types of peripheral components, the creation of core device tree sources has become increasingly complex. Summary of the Invention

[0004] In view of this, in some embodiments, the processing system for dynamically adjusting the hardware core during power-on includes a memory, a peripheral device under test (PDT), and a processor. The memory stores a core device tree source file, a bootloader, and a flag recognition program. The core device tree source file records multiple component flag information, and each component flag information has multiple component environment parameters. The DDT has component flag information. The processor is electrically connected to the memory and the DDT. The processor executes the bootloader and the flag recognition program. The bootloader loads the core device tree source file and obtains the component flag information of the DDT for the flag recognition program to read from the core device tree source file. The flag recognition program obtains the corresponding component environment parameters from the core device tree source file based on the component flag information of the DDT. The flag recognition program selects one of the component environment parameters as the target environment parameter. The bootloader performs environmental testing on the DDT using the target environment parameter and obtains the evaluation results generated by the environmental test. The bootloader generates operating environment information based on the target environment parameter and the corresponding evaluation results. The processing system for dynamically adjusting the hardware core during power-on provides a general-purpose core device tree source file. For developers, there is no need to repeatedly update or modify the core device tree source files. For electronic devices, existing core device tree source files can be used to ensure operation when the device is redesigned.

[0005] In some embodiments, the peripheral device under test returns response information to the bootstrap program upon a test call.

[0006] In some embodiments, the method for dynamically adjusting the hardware core during power-on includes the following steps: a bootloader loads a core device tree source file from memory, wherein the core device tree source file records multiple component flag information, and the component flag information has multiple component environment parameters; a flag recognition program obtains the component flag information of the peripheral component under test; the flag recognition program reads the core device tree source file from memory and obtains the component environment parameters of the component flag information from the core device tree source file; the flag recognition program selects one of the component environment parameters as the target environment parameter; the bootloader performs environmental testing on the peripheral component under test using the target environment parameter and obtains the evaluation results generated by the environmental test; the bootloader generates operating environment information based on the evaluation results of the target environment parameter.

[0007] In some embodiments, the step of reading the core device tree source file of the memory by the flag identification program to obtain the element environment parameters of the corresponding element flag information from the core device tree source file includes: the flag identification program sequentially selecting the target environment parameters according to the sorting result of the running intensity.

[0008] In some embodiments, the step of the bootstrap program performing environmental testing on the peripheral components under test with target environmental parameters and obtaining the evaluation results generated by the environmental test includes: the bootstrap program generating evaluation results based on the component environmental parameters.

[0009] The processing system and method for dynamically adjusting the hardware core during boot provides a universal core device tree source file. For developers, this eliminates the need to repeatedly update or modify the core device tree source file. For electronic devices, existing core device tree source files can be used and operation can be guaranteed even when the device is redesigned. The processing system can dynamically configure the environmental parameters of the peripheral components under test during boot without changing the existing hardware of the electronic device. Attached Figure Description

[0010] Figure 1 This is a schematic diagram of a processing system architecture that dynamically adjusts the hardware core during the boot process, as shown in one embodiment.

[0011] Figure 2 This is a schematic diagram of a method for dynamically adjusting the hardware core during the boot process, as shown in one embodiment.

[0012] Figure 3 This is a detailed flowchart illustrating the process of obtaining component environmental parameters for corresponding component flag information in one embodiment.

[0013] Figure 4 This is a schematic diagram of the component environmental parameters and target environmental parameters in one embodiment.

[0014] Figure 5This is a schematic diagram illustrating the operation flow of an environmental test of the peripheral components under test and the target environmental parameters, as shown in one embodiment.

[0015] Figure 6 This is a schematic diagram of a processing system architecture that dynamically adjusts the hardware core during the boot process, as shown in one embodiment.

[0016] Figure 7 This is a schematic diagram of a portion of the core device tree file in one embodiment.

[0017] The reference numerals in the attached figures are explained as follows:

[0018] 001: Processing System

[0019] 100: Memory

[0020] 110: Core Device Tree Source File

[0021] 120: Bootloader

[0022] 130: Flag Recognition Program

[0023] 131: Driver file

[0024] 132: Component Environmental Parameters

[0025] 133: Target environmental parameters

[0026] 141: Preset environmental parameters

[0027] 200: Peripheral components under test

[0028] 210: Component Flag Information

[0029] 300: Processor

[0030] 400: Storage unit

[0031] 411: Operating System

[0032] 412: Operating Environment Information

[0033] 414: Preset environmental parameters

[0034] S210~280, S310~S360, S341~S346: Steps Detailed Implementation

[0035] Please refer to Figure 1The diagram illustrates a processing system architecture for dynamically adjusting the hardware core during power-on, according to one embodiment. The processing system 001 for dynamically adjusting the hardware core during power-on includes a memory 100, at least one peripheral device under test (DUT) 200, a processor 300, and a storage unit 400. The processing system 001 can be applied to computers, servers, or embedded systems. The processor 300 is electrically connected to the memory 100, the DUT 200, and the storage unit 400.

[0036] The peripheral device under test (DUT) 200 can be, but is not limited to, a backplane, fan, sensor, connector, indicator light, or control chip. For example, the DUT 200 can be a Serial Peripheral Interface Bus (SPI), an Inter-Integrated Circuit (I-ICB), or a similar device. 2 C) Improved Inter-Integrated Circuit (I3C), Central Processing Unit (CPU), Dynamic Random Access Memory (DRAM), Media Access Control (MAC), or Physical Layer (PHY). Each peripheral device under test 200 has its own component flag information 210. The component flag information 210 can be used to identify newly added hardware components (i.e., peripheral devices under test 200).

[0037] The memory 100 stores the device tree source file 110, the bootloader 120, the flag identifier 130, and the driver file 131. The memory 100 can be non-volatile memory, a hard disk, or a solid-state drive, etc. In this embodiment, the device tree source file 110 is not limited to an uncompiled original file or a compiled object file. For example, a file with the extension ".dts" or a compiled file with the extension ".dtb" can both be considered as the device tree source file 110. The device tree source file 110 provides the kernel configuration for the bootloader 120, particularly the configuration of hardware components and parameters of the computing environment.

[0038] The core device tree source file 110 records at least one component flag information 210, and each component flag information 210 has multiple component environment parameters 132. The component environment parameters 132 record the relevant setting parameters of the peripheral component under test 200 during operation. For example, the component's operating clock, power consumption, memory bit width, memory bandwidth, or interrupt vector, etc. Different component environment parameters 132 correspond to their respective operating environments and parameters. The driver file 131 provides the interaction processing between the hardware component and the operating system 411. In order to distinguish between newly added hardware components and configured hardware components, the configured hardware components are called preset peripheral components (unlabeled), while the newly added hardware components are the peripheral components under test 200.

[0039] Storage unit 400 stores operating system 411 and runtime environment information 412. Operating system 411 provides the operating environment for processing system 001. Operating system 411 can be a Linux operating system, a UNIX operating system, or another BSD operating system. Runtime environment information 412 corresponds to the kernel configuration results of bootloader 120. If runtime environment information 412 is stored in storage unit 400, processor 300 will use runtime environment information 412 to perform booting of processing system 001 and configure the environment parameters of peripheral components.

[0040] If the storage unit 400 does not contain the runtime environment information 412, at the initial startup of the processing system 001, the processor 300 first executes the boot program 120 and checks for any newly added peripheral components 200 to be tested. The boot program 120 loads the core device tree source file 110 from the memory 100 and obtains the component flag information 210 from the core device tree source file 110. Next, the processor 300 executes the flag recognition program 130. The flag recognition program 130 obtains the corresponding component environment parameters 132 based on the component flag information 210. The flag recognition program 130 can be a standalone program or a sub-program embedded in the boot program 120; for example, the flag recognition program 130 can be the uboot library. The following is a clear explanation of the dynamic adjustment of the hardware core during the startup process; please refer to it. Figure 2 The diagram shown is a flowchart illustrating a method for dynamically adjusting the hardware core during the boot process, according to one embodiment. The method for dynamically adjusting the hardware core during boot includes the following steps:

[0041] Step S210: The bootloader loads the core device tree source file from memory;

[0042] Step S220: The bootloader determines whether the peripheral component under test is a newly added hardware component based on the component flag information;

[0043] Step S230: If the peripheral component under test is a newly added hardware component, the component flag information of the peripheral component under test is obtained by the flag recognition program;

[0044] Step S240: The flag recognition program reads the core device tree source file of the memory and obtains the component environment parameters of the component flag information from the core device tree source file;

[0045] Step S250: The file recognition program selects one of the component environment parameters as the target environment parameter;

[0046] Step S260: The program guides the surrounding components under test to perform environmental tests with target environmental parameters and obtains the evaluation results generated by the environmental tests;

[0047] Step S270: The bootloader generates runtime environment information based on the evaluation results of the target environment parameters; and

[0048] Step S280: If the peripheral component under test is not a newly added hardware component, the bootloader loads the driver file of the preset peripheral component.

[0049] First, the processing system 001 powers on, and the processor 300 executes the bootloader 120 and the flag recognition program 130. The bootloader 120 loads the core device tree source file 110 from the memory 100. The bootloader 120 retrieves all component flag information 210 from the core device tree source file 110. The bootloader 120 sends acknowledgment calls to the peripheral device under test 200 item by item according to the list of component flag information 210. When the peripheral device under test 200 receives the acknowledgment call, it will respond with information to the bootloader 120.

[0050] Therefore, the bootloader 120 can confirm that the peripheral device under test 200 is connected to the processor 300 based on the response information. The bootloader 120 can also determine whether the peripheral device under test 200 is a newly added hardware device. If the peripheral device under test 200 is a newly added hardware device, it will respond with information to the bootloader 120. If the peripheral device under test 200 is not a newly added hardware device (i.e., a pre-installed peripheral device), the pre-installed peripheral device will return other response information. The bootloader 120 loads the driver file 131 of the pre-installed peripheral device.

[0051] The peripheral component under test 200 transmits response information to the bootloader 120, which then transmits the component flag information 210 to the flag recognition program 130. Since the core device tree source file 110 includes multiple component environment parameters 132 of the component flag information 210, the flag recognition program 130 retrieves the corresponding component environment parameters 132 from the core device tree source file 110 based on the component flag information 210.

[0052] Therefore, the flag identification program 130 selects one of all component environment parameters 132, and the selected component environment parameter 132 becomes the target environment parameter 133. The flag identification program 130 transmits the target environment parameter 133 to the boot program 120. The boot program 120 performs an environmental test on the peripheral component 200 under test based on the target environment parameter 133 to determine whether the peripheral component 200 under test is suitable for the target environment parameter 133. Regardless of whether the peripheral component 200 under test passes the environmental test, the boot program 120 will obtain the evaluation result of this environmental test. The evaluation result records whether the peripheral component 200 under test passes or fails the environmental test. The boot program 120 generates operating environment information 412 based on the target environment parameter 133 and the corresponding evaluation result.

[0053] In some embodiments, each component environment parameter 132 has its own operating strength. Operating strength can be, but is not limited to, the component's operating clock, power consumption, memory bit width, or memory bandwidth. The process of the flag identification program 130 reading the core device tree source file 110 of the memory 100 to obtain the component environment parameter 132 of the corresponding component flag information 210 also includes the following steps, please refer to... Figure 3 As shown:

[0054] Step S310: Sort all component environmental parameters according to operating intensity;

[0055] Step S320: The flag recognition program selects the target environmental parameters in order of the ranking results of the running intensity;

[0056] Step S330: The bootloader generates evaluation results based on the component's environmental parameters;

[0057] Step S340: The bootstrap program determines whether the evaluation result is successful or unsuccessful;

[0058] Step S350: If the target environment parameter fails, the flag recognition program selects the next-highest component environment parameter as the new target environment parameter based on the ranking result of the running intensity; and

[0059] Step S360: If the target environment parameters are successful, the bootloader instructs the flag recognition program to stop selecting new component environment parameters.

[0060] First, the bootloader 120 sorts all component environment parameters 132 according to their operating intensity, in descending order of power. Each component environment parameter 132 records at least one operating parameter; different combinations of operating parameters affect the performance of the peripheral device under test (DUT) 200. Generally, higher operating intensity results in higher performance for the DUT 200, and vice versa. Operating intensity can be determined by any operating parameter of the DUT 200 or specified by the developer. For example, if the operating parameter is the clock speed, a high clock speed corresponds to high operating intensity, while a low clock speed corresponds to low operating intensity.

[0061] Please refer to Figure 4 As shown, it is a schematic diagram of the component environmental parameters and corresponding operating intensity of one embodiment. Figure 4 The top side contains the component flag information 210 of the core device tree source file 110, the component environmental parameters 132, and the operating intensity. Figure 4 The bottom side shows the results sorted by operating intensity in descending order. Flag recognition program 130 selects from component environmental parameters 132 in descending order based on the sorting results of operating intensity. Flag recognition program 130 considers the selected component environmental parameters 132 as the target environmental parameter 133 (corresponding to...). Figure 4 The target environment parameter 133 is sent to the bootloader 120 via a dashed box. The bootloader 120 then performs environmental testing on the peripheral components under test using the target environment parameter 133. The bootloader 120 determines the test result as either success or failure.

[0062] During the environmental testing of the peripheral device under test 200 (corresponding to step S340), the bootloader 120 will send test calls to the peripheral device under test 200 in a time-sharing and multiple-time manner. In other words, the bootloader 120 will send test calls to the peripheral device under test 200 at fixed time intervals within a certain time period to confirm whether the peripheral device under test 200 is still in an operational state. If the peripheral device under test 200 is still in an operational state, the peripheral device under test 200 will return a response message to the bootloader 120 according to the test call. The bootloader 120 can determine whether the target environmental parameter 133 is compatible with the peripheral device under test 200 based on whether there is a response message and the number of response messages. Please cooperate. Figure 5 As shown.

[0063] Step S341: The bootloader sends a test call to the peripheral device under test;

[0064] Step S342: Determine whether the response message exceeds the response time;

[0065] Step S343: If the response information does not exceed the response time, determine whether the number of responses exceeds the threshold number;

[0066] Step S344: If the number of responses is greater than or equal to the threshold number, the bootstrap program records the target environment parameters;

[0067] Step S345: If the number of responses is less than the threshold number, check whether the number of calls sent by the bootstrap program exceeds the upper limit;

[0068] Step S346: Select new target environment parameters; and

[0069] Step S347: If the response information exceeds the response time, proceed to step S345.

[0070] First, the bootloader 120 selects any target environment parameter 133 and makes a test call to the peripheral device under test 200. The bootloader 120 counts the number of responses from the peripheral device under test 200 and the number of test calls sent, and times the response time. After sending the test call, the bootloader 120 times whether the response time for receiving the response information has expired. If the peripheral device under test 200 sends a response information after the response time has expired, the bootloader 120 will also consider this response information invalid. If the bootloader 120 receives a response information within the response time, the bootloader 120 will determine whether the number of responses to the test call is greater than or equal to a threshold number.

[0071] If the number of responses from the peripheral component under test 200 is greater than or equal to the set threshold number, the bootstrap procedure 120 determines that the peripheral component under test 200 matches the target environment parameters 133. If the number of responses from the peripheral component under test 200 is less than the set threshold number, it may be because the number of responses to the test call has not yet reached the upper limit. The bootstrap procedure 120 will continue to send test calls to the peripheral component under test 200. If the number of responses from the peripheral component under test 200 is less than the set threshold number and the number of calls has reached the upper limit, the bootstrap procedure 120 will determine that the peripheral component under test 200 does not match the target environment parameters 133.

[0072] For example, the bootloader 120 can send three test calls to the peripheral device under test (PDT) 200 in a time-sharing manner, with a threshold of two calls. If the PDT 200 responds twice, the bootloader 120 determines that the PDT 200 matches the target environment parameters 133. If the PDT 200 responds once, the bootloader 120 determines that the PDT 200 does not match the target environment parameters 133. Furthermore, as mentioned earlier, if the PDT 200's response exceeds the response time, the bootloader will not record this response in the response count. Therefore, the bootloader 120 can determine whether the target environment parameters 133 are suitable for the operation of the PDT 200 based on the response status of the response information.

[0073] After the bootstrap program 120 completes the testing of the target environmental parameter 133 and the peripheral component under test 200, the bootstrap program 120 selects the component environmental parameter 132 with the highest operating intensity from the remaining component environmental parameters 132 as the new target environmental parameter 133. The bootstrap program 120 repeats the aforementioned environmental test on the newly selected target environmental parameter 133 and obtains the corresponding evaluation results. In addition to selecting the matching component environmental parameter 132 from the evaluation results of all component environmental parameters 132, the bootstrap program 120 can also select the matching component environmental parameter 132 from the operating intensity. The aforementioned matching environmental parameter corresponds to the peripheral component under test 200 being able to operate normally under the target environmental parameter 133. On the other hand, the bootstrap program 120 can select the largest number of responses from the set as the component environmental parameter 132 matching the peripheral component under test 200. The bootstrap program 120 records the matching component environmental parameter 132 in the operating environment information 412.

[0074] If more than one new peripheral component exists in the processing system 001, after the bootloader 120 completes the current peripheral component 200 under test and the operating environment information 412, the bootloader 120 selects a new peripheral component 200 under test from the other peripheral components. The bootloader 120 performs environmental tests on the newly selected peripheral component 200 using the aforementioned component environment parameter 132, and records the evaluation results in the operating environment information 412. The bootloader 120 repeats steps S341 to S347 until the relevant evaluations of all newly added peripheral components are completed.

[0075] In one embodiment, the core device tree source file 110 further includes preset environmental parameters 141, and the component flag information 210 has preset environmental parameters 141. Please refer to... Figure 6 The diagram shows a schematic of a processing system architecture that dynamically adjusts the hardware core during the boot process of an embodiment. If all component environment parameters 132 fail the environment test, the flag recognition program 130 transmits the preset environment parameters 141 to the boot program 120. The boot program 120 records the preset environment parameters 141 in the runtime environment information 412.

[0076] In one embodiment, after the bootloader 120 completes the processing of the runtime environment information 412, the processor 300 executes the operating system 411. The operating system 411 reads the runtime environment information 412 from the storage unit 400. The operating system 411 identifies the corresponding peripheral device under test 200 based on the runtime environment information 412, so that the operating system 411 can directly call the peripheral device under test 200. The operating system 411 does not need to retest each peripheral device under test 200 from the core device tree source file 110.

[0077] When the system 001 boots up, in addition to reading the runtime environment information 412, the bootloader 120 can also transmit the runtime environment information 412 to the operating system 411 via the kernel command line. This saves the operating system 411 the time spent reading the runtime environment information 412 from the storage unit 400.

[0078] To clearly illustrate the operation of this embodiment, please refer to... Figure 7 As shown, it is a schematic diagram of part of the core device tree file of an embodiment. Figure 7 The above is the core device tree file 100, which contains some parameters of I2C. The flag recognition program 130 obtains the corresponding component environment parameters 132 based on the component flag information 210 in the core device tree file 100. Figure 7 Below is component environmental parameter 132 for component flag information 210.

[0079] The dashed box in the core device tree file 100 represents component flag information 210, but is not limited to this example. After the flag recognition program 130 obtains the component flag information 210, the bootloader 120 selects frequency "800000" from the component environment parameters 132 as the target environment parameter 133 for the first test. If the bootloader 120 fails to perform the environment test at frequency "800000", the bootloader 120 changes the frequency to "400000" as the new target environment parameter 133, until a successful target environment parameter 133 is obtained.

[0080] The processing system and method for dynamically adjusting the hardware core during startup provides a general-purpose core device tree source file 110. For developers, this eliminates the need to repeatedly update or modify the core device tree source file 110. For electronic devices, existing core device tree source files 110 can be used during device redesigns to ensure continued operation. The processing system 001 can dynamically configure the environmental parameters of the peripheral component 200 under test during startup without requiring changes to the existing hardware of the electronic device.

Claims

1. A processing system for dynamically adjusting the hardware core during the boot process, characterized in that, include: A memory stores a core device tree source file, a boot program and a flag identification program. The core device tree source file records a component flag information and the component flag information has multiple component environment parameters. A peripheral component to be tested, which has the component's flag information; as well as A processor, electrically connected to the memory and the peripheral device under test (PDT), executes a bootloader and a flag identification program. The bootloader loads a core device tree source file and obtains the component flag information of the DDT for the flag identification program to read from the core device tree source file. The flag identification program obtains the corresponding component environment parameters from the core device tree source file based on the component flag information of the DDT. The flag identification program selects one of the component environment parameters as a target environment parameter. The bootloader performs an environmental test on the DDT using the target environment parameter and obtains an evaluation result from the environmental test. The bootloader generates operating environment information for configuring the operating environment of the DDT based on the target environment parameter and the corresponding evaluation result, wherein the operating environment information records the component environment parameters that match the DDT.

2. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 1, characterized in that, The flag recognition program selects the target environmental parameter from the component environmental parameters based on an operating intensity of the component environmental parameters.

3. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 1, characterized in that, When the bootloader performs environmental testing on the device under test based on each target environmental parameter, the bootloader sends a test call to the device under test.

4. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 3, characterized in that, The peripheral device under test returns a response message to the bootstrap program in response to the test call.

5. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 1, characterized in that, The core device tree source file also includes a preset environmental parameter, and the component flag information has the preset environmental parameter.

6. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 1, characterized in that, When the processor executes the bootloader, the bootloader loads the runtime environment information from a storage unit.

7. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 6, characterized in that, The processor executes an operating system for the storage unit, the operating system loads the operating environment information, and the operating system identifies the corresponding peripheral components under test based on the operating environment information.

8. A method for dynamically adjusting the hardware core during the boot process, characterized in that, include: A core device tree source file is loaded from a memory by a bootloader, wherein the core device tree source file records multiple component flag information, and the component flag information has multiple component environment parameters; A flag recognition program obtains the flag information of a peripheral component under test. The flag identification program reads the core device tree source file of the memory and obtains the component environment parameters of the component flag information from the core device tree source file; The flag recognition program selects one of the component environmental parameters as a target environmental parameter; The bootstrap program performs an environmental test on the component under test using the target environmental parameters, and obtains an evaluation result from the environmental test; and The bootloader generates operating environment information for configuring the operating environment of the peripheral component under test based on the evaluation results of the target environment parameters, wherein the operating environment information records the component environment parameters that match the peripheral component under test.

9. The method for dynamically adjusting the hardware core during the boot process as described in claim 8, characterized in that, The steps of reading the core device tree source file of the memory by the flag identification program and obtaining the component environment parameters corresponding to the component flag information from the core device tree source file include: The component environmental parameters are sorted according to the operating intensity of each component environmental parameter.

10. The method for dynamically adjusting the hardware core during the boot process as described in claim 9, characterized in that, The step of selecting one of the component environmental parameters as the target environmental parameter in the flag identification procedure includes: The flag recognition program selects the target environmental parameters in order based on the ranking results of the operational intensity.

11. The method for dynamically adjusting the hardware core during the boot process as described in claim 10, characterized in that, The steps of the bootstrap procedure to perform environmental testing on the component under test with the target environmental parameters and obtain the evaluation results generated by the environmental test include: The bootloader generates the evaluation results based on the component's environmental parameters.

12. The method for dynamically adjusting the hardware core during the boot process as described in claim 11, characterized in that, The steps in the flag recognition program to select the target environmental parameter sequentially based on the ranking results of each operational intensity include: The bootstrap procedure determines whether the evaluation result is successful or unsuccessful. If the target environment parameter fails, the flag recognition program selects the next highest environmental parameter of the component as the new target environment parameter based on the ranking result of the operational intensity; and If the target environment parameter is successful, the bootloader instructs the flag recognition program to abort the selection of a new component environment parameter.

13. The method for dynamically adjusting the hardware core during the boot process as described in claim 12, characterized in that, The steps of the guiding program to perform environmental testing on the component under test based on the target environmental parameters and obtain the evaluation results of the component under test corresponding to the target environmental parameters include: The bootloader sends a test call to the peripheral device under test; and The peripheral device under test returns a response message to the bootstrap program in response to the test call.

14. The method for dynamically adjusting the hardware core during the boot process as described in claim 10, characterized in that, The step of loading the core device tree source file into the memory by the bootloader includes: The bootloader determines whether the runtime environment information exists in a storage unit; and If the storage unit contains the runtime environment information, the bootloader loads the runtime environment information.

15. The method for dynamically adjusting the hardware core during the boot process as described in claim 14, characterized in that, The step of loading the core device tree source file into the memory by the bootloader includes: Execute an operating system; The operating system loads the runtime environment information from the storage unit; and The operating system identifies the corresponding peripheral components to be tested based on the operating environment information.

Images