Method for starting up an electronic device and its embedded multimedia card

Abstract

The present application discloses a method for starting an electronic device and its embedded multimedia card. The starting method comprises: loading a starting image from a first starting partition of the embedded multimedia card in a first boot mode; reading a plurality of starting register information of the embedded multimedia card when the loading of the starting image from the first starting partition in the first boot mode fails; detecting a starting failure according to the starting register information; adjusting starting related settings of the embedded multimedia card to attempt to repair the starting failure; loading the starting image from the first starting partition in the first boot mode or a second boot mode after attempting to repair the starting failure; and loading the starting image from a second starting partition of the embedded multimedia card in the first or second boot mode after attempting to repair the starting failure and when the loading of the starting image from the first starting partition still fails.

Description

Technical Field

[0001] This case relates to electronic devices with embedded multimedia cards, and more particularly to electronic devices capable of automatically detecting fault causes and automatically switching boot partitions, and their embedded multimedia card boot methods. Background Technology

[0002] As electronic devices become increasingly functional, many systems utilize embedded MultiMediaCards (eMMCs) as non-volatile memory devices to store boot programs, firmware data, and other system data. Generally, the control chip loads a boot image from the eMMC's boot partition via the corresponding controller circuitry during system startup to execute subsequent boot procedures. However, in practical applications, electronic devices may fail to boot from the embedded MultiMediaCard due to various factors. In existing technologies, when the embedded MultiMediaCard's boot program fails, manual switching of the embedded MultiMediaCard's boot partition or manual troubleshooting is required, making the embedded MultiMediaCard's boot program and subsequent fault detection procedures extremely inconvenient. Summary of the Invention

[0003] In some embodiments, one of the objectives of this invention, but not limited to, is to provide a boot method for an electronic device and its embedded multimedia card that can automatically detect the cause of a fault and automatically switch the boot partition, thereby improving the problems of the prior art.

[0004] In some embodiments, the boot method executed via a processor circuit includes: loading a boot image from a first boot partition of an embedded multimedia card in a first boot mode; when loading the boot image from the first boot partition in the first boot mode fails, reading multiple boot register information of the embedded multimedia card; detecting a boot failure based on the multiple boot register information; adjusting a boot-related setting of the embedded multimedia card based on the boot failure to attempt to repair the boot failure; after attempting to repair the boot failure, loading the boot image from the first boot partition in the first boot mode or a second boot mode; and when, after attempting to repair the boot failure, loading the boot image from the first boot partition still fails, loading the boot image from a second boot partition of the embedded multimedia card in the first boot mode or the second boot mode.

[0005] In some embodiments, the electronic device includes a controller circuit and a processor circuit. The controller circuit is coupled to an embedded multimedia card. The processor circuit is configured to: load a boot image from a first boot partition of the embedded multimedia card via the controller circuit in a first boot mode; when loading the boot image from the first boot partition via the controller circuit in the first boot mode fails, read a plurality of boot register information of the embedded multimedia card via the controller circuit; detect a boot failure based on the plurality of boot register information; adjust the boot-related settings of the embedded multimedia card via the controller circuit based on the boot failure to attempt to repair the boot failure; after attempting to repair the boot failure, load the boot image from the first boot partition via the controller circuit in the first boot mode or a second boot mode; and when loading the boot image from the first boot partition via the controller circuit still fails after attempting to repair the boot failure, switch to loading the boot image from a second boot partition of the embedded multimedia card via the controller circuit in the first boot mode or the second boot mode. Attached Figure Description

[0006] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0007] Figure 1 This is a schematic diagram of an electronic device according to some embodiments of the present invention; Figure 2 Drawing based on some embodiments of this case Figure 1 Flowchart of the operation of electronic devices; Figure 3 Drawing based on some embodiments of this case Figure 2 A flowchart of multiple steps corresponding to two operations; Figure 4 Drawing based on some embodiments of this case Figure 2 A flowchart of the multiple steps corresponding to one operation; and Figure 5 An operation flowchart of a startup method is drawn based on some embodiments of this case.

