TW202326428A - Processing system and method of dynamic adjust hardware kernel in booting - Google Patents

Abstract

A processing system and method of dynamic adjust hardware kernel in booting is provided. The processing method comprises steps. Loading a DTS file from a memory by a bootloader. Fetching a flag information of a testing unit by a flag identify process. The flag identify process reads the DTS file in the memory and the flag identify process fetch an environment parament form the DTS file according to the flag information. The flag identify process select an object parament form the environment parament. The bootloader perform an environment testing according to the object parament and the testing unit, and obtains a testing result of the environment testing. The bootloader generates an environment information according to the testing result of the environment testing.

Description

Processing system and method for dynamically adjusting hardware core during startup

The invention relates to a processing system and method for a computer hardware core, in particular to a processing system and method for dynamically adjusting the hardware core during startup.

For computer devices, the environmental configuration of hardware components is an important issue. With the diversification of hardware components, computer devices also need to update the configuration settings of the kernel (kernel) in real time. When the computer device is turned on, the bootloader of the computer will invoke the aforementioned configuration setting file.

The configuration setting file will record the corresponding environmental parameters from the CPU, bus and peripheral components. In order to facilitate the writing of configuration configuration files, the development company proposes a development mechanism of the hardware configuration of the core device tree source. Developers can determine the purpose of adding, changing or removing peripheral components through adding, modifying or deleting core device tree source files. Due to the increase in the number and types of peripheral components, the compilation of the core device tree source is also becoming more and more complicated.

In view of this, in some embodiments, the processing system that dynamically adjusts the hardware core during booting includes a memory, peripheral components to be tested, and a processor. The memory stores the core device tree source file, the boot program and the flag identification program. The core device tree source file records multiple component flag information and each component flag information has multiple component environment parameters; the peripheral components to be tested have component flags Flag information; the processor is electrically connected to the memory and the peripheral components to be tested, the processor executes the boot program and the flag recognition program, the boot program loads the core device tree source file, and the boot program obtains the component flag information of the peripheral components to be tested , for the flag recognition program to read the core device tree source file. The flag recognition program obtains the corresponding component environment parameters from the core device tree source file according to the component flag information of the peripheral components to be tested. The flag recognition program obtains the corresponding component environment parameters from the core device tree source file. One of the component environment parameters is selected as the target environment parameter, and the guide program uses the target environment parameter to perform an environmental test on the surrounding components to be tested, and obtains the evaluation results generated by the environment test, and the guide program generates an operating environment according to the target environment parameters and the corresponding evaluation results. Information. A processing system that dynamically adjusts hardware cores during boot provides a generic core device tree source file. For the developer, the developer does not need to repeatedly update or modify the core device tree source file. For electronic equipment, the existing core device tree source file can also be used to ensure its operation when the electronic equipment is revised.

In some embodiments, the peripheral device under test returns a response message to the bootstrap program according to the test call.

In some embodiments, the processing method for dynamically adjusting the hardware core during boot process includes the following steps: loading the core device tree source file from the memory by the boot program, wherein the core device tree source file records a plurality of component flags information, the component flag information has multiple component environment parameters; the component flag information of the peripheral components to be tested is obtained by the flag recognition program; the core device tree source file of the memory is read by the flag recognition program, and the core device tree source The file obtains the component environment parameters of the component flag information; the flag recognition program selects one of the component environment parameters as the target environment parameter; the guide program uses the target environment parameters to perform environmental tests on the surrounding components to be tested, and obtains the environment test results evaluation results; the bootstrap program generates operating environment information according to the evaluation results of the target environment parameters.

In some embodiments, the step of reading the core device tree source file of the memory by the flag recognition program to obtain the component environment parameters of the corresponding component flag information from the core device tree source file includes the flag recognition program according to The sorting results of the operating intensity sequentially select the target environmental parameters.

In some embodiments, after the boot program conducts environmental tests on the surrounding components to be tested with target environmental parameters, the step of obtaining the evaluation results generated by the environmental tests includes guiding the program to generate evaluation results according to the component environmental parameters.

The processing system and method for dynamically adjusting the hardware core during the startup process provides a general-purpose core device tree source file. For the developer, the developer does not need to repeatedly update or modify the core device tree source file. For electronic equipment, the existing core device tree source file can also be used to ensure operation when the electronic equipment is revised. The processing system can dynamically configure the environmental parameters of the surrounding components to be tested when the device is turned on without changing the relevant hardware of the existing electronic equipment.

