Firmware burning method based on solid state disk

Abstract

The invention relates to the technical field of firmware burning, and discloses a firmware burning method based on a solid state disk, which comprises the steps of data analysis, parameter configuration, firmware burning, multi-stage verification, burning parameter adjustment and final verifier.The method has the advantages that in the aspect of accuracy, data segments and integral firmware are verified, calculated and compared through the multi-stage verification; and errors can be accurately positioned and corrected, and accurate burning is ensured. And in the aspect of adjustability, the burning speed and voltage are dynamically adjusted according to the average time and voltage recorded in the burning state, different conditions are adapted, and burning is optimized. And the burning state is monitored in real time, the burning time and voltage are recorded, and a basis is provided for abnormality checking and parameter adjustment. The programming parameters are reasonably configured, the programming speed and voltage are determined according to the firmware size, the preset time, the basic voltage and the like, it is guaranteed that the programming process is stable and efficient, and the solid state disk firmware programming quality and success rate are comprehensively improved.

Description

Technical Field

[0001] The present invention relates to the technical field of firmware burning, and in particular to a firmware burning method based on a solid state hard disk. Background Art

[0002] With the rapid development of information technology, solid-state drives (SSDs) have been widely used in various electronic devices due to their excellent performance, such as high-speed reading and writing, low power consumption, and good shock resistance. From daily office computers to servers in data centers, to convenient mobile storage devices, they are indispensable. Firmware, as the core software component of solid-state drives, controls key functions such as data storage, reading, erasing, and communication with the host system. Its importance is self-evident.

[0003] In practical applications, with the emergence of new storage technologies, continuous upgrades of operating systems, and the emergence of hardware compatibility issues, the update and upgrade of SSD firmware has become more frequent. However, traditional firmware burning methods have many disadvantages. On the one hand, data transmission is easily affected by factors such as electromagnetic interference and hardware failure, resulting in data loss or damage, and the lack of an effective data integrity protection mechanism makes it difficult to detect these problems, which in turn affects the performance and stability of the device. On the other hand, the hardware characteristics of SSDs of different models and specifications vary greatly, such as storage capacity, read and write speed, voltage requirements, etc., but the parameters of existing burning methods are often fixed and cannot be flexibly adapted. It is easy to cause burning failure or poor firmware performance due to improper burning speed and voltage settings. At the same time, during the burning process, many technologies lack real-time monitoring of key parameters such as burning time and voltage, making it difficult to detect abnormalities in time and dynamically adjust parameters, and it is difficult to adapt to complex hardware conditions and burning environments.

[0004] In summary, in order to meet the needs of SSD firmware updates and improve the burning success rate and firmware quality, a new firmware burning method is urgently needed that can ensure data integrity, flexibly adjust burning parameters and monitor the burning status in real time. Summary of the invention

[0005] The purpose of the present invention is to provide a firmware burning method based on a solid state hard disk, which solves the technical problems raised in the background technology.

[0006] The purpose of the present invention can be achieved by the following technical solutions: The firmware burning method based on the solid state drive includes the following steps: Step 1: Data analysis: Obtain the firmware data to be burned, then accumulate and perform modulus operations on all bytes in the firmware data to obtain the checksum value of the firmware data; then segment the firmware data in byte order, then accumulate and perform modulus operations on all bytes in each data segment to obtain the checksum value of each data segment; Step 2: Parameter configuration: Obtain the firmware size in the solid-state drive, and configure the solid-state drive burning speed in combination with the preset burning time; at the same time, obtain the basic voltage value of the solid-state drive when it is working normally, and configure the solid-state drive burning voltage in combination with the preset adjustment coefficient and voltage adjustment amount; Step 3: Firmware burning: The burning time of each data segment is determined according to the size of the firmware in the solid state drive and the burning speed of the solid state drive, and then the data segments are burned to the solid state drive in sequence according to the order of the firmware data segmentation and the burning time of each data segment; Step 4: Multi-stage verification: When each data segment is burned, the checksum is calculated and compared with the checksum value before burning. When all data segments are burned, the overall checksum is calculated for all data segments after burning, and the firmware data is compared with the checksum value of the firmware data. Step 5: Adjust the burning parameters: The programming speed and programming voltage are dynamically adjusted according to the data recorded by the programming status monitoring.