[0008] Explanation of reference numerals in the attached figures: 100: Electronic devices 110: Control chip 112: Processor circuit 114: Controller Circuit 116: Memory Circuit 1162: Startup partition table 118: Direct Memory Access Controller Circuit 120: Embedded Multimedia Card 122, 124: Boot partition 126: User Data Area 128: Register 1281: Reset function register information 1282: Startup Bus Condition Register Information 1283: Partition Setting Register Information 1284: Startup Information Register Information 130: Controller circuit 500: Startup Method BL: Boot Image S202, S204, S206, S208, S210, S212: Operation S302, S304, S306, S308, S310, S312, S314, S316, S318, S320: Steps S402, S404, S406, S408: Steps S502, S504, S506, S508, S510, S512: Operation Detailed Implementation All terms used herein have their ordinary meanings. The definitions of these terms in commonly used dictionaries, and any examples of the use of any term discussed herein, are merely illustrative and should not limit the scope or meaning of this application. Similarly, this application is not limited to the various embodiments shown in this specification.

[0009] As used herein, “coupled” or “connected” can refer to two or more components making direct physical or electrical contact with each other, or indirectly making direct physical or electrical contact with each other, or to two or more components operating or acting on each other. As used herein, the term “circuit” can be a device consisting of at least one transistor and / or at least one active or passive component connected in a certain manner to process signals.

[0010] Figure 1This is a schematic diagram of an electronic device 100 according to some embodiments of the present invention. The electronic device 100 includes a control chip 110 and an embedded multimedia card 120. The control chip 110 includes a processor circuit 112, a controller circuit 114, a memory circuit 116, and a direct memory access controller circuit 118. The controller circuit 114 is coupled between the processor circuit 112 and the embedded multimedia card 120. Based on the requirements or control of the processor circuit 112, the controller circuit 114 can obtain relevant boot register information (e.g., at least one of reset function register information 1281, boot bus condition register information 1282, partition setting register information 1283, and / or boot information register information 1284) and data (e.g., a bootloader image BL) from the embedded multimedia card 120, and store this register information and data in the memory circuit 116 via the direct memory access controller circuit 118. Thus, the processor circuit 112 can perform a boot procedure based on this register information and data stored in the memory circuit 116. In some embodiments, memory circuitry 116 may be (but is not limited to) dynamic random access memory. Furthermore, in some embodiments, memory circuitry 116 may also store a boot partition table 1162, allowing processor circuitry 112 to record the status of each boot partition and determine which boot partition to attempt to load the boot image BL.

[0011] In some embodiments, the embedded multimedia card 120 may include a boot partition 122, a boot partition 124, and a user data area 126. In some embodiments, boot partition 122 and boot partition 124 may each store a copy of the aforementioned boot image BL. In some embodiments, boot partition 122 and boot partition 124 may correspond to a first boot partition (Boot Area partition 1) and a second boot partition (Boot Area partition 2), respectively. In some embodiments, the initial storage area of ​​the user data area 126 may also store the boot image BL.

[0012] In some embodiments, the embedded multimedia card 120 may further include a controller circuit 130, which may include a plurality of registers 128. The plurality of registers 128 are used to store reset function register information 1281, boot bus condition register information 1282, partition setting register information 1283, and boot information register information 1284, respectively. The processor circuit 112 may adjust a boot-related setting of the embedded multimedia card 120 according to the state indicated by the aforementioned plurality of boot register information to attempt to repair boot failures. In some embodiments, the aforementioned boot-related settings may include (but are not limited to) at least one of hardware reset function settings, boot bit width settings, boot mode settings, rate mode settings, and boot ACK function settings. In some embodiments, the processor circuit 112 may first load the boot image BL from the boot partition 122 in a first boot mode. If loading fails, the boot image BL may be loaded again in the boot partition 122 in the first boot mode or the second boot mode, depending on the detection result, and if necessary, the boot image BL may be loaded from the boot partition 124.

