A firmware system data transmission method and burning device

Abstract

The present invention relates to the field of firmware burning of embedded devices, and in particular to a method for transmitting firmware system data and a burning device thereof. The transmission method includes S1. opening a PC end, powering on an embedded mainboard, and connecting the embedded mainboard to the PC end; S2. opening a PC control module, calling a native tool to burn ExtBoot to the embedded mainboard; S3. The embedded mainboard restarts, runs the ExtBoot system, and reports a Ready indication signal; S4. The PC control module receives the Ready indication signal, the handshake is successful, and starts to send control instructions and data transmission; S5. The embedded mainboard processes instructions and data, and replies with response information; S6. The PC control module continues to send control instructions and data transmission until the processing is completed; S7. Calling a native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning. The operator only needs to load the required firmware system data in the transmission unit of the PC control module to transfer the firmware system data to the embedded mainboard for burning, which is simple and fast.

Description

Technical Field

[0001] The invention relates to the field of embedded device firmware burning, and in particular to a firmware system data transmission method and a burning device thereof. Background Art

[0002] In the wireless electronic product solutions provided by AmbiqMicro, by default, only the burning tool provided by it can be used to burn the firmware into the on-chip memory of the Ambiq series MCU. Due to the limitation of the on-chip storage space, the functions that can be realized are limited, and more functions cannot be expanded to meet customer needs. Summary of the invention

[0003] The present invention provides a firmware system data transmission method and a firmware system data burning device, aiming to solve the problem of limited storage space in the solution provided by AmbiqMicro.

[0004] The present invention provides a method for transmitting firmware system data, comprising the following steps:

[0005] S1. Turn on the PC, power on the embedded mainboard, and connect the embedded mainboard to the PC;

[0006] S2. Turn on the PC control module and call the native tool to burn ExtBoot to the embedded motherboard;

[0007] S3. The embedded mainboard restarts, runs the ExtBoot system, and reports a Ready indication signal;

[0008] S4. The PC control module receives the Ready indication signal, the handshake is successful, and it starts to send control instructions and data transmission;

[0009] S5. The embedded mainboard processes the instructions and data and replies with the response information;

[0010] S6. The PC control module continues to send control instructions and data transmission until the processing is completed;

[0011] S7. Call the native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning.

[0012] As a further improvement of the present invention, the transmission method also includes a work flow of a PC control module in data transmission, comprising the following steps:

[0013] a1. Turn on the PC control module, call the native tool to burn ExtBoot, and wait for the Ready indication of the embedded motherboard;

[0014] a2. After receiving the Ready indication signal from the embedded motherboard, the PC control module performs parameter configuration and starts sending control instructions and data transmission;

[0015] a3. After successfully receiving the response information from the embedded motherboard, read the data, encapsulate the frame data, and continue to send control instructions and data transmission;

[0016] a4. Successfully receive the response information from the embedded mainboard again. If a successful end response is received, call the native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning.

[0017] As a further improvement of the present invention, the step a2 specifically further includes:

[0018] a21. The PC control module determines whether it has received the Ready indication signal from the embedded motherboard. If it has received it, it executes step a22; if it has not received it within the time limit, it accumulates the number of timeouts and determines whether the number exceeds the limit. If the number does not exceed the limit, it continues to wait for the Ready indication from the embedded motherboard. If the number exceeds the limit, it ends the task directly;

[0019] a22. Determine whether the Ready indication signal is formatted. If not, directly perform parameter configuration. If yes, send the formatting instruction and determine whether a response is received. If not, terminate the task directly. If a response is received, continue to determine whether the formatting is successful. If the formatting is unsuccessful, terminate the task directly. If the formatting is successful, perform parameter configuration.

[0020] As a further improvement of the present invention, the step a3 specifically further includes:

[0021] s31. The PC control module determines whether it has received the response information from the embedded motherboard. If it has received the response information, it executes step a32; if it has not received the response information within the time limit, it executes step a33;

[0022] a32 determines whether the response information is successfully received, if successfully received, read the data, if not successfully received, execute step a33;