[0007] As a further solution of the present invention: In Step A1, the calculation formula of the checksum value of the firmware data is: ; Where, C0 is the checksum value of the firmware data, Bi is each byte of the firmware data, i=1, 2, ... L, L is the total number of bytes of the firmware data; The calculation formula for the checksum value of each data segment in StepA2 is: ; Where C1 j B0 is the checksum value of each data segment. k，j is the byte of each data segment, k=1, 2, ...N.

[0008] As a further solution of the present invention: the segmentation method in Step A2 is as follows: The firmware data is divided into several data segments with the pre-specified number of bytes N as the unit, and the data segment size of each data segment is marked as D j , j = 1, 2, ... m, m is the total number of data segments, and ,in, Indicates the round-up symbol.

[0009] As a further solution of the present invention: the calculation formula for the burning time of each data segment is: , where t j The burning time for each data segment.

[0010] As a further solution of the present invention: in step 2, the calculation formula of the burning speed of the solid state hard disk is: ; In the formula, V is the burning speed of the SSD, S is the firmware size in the SSD, and T is the preset burning time; The calculation formula for the solid state drive burning voltage is: ; Where U is the SSD programming voltage, U1 is the SSD base voltage, λ is the preset adjustment coefficient, and U t is the preset voltage adjustment amount.

[0011] As a further solution of the present invention: the data segment checksum calculation method is as follows: Mark the bytes of each data segment after programming as LB0 k1，j1 , j1=1, 2, ..., m1, m1 is the total number of data segments after programming is completed, k1=1, 2, ..., N1, N1 is the number of bytes in the j1th data segment; pass: ; After the burning is completed, all bytes in each data segment are accumulated and modulo operation is performed to obtain the checksum value LC1 of each data segment after the burning is completed. j1 ; The data segment comparison method is as follows: Extract the checksum value C1 of each data segment before burning j ; Then the checksum value LC1 of each data segment after burning is completed j1 The checksum value C1 of each data segment before burning j For comparison: If LC1 j1 =C1 j , it indicates that the corresponding data segment is burned correctly; otherwise, it means that an error occurs in the burning process of the data segment, and the corresponding data segment is re-burned.

[0012] As a further solution of the present invention: the overall checksum calculation method is as follows: Extract the checksum value LC1 of each data segment after burning is completed j1 ; Then through: ; Set the checksum value of all data segments to LC1j1 Accumulate and perform a 256 modulo operation on the accumulated result to obtain the overall checksum LC0 of all data segments; The firmware data comparison is as follows: Extract the checksum value C0 of the firmware data before burning; Then compare the overall checksum LC0 of all data segments after burning is completed with the checksum value C0 of the firmware data before burning: If LC0=C0, it means the entire firmware data is burned correctly; If the two are inconsistent, re-burn the entire firmware.

[0013] As a further solution of the present invention: during the programming process, the programming status is monitored in real time, and the programming time and programming voltage of each data segment are recorded in detail, and are marked as t1 and t2, respectively. j and U1 j ; Among them, for the monitoring of the burning time, the time point when each data segment starts burning and ends burning is recorded by a timer, and the difference between the two is the burning time t1 of the data segment. j ; For the monitoring of the burning voltage, use the voltage sensor to measure the voltage value U1 in real time during the burning process j .

[0014] As a further solution of the present invention: the dynamic adjustment method in step 5 is as follows: First pass: , calculate the dynamically adjusted burning speed VT; Among them, t0 is the average burning time; Then pass: , calculate the dynamically adjusted burning speed UT; Among them, U0 is the average burning voltage; As a further solution of the present invention: it also includes the steps of: final verification: Get the firmware data after burning is completed, and mark each byte of the firmware data as BW i1 , i1=1, 2, ... L1, L1 is the total number of bytes of firmware data after burning is completed; pass: ; After the burning is completed, all bytes in the firmware data are accumulated and modulo operation is performed to obtain the checksum value CW0 of the firmware data after the burning is completed; Then extract the checksum value C0 of the firmware data before burning; Then compare the checksum value CW0 of the firmware data after burning with the checksum value C0 of the firmware data before burning: If CW0=C0, it indicates that the entire firmware data is burned correctly; otherwise, the entire firmware needs to be re-burned.

[0015] Beneficial effects of the present invention: The present invention calculates and compares the checksums before and after the data segments are burned, calculates and compares the checksums of all data segments as a whole and compares them with the checksums of the firmware data before burning, and finally calculates and compares the checksums of the firmware data after burning is completed. The multiple check mechanisms can effectively find errors in the data segments and the overall firmware data during the burning process, thereby ensuring the accuracy of burning.