Please refer to FIG. 1 , which is a schematic diagram of a processing system architecture for dynamically adjusting hardware cores during booting according to an embodiment. The processing system 001 for dynamically adjusting the hardware core during booting includes a memory 100 , at least one peripheral component to be tested 200 , a processor 300 and a storage unit 400 . The processing system 001 can be applied in computers, servers or embedded systems. The processor 300 is electrically connected to the memory 100 , the peripheral components to be tested 200 and the storage unit 400 .

The peripheral component 200 to be tested can be, but not limited to, a backplane, a fan, a sensor, a connection port, a signal light, or a control chip. For example: the peripheral component 200 to be tested may be a Serial Peripheral Interface Bus (SPI for short), an Inter-Integrated Circuit (I²C for short), an Improved Inter Integrated Circuit (I²C) , I3C), central processing unit (Central Processing Unit, CPU), dynamic memory (Dynamic Random Access Memory, DRAM), media access controller (Media Access Control, MAC) or physical layer connection (Physical Layer, PHY). Each peripheral device 200 to be tested has its own device flag information 210 . The component flag information 210 can be used to identify the newly added hardware component (that is, the peripheral component to be tested 200).

The memory 100 stores a core device tree source file 110 (Device Tree Source), a boot program 120 (boot loader), a flag recognition program 130 and a driver file 131 (driver). The memory 100 may be a non-volatile memory 100 (Non-Volatile Memory), a hard disk (Hard Disk) or a solid-state disk (Solid-state drive) and the like. In this embodiment, the core device tree source file 110 is not limited to an uncompiled original file or a compiled target file. For example, a compiled file with the suffix extension “dts” or a compiled file with the suffix extension “dtb” can be regarded as the core device tree source file 110 . The kernel device tree source file 110 provides the kernel configuration of the boot program 120 , especially the configuration of hardware components and parameters of the computing environment.

The core device tree source file 110 records at least one component flag information 210 , and each component flag information 210 has a plurality of component environment parameters 132 . The component environment parameter 132 records related setting parameters when the peripheral component 200 to be tested operates. For example: operating clock, power consumption, memory bit width, memory bandwidth, or interrupt vector (interrupt) of components. Different component environment parameters 132 correspond to respective operating environments and parameters. The driver file 131 provides interactive processing between hardware components and the operating system 411 . In order to distinguish the newly added hardware components from the configured hardware components, the configured hardware components are called default peripheral components (without labels), and the newly added hardware components are the peripheral components to be tested 200.

The storage unit 400 stores the operating system 411 and the operating environment information 412 . The operating system 411 provides an operating environment for the processing system 001 . The type of operating system 411 is Linux operating system, UNIX operating system or other BSD operating systems. The operating environment information 412 corresponds to the kernel configuration result of the boot program 120 . If the storage unit 400 stores the operating environment information 412, the processor 300 will start the processing system 001 and configure the environmental parameters of peripheral components according to the operating environment information 412.

If the storage unit 400 does not store the operating environment information 412 , when the processing system 001 is initially powered on, the processor 300 will first execute the boot program 120 and detect whether there is an additional peripheral component 200 to be tested. The boot program 120 loads the core device tree source file 110 from the memory 100 , boots the program 120 and obtains the component flag information 210 of the core device tree source file 110 . Next, the processor 300 executes the flag identification program 130 . The flag recognition program 130 obtains the corresponding component environment parameters 132 according to the component flag information 210 . The flag recognition program 130 can be an independent program or a subprogram embedded in the boot program 120 , for example, the flag recognition program 130 can be a uboot library. The following is a clear description of the operation process of dynamically adjusting the hardware core during the boot process. Please also refer to FIG. 2 , which is a schematic flowchart of a processing method for dynamically adjusting the hardware core during the boot process of an embodiment. The processing method for dynamically adjusting the hardware core during the boot process includes the following steps: Step S210: loading the core device tree source file from the memory by the boot program; Step S220: the boot program determines whether the peripheral component to be tested is a newly added hardware component according to the component flag information; Step S230: if the peripheral component to be tested is a newly added hardware component, the component flag information of the peripheral component to be tested is obtained by the flag recognition program; Step S240: read the core device tree source file of the memory by the flag recognition program, and obtain the component environment parameters of the component flag information from the core device tree source file; Step S250: the flag recognition program selects one of the component environment parameters as the target environment parameter; Step S260: guide the program to perform an environmental test on the surrounding components to be tested with the target environmental parameters, and obtain the evaluation results generated by the environmental test; Step S270: the boot program generates operating environment information according to the evaluation results of the target environment parameters; and Step S280: If the peripheral component to be tested is not a new hardware component, the boot program loads the driver file of the default peripheral component.

