CN117348910A - BootLoader upgrading method and system of intelligent cabin MCU - Google Patents

BootLoader upgrading method and system of intelligent cabin MCU Download PDF

Info

Publication number
CN117348910A
CN117348910A CN202311215224.XA CN202311215224A CN117348910A CN 117348910 A CN117348910 A CN 117348910A CN 202311215224 A CN202311215224 A CN 202311215224A CN 117348910 A CN117348910 A CN 117348910A
Authority
CN
China
Prior art keywords
mcu
data
upgrading
file
info
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311215224.XA
Other languages
Chinese (zh)
Inventor
鄢浩
陈星�
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
South Sagittarius Integration Co Ltd
Original Assignee
South Sagittarius Integration Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by South Sagittarius Integration Co Ltd filed Critical South Sagittarius Integration Co Ltd
Priority to CN202311215224.XA priority Critical patent/CN117348910A/en
Publication of CN117348910A publication Critical patent/CN117348910A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/654—Updates using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
    • G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
    • G06F11/1004—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's to protect a block of data words, e.g. CRC or checksum
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping

Abstract

A BootLoader upgrading method of an intelligent cabin MCU comprises the following steps: TOOL sends an upgrade request signal to MCU, MCU writes the appointed memory into upgrade identification and restarts; after the MCU is restarted, the MCU replies a response to start upgrading; TOOL sends file information to MCU through serial port, and calculates CRC check value; after MCU verification is completed, circularly requesting the TOOL for upgrading data; TOOL sends a receipt packet to MCU, after receipt packet sending is completed, MCU checks info content with received length data packet, and continuously requests app content of MCU to TOOL; the MCU receives the complete data of one packet, and processes the received data according to a preset rule; the MCU sends a verification request to the TOOL, the TOOL replies a verification value, and after verification is passed, the MCU writes info information into the partition and responds that the upgrade is successful; and the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed. The invention can greatly save the protection cost of the system and has obvious practicability on the service life and the reliability of the equipment.

Description