[0013] In some embodiments, the aforementioned plurality of boot register information may correspond to multiple fields in the Extended Card Specific Data (EXT_CSD) of the embedded multimedia card 120. For example, the reset function register information 1281 may correspond to the RST_n_FUNCTION field, the boot bus condition register information 1282 may correspond to the BOOT_BUS_CONDITIONS field, the partition setting register information 1283 may correspond to the PARTITION_CONFIG field, and the boot information register information 1284 may correspond to the BOOT_INFO field. In some embodiments, the aforementioned field definitions may conform to the eMMC compatibility specifications defined by JEDEC, such as, but not limited to, the JESD84-B51 compatibility specification.

[0014] In some embodiments, the first boot mode may be a fast boot mode, and the second boot mode may be a slow boot mode. The fast boot mode may correspond to a more streamlined or faster boot loader. For example, the fast boot mode may correspond to an alternate boot mode, which triggers the boot loader via software based on a default instruction to obtain the boot image BL from the embedded multimedia card 120. On the other hand, the slow boot mode may correspond to a more general, highly compatible loader, and can be precisely and completely timed via hardware to trigger the embedded multimedia card 120 to transfer the boot image BL.

[0015] In some embodiments, the processor circuitry 112 can detect startup failures based on the status indicated by multiple startup register information and further determine the startup-related settings to be adjusted. Details regarding this will be provided later. Figure 2 Please provide an explanation.

[0016] In some embodiments, if the processor circuit 112 fails to successfully load the boot image BL from the boot partition 122 after attempting to repair the boot failure, it indicates that the boot image BL stored in the boot partition 122 may be corrupted. Under this condition, the processor circuit 112 may further switch to loading the boot image BL from another boot partition. For example, the processor circuit 112 may first record that the boot partition 122 is a boot partition that has attempted to boot, update the corresponding information to the boot partition table 1162 in the memory circuit 116, and then select a boot partition 124 that has not yet attempted to boot as another boot partition according to the boot partition table 1162, and set the other boot partition 124 as the current boot partition of the embedded multimedia card 120. In some embodiments, after switching to another boot partition, the processor circuit 112 may selectively load the boot image BL from the other boot partition 124 in a first boot mode or a second boot mode to increase the chance of the system successfully completing the boot process. The relevant operations here will be referred to later. Figure 4 Please provide an explanation.

[0017] Figure 2 Drawing based on some embodiments of this case Figure 1 The operation flowchart of the electronic device 100 is shown below. In operation S202, the processor circuit 112 loads the boot image BL from the boot partition 122 in a first boot mode. As mentioned above, the first boot mode can be a fast boot mode. In this case, the controller circuit 114 can issue a corresponding boot command to the embedded multimedia card 120 according to the control of the processor circuit 112, so that the embedded multimedia card 120 transfers the boot image BL from the currently specified boot partition (e.g., boot partition 122). Then, the controller circuit 114 can move the boot image BL to the memory circuit 116 via the direct memory access controller circuit 118 for further execution by the processor circuit 112.

[0018] In operation S204, the processor circuit 112 determines whether loading the boot image BL from the boot partition 122 has failed. In some embodiments, the aforementioned loading failure may include at least one of the following: the embedded multimedia card 120 fails to return the boot image BL as expected, the returned data is incomplete, the returned data format is incorrect, data verification fails, the boot mode is not supported, the bus conditions do not match, or the processor circuit 112 is unable to successfully enter the subsequent boot process based on the loaded data, etc. If the loading is determined to be successful, the processor circuit 112 can continue to execute the subsequent system boot process based on the boot image BL, thereby enabling the embedded multimedia card 120; or, if the loading is determined to be unsuccessful, operation S206 is executed.