[0016] The present invention calculates the checksum for each data segment separately, and compares the checksum after burning with that before burning, so as to accurately locate the data segment with error, so as to timely re-burn and avoid error propagation, thereby ensuring the accuracy of burning each data segment.

[0017] The present invention dynamically adjusts the burning speed and the burning voltage according to the average burning time and the average burning voltage recorded by the burning state monitoring, can adapt to the characteristics of different solid state hard disks and the actual situation during the burning process, optimize the burning process, and improve the burning success rate.

[0018] The present invention monitors the burning time and burning voltage of each data segment in real time during the burning process, and records relevant data in detail, so as to timely discover abnormal situations in the burning process and provide a basis for subsequent burning parameter adjustment.

[0019] The present invention calculates a suitable burning speed according to the size of the firmware in the solid state hard disk and the preset burning time, so that the burning process can be reasonably planned in terms of time.

[0020] The present invention determines the programming voltage according to the basic voltage value required for the normal operation of the solid state hard disk in combination with a preset adjustment coefficient and a voltage adjustment amount, thereby ensuring that the programming process is performed under appropriate voltage conditions and improving the programming stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The present invention will be further described below in conjunction with the accompanying drawings.

[0022] Figure 1 It is a flow chart of a firmware burning method based on a solid state hard disk of the present invention.

[0023] Figure 2 It is a flow chart of multi-stage verification in the firmware burning method based on solid state hard disk of the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] Embodiment 1

[0026] See also Figure 1 and Figure 2 As shown, the present invention is a firmware burning method based on a solid state drive, comprising the following steps: Step 1: Data analysis: StepA1, obtain the firmware data to be burned; Each byte of the firmware data is marked as Bi, i=1, 2, ..., L, where L is the total number of bytes of the firmware data; pass: ; All bytes in the firmware data are accumulated and modulo-operated to generate a checksum value C0 for identifying the integrity of the firmware data; StepA2, firstly segment the firmware data in byte order; The method is as follows: The firmware data is divided into several data segments with the pre-specified number of bytes N as the unit, and the data segment size of each data segment is marked as D j , j = 1, 2, ... m, m is the total number of data segments, and ,in, Indicates the rounding up symbol; In this embodiment, for example, if the total number of bytes of the firmware data is L=1025, and the pre-specified number of bytes is N=100, then ; Then mark the bytes of each data segment as B0 k，j , k=1, 2, ... N; pass: ; All bytes in each data segment are accumulated and modulo-operated to generate a checksum value C1 used to identify the integrity of each data segment in the firmware data. j ; Step 2: Parameter configuration: StepB1, burn speed configuration; First, obtain the firmware size in the SSD and mark it as S; Then extract the preset burning time and mark it as T; Then through: ; Calculate the burning speed V of the solid state drive; StepB2, programming voltage configuration; First, obtain the basic voltage value required for the SSD to work normally and mark it as U1; In this embodiment, the basic voltage value is obtained from a technical specification document of the solid state drive; Then pass: ; In the formula, λ is the preset adjustment coefficient, U t is the preset voltage adjustment amount; In this embodiment, the adjustment coefficient is adjusted according to the characteristics of the solid state drive and the actual burning situation; for example, if the solid state drive is sensitive to voltage changes, a smaller adjustment coefficient may need to be selected to avoid excessive voltage fluctuations; otherwise, the adjustment coefficient may be appropriately increased; the voltage adjustment amount is determined according to some factors in the burning process, such as ambient temperature, stability of the burning device, etc., which is determined through experiments and experience; Step 3: Firmware burning: pass: ; Calculate the burning time t of each data segment j ; According to the order of firmware data segmentation, and according to the burning time t of each data segment j Burn each data segment to the solid state drive in sequence; When the programming time of a data segment is obviously too long or the programming voltage fluctuates abnormally, dynamically adjust the programming parameters or check whether there is a problem with the hardware device; Step 4: Multi-stage verification: Step D1, data segment verification; When each data segment is burned, the checksum is calculated and compared with the checksum value before burning; Step D1.1, checksum calculation method is as follows: Mark the bytes of each data segment after programming as LB0 k1，j1 , j1=1, 2, ..., m1, m1 is the total number of data segments after programming is completed, k1=1, 2, ..., N1, N1 is the number of bytes in the j1th data segment; pass: ; After the burning is completed, all bytes in each data segment are accumulated and modulo operation is performed to generate a checksum value LC1 used to identify the integrity of each data segment after the burning is completed. j1 ; Step D1.2, the data segment comparison method is as follows: Extract the checksum value C1 of each data segment before burning j ; Then the checksum value LC1 of each data segment after burning is completed j1 The checksum value C1 of each data segment before burning j For comparison: If LC1 j1 =C1 j , it indicates that the corresponding data segment is correctly burned; otherwise, it means that an error occurs in the burning process of the data segment, and the corresponding data segment is re-burned; Step D2, firmware data verification; When all data segments are burned, the overall checksum calculation is performed on all the data segments after the burning is completed, and the firmware data is compared with the checksum value of the firmware data; Step D2.1, the overall checksum calculation method is as follows: Extract the checksum value LC1 of each data segment after burning is completed j1 ; Then through: ; Set the checksum value of all data segments to LC1 j1 Accumulate and perform a 256 modulo operation on the accumulated result to obtain the overall checksum LC0 of all data segments; Step D2.2, firmware data comparison method is as follows: Extract the checksum value C0 of the firmware data before burning; Then compare the overall checksum LC0 of all data segments after burning is completed with the checksum value C0 of the firmware data before burning: If LC0=C0, it means the entire firmware data is burned correctly; If the two are inconsistent, it means that there are errors in some data segments or data transmission problems during the burning process, and the entire firmware needs to be reburned.