BootLoader upgrading method and system of intelligent cabin MCU
Technical Field
The invention relates to the field of intelligent cabins, in particular to a BootLoader upgrading method and a BootLoader upgrading system of an intelligent cabin MCU.
Background
For the embedded MCU, when the product is stably put into production, after the program is burnt, the MCU cannot be seen generally, and because the outside is covered by materials such as a shell, the problem that a burning port cannot be used because the later-stage product needs to be upgraded is caused, and the BootLoader is designed for solving the problem, which is equivalent to a bootstrap program. In embedded systems, the system usually starts to execute from address 0x0000 when powering up or resetting, and the BootLoader starts to execute from the address, i.e. the first code executed after powering up or resetting.
Bootloader is a hardware-initiated bootstrap program, which is a precondition for running an operating system. A piece of small code that runs before the operating system kernel or user application runs. The hardware is initialized and set correspondingly, and only one main necessary role of bootloader is finally provided for the ready environment of the operating system: the operating system image file is copied into RAM and then jumps to its entry for execution. To achieve this function (as well as other additional functions). Besides the necessary bootloader, the function 1 is often added, namely, the read operating system file can be copied into the RAM to run directly, can be burnt into the FLASH, or can be written into the hard disk to be permanently stored, so that the operating system image can be directly read from the local machine next time. 2. Hardware diagnostics, as with the BIOS of a PC, detects if the hardware is functioning properly. 3. One LOGO is displayed, and because of the time required to copy operating system files and boot the operating system, a commercialized device typically needs to display one LOGO during this time.
Under normal conditions, the Bootloader program is relatively reliable and does not change, so that the Bootloader program can be written into the MCU in a burning mode before the MCU leaves the factory. If a problem occurs, the vehicle needs to be recalled, the MCU is removed from the vehicle, and the Bootloader program is re-recorded on the MCU. However, for an intelligent cabin MCU, when the MCU is packaged inside the device and the device has no reserved upgrade interface, the device is damaged by disassembling the MCU, and the upgrade cost is increased.
Disclosure of Invention
In view of the above, the present invention has been made in order to provide a BootLoader upgrade method and system for an intelligent cockpit MCU that overcomes or at least partially solves the above-mentioned problems.
In order to solve the technical problems, the embodiment of the application discloses the following technical scheme:
a BootLoader upgrading method of an intelligent cabin MCU comprises the following steps:
s100, the TOOL platform sends an upgrade request signal to the MCU, and the MCU writes the appointed memory into an upgrade identifier and restarts;
s200, after the MCU is restarted, the MCU replies a response to start upgrading;
s300, the TOOL platform sends file information to the MCU through a serial port, and calculates a CRC value; after MCU verification is finished, circularly requesting the TOOL platform for upgrading data;
s400, the TOOL platform sends a receipt packet to the MCU, after the receipt packet is sent, the MCU checks info content of the received length data packet, and continuously requests app content of the MCU to the TOOL platform;
s500, the MCU receives a complete packet of data, and processes the received data according to a preset rule; after the processing is finished, the MCU sends a verification request to the TOOL platform, the TOOL platform replies a verification value, and after the verification is finished, the MCU writes info information into the partition and responds that the upgrading is successful;
s600, the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
Further, in S200, after the MCU is restarted, the MCU enters boot according to the upgrade identifier and clears the upgrade identifier, and the MCU replies a response to start upgrading.
Further, in S300, the tol platform sends file information to the MCU through the serial port, where the file information includes a type of a file and a length of the file, and the type of the file at least includes: bin file, hex file, and s19 file.
Further, in S300, the method for calculating the CRC check value includes:
selecting a K-bit binary data string as a standard divisor;
adding K-1 bit 0 to m bits of data to be transmitted, and dividing the new number by the standard divisor by modulo 2, wherein the remainder is the CRC check code of the data; wherein the remainder must be less than the divisor and one bit less, and 0 is not sufficiently complemented;
attaching the check code to the back of the original M-bit data to form new M+K-1-bit data, and sending the new M+K-1-bit data to a receiving end;
the receiving end divides the received data by the standard divisor, and considers the data to be correct if the remainder is 0.
Further, in S400, the tol platform verifies the info content of the received length data packet, and after verification is successful, the app and info partition are erased, and the app content of the MCU is continuously requested to the tol.
Further, in S500, the MCU receives a complete packet of data, and processes the received data according to a preset rule, where the preset rule includes: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
The invention also discloses a BootLoader upgrading system of the intelligent cabin MCU, which comprises the following steps: TOOP platform and MCU, wherein:
the TOOP platform is used for sending an upgrade request signal to the MCU, sending file information to the MCU through the serial port and calculating a CRC value; the method is also used for sending a receipt packet to the MCU, replying a check value to the MCU, and writing info information into the partition by the MCU after the check is passed and replying that the upgrading is successful;
the MCU is used for writing the appointed memory into the upgrading identifier and restarting; after restarting, replying to answer to start upgrading; for receiving a CRC check value; after the verification is finished, circularly requesting upgrading data from the TOOL platform; the method comprises the steps of checking info content of a received length data packet, and continuously requesting app content of an MCU to a TOOL platform; the method is also used for receiving a complete packet of data and processing the received data according to a preset rule; after the processing is finished, a verification request is sent to the TOOL platform, after the verification is passed, the MCU writes info information into the partition and responds that the upgrading is successful; and the method is also used for reading back the app data in the flash, calculating a crc32 check value, and starting hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
Further, the TOOL platform sends file information to the MCU through the serial port, wherein the file information comprises a file type and a file length, and the file type at least comprises: bin file, hex file, and s19 file.
Further, the MCU receives a complete packet of data, and processes the received data according to preset rules, wherein the preset rules include: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
Further, the TOOL platform verifies the info content of the received length data packet, after verification is successful, the app and info partitions are erased, and the app content of the MCU is continuously requested to the TOOL.
The technical scheme provided by the embodiment of the invention has the beneficial effects that at least:
the invention discloses a BootLoader upgrading method of an intelligent cabin MCU, which comprises the following steps: the TOOL platform sends an upgrade request signal to the MCU, and the MCU writes the appointed memory into an upgrade identifier and restarts; after the MCU is restarted, the MCU replies a response to start upgrading; the TOOL platform sends file information to the MCU through the serial port and calculates a CRC check value; after MCU verification is finished, circularly requesting the TOOL platform for upgrading data; the TOOL platform sends a receipt packet to the MCU, after the receipt packet is sent, the MCU checks the info content of the received length data packet, and continuously requests the TOOL platform for the app content of the MCU; the MCU receives the complete data of one packet, and processes the received data according to a preset rule; after the processing is finished, the MCU sends a verification request to the TOOL platform, the TOOL platform replies a verification value, and after the verification is finished, the MCU writes info information into the partition and responds that the upgrading is successful; and the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
According to the BootLoader upgrading method of the intelligent cabin MCU, when the system needs to be in a level, the BootLoader can read a new program file from an external memory and update the system, so that the protection cost of the system can be greatly saved, and the service life and the reliability of equipment are obviously improved.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
fig. 1 is a flowchart of a BootLoader upgrading method of an intelligent cabin MCU in embodiment 1 of the present invention;
FIG. 2 is a schematic diagram of interaction between a TOOL platform and an MCU according to embodiment 1 of the present invention;
fig. 3 is a schematic diagram of a TOOL platform and MCU interactive error response in embodiment 1 of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In order to solve the problems in the prior art, the embodiment of the invention provides a BootLoader upgrading method and a BootLoader upgrading system for an intelligent cabin MCU.
Example 1
The embodiment discloses a BootLoader upgrading method of an intelligent cabin MCU, as shown in FIG. 1, comprising the following steps:
s100, the TOOL platform sends an upgrade request signal to the MCU, and the MCU writes the appointed memory into an upgrade identifier and restarts;
specifically, in this embodiment, the TOOL platform and the MCU perform information interaction through the service and the sub-service, the specific data of the service and the sub-service conform to and have the meaning as shown in fig. 2, for example, when the TOOL platform sends a request upgrade signal to the MCU, the TOOL platform sends an "F101" instruction to the MCU, and the MCU receives an upgrade request response "F10201" instruction, upgrades the identifier, and restarts;
s200, after the MCU is restarted, the MCU replies a response to start upgrading; in S200 of this embodiment, after the MCU is restarted, the MCU enters boot according to the upgrade identifier and clears the upgrade identifier, and the MCU replies a response to start upgrading. Specifically, after the MCU is restarted, an F10202 instruction response is sent to the TOOL platform, and an upgrade starting signal is transmitted.
S300, the TOOL platform sends file information to the MCU through a serial port, and calculates a CRC value; after MCU verification is finished, circularly requesting the TOOL platform for upgrading data; after receiving the upgrade starting signal, the TOOL platform sends file information to the MCU through the serial port, and the TOOL platform sends the file information to the MCU through the serial port, wherein the file information comprises the type of the file and the length of the file, and the type of the file at least comprises: bin file, hex file, and s19 file. Specifically, in S300, the method for calculating the CRC check value includes:
selecting a K-bit binary data string as a standard divisor;
adding K-1 bit 0 to m bits of data to be transmitted, and dividing the new number by the standard divisor by modulo 2, wherein the remainder is the CRC check code of the data; wherein the remainder must be less than the divisor and one bit less, and 0 is not sufficiently complemented;
attaching the check code to the back of the original M-bit data to form new M+K-1-bit data, and sending the new M+K-1-bit data to a receiving end;
the receiving end divides the received data by the standard divisor, and considers the data to be correct if the remainder is 0.
S400, the TOOL platform sends a receipt packet to the MCU, after the receipt packet is sent, the MCU checks info content of the received length data packet, and continuously requests app content of the MCU to the TOOL platform; in S400 of this embodiment, the tol platform verifies the info content of the received length data packet, and after the verification is successful, erases app and info partition, and continues to request the app content of the MCU from the tol.
S500, the MCU receives a complete packet of data, and processes the received data according to a preset rule; after the processing is finished, the MCU sends a verification request to the TOOL platform, the TOOL platform replies a verification value, and after the verification is finished, the MCU writes info information into the partition and responds that the upgrading is successful;
in S500 of this embodiment, the MCU receives a complete packet of data, and processes the received data according to preset rules, where the preset rules include: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
S600, the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed. In this embodiment, when the MCU interacts with the tol platform, a response error may also occur, and the specific error and the corresponding identifier are shown in fig. 3.
The BootLoader upgrading method of the intelligent cabin MCU disclosed by the embodiment comprises the following steps: the TOOL platform sends an upgrade request signal to the MCU, and the MCU writes the appointed memory into an upgrade identifier and restarts; after the MCU is restarted, the MCU replies a response to start upgrading; the TOOL platform sends file information to the MCU through the serial port and calculates a CRC check value; after MCU verification is finished, circularly requesting the TOOL platform for upgrading data; the TOOL platform sends a receipt packet to the MCU, after the receipt packet is sent, the MCU checks the info content of the received length data packet, and continuously requests the TOOL platform for the app content of the MCU; the MCU receives the complete data of one packet, and processes the received data according to a preset rule; after the processing is finished, the MCU sends a verification request to the TOOL platform, the TOOL platform replies a verification value, and after the verification is finished, the MCU writes info information into the partition and responds that the upgrading is successful; and the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
According to the BootLoader upgrading method of the intelligent cabin MCU, when the system needs to be in a level, the BootLoader can read a new program file from an external memory and update the system, so that the protection cost of the system can be greatly saved, and the service life and the reliability of equipment are obviously improved.
Example 2
Based on the BootLoader upgrading method of the intelligent cabin MCU in embodiment 1, the embodiment discloses a BootLoader upgrading system of the intelligent cabin MCU, comprising: TOOP platform and MCU, wherein:
the TOOP platform is used for sending an upgrade request signal to the MCU, sending file information to the MCU through the serial port and calculating a CRC value; the method is also used for sending a receipt packet to the MCU, replying a check value to the MCU, and writing info information into the partition by the MCU after the check is passed and replying that the upgrading is successful;
the MCU is used for writing the appointed memory into the upgrading identifier and restarting; after restarting, replying to answer to start upgrading; for receiving a CRC check value; after the verification is finished, circularly requesting upgrading data from the TOOL platform; the method comprises the steps of checking info content of a received length data packet, and continuously requesting app content of an MCU to a TOOL platform; the method is also used for receiving a complete packet of data and processing the received data according to a preset rule; after the processing is finished, a verification request is sent to the TOOL platform, after the verification is passed, the MCU writes info information into the partition and responds that the upgrading is successful; and the method is also used for reading back the app data in the flash, calculating a crc32 check value, and starting hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
In this embodiment, the TOOL platform sends file information to the MCU through the serial port, where the file information includes a file type and a file length, and the file type includes at least: bin file, hex file, and s19 file.
In this embodiment, the MCU receives a complete packet of data, and processes the received data according to preset rules, where the preset rules include: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
In this embodiment, the TOOL platform verifies the info content of the received length data packet, and after verification is successful, erases app and info partitions, and continues to request the app content of the MCU from the TOOL.
It should be understood that the specific order or hierarchy of steps in the processes disclosed are examples of exemplary approaches. Based on design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged without departing from the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
In the foregoing detailed description, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate preferred embodiment of this invention.
Those of skill would further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. The processor and the storage medium may reside as discrete components in a user terminal.
For a software implementation, the techniques described herein may be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. These software codes may be stored in memory units and executed by processors. The memory unit may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
The foregoing description includes examples of one or more embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations of various embodiments are possible. Accordingly, the embodiments described herein are intended to embrace all such alterations, modifications and variations that fall within the scope of the appended claims. Furthermore, as used in the specification or claims, the term "comprising" is intended to be inclusive in a manner similar to the term "comprising," as interpreted when employed as a transitional word in a claim. Furthermore, any use of the term "or" in the specification of the claims is intended to mean "non-exclusive or".