First, the processing system 001 is powered on, and the processor 300 executes the boot program 120 and the flag identification program 130 . The boot program 120 loads the core device tree source file 110 from the memory 100 . The bootloader 120 obtains all component flag information 210 from the core device tree source file 110 . The boot program 120 sends confirmation calls to the peripheral components 200 to be tested item by item according to the list of component flag information 210 . When the peripheral device 200 to be tested receives the confirmation call, the peripheral device 200 to be tested will respond a message to the boot program 120 .

Therefore, the boot program 120 can confirm that the peripheral component 200 to be tested has been connected to the processor 300 according to the response message, and the boot program 120 can also determine whether the peripheral component 200 to be tested is a new hardware component. If the peripheral component 200 to be tested is a newly added hardware component, the peripheral component 200 to be tested will respond a message to the boot program 120 . If the peripheral component 200 to be tested is not a newly added hardware component (that is, a default peripheral component), the default peripheral component will return a response message with other contents. The boot program 120 loads the driver file 131 of the default peripheral components.

The peripheral component 200 to be tested sends a response message to the boot program 120 , and the boot program 120 sends the device flag information 210 to the flag recognition program 130 . Because the core device tree source file 110 includes a plurality of component environment parameters 132 of the component flag information 210 . The flag recognition program 130 obtains the corresponding component environment parameter 132 from the core device tree source file 110 according to the component flag information 210 .

Therefore, the flag recognition program 130 selects one of all the component environment parameters 132 , and the selected component environment parameter 132 is the target environment parameter 133 . The flag recognition 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 to be tested according to the target environment parameter 133 , so as to determine whether the peripheral component 200 to be tested is suitable for the target environment parameter 133 . Regardless of whether the peripheral component 200 to be tested passes the environmental test or not, the boot program 120 will obtain the evaluation result of the environmental test. The evaluation result records whether the peripheral element 200 to be tested passes the environmental test or fails the environmental test. The boot program 120 generates the operating environment information 412 according to the target environment parameters 133 and corresponding evaluation results.

In some embodiments, each component environment parameter 132 has a respective operating intensity. The operating strength can be but not limited to the operating clock, power consumption, memory bit width or memory bandwidth of the device. The flag recognition program 130 reads 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, and further includes the following steps, as shown in FIG. 3 : Step S310: Sorting all component environmental parameters according to the operating intensity; Step S320: the flag recognition program sequentially selects the target environment parameters according to the sorting results of the operation intensity; Step S330: the boot program generates an evaluation result according to the component environment parameters; Step S340: the boot program judges whether the evaluation result is success or failure; Step S350: If the target environment parameter is failure, the flag recognition program selects the next component environment parameter as the new target environment parameter according to the ranking result of the operation intensity; and Step S360: If the target environment parameter is successful, the boot program makes the flag recognition program stop selecting new component environment parameters.

Firstly, the boot program 120 sorts all the component environment parameters 132 according to the operating intensity, and here the operating intensity is sorted in a descending power manner. At least one operating parameter is recorded in the component environment parameter 132 , and different combinations of operating parameters will affect the operating performance of the peripheral component 200 to be tested. Generally speaking, the higher the operating intensity, the higher the operating efficiency of the peripheral component 200 to be tested, and vice versa. The operating intensity may be determined by any operating parameter of the peripheral device 200 to be tested, or specified by the developer. For example, if the operating parameter is the operating clock, a high operating clock corresponds to a high operating intensity, and a low operating clock corresponds to a low operating intensity.

Please refer to FIG. 4 , which is a schematic diagram of component environmental parameters and corresponding operating intensity in an embodiment. The upper side of FIG. 4 shows the component flag information 210 of the core device tree source file 110 , the associated component environment parameters 132 and the operating strength. The bottom side of Figure 4 shows the results sorted by descending power according to the operation intensity. The flag recognition program 130 selects from the component environment parameters 132 in order from high to low according to the sorting result of the operation intensity. The flag recognition program 130 regards the selected component environment parameter 132 as a target environment parameter 133 (corresponding to the dashed box in FIG. 4 ), and sends the target environment parameter 133 to the boot program 120 . Next, the boot program 120 conducts an environmental test on the peripheral element 200 to be tested with the target environmental parameters 133 . The bootstrap program 120 judges the evaluation result as success or failure.