[0027] This embodiment generates a checksum value by accumulating and taking the modulus of all bytes of the firmware data and generating a checksum value by accumulating and taking the modulus of bytes of each data segment, thereby marking the integrity of the firmware data before burning, providing a basis for subsequent verification of the burning result, and being able to effectively detect data errors that may occur during the burning process; the burning speed is calculated according to the firmware size of the solid-state hard disk and the preset burning time, and the burning voltage is configured in combination with the basic voltage value of the normal operation of the solid-state hard disk and the preset adjustment coefficient and voltage adjustment amount, so that the burning process can be optimized in terms of speed and voltage according to actual conditions, thereby improving the stability and success rate of burning; in the two stages of data segment verification and firmware data verification, each data segment and the entire firmware data are checked and compared before and after burning, respectively, to ensure the accuracy of the burning data, and if there is any inconsistency, it is re-burned to ensure the correctness of the final burning result.

[0028] Embodiment 2

[0029] See also Figure 1 and Figure 2 As shown, as the second embodiment of the present invention, when the present application is implemented, compared with the first embodiment, the technical solution of the present embodiment is different from the first embodiment only in that in the present embodiment, when the firmware is burned, the burning status is also monitored, as follows: During the programming process, the programming status is monitored in real time, and the programming time and programming voltage of each data segment are recorded in detail, and marked as t1 respectively. j and U1 j ; In this embodiment, for monitoring the burning time, a timer is used to record the time point when each data segment starts burning and ends burning, and the difference between the two is the burning time t1 of the data segment. j ; For the monitoring of the burning voltage, use the voltage sensor to measure the voltage value U1 in real time during the burning process j ; This embodiment also includes the step of programming parameter adjustment: According to the data recorded by the burning status monitoring, the burning speed and burning voltage are dynamically adjusted; In this embodiment, through dynamic adjustment, the burning process can be more adapted to different hardware conditions and burning situations, thereby improving the burning success rate; First pass: , calculate the dynamically adjusted burning speed VT; Among them, t0 is the average burning time; In this embodiment, the burning speed is reasonably adjusted according to the difference between the actual burning time and the average time; Then pass: , calculate the dynamically adjusted burning speed UT; Among them, U0 is the average burning voltage; In this embodiment, the programming voltage is dynamically corrected according to the relationship between the actual programming voltage and the average voltage; This embodiment monitors the programming time and programming voltage of each data segment in real time during the programming process, so as to timely grasp the changes of key parameters in the programming process and provide data support for subsequent adjustment and analysis; according to the data recorded by the programming status monitoring, the programming speed and programming voltage are dynamically adjusted through formula calculation; this dynamic adjustment mechanism makes the programming process more adaptable to different hardware conditions and programming situations, can further improve the programming success rate, and enhance the adaptability and robustness of the programming method.

[0030] Embodiment 3