[0019] In operation S206, the processor circuit 112 can read multiple boot register information from the embedded multimedia card 120 via the controller circuit 114 to detect boot failures. As mentioned above, the aforementioned multiple boot register information may include at least one of the following: reset function register information 1281, boot bus condition register information 1282, partition setting register information 1283, and / or boot information register information 1284. The processor circuit 112 can compare the aforementioned boot register information with the loaded relevant data or known correct data settings to determine the possible causes of the boot failure. For example, the processor circuit 112 can determine whether the hardware reset function is not permanently enabled, whether the boot bit width is different from the host control bit width, whether the embedded multimedia card 120 does not support the first boot mode, whether the boot rate mode is different from the supported rate mode, or whether the boot confirmation function is enabled.

[0020] In operation S208, the processor circuit 112 adjusts the boot-related settings of the embedded multimedia card 120 according to the boot failure in an attempt to repair the boot failure. In operation S210, after attempting to repair the boot failure, the processor circuit 112 loads the boot image BL again from the boot partition 122. In some embodiments, if the aforementioned boot failure does not involve factors such as the first boot mode not being supported, the processor circuit 112 may maintain loading the boot image BL from the boot partition 122 in the first boot mode. On the other hand, if the aforementioned boot failure includes the embedded multimedia card 120 not supporting the first boot mode, the processor circuit 112 may switch to loading the boot image BL from the boot partition 122 in the second boot mode. In other words, in some embodiments, when reloading the boot image BL in the same boot partition, the boot mode used may change depending on the boot failure, and is not necessarily fixed to the boot mode used during the first loading.

[0021] In operation S212, if loading the boot image BL from boot partition 122 still fails after attempting to repair the boot failure, processor circuit 112 can execute a program to switch boot partitions, thereby loading the boot image BL from another boot partition of the embedded multimedia card 120 in either the first boot mode or the second boot mode. On the other hand, if processor circuit 112 successfully loads the boot image BL from boot partition 122 in operation S210, processor circuit 112 can then execute subsequent system boot procedures to enable electronic device 100. Specific details regarding boot partition switching will be provided later. Figure 4 To provide a more detailed explanation.

[0022] Figure 3 Drawing based on some embodiments of this case Figure 2 The flowchart shows the multiple steps corresponding to operations S206 and S208. In some embodiments, operation S206 may include steps S302, S306, S310, S314 and S318, and operation S208 may include steps S304, S308, S312, S316 and S320.

[0023] In step S302, the processor circuit 112 determines whether the hardware reset function of the embedded multimedia card 120 is not permanently enabled based on the reset function register information 1281. If yes, step S304 is executed; otherwise, step S306 is executed. In step S304, the processor circuit 112 enables the hardware reset function. For example, if the hardware reset function of the embedded multimedia card 120 is not permanently enabled, the embedded multimedia card 120 may not be able to enter a state suitable for loading the boot image BL through the expected reset mechanism during the boot process, thus increasing the possibility of boot failure. In this case, the processor circuit 112 can enable the hardware reset function of the embedded multimedia card 120 via the controller circuit 114 (e.g., set it to be permanently enabled) as a corresponding repair action. After step S304, the processor circuit 112 can execute... Figure 2 Operation S210 is used to attempt to load the boot image BL again.

[0024] In step S306, the processor circuit 112 determines whether the bit width corresponding to the boot bus condition register information 1282 is different from the bit width of the main control terminal based on the boot bus condition register information 1282. If yes, step S308 is executed; otherwise, step S310 is executed. In step S308, the processor circuit 112 adjusts the bit width corresponding to the boot bus condition register information 1282 in the embedded multimedia card 120 to the bit width of the main control terminal via the controller circuit 114. For example, if the bit width indicated by the boot bus condition register information 1282 is inconsistent with the bit width of the main control terminal, it means that the bus bit width setting of the control chip 110 (i.e., the main control terminal) is inconsistent with the bus bit width setting of the embedded multimedia card 120, which may cause the two sides to be unable to correctly exchange the boot image BL, thus resulting in a boot failure. In this case, the processor circuit 112 can adjust the bit width corresponding to the boot bus condition register information 1282 in the embedded multimedia card 120 to be the same as the bit width of the main control terminal via the controller circuit 114 as a corresponding repair action. After step S308, the processor circuit 112 can execute... Figure 2 Operation S210 is used to attempt to load the boot image BL again.