During the environmental test of the peripheral device 200 under test (corresponding to step S340 ), the boot program 120 will send a test call to the peripheral device 200 under test in a time-division and multiple times manner. In other words, the boot program 120 will send a test call to the peripheral device 200 to be tested at a fixed time interval in a period of time, so as to confirm whether the peripheral device 200 to be tested is still in the operating state. If the peripheral device 200 to be tested is still in the operating state, the peripheral device 200 to be tested will return a response message to the boot program 120 according to the test call. The boot program 120 can determine whether the target environment parameter 133 matches the peripheral component 200 to be tested according to whether there is a response message and the number of response messages, as shown in FIG. 5 . Step S341: the boot program sends a test call to the peripheral component to be tested; Step S342: determine whether the response message exceeds the response time; Step S343: If the current response message does not exceed the response time, determine whether the response times are greater than the threshold times; Step S344: if the number of responses is greater than or equal to the threshold number, the boot program records the target environment parameters; Step S345: If the number of responses is less than the threshold number, whether the boot program counts and sends the number of calls exceeds the upper limit; Step S346: selecting new target environment parameters; and Step S347: If the current response message exceeds the response time, execute step S345.

Firstly, the boot program 120 selects any target environment parameter 133 and makes a test call to the peripheral element 200 to be tested. The boot program 120 will respectively count the number of responses and the number of test calls sent by the peripheral component 200 to be tested, and time the response time. After the pilot program 120 sends the test call, it will count whether the response time for receiving the response message is overtime. If the peripheral component 200 under test sends the response message after the response time, the boot program 120 also regards the response message as invalid. If the guiding program 120 receives the response message within the response time, the guiding program 120 will determine whether the response times of the test call are greater than or equal to the threshold times.

If the response times of the peripheral component 200 to be tested are greater than or equal to the set threshold times, the boot program 120 determines that the peripheral component 200 to be tested matches the set of target environment parameters 133 . If the response times of the peripheral component 200 to be tested are less than the set threshold times, it may be that the response times of the test call has not reached the upper limit. The bootstrap program 120 will continue to send the test call to the peripheral device 200 to be tested. If the response times of the peripheral component 200 to be tested are less than the set threshold and the call times reach the upper limit, the boot program 120 will determine that the peripheral component 200 to be tested does not match the set of target environment parameters 133 .

For example, the boot program 120 can send "three" test calls to the peripheral component 200 to be tested in a time-sharing manner, and the threshold number of times is "twice". If the response times of the peripheral component 200 to be tested are "twice" , the guide program 120 determines that the peripheral element 200 to be tested matches the set of target environment parameters 133 . If the response times of the peripheral component 200 to be tested is “one time”, the boot program 120 determines that the peripheral component 200 to be tested does not match the set of target environment parameters 133 . And as mentioned above, if the response message of the peripheral component 200 to be tested exceeds the response time, the boot program 120 will not record the response message in the response times. Therefore, the boot program 120 can judge whether the set of target environment parameters 133 conforms to the operation of the peripheral component 200 to be tested according to the response state of the response message.

After the boot program 120 completes the aforementioned testing of the target environment parameter 133 and the surrounding component 200 to be tested, the boot program 120 selects the component environment parameter 132 with the highest operating intensity from the remaining component environment parameters 132 as the new target environment parameter 133 . The boot program 120 repeats the aforementioned environmental test on the newly selected target environment parameter 133 and obtains corresponding evaluation results. In addition to selecting the matching component environment parameters 132 from the evaluation results of all component environment parameters 132 , the bootstrap program 120 can also select the matching component environment parameters 132 from the operation intensity. The aforementioned matched environmental parameters correspond to the above-mentioned peripheral element 200 to be tested can operate normally under the target environmental parameters 133 . On the other hand, the guidance program 120 may select the largest element environment parameter 132 matched with the surrounding element 200 to be tested from the set of response times. The boot program 120 records the matched component environment parameters 132 into the operating environment information 412 .

If there is more than one new peripheral component in the processing system 001, after the boot program 120 completes the current peripheral component 200 to be tested and the operating environment information 412, the boot program 120 selects a new peripheral component 200 to be tested from other peripheral components. The boot program 120 performs the environmental test of the aforementioned component environmental parameters 132 on the newly selected peripheral components 200 to be tested, and records the evaluation results into the operating environment information 412 . The bootstrap program 120 repeats steps S341 - S347 until the relevant evaluation of all newly added peripheral components is completed.