[0031] See also Figure 1 and Figure 2 As shown, as the third embodiment of the present invention, when the present application is specifically implemented, compared with the first and second embodiments, the technical solution of this embodiment is to combine the solutions of the first and second embodiments, and the difference between the technical solution of this embodiment and the first and second embodiments is that this embodiment also includes the final verification step: Get the firmware data after burning is completed, and mark each byte of the firmware data as BW i1 , i1=1, 2, ... L1, L1 is the total number of bytes of firmware data after burning is completed; pass: ; After the burning is completed, all bytes in the firmware data are accumulated and modulo operation is performed to obtain the checksum value CW0 of the firmware data after the burning is completed; Then extract the checksum value C0 of the firmware data before burning; Then compare the checksum value CW0 of the firmware data after burning with the checksum value C0 of the firmware data before burning: If CW0=C0, it means the entire firmware data is burned correctly; If the two are inconsistent, it means that there are errors in some data segments or data transmission problems during the burning process, and the entire firmware needs to be reburned; In this embodiment, the final checksum is compared with the previously calculated related checksum to ensure that the firmware is still intact after the entire burning process; In this embodiment, key data in the programming process are also recorded, including programming time, programming voltage, checksum and other information; these records not only provide a basis for subsequent possible troubleshooting, but also help to analyze the data of the programming process and further optimize the programming method; After the burning is completed, the present embodiment performs checksum calculation on the burned firmware data again, and compares it with the checksum value before burning; through this final verification step, it is further ensured that the entire firmware data is still accurate after the complete burning process, avoiding errors that may be missed in the previous stage; recording key data in the burning process, such as burning time, burning voltage, checksum and other information, not only provides a detailed basis for subsequent possible troubleshooting, but also helps to perform data analysis on the burning process, and provides data support for further optimizing the burning method.

[0032] Embodiment 4

[0033] See also Figure 1 and Figure 2 As shown, as the fourth embodiment of the present invention, when the present application is specifically implemented, compared with the first, second and third embodiments, the technical solution of this embodiment is to combine and implement the solutions of the above-mentioned first, second and third embodiments.

[0034] This embodiment combines the advantages of embodiments one, two and three. It has the data integrity check, parameter configuration optimization and multi-stage verification mechanism in embodiment one, and the ability to monitor the burning status in real time and dynamically adjust the burning parameters in embodiment two. It also includes the advantages of the final verification in embodiment three to ensure accuracy and the key data recording to assist in troubleshooting and optimization. It comprehensively improves the reliability, adaptability and optimizability of the firmware burning method based on solid-state drives, and maximizes the success rate of firmware burning and the accuracy of the burning results.

[0035] The above formulas are all dimensionless and numerical calculations. The formula is a formula for the most recent real situation obtained by collecting a large amount of data and performing software simulation. The preset parameters and thresholds in the formula are set by technicians in this field according to actual conditions.

[0036] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A firmware burning method based on a solid state drive, characterized in that: The following steps are involved: Step 1: Data analysis: Obtain the firmware data to be burned, then accumulate and perform modulus operations on all bytes in the firmware data to obtain the checksum value of the firmware data; then segment the firmware data in byte order, then accumulate and perform modulus operations on all bytes in each data segment to obtain the checksum value of each data segment; Step 2: Parameter configuration: Obtain the firmware size in the solid-state drive, and configure the solid-state drive burning speed in combination with the preset burning time; at the same time, obtain the basic voltage value of the solid-state drive when it is working normally, and configure the solid-state drive burning voltage in combination with the preset adjustment coefficient and voltage adjustment amount; Step 3: Firmware burning: The burning time of each data segment is determined according to the size of the firmware in the solid state drive and the burning speed of the solid state drive, and then the data segments are burned to the solid state drive in sequence according to the order of the firmware data segmentation and the burning time of each data segment; Step 4: Multi-stage verification: When each data segment is burned, the checksum is calculated and compared with the checksum value before burning. When all data segments are burned, the overall checksum is calculated for all data segments after burning, and the firmware data is compared with the checksum value of the firmware data. Step 5: Adjust the burning parameters: The programming speed and programming voltage are dynamically adjusted according to the data recorded by the programming status monitoring.

2. The method for burning firmware based on a solid state drive according to claim 1, characterized in that: In StepA1, the calculation formula for the checksum value of the firmware data is: ; Wherein, C0 is the checksum value of the firmware data, Bi is each byte of the firmware data, i=1, 2, ... L, and L is the total number of bytes of the firmware data.

3. The method for burning firmware based on a solid state drive according to claim 2, characterized in that: The segmentation method in StepA2 is as follows: The firmware data is divided into several data segments with the pre-specified number of bytes N as the unit, and the data segment size of each data segment is marked as D j , j = 1, 2, ... m, m is the total number of data segments, and ,in, Indicates the rounding up symbol; The calculation formula for the checksum value of each data segment in StepA2 is: ; Where C1 j B0 is the checksum value of each data segment. k，j is the byte of each data segment, k=1, 2, ...N.

4. The method for burning firmware based on a solid state drive according to claim 3, characterized in that: The calculation formula for the burning time of each data segment is: , where t j The burning time for each data segment.

5. The method for burning firmware based on a solid state drive according to claim 1, characterized in that: In step 2, the calculation formula for the burning speed of the solid state drive is: ; In the formula, V is the burning speed of the SSD, S is the firmware size in the SSD, and T is the preset burning time; The calculation formula for the solid state drive burning voltage is: ; Where U is the SSD programming voltage, U1 is the SSD base voltage, λ is the preset adjustment coefficient, and U t is the preset voltage adjustment amount.

6. The method for burning firmware based on a solid state drive according to claim 3, characterized in that: The data segment checksum is calculated as follows: Mark the bytes of each data segment after programming as LB0 k1，j1 , j1=1, 2, ..., m1, m1 is the total number of data segments after programming is completed, k1=1, 2, ..., N1, N1 is the number of bytes in the j1th data segment; pass: ; After the burning is completed, all bytes in each data segment are accumulated and modulo operation is performed to obtain the checksum value LC1 of each data segment after the burning is completed. j1 ; The data segment comparison method is as follows: Extract the checksum value C1 of each data segment before burning j ; Then the checksum value LC1 of each data segment after burning is completed j1 The checksum value C1 of each data segment before burning j For comparison: If LC1 j1 =C1 j , it indicates that the corresponding data segment is burned correctly; otherwise, it means that an error occurs in the burning process of the data segment, and the corresponding data segment is re-burned.

7. The method for burning firmware based on a solid state drive according to claim 2, characterized in that: The overall checksum is calculated as follows: Extract the checksum value LC1 of each data segment after burning is completed j1 ; Then through: ; Set the checksum value of all data segments to LC1 j1 Accumulate and perform a 256 modulo operation on the accumulated result to obtain the overall checksum LC0 of all data segments; The firmware data comparison is as follows: Extract the checksum value C0 of the firmware data before burning; Then compare the overall checksum LC0 of all data segments after burning is completed with the checksum value C0 of the firmware data before burning: If LC0=C0, it means the entire firmware data is burned correctly; If the two are inconsistent, re-burn the entire firmware.

8. The method for burning firmware based on a solid state drive according to claim 5, characterized in that: During the programming process, the programming status is monitored in real time, and the programming time and programming voltage of each data segment are recorded in detail, and marked as t1 respectively. j and U1 j ; Among them, for the monitoring of the burning time, the time point when each data segment starts burning and ends burning is recorded by a timer, and the difference between the two is the burning time t1 of the data segment. j ; For the monitoring of the burning voltage, use the voltage sensor to measure the voltage value U1 in real time during the burning process j .

9. The method for burning firmware based on a solid state drive according to claim 8, characterized in that: The dynamic adjustment method in step 5 is as follows: First pass: , calculate the dynamically adjusted burning speed VT; Among them, t0 is the average burning time; Then pass: , calculate the dynamically adjusted burning speed UT; Among them, U0 is the average programming voltage.

10. The method for burning firmware based on a solid state drive according to claim 2, characterized in that: Also includes the steps: Final verification: Get the firmware data after burning is completed, and mark each byte of the firmware data as BW i1 , i1=1, 2, ... L1, L1 is the total number of bytes of firmware data after burning is completed; pass: ; After the burning is completed, all bytes in the firmware data are accumulated and modulo operation is performed to obtain the checksum value CW0 of the firmware data after the burning is completed; Then extract the checksum value C0 of the firmware data before burning; Then compare the checksum value CW0 of the firmware data after burning with the checksum value C0 of the firmware data before burning: If CW0=C0, it indicates that the entire firmware data is burned correctly; otherwise, the entire firmware needs to be re-burned.

Images