[0023] a33. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

[0024] As a further improvement of the present invention, the step a4 specifically further includes:

[0025] a41. The PC control module determines whether it has received a response from the embedded motherboard. If it has received a response, it executes step a42. If it has not received a response after a timeout, it executes step a45.

[0026] a42. Determine whether the response information is successfully received. If it is successfully received, execute step a43; if it is not successfully received, determine whether to end the task. If it is, end the task directly. Otherwise, execute step a45;

[0027] a43 determines whether the data transmission is completed, if so, execute step a44, if otherwise, return to step a3 to continue reading data;

[0028] a44 determines whether a successful end response message is received, if so, the native tool is called to burn the firmware kernel to the embedded motherboard to complete the embedded motherboard firmware burning; if otherwise, execute step a45;

[0029] a45. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

[0030] As a further improvement of the present invention, the transmission method includes a workflow of an embedded motherboard in data burning, comprising the following steps:

[0031] b1. The embedded mainboard is started and in standby mode. It determines whether to execute ExtBoot. If it is not executed within the time limit, it continues to wait. If it is executed, the system restarts and runs the ExtBoot system, sending a Ready indication signal.

[0032] b2 determines whether the data is received from the PC control module, if the timeout is not received, continue to send the Ready indication signal; if received, the configuration parameters are processed and a response instruction is sent and then step b3 is executed;

[0033] b3 determines whether the response command feedback data is received, if the timeout is not received, continue to send a response command, if received, execute step b4;

[0034] b4. Check the frame data and determine whether the check is successful. If the check is successful, execute step b5; if the check fails, send the data check failure result and return to step b3;

[0035] b5 determines whether the data is the last frame of data, if it is the remaining block data burned, read the data and determine whether it is consistent with the burned data, if the same is sent a successful end response and end the task, if not the error end response is sent and end the task; if otherwise, execute step b6;

[0036] b6. Determine whether the data is a whole block of data. If so, burn the block data, read the block data and determine whether it is consistent with the burned data. If it is consistent, return to step b3. If it is inconsistent, send an error end response and end the task; otherwise, return to step b3.

[0037] As a further improvement of the present invention, in step b2, after receiving the data sent by the PC control module, the following steps are also included:

[0038] b21 determines whether the formatting instruction is received, if received, the data is formatted, and whether the formatting is successful, if successful, a successful response instruction is sent and step b22 is executed; if failed, a failure response instruction is sent and the task is terminated; if the formatting instruction is not received, step b22 is executed;

[0039] b22. Determine whether the configuration parameter instruction is received. If it is received, perform configuration parameter processing. If it is not received after a timeout, re-execute step b22.

[0040] The present invention also provides a device for burning firmware system data, which comprises:

[0041] PC control module: calls native tools to burn ExtBoot to the embedded mainboard, receives the Ready indication signal, sends control instructions and data transmission, and calls native tools to burn the firmware kernel to the embedded mainboard;

[0042] Embedded device mainboard: runs the ExtBoot system, reports the Ready indication signal, receives and processes instructions and data, replies with response information, and completes firmware burning;

[0043] The PC control module is connected to the embedded device mainboard.

[0044] As a further improvement of the present invention, the PC control module comprises:

[0045] Data reading unit: responsible for reading firmware system data into PC memory for pre-processing;

[0046] Encapsulation data unit; responsible for encapsulating firmware system data into frame data according to the protocol;

[0047] Transmission unit: responsible for transmitting frame data to the embedded mainboard;

[0048] Native burning tool control unit: responsible for calling the burning tool provided by AmbiqMicro to burn the firmware, compatible with the original burning method;

[0049] The data reading unit, the data encapsulation unit and the transmission unit are connected in sequence.

[0050] As a further improvement of the present invention, the embedded device mainboard comprises:

[0051] Data receiving unit: responsible for receiving frame data from PC;

[0052] Data verification unit: responsible for verifying the received frame data;

[0053] Burning data unit: responsible for burning the received block data into the extended memory;

[0054] The data receiving unit, the data checking unit and the data burning unit are connected in sequence.

[0055] The beneficial effects of the present invention are as follows: the present invention proposes a stable, reliable and simple method for transmitting and burning firmware system data into the expanded storage space of the embedded mainboard. The invention is simple to operate. The operator only needs to load the required firmware system data in the transmission unit of the PC control module to transmit the firmware system data to the embedded mainboard for burning, which is simple and fast. It is efficient for early R&D debugging and mid-term product testing. Especially for the later batch production of the factory, it is very convenient for the operation of the production line staff, improves production efficiency, and is also extremely convenient for after-sales maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Figure 1 It is a structural block diagram of a device for burning firmware system data of the present invention;

[0057] Figure 2 It is a working diagram of a PC control module with a firmware system data transmission function in the present invention;

[0058] Figure 3 It is a working flow chart of the embedded mainboard with the firmware system data burning function in the present invention. DETAILED DESCRIPTION

[0059] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0060] The present invention provides a method for transmitting and burning firmware system data by only cooperating with an embedded mainboard in a transmission unit of a PC control module, so as to meet the customer's demand for rich and colorful product functions. To achieve this purpose, the present invention adopts two technical solutions to achieve the goal.

[0061] Embodiment 1:

[0062] According to a first aspect of the present invention, there is provided a method for transmitting firmware system data which is simple to operate and only needs to be performed on a transmission unit of a PC control module, comprising the following steps:

[0063] S1. Turn on the PC, power on the embedded mainboard, and connect the embedded mainboard to the PC; turn on the transmission unit of the PC control module and connect it to the embedded mainboard;

[0064] S2. Turn on the PC control module and call the native tool to burn ExtBoot to the embedded motherboard;

[0065] S3. The embedded mainboard restarts, runs the ExtBoot system, and reports a Ready indication signal;

[0066] S4. The PC control module receives the Ready indication signal, the handshake is successful, and it starts to send control instructions and data transmission; the transmission unit of the PC control module sets the communication parameters, loads the data, issues a start transmission instruction, waits for the handshake with the embedded mainboard to succeed, and starts to transmit data until the end;

[0067] S5. The embedded mainboard processes the instructions and data and replies with the response information;

[0068] S6. The PC control module continues to send control instructions and data transmission until the processing is completed;

[0069] S7. Call the native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning.

[0070] Specifically, the transmission method is divided into a PC control module workflow with a firmware system data transmission function and an embedded mainboard workflow with a firmware system data burning function.

[0071] like Figure 2 As shown in the figure, the workflow of the PC control module in data transmission includes the following steps:

[0072] a1. Turn on the PC control module, call the native tool to burn ExtBoot, and wait for the Ready indication of the embedded motherboard.

[0073] a2. After receiving the Ready indication signal from the embedded motherboard, the PC control module performs parameter configuration and starts sending control instructions and data transmission.

[0074] a21. The PC control module determines whether it has received the Ready indication signal from the embedded motherboard. If it has received it, it executes step a22; if it has not received it within the time limit, it accumulates the number of timeouts and determines whether the number exceeds the limit. If the number does not exceed the limit, it continues to wait for the Ready indication from the embedded motherboard. If the number exceeds the limit, it ends the task directly;

[0075] a22. Determine whether the Ready indication signal is formatted. If not, directly perform parameter configuration. If yes, send the formatting instruction and determine whether a response is received. If not, terminate the task directly. If a response is received, continue to determine whether the formatting is successful. If the formatting is unsuccessful, terminate the task directly. If the formatting is successful, perform parameter configuration.

[0076] Formatting refers to erasing data on the external memory of the embedded motherboard. Whether to format is determined by whether the operator checks the format option in the control module of the PC. The benefit of formatting is that the external memory of the embedded motherboard only stores the latest data, eliminating the interference of old data.

[0077] a3. After successfully receiving the response information from the embedded mainboard, read the data, encapsulate the frame data, and continue to send control instructions and data transmission.

[0078] s31. The PC control module determines whether it has received a response message from the embedded motherboard. If it has received a response message, it executes step a32; if it has not received a response message after a timeout, it executes step a33; in this step, the PC control module receives a response message of configuration parameters;

[0079] a32 determines whether the response information is successfully received, if successfully received, read the data, if not successfully received, execute step a33;

[0080] a33. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

[0081] a4. Successfully receive the response information from the embedded mainboard again. If a successful end response is received, call the native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning.

[0082] a41. The PC control module determines whether it has received the response information from the embedded motherboard. If it has received it, it executes step a42. If it has not received it within a timeout, it executes step a45. In this step, the PC control module receives the response information of the transmission data.

[0083] a42. Determine whether the response information is successfully received. If it is successfully received, execute step a43; if it is not successfully received, determine whether to end the task. If it is, end the task directly. Otherwise, execute step a45;

[0084] a43 determines whether the data transmission is completed, if so, execute step a44, if otherwise returns to step a3 to continue reading data; in this step "determine whether the data transmission is completed" is for the end of the transmission frame data;

[0085] a44. Determine whether a successful end response message is received. If so, call the native tool to burn the firmware kernel to the embedded motherboard to complete the embedded motherboard firmware burning; if not, execute step a45; in this step, "determine whether a successful end response message is received" is for the end of the entire transfer file.

[0086] a45. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

[0087] like Figure 3 As shown in the figure, the workflow of the embedded motherboard in data burning includes the following steps:

[0088] b1. The embedded mainboard is started and in standby mode. It determines whether to execute ExtBoot. If it is not executed within the time limit, it continues to wait. If it is executed, the system restarts and runs the ExtBoot system, sending a Ready indication signal.

[0089] b2 determines whether the data is received from the PC control module, if the timeout is not received, continue to send the Ready indication signal; if received, the configuration parameters are processed and a response instruction is sent and then step b3 is executed;

[0090] b3 determines whether the response command feedback data is received, if the timeout is not received, continue to send a response command, if received, execute step b4;

[0091] b4. Check the frame data and determine whether the check is successful. If the check is successful, execute step b5; if the check fails, send the data check failure result and return to step b3;

[0092] b5 determines whether the data is the last frame of data, if it is the remaining block data burned, read the data and determine whether it is consistent with the burned data, if the same is sent a successful end response and end the task, if not the error end response is sent and end the task; if otherwise, execute step b6;

[0093] b6. Determine whether the data is a whole block of data. If so, burn the block data, read the block data and determine whether it is consistent with the burned data. If it is consistent, return to step b3. If it is inconsistent, send an error end response and end the task; otherwise, return to step b3.

[0094] "Whole block of data" refers to the operating unit of the external memory of the embedded motherboard, and "frame data" refers to the operating unit of data transmission between the PC and the embedded motherboard. One "whole block of data" can contain multiple "frame data".

[0095] Wherein, in step b2, after receiving the data sent by the PC control module, the following steps are also included:

[0096] b21 determines whether the formatting instruction is received, if received, the data is formatted, and whether the formatting is successful, if successful, a successful response instruction is sent and step b22 is executed; if failed, a failure response instruction is sent and the task is terminated; if the formatting instruction is not received, step b22 is executed;

[0097] b22. Determine whether the configuration parameter instruction is received. If it is received, perform configuration parameter processing. If it is not received after a timeout, re-execute step b22.

[0098] Formatting refers to erasing data on the external memory of the embedded motherboard. Whether to format is determined by whether the operator checks the format option in the control module of the PC. The benefit of formatting is that the external memory of the embedded motherboard only stores the latest data, eliminating the interference of old data.

[0099] The present invention proposes a method for transmitting and burning firmware system data to the expanded storage space in the embedded motherboard in a stable, reliable and simple manner. According to the above method, the operator only needs to perform simple operations on the transmission unit of the PC control module to start and complete the process of transmitting and burning the firmware system data to the embedded motherboard.

[0100] Embodiment 2:

[0101] like Figure 1 As shown, the present invention also provides a device for burning firmware system data, comprising:

[0102] PC control module 1: calls native tools to burn ExtBoot to the embedded mainboard, receives the Ready indication signal, sends control instructions and data transmission, and calls native tools to burn the firmware kernel to the embedded mainboard;

[0103] Embedded device mainboard 2: runs the ExtBoot system, reports the Ready indication signal, receives and processes instructions and data, replies with response information, and completes firmware burning;

[0104] The PC control module 1 is connected to the embedded device mainboard 2 .

[0105] The specific PC control module 1 includes:

[0106] Data reading unit 3: responsible for reading firmware system data into PC memory for pre-processing;

[0107] Encapsulation data unit 4; responsible for encapsulating firmware system data into frame data according to the protocol;

[0108] Transmission unit 5: responsible for transmitting frame data to the embedded mainboard;

[0109] Native burning tool control unit 6: responsible for calling the burning tool provided by Ambiq Micro to burn the firmware, compatible with the original burning method;

[0110] The data reading unit 3, the data encapsulation unit 4, and the transmission unit 5 are connected in sequence.

[0111] The embedded device mainboard 2 includes:

[0112] Data receiving unit 7: responsible for receiving frame data from PC;

[0113] Data verification unit 8: responsible for verifying the received frame data to ensure the correctness of the transmitted data;

[0114] Burning data unit 9: responsible for burning the received block data into the extended memory;

[0115] The data receiving unit 7, the data checking unit 8 and the data burning unit 9 are connected in sequence.

[0116] The present invention maintains the original burning mode unchanged, and adds a firmware system data transmission burning system. The difficulty and also the characteristic of the present invention is to add a data transmission burning method for expanding the storage space without affecting the original burning mode.

[0117] The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A method for transmitting firmware system data, characterized in that: The following steps are involved: S1. Turn on the PC, power on the embedded mainboard, and connect the embedded mainboard to the PC; S2. Turn on the PC control module and call the native tool to burn ExtBoot to the embedded motherboard; S3. The embedded mainboard restarts, runs the ExtBoot system, and reports a Ready indication signal; S4. The PC control module receives the Ready indication signal, the handshake is successful, and it starts to send control instructions and data transmission; S5. The embedded mainboard processes the instructions and data and replies with the response information; S6. The PC control module continues to send control instructions and data transmission until the processing is completed; S7. Call the native tool to burn the firmware kernel to the embedded mainboard, completing the embedded mainboard firmware burning; The workflow of the PC control module in data transmission includes the following steps: a1. Turn on the PC control module, call the native tool to burn ExtBoot, and wait for the Ready indication of the embedded motherboard; a2. After receiving the Ready indication signal from the embedded motherboard, the PC control module performs parameter configuration and starts sending control instructions and data transmission; a3. After successfully receiving the response information from the embedded motherboard, read the data, encapsulate the frame data, and continue to send control instructions and data transmission; a4. Successfully receive the response information of the embedded mainboard again. If a successful end response is received, call the native tool to burn the firmware kernel to the embedded mainboard to complete the embedded mainboard firmware burning; The step a2 specifically includes: a21. The PC control module determines whether it has received the Ready indication signal from the embedded motherboard. If it has received it, it executes step a22; if it has not received it within the time limit, it accumulates the number of timeouts and determines whether the number exceeds the limit. If the number does not exceed the limit, it continues to wait for the Ready indication from the embedded motherboard. If the number exceeds the limit, it ends the task directly; a22. Determine whether the Ready indication signal is formatted. If not, directly perform parameter configuration. If yes, send the formatting instruction and determine whether a response is received. If not, terminate the task directly. If a response is received, continue to determine whether the formatting is successful. If the formatting is unsuccessful, terminate the task directly. If the formatting is successful, perform parameter configuration.

2. The method for transmitting firmware system data according to claim 1, characterized in that: The step a3 specifically includes: s31 PC control module determines whether it has received a response message from the embedded motherboard, if received, execute step a32; if the timeout is not received, execute step a33; a32 determines whether the response information is successfully received, if successfully received, read the data, if not successfully received, execute step a33; a33. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

3. The method for transmitting firmware system data according to claim 1, characterized in that: The step a4 specifically includes: a41 PC control module determines whether it has received a response message from the embedded motherboard, if received, execute step a42, if the timeout is not received, execute step a45; a42. Determine whether the response information is successfully received. If it is successfully received, execute step a43; if it is not successfully received, determine whether to end the task. If it is, end the task directly. Otherwise, execute step a45; a43 determines whether the data transmission is completed, if so, execute step a44, if otherwise, return to step a3 to continue reading data; a44 determines whether a successful end response message is received, if so, the native tool is called to burn the firmware kernel to the embedded motherboard to complete the embedded motherboard firmware burning; if otherwise, execute step a45; a45. Resend control instructions and data transmission, accumulate timeout times, and determine whether the times exceed the limit. If the times do not exceed the limit, perform parameter configuration. If the times exceed the limit, terminate the task directly.

4. The method for transmitting firmware system data according to claim 1, characterized in that: The workflow of the embedded motherboard during data burning includes the following steps: b1. The embedded mainboard is started and in standby mode. It determines whether to execute ExtBoot. If it is not executed within the time limit, it continues to wait. If it is executed, the system restarts and runs the ExtBoot system, sending a Ready indication signal. b2 determines whether the data is received from the PC control module, if the timeout is not received, continue to send the Ready indication signal; if received, the configuration parameters are processed and a response instruction is sent and then step b3 is executed; b3 determines whether the response command feedback data is received, if the timeout is not received, continue to send a response command, if received, execute step b4; b4. Check the frame data and determine whether the check is successful. If the check is successful, execute step b5; if the check fails, send the data check failure result and return to step b3; b5 determines whether the data is the last frame of data, if it is the remaining block data burned, read the data and determine whether it is consistent with the burned data, if the same is sent a successful end response and end the task, if not the error end response is sent and end the task; if otherwise, execute step b6; b6. Determine whether the data is a whole block of data. If so, burn the block data, read the block data and determine whether it is consistent with the burned data. If it is consistent, return to step b3. If it is inconsistent, send an error end response and end the task; otherwise, return to step b3.

5. The method for transmitting firmware system data according to claim 4, characterized in that: In the step b2, after receiving the data sent by the PC control module, the following steps are also included: b21 determines whether the formatting instruction is received, if received, the data is formatted, and whether the formatting is successful, if successful, a successful response instruction is sent and step b22 is executed; if failed, a failure response instruction is sent and the task is terminated; if the formatting instruction is not received, step b22 is executed; b22. Determine whether the configuration parameter instruction is received. If it is received, perform configuration parameter processing. If it is not received after a timeout, re-execute step b22.

6. A device for burning firmware system data, characterized in that: A method for transmitting firmware system data according to any one of claims 1 to 5, comprising: PC control module: calls native tools to burn ExtBoot to the embedded mainboard, receives the Ready indication signal, sends control instructions and data transmission, and calls native tools to burn the firmware kernel to the embedded mainboard; Embedded device mainboard: runs the ExtBoot system, reports the Ready indication signal, receives and processes instructions and data, replies with response information, and completes firmware burning; The PC control module is connected to the embedded device mainboard.

7. The device for burning firmware system data according to claim 6, characterized in that: The PC control module comprises: Data reading unit: responsible for reading firmware system data into PC memory for pre-processing; Encapsulation data unit; responsible for encapsulating firmware system data into frame data according to the protocol; Transmission unit: responsible for transmitting frame data to the embedded mainboard; Native burning tool control unit: responsible for calling the burning tool provided by Ambiq Micro to burn the firmware, compatible with the original burning method; The data reading unit, the data encapsulation unit and the transmission unit are connected in sequence.

8. The device for burning firmware system data according to claim 6, characterized in that: The embedded device mainboard comprises: Data receiving unit: responsible for receiving frame data from PC; Data verification unit: responsible for verifying the received frame data; Burning data unit: responsible for burning the received block data into the extended memory; The data receiving unit, the data checking unit and the data burning unit are connected in sequence.

Images