In one embodiment, the core device tree source file 110 further includes a default environment parameter 414 , and the component flag information 210 has the default environment parameter 414 . Please refer to FIG. 6 , which is a schematic diagram of a processing system architecture for dynamically adjusting hardware cores during a boot process according to an embodiment. If all the component environment parameters 132 fail the environment test, the flag recognition program 130 transmits the default environment parameters 414 to the boot program 120 . The boot program 120 records the default environment parameter 414 into the operation environment information 412 .

In one embodiment, after the boot program 120 finishes processing the operating environment information 412 , the processor 300 executes the operating system 411 . The operating system 411 reads the operating environment information 412 of the storage unit 400 . The operating system 411 identifies the corresponding peripheral device 200 to be tested according to the operating environment information 412 , so that the operating system 411 can directly invoke the peripheral device 200 to be tested. The operating system 411 does not need to retest each peripheral device 200 to be tested from the core device tree source file 110 .

When the processing system 001 is booted, besides reading the operating environment information 412 , the boot program 120 can also transmit the operating environment information 412 to the operating system 411 through a kernel command line. The operating system 411 can save the time of reading the operating environment information 412 from the storage unit 400 .

In order to clearly illustrate the operation of this embodiment, please refer to FIG. 7 , which is a schematic diagram of part of the content of the core device tree source file of an embodiment. The upper part of FIG. 7 is the core device tree source file 110 which is part of the parameters of I2C. The flag recognition program 130 obtains the corresponding component environment parameters 132 according to the component flag information 210 in the core device tree source file 110 . The lower part of FIG. 7 is the component environment parameter 132 of the component flag information 210 .

The dotted box of the core device tree source file 110 represents the component flag information 210, but it is not limited to this example. After the flag recognition program 130 obtains the component flag information 210 , the boot program 120 selects the frequency “800000” from the component environment parameters 132 as the target environment parameter 133 for the first test. If the boot program 120 fails to execute the environmental test with the frequency "800000", then the boot program 120 reselects the frequency "400000" as the new target environment parameter 133 until a successful target environment parameter 133 is obtained.

The processing system and method for dynamically adjusting the hardware core during the boot process provides a general-purpose core device tree source file 110 . For the developer, the developer does not need to repeatedly update or modify the core device tree source file 110 . For electronic equipment, the existing core device tree source file 110 can also be used when the electronic equipment is updated, and the long-term operation can also be guaranteed. The processing system 001 can dynamically configure the environmental parameters of the peripheral components 200 to be tested when starting up without changing the relevant hardware of the existing electronic equipment.

001: Processing system 100: memory 110: Core device tree source file 120: bootloader 130:Flag recognition program 131: Driver file 132: Component environment parameters 133: target environment parameters 200: Peripheral components to be tested 210: Component flag information 300: Processor 400: storage unit 411: operating system 412: Operational environment information 414: Preset environment parameters S210~280, S310~S360, S341~S347: steps

[ FIG. 1 ] is a schematic diagram of an embodiment of a processing system architecture for dynamically adjusting hardware cores during booting. [ FIG. 2 ] is a schematic flow chart of a processing method for dynamically adjusting hardware cores during boot process according to an embodiment. [ FIG. 3 ] is a detailed flowchart of obtaining component environment parameters corresponding to component flag information according to an embodiment. [ FIG. 4 ] is a schematic diagram of component environment parameters and corresponding operating intensity of an embodiment. [ FIG. 5 ] is a schematic diagram of the operation flow of the environmental testing of the peripheral components to be tested and the target environmental parameters according to an embodiment. [ FIG. 6 ] is a schematic diagram of an embodiment of a processing system architecture for dynamically adjusting hardware cores during booting. [ FIG. 7 ] is a schematic diagram of partial content of a core device tree source file in an embodiment.

001: Processing system

100: memory

110: Core device tree source file

120: bootloader

130:Flag recognition program

131: Driver file

132: Component environment parameters

200: Peripheral components to be tested

210: Component flag information

300: Processor

400: storage unit

411: operating system

412: Operational environment information

Claims (15)

A processing system for dynamically adjusting hardware cores during startup, comprising: a memory storing 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 a plurality of component environment parameters; A peripheral component to be tested has flag information of the component; and A processor, electrically connected to the memory and the peripheral component to be tested, the processor executes the boot program and the flag recognition program, the boot program loads the core device tree source file, and the boot program obtains the waiting program The component flag information of the peripheral component to be tested is used for the flag identification program to read the core device tree source file, and the flag identification program reads the core device tree source file from the core device tree source file according to the component flag information of the peripheral component to be tested obtain the corresponding component environment parameters, the flag identification program selects one of the component environment parameters as a target environment parameter, and the boot program uses the target environment parameter to perform an environment test on the peripheral component to be tested, An evaluation result generated by the environment test is acquired, and the boot program generates operating environment information according to the target environment parameter and the corresponding evaluation result. In the processing system for dynamically adjusting hardware cores during boot process as described in Claim 1, wherein the flag identification program selects the target environment parameter from the component environment parameters according to an operation intensity of the component environment parameter. The processing system for dynamically adjusting the hardware core during the boot process as described in claim 1, wherein when the boot program performs the environmental test on the peripheral component to be tested according to each target environmental parameter, the boot program sends to the peripheral to be tested The component sends a test call. In the processing system for dynamically adjusting the hardware core during the booting process as described in claim 3, wherein the peripheral component to be tested returns a response message to the boot program according to the test call. In the processing system for dynamically adjusting hardware cores during booting as described in Claim 1, wherein the core device tree source file further includes a default environment parameter, and the component flag information has the default environment parameter. In the processing system for dynamically adjusting hardware cores during boot process as described in claim 1, when the processor executes the boot program, the boot program loads the operating environment information from a storage unit. The processing system that dynamically adjusts the hardware core during the boot process as described in claim 6, wherein the processor executes an operating system of the storage unit, the operating system loads the operating environment information, and the operating system is based on the operating environment information Identify the corresponding peripheral elements to be tested. A processing method for dynamically adjusting hardware cores during startup, comprising: loading a core device tree source file from a memory by a boot program, wherein the core device tree source file records a plurality of component flag information, and the component flag information has a plurality of component environment parameters; Obtaining the component flag information of a peripheral component to be tested by a flag recognition program; reading the core device tree source file of the memory by the flag recognition program, and obtaining 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 a target environment parameter; The boot program performs an environmental test on the peripheral component to be tested with the target environmental parameters, and obtains an evaluation result generated by the environmental test; and The boot program generates operating environment information according to the evaluation result of the target environment parameter. The processing method of dynamically adjusting the hardware core during the boot process as described in claim item 8, read the core device tree source file of the memory by the flag identification program, and obtain the corresponding components from the core device tree source file The steps for flagging these component environment parameters of information include: The component environment parameters are sorted according to an operation intensity of each component environment parameter. According to the processing method for dynamically adjusting the hardware core during the startup process described in claim 9, the step of selecting one of the component environment parameters as the target environment parameter in the flag recognition program includes: The flag recognition program sequentially selects the target environment parameter according to the sorting result of the operation intensity. The processing method of dynamically adjusting the hardware core during the boot process as described in claim item 10, performing the environmental test on the peripheral component to be tested with the target environmental parameters in the boot program, and obtaining the evaluation result generated by the environmental test. include: The boot program generates the evaluation results according to the component environment parameters. The processing method for dynamically adjusting the hardware core during the booting process as described in claim 11, wherein the step of selecting the target environment parameters sequentially according to the sorting results of the operating intensities in the flag recognition program includes: The bootstrap judges the evaluation result as success or failure; If the target environment parameter is failure, the flag identification program selects the next component environment parameter as the new target environment parameter according to the sorting result of the operation intensity; and If the target environment parameter is successful, the bootstrap program causes the flag recognition program to abort selection of the new component environment parameter. The processing method for dynamically adjusting the hardware core during the boot process as described in claim 12, wherein the boot program performs the environmental test on the peripheral component to be tested according to the target environment parameters, and obtains the peripheral component to be tested and the target environment The steps for parameters corresponding to the evaluation results include: the bootstrap program sends a test call to the peripheral component under test; and The peripheral component to be tested returns a response message to the boot program according to the test call. The processing method for dynamically adjusting the hardware core during boot process as described in claim 10, wherein the step of loading the core device tree source file into the memory by the boot program includes: The boot program determines whether the operating environment information exists in a storage unit; and If the storage unit has the operating environment information, the boot program loads the operating environment information. The processing method for dynamically adjusting the hardware core during the boot process as described in claim 14, wherein the step of loading the core device tree source file into the memory by the boot program includes: execute an operating system; the operating system loads the operating environment information from the storage unit; and The operating system identifies the corresponding peripheral components to be tested according to the operating environment information.