Claims (10)

1. A BootLoader upgrading method of an intelligent cabin MCU is characterized by comprising the following steps:
s100, the TOOL platform sends an upgrade request signal to the MCU, and the MCU writes the appointed memory into an upgrade identifier and restarts;
s200, after the MCU is restarted, the MCU replies a response to start upgrading;
s300, the TOOL platform sends file information to the MCU through a serial port, and calculates a CRC value; after MCU verification is finished, circularly requesting the TOOL platform for upgrading data;
s400, the TOOL platform sends a receipt packet to the MCU, after the receipt packet is sent, the MCU checks info content of the received length data packet, and continuously requests app content of the MCU to the TOOL platform;
s500, the MCU receives a complete packet of data, and processes the received data according to a preset rule; after the processing is finished, the MCU sends a verification request to the TOOL platform, the TOOL platform replies a verification value, and after the verification is finished, the MCU writes info information into the partition and responds that the upgrading is successful;
s600, the MCU reads back the app data in the flash, calculates a crc32 check value, and starts hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
2. The BootLoader upgrading method of the intelligent cabin MCU according to claim 1, wherein in S200, after the MCU is restarted, the MCU enters boot according to the upgrading identifier and clears the upgrading identifier, and the MCU replies to start upgrading.
3. The BootLoader upgrading method of the intelligent cabin MCU according to claim 1, wherein in S300, the tol platform sends file information to the MCU through a serial port, the file information includes a file type and a file length, and the file type at least includes: bin file, hex file, and s19 file.
4. The BootLoader upgrading method of an intelligent cabin MCU according to claim 1, wherein in S300, the method for calculating the CRC check value comprises:
selecting a K-bit binary data string as a standard divisor;
adding K-1 bit 0 to m bits of data to be transmitted, and dividing the new number by the standard divisor by modulo 2, wherein the remainder is the CRC check code of the data; wherein the remainder must be less than the divisor and one bit less, and 0 is not sufficiently complemented;
attaching the check code to the back of the original M-bit data to form new M+K-1-bit data, and sending the new M+K-1-bit data to a receiving end;
the receiving end divides the received data by the standard divisor, and considers the data to be correct if the remainder is 0.
5. The BootLoader upgrading method of the intelligent cabin MCU according to claim 1, wherein in S400, the tol platform verifies the info content of the received length data packet, and after verification is successful, erases app and info partitions, and continues to request the app content of the MCU to the tol.
6. The BootLoader upgrading method of an intelligent cabin MCU according to claim 1, wherein in S500, the MCU receives a complete packet of data and processes the received data according to preset rules, and the preset rules include: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
7. BootLoader upgrading system of intelligent cabin MCU, its characterized in that includes: TOOP platform and MCU, wherein:
the TOOP platform is used for sending an upgrade request signal to the MCU, sending file information to the MCU through the serial port and calculating a CRC value; the method is also used for sending a receipt packet to the MCU, replying a check value to the MCU, and writing info information into the partition by the MCU after the check is passed and replying that the upgrading is successful;
the MCU is used for writing the appointed memory into the upgrading identifier and restarting; after restarting, replying to answer to start upgrading; for receiving a CRC check value; after the verification is finished, circularly requesting upgrading data from the TOOL platform; the method comprises the steps of checking info content of a received length data packet, and continuously requesting app content of an MCU to a TOOL platform; the method is also used for receiving a complete packet of data and processing the received data according to a preset rule; after the processing is finished, a verification request is sent to the TOOL platform, after the verification is passed, the MCU writes info information into the partition and responds that the upgrading is successful; and the method is also used for reading back the app data in the flash, calculating a crc32 check value, and starting hardware reset after the crc32 in the info is read to be checked to be qualified, so that BootLoader upgrading is completed.
8. The BootLoader upgrade system of the intelligent cockpit MCU of claim 7, wherein the tol platform sends file information to the MCU through a serial port, the file information including a type of a file and a length of the file, wherein the type of the file at least includes: bin file, hex file, and s19 file.
9. The BootLoader upgrade system of an intelligent cabin MCU according to claim 7, wherein the MCU receives a complete packet of data and processes the received data according to preset rules, and the preset rules for processing include: the MCU writes the received complete data of one package into the corresponding flash address, writes one page at a time, calculates the crc32 check value of the app program after all the data are received, and calculates the md5 value of the complete data.
10. The BootLoader upgrade system of claim 7, wherein the tol platform verifies the info content of the received length data packet, and after verification is successful, erases the app and info partition, and continues to request the app content of the MCU from the tol.
CN202311215224.XA 2023-09-20 2023-09-20 BootLoader upgrading method and system of intelligent cabin MCU Pending CN117348910A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311215224.XA CN117348910A (en) 2023-09-20 2023-09-20 BootLoader upgrading method and system of intelligent cabin MCU

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311215224.XA CN117348910A (en) 2023-09-20 2023-09-20 BootLoader upgrading method and system of intelligent cabin MCU

