Electronic device, solid-state drive device, and artificial satellite
By introducing firmware judgment, backup firmware judgment and off-site backup firmware judgment steps in solid-state hard disk devices, the automatic startup and backup storage problems when the firmware of solid-state hard disk devices are damaged in harsh environments such as artificial satellites are solved, and the equipment is improved Convenience and maintenance efficiency.
Patent Information
- Application Number
- PCT/CN2023/097391
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-31
- Publication Date
- 2024-12-05
AI Technical Summary
In harsh environments such as artificial satellites, when the firmware of the solid-state drive device cannot operate normally, it will be difficult for ground personnel to solve the problem, resulting in the equipment being unable to start.
An electronic device is designed, including a substrate, a main controller, a solid state hard disk device and an electronic erasable rewriteable read-only memory. Through the steps of firmware judgment, backup firmware judgment and off-site backup firmware judgment, it can automatically judge and use the non-site firmware judgment. A damaged backup or off-site backup firmware boots up the SSD device and writes it to memory.
It realizes automatic startup and backup of the firmware when the firmware is damaged, which improves the convenience of the equipment and maintenance efficiency, and reduces manual intervention.
Smart Images

Figure CN2023097391_05122024_PF_FP_ABST
Abstract
Description
Electronic devices, solid-state drive devices, and artificial satellites Technical Field
[0001] The present invention relates to an electronic device, a solid state hard disk device and an artificial satellite, and more particularly to an electronic device, a solid state hard disk device and an artificial satellite having a firmware backup function of a solid state hard disk. Background Art
[0002] Solid-state drive (SSD) devices are currently installed in harsh environments, such as those on satellites. If the SSD device fails to execute its firmware properly during startup in space, it would be difficult for personnel on Earth to resolve the issue.
[0003] Summary of the Invention
[0004] The present invention discloses an electronic device, a solid-state hard disk device and an artificial satellite, which are mainly used to improve the problem that if the firmware of the existing solid-state hard disk device used in harsh environments fails to operate normally, it is difficult for relevant personnel to handle it.
[0005] One embodiment of the present invention discloses an electronic device, which includes: a substrate, which includes a PCIE port; a main controller, which is arranged on the substrate; a solid-state hard disk device, which is connected to the substrate via the PCIE port; the solid-state hard disk device includes a hard disk controller, multiple flash memories, at least one electronically erasable rewritable read-only memory and a PCIE controller, and a backup firmware is stored in the electronically erasable rewritable read-only memory; wherein, when the electronic device executes a hard disk startup program, the following steps are included: a startup signal transmission step: the main controller transmits a startup signal to the solid-state hard disk device; a firmware judgment step: after the hard disk controller receives the startup signal, the hard disk controller will judge whether a firmware in the flash memory is damaged; if the hard disk controller determines that the firmware is not damaged, the hard disk controller will use the firmware to start the solid-state hard disk device; if the hard disk controller determines that the firmware is damaged, the hard disk controller will execute the following steps: a backup firmware judgment step: read the backup firmware , and determines whether the backup firmware is damaged; if the hard disk controller determines that the backup firmware is damaged, the hard disk controller will transmit a startup failure signal to the main controller; wherein, when the main controller receives the startup failure signal, the main controller will perform the following steps: a remote connection step: communicating with a remote electronic device to obtain an off-site backup firmware, and transmitting the off-site backup firmware to the solid-state hard disk device; wherein, after the solid-state hard disk device receives the off-site backup firmware, it will perform the following steps: a off-site backup firmware judgment step: judging whether the off-site backup firmware is damaged; if the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller will use the firmware to start the solid-state hard disk device, and the hard disk controller will also return a startup success signal to the main controller, and the hard disk controller will also write the off-site backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller; if the hard disk controller determines that the off-site backup firmware is damaged, it will return a startup failure signal to the main controller.
[0006] Preferably, when the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller further stores at least one additional off-site backup firmware in one of the flash memories.
[0007] Preferably, at least one first backup firmware is stored in at least one flash memory, and the backup firmware stored in the electronically erasable rewritable read-only memory is defined as a second backup firmware; when the hard disk controller determines that the firmware is damaged, the hard disk controller first determines whether the first backup firmware is damaged; if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will use the first backup firmware to start the solid-state hard disk device; if the hard disk controller determines that the first backup firmware is damaged, the hard disk controller will execute the backup firmware determination step.
[0008] Preferably, if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will write the first backup firmware into the electrically erasable rewritable read-only memory through the PCIE controller.
[0009] One embodiment of the present invention discloses a solid-state hard disk device that can be connected to a substrate of an electronic device through a PCIE port. The substrate includes a main controller. The main controller can, upon receiving a startup failure signal transmitted by the solid-state hard disk device, communicate with a remote electronic device to obtain a remote backup firmware and transmit the remote backup firmware to the solid-state hard disk device. The solid-state hard disk device includes: a motherboard; a plurality of flash memories disposed on the motherboard, wherein one of the flash memories stores a firmware; at least one electronically erasable rewritable read-only memory disposed on the motherboard, wherein the electronically erasable rewritable read-only memory stores a backup firmware; a hard disk controller disposed on the motherboard, wherein the hard disk controller can receive a startup signal transmitted by the main controller; a PCIE controller disposed on the motherboard, wherein the PCIE controller is connected to the electronically erasable rewritable read-only memory; wherein, when the hard disk controller receives the startup signal, The hard disk controller will execute a firmware judgment step: judging whether the firmware is damaged; if the hard disk controller judges that the firmware is damaged, the hard disk controller will execute the following steps: a backup firmware judgment step: reading the backup firmware and judging whether the backup firmware is damaged; if the hard disk controller judges that the backup firmware is damaged, the hard disk controller will transmit a startup failure signal to the main controller; wherein, after the hard disk controller receives the remote backup firmware, it will execute the following steps: a remote backup firmware judgment step: judging whether the remote backup firmware is damaged; if the hard disk controller judges that the remote backup firmware is not damaged, the hard disk controller will use the firmware to start the solid-state hard disk device, and the hard disk controller will also return a startup success signal to the main controller, and the hard disk controller will also write the remote backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller; if the hard disk controller judges that the remote backup firmware is damaged, it will return a startup failure signal to the main controller.
[0010] Preferably, when the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller further stores at least one additional off-site backup firmware in one of the flash memories.
[0011] Preferably, at least one first backup firmware is stored in at least one flash memory, and the backup firmware stored in the electronically erasable rewritable read-only memory is defined as a second backup firmware; when the hard disk controller determines that the firmware is damaged, the hard disk controller first determines whether the first backup firmware is damaged; if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will use the first backup firmware to start the solid-state hard disk device; if the hard disk controller determines that the first backup firmware is damaged, the hard disk controller will execute the backup firmware determination step.
[0012] Preferably, if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will write the first backup firmware into the electrically erasable rewritable read-only memory through the PCIE controller.
[0013] One embodiment of the present invention discloses an artificial satellite, which includes an artificial satellite body and the electronic device of the present invention; the remote electronic device is a ground base station, and the electronically erasable rewritable read-only memory meets space standards.
[0014] In summary, the electronic device, solid-state drive device, and artificial satellite of the present invention, through designs such as a firmware determination step, a backup firmware determination step, and a remote backup firmware determination step, can automatically determine whether the backup firmware and the remote backup firmware are damaged when the firmware in the flash memory of the solid-state drive device is damaged. If the backup firmware or the remote backup firmware is not damaged, the hard disk controller of the solid-state drive device will directly use the backup firmware or the remote backup firmware to start the solid-state drive device. The hard disk controller will also write the undamaged backup firmware or the remote backup firmware to the electronically erasable rewritable read-only memory via the PCIE controller.
[0015] To further understand the features and technical contents of the present invention, please refer to the following detailed description and drawings of the present invention. However, such description and drawings are only used to illustrate the present invention and are not intended to limit the scope of protection of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] FIG1 is a schematic diagram of an electronic device according to the present invention.
[0017] FIG. 2 is a block diagram of an electronic device according to the present invention.
[0018] FIG. 3 is a flow chart showing the electronic device executing the hard disk booting procedure according to the present invention.
[0019] FIG. 4 is a flow chart illustrating another embodiment of the electronic device executing the hard disk booting procedure according to the present invention.
[0020] FIG. 5 is a block diagram of another embodiment of a solid state drive device according to the present invention.
[0021] FIG. 6 is a flow chart illustrating a process of executing a hard disk booting procedure in an electronic device according to another embodiment of the present invention.
[0022] FIG7 is a schematic diagram of an artificial satellite of the present invention. DETAILED DESCRIPTION
[0023] In the following description, if it is indicated to refer to a specific figure or as shown in a specific figure, it is only used to emphasize that most of the relevant content described in the subsequent description appears in the specific figure, but it does not limit the subsequent description to only referring to the specific figure.
[0024] Please refer to Figures 1 and 2 . Figure 1 is a schematic diagram of the electronic device of the present invention, and Figure 2 is a block diagram of the electronic device of the present invention. The electronic device 100 of the present invention includes a substrate 11, a main controller 12, and a solid-state drive device 13. The substrate 11 includes a PCIE port 111, and the main controller 12 is disposed on the substrate 11. Specifically, the substrate 11 is a circuit board, and the main controller is a field programmable gate array (FPGA). The solid-state drive device 13 is pluggably connected to the substrate 11 via the PCIE port 111.
[0025] The solid-state drive device 13 includes a motherboard 130, a hard drive controller 131, multiple flash memories 132, at least one electrically erasable programmable read-only memory (EEPROM) 133, and a PCIE controller 134. The hard drive controller 131, flash memories 132, EEPROM 133, and PCIE controller 134 are mounted on the motherboard 130. The hard drive controller 131 is electrically connected to the flash memories 132 and the PCIE controller 134. The PCIE controller 134 is electrically connected to the EEPROM 133. The EEPROM 133 stores a backup firmware 1331.
[0026] When the electronic device 100 executes a hard drive boot process, it sequentially performs a boot signal transmission step S11 and a firmware determination step S12. In the boot signal transmission step S11, the main controller 12 transmits a boot signal 121 to the solid-state drive device 13. In the firmware determination step S12, after receiving the boot signal 121, the hard drive controller 131 determines whether a firmware 1321 in the flash memory 132 is damaged.
[0027] If the hard disk controller 131 determines that the firmware 1321 is not damaged, the electronic device 100 executes a storage and firmware startup step S12X: the hard disk controller 131 will use the firmware 1321 to start the solid-state hard disk device 13, and the hard disk controller 131 will transmit a startup success signal 1311 to the main controller 12. After the main controller 12 receives the startup success signal 1311, the main controller 12 will end the hard disk startup program, and the main controller 12 will continue to execute other default programs, such as accessing data in the solid-state hard disk device 13.
[0028] In the firmware determination step S12 , if the hard disk controller 131 determines that the firmware 1321 is damaged, the electronic device 100 will execute a backup firmware determination step S13 : the hard disk controller 131 will read the backup firmware 1331 and determine whether the backup firmware 1331 is damaged.
[0029] If the hard disk controller 131 determines that the backup firmware 1331 is not damaged, the electronic device 100 executes a storage and firmware startup step S13X: the hard disk controller 131 will store the backup firmware 1331 in the flash memory 132, and use the backup firmware 1331 to start the solid-state hard disk device 13, and the hard disk controller 131 will transmit a startup success signal 1311 to the main controller 12. After the main controller 12 receives the startup success signal 1311, the main controller 12 will end the hard disk startup program, and the main controller 12 will continue to execute other default programs.
[0030] In actual applications, when the hard disk controller 131 determines that the backup firmware 1331 is not damaged, the hard disk controller 131 can store the backup firmware 1331 in the location originally used to store the firmware 1321 in the flash memory 132 to replace the original firmware 1321, or the hard disk controller 131 can store the backup firmware 1331 in a different location in the flash memory 132.
[0031] In a preferred embodiment, when the hard disk controller 131 determines that the backup firmware 1331 is not damaged, the hard disk controller 131 can also store at least one additional copy of the backup firmware 1331 in at least one flash memory 132. Thus, at least two (or more) copies of the backup firmware 1331 will be stored in the flash memory 132 of the solid state drive device 13.
[0032] In the backup firmware determination step S13, if the hard disk controller 131 determines that the backup firmware 1331 is damaged, the hard disk controller 131 transmits a startup failure signal 1312 to the main controller 12. When the main controller 12 receives the startup failure signal 1312, the electronic device 100 executes a remote connection step S14: the main controller 12 communicates with a remote electronic device 200 to obtain a remote backup firmware 201, and transmits the remote backup firmware 201 to the solid-state drive device 13.
[0033] In one embodiment, the electronic device 100 may be an artificial satellite installed in space, and the remote electronic device 200 may be a base station located on Earth, and the solid-state drive device 13 meets space specifications (for example, having higher radiation resistance, etc.), especially the electronically erasable rewritable read-only memory 133 must meet space specifications because the electronically erasable rewritable read-only memory 133 is mainly used to store backup firmware 1331.
[0034] After the solid-state drive device 13 receives the remote backup firmware 201, it executes a remote backup firmware determination step S15: the hard disk controller 131 determines whether the remote backup firmware 201 is damaged. If the hard disk controller 131 determines that the remote backup firmware 201 is not damaged, the electronic device 100 executes a storage and firmware startup step S15X: the hard disk controller 131 stores the remote backup firmware 201 in the flash memory 132 and uses the remote backup firmware 201 to start the solid-state drive device 13. The hard disk controller 131 also transmits a startup success signal 1311 back to the main controller 12. After receiving the startup success signal 1311, the main controller 12 ends the hard disk startup process.
[0035] In one preferred embodiment, after the hard disk controller 131 stores the off-site backup firmware 201 in the flash memory 132, the hard disk controller 131 also writes the off-site backup firmware 201 into the electronically erasable rewritable read-only memory 133 via the PCIE controller 134. With this design, if the hard disk controller 131 determines that the off-site backup firmware 201 stored in the flash memory 132 is damaged the next time, the hard disk controller 131 can still obtain the intact off-site backup firmware 201 from the electronically erasable rewritable read-only memory 133 via the PCIE controller 134.
[0036] In one embodiment, in the off-site backup firmware determination step S15, if the hard disk controller 131 determines that the off-site backup firmware 201 is not damaged, the hard disk controller 131 may store the off-site backup firmware 201 in the flash memory 132 at the location where the firmware 1321 is originally stored, or the hard disk controller 131 may store the off-site backup firmware 201 in another location of the flash memory 132. In addition, the hard disk controller 131 may also store at least one additional copy of the off-site backup firmware 201 in the flash memory 132, so that the flash memory 132 stores at least two copies of the off-site backup firmware 201.
[0037] In the remote backup firmware determination step S15, if the hard disk controller 131 determines that the remote backup firmware 201 is damaged, the electronic device 100 will execute a failure feedback step S16: the hard disk controller 131 returns a remote backup startup failure signal 1313 to the main controller 12. After receiving the remote backup startup failure signal 1313, the main controller 12 will transmit a startup failure message 122 to the remote electronic device 200. The startup failure message 122 may include, for example, basic information related to the solid-state drive device 13 (such as a product serial number, etc.), the firmware serial number, the backup firmware serial number, the remote backup firmware serial number, data related to the firmware execution failure (such as an error code, etc.), data related to the backup firmware execution failure (such as an error code, etc.), and data related to the remote backup firmware execution failure (such as an error code, etc.).
[0038] In practice, after the remote electronic device 200 receives the startup failure message 122, the remote electronic device 200 can re-send a new off-site backup firmware to the main controller 12 of the electronic device 100, and the electronic device 100 can re-execute the hard disk startup program. Alternatively, the main controller 12 can pass the new off-site backup firmware to the solid-state drive device 13, so that the solid-state drive device 13 can execute the off-site backup firmware judgment step S15 again.
[0039] By designing that the electronic device 100 transmits the startup failure information 122 to the remote electronic device 200, relevant personnel (for example, relevant personnel located on Earth) can clearly know which firmware the electronic device 100 has determined to be damaged and unusable. In this way, relevant personnel can determine whether it is necessary to use the remote electronic device 200 to transmit a different version of firmware (for example, a relatively older version) to the electronic device 100, so that the electronic device 100 uses the relatively older version of firmware to start the solid-state drive device 13.
[0040] It is worth mentioning that the solid-state drive device 13 of the present invention can also be manufactured, implemented or sold independently.
[0041] As described above, the electronic device 100 and the solid-state drive device 13 of the present invention, through the designs of the firmware determination step S12, the backup firmware determination step S13, and the remote backup firmware determination step S15, allow the electronic device 100 and the solid-state drive device 13 to automatically determine whether the backup firmware 1331 and the remote backup firmware 201 are damaged when the firmware 1321 in the flash memory 132 of the solid-state drive device 13 is damaged. If the backup firmware 1331 or the remote backup firmware 201 is not damaged, the hard disk controller 131 of the solid-state drive device 13 will directly use the backup firmware 1331 or the remote backup firmware 201 to boot the solid-state drive device 13. During the above process, no relevant personnel are required to participate, and the electronic device 100 and the solid-state drive device 13 can complete the process automatically. Therefore, the electronic device 100 and the solid-state drive device 13 of the present invention can significantly improve the convenience of use of the electronic device 100 and the solid-state drive device 13.
[0042] Please refer to Figure 5, which shows a flow chart of another embodiment of the electronic device of the present invention executing the hard disk boot program. The biggest difference between this embodiment and the process shown in Figure 4 is that: after the off-site backup firmware judgment step S15, if the electronic device 100 determines that the off-site backup firmware is damaged, the electronic device 100 will execute a number judgment step S15Y: determine whether the number of off-site backups obtained is greater than a predetermined number. If it is determined that the number of off-site backups obtained is greater than the predetermined number, the failure feedback step S16 is executed; if it is determined that the number of off-site backups obtained is not greater than the predetermined number, the remote connection step S14 is executed. Among them, the predetermined number is not less than 2.
[0043] More specifically, in practice, the remote backup firmware may occasionally experience errors during transmission, causing the main controller to determine that the remote backup firmware is damaged after the remote backup firmware determination step S15. Therefore, by setting the above-mentioned number determination step S15Y, the main controller can obtain the remote backup firmware from the remote electronic device again, thereby effectively reducing the possibility of remote backup firmware damage due to occasional transmission errors. Conversely, if the main controller determines that the remote backup firmware is damaged three times in a row (i.e., the aforementioned predetermined number of times), the remote backup firmware may not be damaged due to transmission issues, but may contain an error in the remote backup firmware itself.
[0044] Please refer to Figures 4 to 6 together. Figure 4 is a flow chart of the electronic device of the present invention executing the hard disk startup program, Figure 5 is a block diagram of another embodiment of the solid-state hard disk device of the present invention, and Figure 6 is a flow chart of the electronic device of another embodiment of the solid-state hard disk device of the present invention executing the hard disk startup program.
[0045] The major difference between this embodiment and the previous embodiment is that the at least one flash memory 132 of the solid-state drive device 13 also stores at least one first backup firmware 1322, while the backup firmware stored in the electrically erasable and rewritable read-only memory 133 is defined as a second backup firmware 1332. In other words, the flash memory 132 of the solid-state drive device 13 stores firmware 1321 and at least one first backup firmware 1322, and the electrically erasable and rewritable read-only memory 133 of the solid-state drive device 13 also stores the second backup firmware 1332. More simply, the solid-state drive device 13 stores firmware 1321, at least one first backup firmware 1322, and at least one second backup firmware 1332.
[0046] When the electronic device 100 of this embodiment executes the hard disk boot process, it sequentially executes the boot signal transmission step S11 and the firmware determination step S12. In the firmware determination step S12, if the hard disk controller 131 determines that the first backup firmware 1322 is not damaged, the electronic device 100 executes the aforementioned storage and firmware boot step S12X. If the hard disk controller 131 determines that the firmware 1321 is damaged, the electronic device 100 executes a first backup firmware determination step SX, which utilizes the hard disk controller 131 to determine whether the first backup firmware 1322 is damaged.
[0047] If the hard disk controller 131 determines that the first backup firmware 1322 is not damaged, the electronic device 100 will execute a storage and firmware startup step SXX: the hard disk controller 131 uses the first backup firmware 1322 to boot the solid-state drive device 13 and transmits a startup success signal 1311 to the main controller 12. In a preferred embodiment, when the hard disk controller 131 determines that the first backup firmware 1322 is not damaged, the hard disk controller 131 also controls the PCIE controller 134 to write the first backup firmware 1322 into the electronically erasable rewritable read-only memory 133.
[0048] If the hard disk controller 131 determines that the second backup firmware 1332 is damaged, the electronic device 100 will execute a backup firmware determination step S13′: the hard disk controller 131 will read the second backup firmware 1332 and determine whether the second backup firmware 1332 is damaged. If the hard disk controller 131 determines that the second backup firmware 1332 is not damaged, the electronic device 100 will execute a storage and firmware startup step S13X′: the hard disk controller 131 will use the second backup firmware 1332 to start the solid-state drive device 13 and transmit a startup success signal 1311 to the main controller 12. In the backup firmware determination step S13′, if the hard disk controller 131 determines that the second backup firmware 1332 is not damaged, the electronic device 100 will execute the aforementioned remote backup firmware determination step S15.
[0049] It is worth mentioning that in practice, if the firmware 1321 in the flash memory 132 is damaged, the probability that other backup firmware stored in the same or different flash memory 132 will also be damaged is relatively high; because the electronically erasable and rewritable read-only memory 133 is a storage component independent of the flash memory 132, and the electronically erasable and rewritable read-only memory 133 and the flash memory 132 have different storage methods, therefore, if the firmware 1321 in the flash memory 132 is damaged, the probability that the backup firmware 1331 of the electronically erasable and rewritable read-only memory 133 will also be damaged is relatively low.
[0050] It is worth mentioning that in actual applications, the number judgment step S15Y in Figure 4 can also be added to the flowchart shown in Figure 6 to form a new embodiment. For detailed description of the number judgment step S15Y, please refer to the description of the embodiment, which will not be repeated here.
[0051] Please refer to Figure 7, which is a schematic diagram of an artificial satellite according to the present invention. The artificial satellite 300 according to the present invention comprises an artificial satellite body 31 and the aforementioned electronic device 100 according to the present invention. For a detailed description of the electronic device 100, please refer to the previous embodiment and will not be repeated here. It should be noted that in this embodiment, the remote electronic device described in the previous embodiment is a ground base station 400. The artificial satellite body 31 refers to the components of the artificial satellite 300 excluding the electronic device 100.
[0052] It should be noted that, in the above description, the specific method by which the hard disk controller 131 determines whether the firmware 1321, the backup firmware 1331, the first backup firmware 1322, the second backup firmware 1332, or the remote backup firmware 201 is damaged can be designed according to needs. For example, the hard disk controller 131 can first determine whether the firmware to be determined contains complete data. If it contains complete data, it can then determine whether it can be correctly executed. If it is determined that the firmware can be correctly executed, the hard disk controller 131 will determine that the firmware is not damaged. Otherwise, it will determine that the firmware is damaged.
[0053] In summary, the electronic device, solid-state drive device, and artificial satellite of the present invention, through the firmware determination step and remote backup firmware determination step included in the hard drive boot process, can automatically access the backup firmware and remote backup firmware when the firmware in the flash memory is damaged. If the backup firmware or remote backup firmware is determined to be intact, the backup firmware or remote backup firmware is used to boot the solid-state drive device. In contrast, conventional solid-state drive devices require waiting for repair personnel when the firmware in the flash memory is damaged.
[0054] The above description is only a preferred embodiment of the present invention and does not limit the patent scope of the present invention. Therefore, any equivalent technical changes made using the contents of the present invention description and drawings are included in the protection scope of the present invention.
Claims
1. An electronic device, characterized in that: The electronic device comprises: A base plate comprising a PCIE port; a main controller, which is disposed on the substrate; A solid state hard disk device connected to the substrate via the PCIE port. The solid state hard disk device comprises a hard disk controller, a plurality of flash memories, at least one electronically erasable rewritable read-only memory and a PCIE controller. The electronically erasable rewritable read-only memory stores a backup firmware; When the electronic device executes a hard disk startup procedure, the following steps are included: A startup signal transmission step: the main controller transmits a startup signal to the solid state hard disk device; A firmware determination step: after the hard disk controller receives the start signal, the hard disk controller determines whether a firmware in the flash memory is damaged; If the hard disk controller determines that the firmware is not damaged, the hard disk controller will use the firmware to start the solid state hard disk device; If the hard disk controller determines that the firmware is damaged, the hard disk controller will perform the following steps: A backup firmware determination step: reading the backup firmware and determining whether the backup firmware is damaged; If the hard disk controller determines that the backup firmware is damaged, the hard disk controller will transmit a startup failure signal to the main controller; When the main controller receives the startup failure signal, the main controller will perform the following steps: A remote connection step: communicating with a remote electronic device to obtain a remote backup firmware, and transmitting the remote backup firmware to the solid state drive device; After receiving the remote backup firmware, the solid state drive device will perform the following steps: A remote backup firmware determination step: determining whether the remote backup firmware is damaged; If the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller will use the firmware to start the solid-state hard disk device, and the hard disk controller will also return a startup success signal to the main controller, and the hard disk controller will also write the off-site backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller; If the hard disk controller determines that the remote backup firmware is damaged, a startup failure signal is sent back to the main controller.
2. The electronic device according to claim 1, characterized in that: When the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller further stores at least one additional copy of the off-site backup firmware in one of the flash memories.
3. The electronic device according to claim 1, characterized in that: At least one of the flash memories stores at least one first backup firmware, and the backup firmware stored in the electronically erasable rewritable read-only memory is defined as a second backup firmware; when the hard disk controller determines that the firmware is damaged, the hard disk controller first determines whether the first backup firmware is damaged; if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will use the first backup firmware to start the solid-state hard disk device; if the hard disk controller determines that the first backup firmware is damaged, the hard disk controller will execute the backup firmware determination step.
4. The electronic device according to claim 3, characterized in that: If the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will write the first backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller.
5. A solid state hard disk device, characterized in that: The solid state drive device can be connected to a substrate of an electronic device through a PCIE port, and the substrate includes a main controller. When receiving a startup failure signal transmitted by the solid state drive device, the main controller can communicate with a remote electronic device to obtain a remote backup firmware and transmit the remote backup firmware to the solid state drive device. The solid state drive device includes: A motherboard; A plurality of flash memories are arranged on the mainboard, wherein a firmware is stored in one of the flash memories; At least one electronically erasable rewritable read-only memory, which is disposed on the mainboard, and the electronically erasable rewritable read-only memory stores a backup firmware; a hard disk controller, which is disposed on the mainboard and can receive a start signal transmitted by the main controller; A PCIE controller, which is disposed on the mainboard and connected to the electronically erasable rewritable read-only memory; When the hard disk controller receives the start signal, the hard disk controller will execute a firmware determination step: determining whether the firmware is damaged; If the hard disk controller determines that the firmware is damaged, the hard disk controller will perform the following steps: A backup firmware determination step: reading the backup firmware and determining whether the backup firmware is damaged; If the hard disk controller determines that the backup firmware is damaged, the hard disk controller will transmit a startup failure signal to the main controller; After receiving the remote backup firmware, the hard disk controller will perform the following steps: A remote backup firmware determination step: determining whether the remote backup firmware is damaged; If the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller will use the firmware to start the solid-state hard disk device, and the hard disk controller will also return a startup success signal to the main controller, and the hard disk controller will also write the off-site backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller; If the hard disk controller determines that the remote backup firmware is damaged, a startup failure signal is sent back to the main controller.
6. The solid state hard disk device according to claim 5, characterized in that: When the hard disk controller determines that the off-site backup firmware is not damaged, the hard disk controller further stores at least one additional copy of the off-site backup firmware in one of the flash memories.
7. The solid state hard disk device according to claim 5, characterized in that: At least one of the flash memories stores at least one first backup firmware, and the backup firmware stored in the electronically erasable rewritable read-only memory is defined as a second backup firmware; when the hard disk controller determines that the firmware is damaged, the hard disk controller first determines whether the first backup firmware is damaged; if the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will use the first backup firmware to start the solid-state hard disk device; if the hard disk controller determines that the first backup firmware is damaged, the hard disk controller will execute the backup firmware determination step.
8. The solid state hard disk device according to claim 7, characterized in that: If the hard disk controller determines that the first backup firmware is not damaged, the hard disk controller will write the first backup firmware into the electronically erasable rewritable read-only memory through the PCIE controller.
9. An artificial satellite, characterized in that: The artificial satellite comprises an artificial satellite body and the electronic device described in any one of claims 1 to 4; the remote electronic device is a ground base station, and the electronically erasable rewritable read-only memory complies with space specifications.
Citation Information
Patent Citations
Method for updating firmware
CN101295253A
Solid state disk
CN104423890A
Method for automatically replying firmware of baseboard management controller
CN113687843A
Solid-state disk and startup method
TWI722852B
System and Method for Transparent Hard Disk Drive Update
US20080141235A1