[0025] In step S310, the processor circuit 112 determines whether the embedded multimedia card 120 does not support the first boot mode based on the boot information register information 1284. If yes, step S312 is executed; otherwise, step S314 is executed. In step S312, the processor circuit 112 switches the boot mode from the first boot mode to the second boot mode. For example, if the boot information register information 1284 indicates that the embedded multimedia card 120 does not support the first boot mode, even if the same boot partition is maintained, the control chip 110 may still fail to correctly obtain the boot image BL through the first boot mode, resulting in a boot failure. In this case, the processor circuit 112 can reload the boot image BL from the original boot partition (e.g., boot partition 122) using the second boot mode as a corresponding repair action. After step S312, the processor circuit 112 can execute... Figure 2 The S210 was operated and attempted to load the boot image BL in the second boot mode.

[0026] In step S314, the processor circuit 112 determines, based on the boot bus condition register information 1282 and the boot information register information 1284, whether the rate mode corresponding to the boot bus condition register information 1282 is different from the supported rate mode corresponding to the boot information register information 1284. If yes, step S316 is executed; otherwise, step S318 is executed. In step S316, the processor circuit 112 adjusts the rate mode corresponding to the boot bus condition register information 1282 in the embedded multimedia card 120 to a compatible mode via the controller circuit 114. For example, if the actual supported rate mode of the embedded multimedia card 120 is different from the rate mode currently set for loading the boot image BL, the data transmission timing between the control chip 110 and the embedded multimedia card 120 may not match correctly, resulting in a boot failure. In this case, the processor circuit 112 can switch the aforementioned rate mode to a compatible mode with higher timing compatibility as a corresponding repair action. After step S316, the processor circuit 112 can execute... Figure 2 Operation S210 is used to attempt to load the boot image BL again.

[0027] In step S318, the processor circuit 112 determines whether the startup confirmation function is enabled based on the partition setting register information 1283. If yes, step S320 is executed; otherwise, the following steps can be performed. Figure 2 In step S212, the processor circuit 112 performs the operation of switching the boot partition. In step S320, the processor circuit 112 disables the aforementioned boot confirmation function via the controller circuit 114. For example, in some embodiments, if the boot confirmation function is enabled, the embedded multimedia card 120 may output an additional confirmation signal during the boot process, and the timing or handshake behavior of this confirmation signal may be inconsistent with the expectations of the control chip 110, thereby increasing the possibility of boot failure. In addition, different manufacturers may have different settings for the boot confirmation function. In this case, the processor circuit 112 can disable the aforementioned boot confirmation function via the controller circuit 114 to improve compatibility as a corresponding repair action. After step S320, the processor circuit 112 can execute Figure 2 Operation S210 is used to attempt to load the boot image BL again.

[0028] Figure 4 Drawing based on some embodiments of this case Figure 2The flowchart below describes the multiple steps corresponding to operation S212. In step S402, the processor circuit 112 records the boot partition 122 as a boot partition that has been attempted to boot. In some embodiments, the processor circuit 112 can complete step S402 by updating the boot partition table 1162 stored in the memory circuit 116. For example, the boot partition table 1162 can record the status of each boot partition in the embedded multimedia card 120, such as whether each boot partition has been attempted to load the boot image BL, whether it is the current boot partition, or whether it can still be used as a candidate boot partition. In this way, the processor circuit 112 can avoid repeatedly selecting boot partitions that have been confirmed to be unable to successfully load the boot image BL in subsequent procedures.

[0029] In step S404, the processor circuit 112 selects a boot partition that has not yet been attempted to boot according to the boot partition table 1162, and designates the boot partition that has not yet been attempted to boot as another boot partition. In some embodiments, the other boot partition may be boot partition 124. As long as boot partition 124 has not been attempted to load the boot image BL and is available for the electronic device 100 to perform subsequent boot procedures, boot partition 124 can be selected as another boot partition. In other words, in different embodiments, the processor circuit 112 can dynamically determine the other boot partition according to the boot partition status recorded in the boot partition table 1162.

[0030] In step S406, the processor circuit 112 sets another boot partition as the current boot partition of the embedded multimedia card 120. In some embodiments, the processor circuit 112 may adjust the partition setting information of the embedded multimedia card 120 via the controller circuit 114 so that the embedded multimedia card 120 subsequently loads the boot image BL from the aforementioned other boot partition. For example, if the processor circuit 112 selects boot partition 124 as another boot partition in step S404, the processor circuit 112 may set boot partition 124 as the current boot partition via the controller circuit 114. In this way, the embedded multimedia card 120 can output the boot image BL from the newly selected boot partition according to the updated partition settings.

[0031] In step S408, the processor circuit 112 selects either a first boot mode or a second boot mode to load the boot image BL from another boot partition. For example, if the previous boot failure was due to the embedded multimedia card 120 not supporting the first boot mode, the processor circuit 112 can select to load the boot image BL from another boot partition using the second boot mode. On the other hand, if the previous boot failure did not involve factors such as the first boot mode not being supported, the processor circuit 112 can select to load the boot image BL from another boot partition using the first boot mode. In other words, the processor circuit 112 can execute operation S210 again, whereby the processor circuit 112 can load the boot image BL from another boot partition using either the first boot mode or the second boot mode. If the processor circuit 112 still fails to load the boot image BL from another boot partition, the processor circuit 112 can further, according to system design requirements, re-execute the aforementioned boot failure detection process, switch to another candidate boot partition again, or terminate the boot process. In this way, the electronic device 100 can perform fault-tolerant switching between multiple available boot partitions to improve the overall boot success rate.

[0032] Figure 5 A flowchart of an operation method 500 is provided according to some embodiments of this case. In some embodiments, Figure 5 The startup method 500 can be (but is not limited to) Figure 1 The processor circuit 112 in the middle is executed.

[0033] In operation S502, a boot image is loaded from a first boot partition of an embedded multimedia card in a first boot mode. In operation S504, if loading the boot image from the first boot partition in the first boot mode fails, multiple boot register information of the embedded multimedia card is read. In operation S506, a boot failure is detected based on the multiple boot register information. In operation S508, a boot-related setting of the embedded multimedia card is adjusted according to the boot failure to attempt to repair the boot failure. In operation S510, after attempting to repair the boot failure, the boot image is loaded from the first boot partition in either the first boot mode or a second boot mode. In operation S512, after attempting to repair the boot failure, and if loading the boot image from the first boot partition still fails, the boot image is loaded from a second boot partition of the embedded multimedia card in either the first boot mode or the second boot mode.

[0034] The above operations can be understood by referring to the descriptions of the foregoing embodiments, and therefore will not be repeated here. Figures 2 to 5 The operations described herein are merely examples and are not intended to be performed in the order shown in these examples. Without departing from the mode and scope of operation of the various embodiments of this invention, these operations may be appropriately added, replaced, omitted, performed in a different order, or performed simultaneously or partially simultaneously.

[0035] In summary, the electronic device and its embedded multimedia card boot method provided in some embodiments of this case can automatically detect the cause of the fault and automatically switch the boot partition by reading one or more register information of the embedded multimedia card, thereby increasing the chance of successful boot and improving ease of use.

[0036] Although the embodiments of this case are described above, these embodiments are not intended to limit this case. Those skilled in the art can make variations to the technical features of this case based on the express or implied content of this case. All such variations may fall within the scope of patent protection sought in this case. In other words, the scope of patent protection in this case shall be determined by the scope of the patent application in this specification.

Claims

1. A startup method, characterized in that, The startup method is executed via a processor circuit and includes: Load a boot image from a first boot partition of an embedded multimedia card in a first boot mode; When loading the boot image from the first boot partition fails in the first boot mode, read multiple boot register information from the embedded multimedia card; Detect a startup failure based on the information from these multiple startup registers; Adjust a boot-related setting of the embedded multimedia card based on the boot failure in an attempt to fix the boot failure; After attempting to repair the boot failure, the boot image is loaded from the first boot partition in either the first boot mode or a second boot mode; and If, after attempting to repair the boot failure, loading the boot image from the first boot partition still fails, the boot image is loaded from a second boot partition of the embedded multimedia card in either the first boot mode or the second boot mode.

2. The startup method as described in claim 1, characterized in that, The first boot mode is a fast boot mode, and the second boot mode is a slow boot mode.

3. The startup method as described in claim 1, characterized in that, When loading the boot image from the first boot partition still fails after attempting to repair the boot failure, loading the boot image from the second boot partition in either the first boot mode or the second boot mode includes: Record this first boot partition as a boot partition that has been attempted to boot. Select a boot partition that has not yet been attempted to boot from a boot partition table, and designate this boot partition as the second boot partition; and Set the second boot partition as the current boot partition of the embedded multimedia card.

4. The startup method as described in claim 1, characterized in that, The multiple boot register information includes a reset function register information, and the boot-related settings of the embedded multimedia card are adjusted according to the boot failure in an attempt to repair the boot failure, including: Enable the hardware reset function when the reset function register information indicates that a hardware reset function of the embedded multimedia card is not permanently enabled.

5. The startup method as described in claim 1, characterized in that, The multiple boot register information includes boot bus condition register information, and the boot-related settings of the embedded multimedia card are adjusted according to the boot failure in an attempt to repair the boot failure, including: When the bit width corresponding to the boot bus condition register information is different from the bit width of a master control terminal, the bit width corresponding to the boot bus condition register information is adjusted to the bit width of the master control terminal.

6. The startup method as described in claim 1, characterized in that, The multiple boot register information includes a boot information register, and loading the boot image from the first boot partition in the first boot mode or the second boot mode after attempting to repair the boot failure includes: When the boot information register indicates that the embedded multimedia card does not support the first boot mode, the boot mode is switched from the first boot mode to the second boot mode, and the boot image is loaded from the first boot partition in the second boot mode.

7. The startup method as described in claim 6, characterized in that, When loading the boot image from the first boot partition still fails after attempting to repair the boot failure, loading the boot image from the second boot partition of the embedded multimedia card in either the first boot mode or the second boot mode includes: If loading the boot image from the first boot partition using the second boot mode still fails, switch to loading the boot image from the second boot partition using the second boot mode.

8. The startup method as described in claim 1, characterized in that, The multiple boot register information includes a boot bus condition register and a boot information register, and the boot-related settings of the embedded multimedia card are adjusted according to the boot failure in an attempt to repair the boot failure, including: When the rate mode corresponding to the boot bus condition register information is different from the supported rate mode corresponding to the boot information register information, the rate mode corresponding to the boot bus condition register information is adjusted to a compatible mode.

9. The startup method as described in claim 1, characterized in that, The multiple boot register information includes partition setting register information, and the boot-related settings of the embedded multimedia card are adjusted according to the boot failure in an attempt to repair the boot failure, including: When the partition setting register information indicates that a boot confirmation function is enabled, disable the boot confirmation function.

10. An electronic device, characterized in that, include: A controller circuit is coupled to an embedded multimedia card; as well as A processor circuit, used for: A boot image is loaded from a first boot partition of the embedded multimedia card via the controller circuitry in a first boot mode. When loading the boot image from the first boot partition via the controller circuit fails in the first boot mode, the controller circuit reads multiple boot register information of the embedded multimedia card; and detects a boot failure based on the multiple boot register information. Based on the startup failure, the startup-related settings of the embedded multimedia card are adjusted via the controller circuit in an attempt to repair the startup failure; After attempting to repair the boot failure, the boot image is loaded from the first boot partition via the controller circuitry in either the first boot mode or a second boot mode. as well as When attempting to repair the boot failure and failing to load the boot image from the first boot partition via the controller circuitry, the system switches to loading the boot image from a second boot partition of the embedded multimedia card via the controller circuitry in either the first boot mode or the second boot mode.

Images