Publications (1)

Publication Number Publication Date
CN117348910A true CN117348910A (en) 2024-01-05

Family

ID=89370125

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311215224.XA Pending CN117348910A (en) 2023-09-20 2023-09-20 BootLoader upgrading method and system of intelligent cabin MCU

Country Status (1)

Country Link
CN (1) CN117348910A (en)

Similar Documents

Publication Publication Date Title
US6622246B1 (en) Method and apparatus for booting and upgrading firmware
US9286164B2 (en) Electronic device to restore MBR, method thereof, and computer-readable medium
US8595716B2 (en) Failsafe firmware updates
US20100169709A1 (en) System Of Updating Firmware And Method Thereof, And Method Of Creating Firmware
CN109189445B (en) Method for upgrading program of equipment of Internet of things
US9205809B2 (en) Vehicle unit and method for operating the vehicle unit
EP1617328A2 (en) Modular BIOS update mechanism
EP1591893A1 (en) Method and system for fail-safe updating of boot code
CN107239411B (en) Memory management method and system for vehicle-mounted controller
CN109614265B (en) Double-backup system of intelligent inertial navigation sensing system and configuration starting method thereof
CN111813428A (en) Method and device for upgrading terminal firmware, electronic equipment and storage medium
CN112015447A (en) System updating method and device for electronic equipment, electronic equipment and storage medium
US7934050B2 (en) Microcomputer for flash memory rewriting
JP4743182B2 (en) Microcomputer
CN109189457B (en) Firmware upgrading system and method of intelligent inertial navigation sensing system
US7490321B2 (en) Method for updating firmware via determining program code
US7428635B2 (en) Method of writing non-volatile memory that avoids corrupting the vital initialization code
CN117348910A (en) BootLoader upgrading method and system of intelligent cabin MCU
WO2022199622A1 (en) Method for running startup program of electronic device, and electronic device
US11586504B2 (en) Electronic apparatus and boot method thereof
CN115481405A (en) Safe starting and optimized upgrading method of embedded system
US11768669B2 (en) Installing application program code on a vehicle control system
KR20150075867A (en) Method and apparatus for executing bootloader
CN112667444A (en) System upgrading method, storage medium and terminal equipment
CN116225490B (en) Upgrading method and upgrading device of memory firmware, electronic equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination