Automobile radio frequency processing chip bridge connection type double-guide program updating method and automobile radio frequency processing chip bridge connection type double-guide program updating system

Abstract

The invention discloses an automobile radio frequency processing chip bridge type dual-boot program updating method, which comprises the following steps of: respectively controlling a main processor and an automobile radio frequency processing chip to run boot programs thereof in response to an updating instruction aiming at the automobile radio frequency processing chip; receiving firmware update data through a bootstrap program of the main processor; the main processor and the automobile radio frequency processing chip establish a communication session between the bootstrap programs of the main processor and the automobile radio frequency processing chip through a communication bus, and transmit the firmware update data from the main processor to the automobile radio frequency processing chip; writing the received firmware updating data into an application program storage area of the automobile radio frequency processing chip through a bootstrap program of the automobile radio frequency processing chip; a special downloader and a disassembly process are thoroughly omitted, updating can be completed through an existing diagnosis interface (such as a CAN) and an existing communication bus, a complex disassembly process is avoided, and the after-sales maintenance cost in the service cycle of a vehicle is greatly reduced.

Description

Technical Field

[0001] This invention relates to the field of automotive electronics technology, and more particularly to firmware update technology for embedded systems. Background Technology

[0002] In automotive electronic control units (ECUs), a "main processor + RF transceiver chip" architecture is commonly used. NXP's NCK2912 chip is specifically designed for processing RF signals and connects to the main processor via a communication bus (such as the SPI bus). For example, the published document with authorization announcement number CN210109880U, authorization announcement date of February 21, 2020, and patent title "A Cloud Computing-Based Vehicle Automatic Diagnostic System" discloses a system including an STM32F103CBT6 microcontroller chip and an electronic control unit (ECU). The ECU generates CAN line commands and K-line commands. The K-line commands are sequentially sent to the first input terminal of the STM32F103CBT6 microcontroller chip via a 74HC02 NOR gate chip and an LM393 comparator. The CAN line is connected to the second input terminal of the STM32F103CBT6 microcontroller chip via the data transceiver bus of a TJA1050 transceiver chip. The two output ports of the STM32F103CBT6 microcontroller chip are respectively connected to a GPS circuit and an M35GSM circuit to transmit and receive GPS signals and GPRS signals. A similar main processor + RF transceiver chip architecture has the following significant drawbacks: 1. Lack of convenient upgrade interface: Although the NCK2912 chip has a debugging interface for engineering development, in automotive controllers, due to cost and design considerations, this debugging interface is usually not brought out to an external connector during the mass production stage. Therefore, for controllers already deployed in automotive environments or with completed housing assembly, there is no convenient physical interface for field firmware updates.

[0003] 2. Lack of application update mechanism: When the chip leaves the factory, its firmware is burned entirely by dedicated debugging tools, and there is no internal bootloader that can be used to receive and update its applications; therefore, it cannot receive and process update data from the main processor on its own through the communication bus.

[0004] 3. Complex and costly update process: The only current upgrade method is to physically program the chip through its debugging interface using a dedicated programmer in a production or repair workshop. If the controller is already in an in-vehicle environment or has been assembled, a cumbersome process of "disassembling the vehicle -> removing the controller -> opening the cover -> programming -> reassembling" must be performed, which leads to a sharp increase in maintenance costs and makes remote or non-intrusive online updates impossible.

[0005] Therefore, there is an urgent need in this field for an innovative solution to overcome the technical obstacles posed by the NCK2912 chip's lack of a convenient upgrade interface and application update mechanism. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to realize a method and system for updating the firmware of automotive radio frequency processing chips in an assembled state without the need for a dedicated downloader and physical disassembly.

[0007] To achieve the above objectives, the technical solution adopted by the present invention is as follows: a bridged dual-boot program update method for automotive radio frequency processing chips, comprising the following steps: Step 1: In response to the update command for the automotive RF processing chip, control the main processor and the automotive RF processing chip to run their boot programs respectively; Step 2: Receive firmware update data through the main processor's bootloader; Step 3: The main processor and the automotive radio frequency processing chip establish a communication session between their respective boot programs via a communication bus, and the firmware update data is transmitted from the main processor to the automotive radio frequency processing chip. Step 4: The received firmware update data is written to the application storage area of ​​the automotive radio frequency processing chip through the boot program of the automotive radio frequency processing chip.

[0008] The bootloader includes session management, data block transmission, and session verification commands.

[0009] The session verification command includes the target address, data length, data content, and cyclic redundancy check code for the data block.

[0010] In step 3, the communication session established by the communication bus adopts a command-response communication protocol. The communication protocol adopts an automatic retransmission mechanism, and after receiving a negative acknowledgment from the receiver, it retransmits the current data block.

[0011] The command set of the communication protocol includes: Session initialization command: sent by the main processor to establish an upgrade session. After the automotive RF processing chip replies with confirmation, it enters the programming state. Data block transmission command: sent cyclically by the main processor to transmit firmware data. The transmitted firmware data includes the target address, data length, data content and block checksum. The automotive RF processing chip performs real-time verification on each packet. If it passes, it replies with an acknowledgment; if it fails, it replies with a negative acknowledgment. Session verification command: Sent by the main processor after all data has been sent, it is used to trigger the final integrity verification. After the automotive RF processing chip completes the verification, it sets the start flag based on the result.

[0012] In step 3, the communication session method includes: Step S1: Session establishment and authentication. The main processor receives the update command through the diagnostic interface. After verification, the upgrade mode will be started. Step S2: Boot program switching, the main processor performs a soft reset. After the reset, the main Boot area enters upgrade mode and notifies the automotive RF processing chip to jump to the NCK2912_Boot area via the communication bus; Step S3: Protocol initialization, the main Boot area sends the INIT_PRG command to the NCK2912_Boot area, the NCK2912_Boot area replies with confirmation, and the session is established; Step S4: Reliable data transmission. The main boot encapsulates the firmware data into a CMD_DATA command packet and sends it through the communication bus. The NCK2912_Boot area performs real-time verification and replies with confirmation or negative confirmation, triggering necessary retransmissions. Step S5: Stream programming, the NCK2912_Boot area writes the verified data block to the corresponding address; Step S6: Final verification and activation. The main Boot area sends the CMD_ACTIVATE command, and the NCK2912_Boot area performs the final integrity verification. If it passes, the parameters of the automotive RF processing chip are set to "valid". Step S7: System recovery. The main boot area's heavy vehicle RF processing chip is set to "normal startup" and triggers a system reset. After the system starts normally, the updated application runs.

[0013] In step 4, the step of writing the firmware update data to the application storage area is performed using a streaming burning method.

[0014] A bridged dual-boot program update system for automotive radio frequency processing chips, the system comprising a main processor connected to the automotive radio frequency processing chip; The main processor includes: Boot module: Upon receiving an update instruction, it controls the main processor to run the main processor's boot program; Receiving module: Receives firmware update data through the bootloader of the boot module; Communication module: Follows a preset custom boot communication protocol to establish a communication session with the automotive radio frequency processing chip; The automotive radio frequency processing chip includes: Boot module: Upon receiving an update command, it controls the automotive RF processing chip to run its boot program. Communication module: Follows the preset custom boot communication protocol to establish a communication session with the main processor; Program storage area: Stores the automotive radio frequency processing chip program, as well as firmware update data that can be written.

[0015] The main processor is an automotive electronic control unit; the flash memory of the main processor is divided into: a main boot area, a main app area, and an NVM parameter area; The automotive radio frequency processing chip is NXP's NCK2912 chip; the memory of the automotive radio frequency processing chip is divided into: NCK2912_Boot area, NCK2912_App area, and internal EEPROM.

[0016] The upgrade session between the main processor and the automotive radio frequency processing chip follows a matching communication protocol between the main boot area of ​​the main processor and the NCK2912_Boot area of ​​the automotive radio frequency processing chip.

[0017] The advantages of this invention are: 1. From nothing to something: It created the ability to remotely update the NCK2912 chip, which originally lacked an application update mechanism, representing a fundamental leap in functionality.

[0018] 2. High reliability and robustness: Through a proprietary customized boot communication protocol, dual protection of block transmission verification and final integrity verification is achieved. Combined with a secure switching mechanism for boot parameter flags, the reliability of the update process is ensured, effectively preventing the NCK2912 chip from becoming "bricked".

[0019] 3. Low cost and high efficiency: Completely eliminates the need for a dedicated downloader and disassembly process. Updates can be completed through existing diagnostic interfaces (such as CAN) and existing communication buses, avoiding complex disassembly and assembly processes and greatly reducing after-sales maintenance costs during the vehicle's service life. Attached Figure Description

[0020] The following is a brief explanation of the content represented by each figure in this specification: Figure 1 Flowchart of a bridged dual-boot program update method for automotive radio frequency processing chips. Detailed Implementation

[0021] The following description, with reference to the accompanying drawings, details the specific implementation of the present invention, including the shape and structure of each component, the relative positions and connections between the parts, the function and working principle of each part, the manufacturing process, and the operation and use methods, to help those skilled in the art to have a more complete, accurate, and in-depth understanding of the inventive concept and technical solution of the present invention.

[0022] This invention relates to a method and system for wireless firmware updates on the NCK2912 RF transceiver chip, which lacks an independent upgrade interface and application update mechanism in an in-vehicle environment or when the controller is already installed. This method and system allows for firmware updates on the NCK2912 chip in its installed state without the need for a dedicated downloader or physical disassembly. Its core is the construction of a "software bridge" from the main processor to the NCK2912, achieving reliable transmission and burning of firmware data through the collaborative work of two "bridged" bootloaders.

[0023] The following details the bridged dual-boot program update method for automotive radio frequency (RF) processing chips. Using NXP's NCK2912 chip, specifically designed for RF signal processing, as an example, the NCK2912 chip lacks an independent upgrade interface and application update mechanism in automotive environments or when the controller is already installed. The method includes: In response to an update instruction for the NCK2912 chip, the main processor is controlled to run its bootloader, and the NCK2912 chip is also controlled to run its bootloader. Firmware update data is received through the bootloader of the main processor; Through the communication bus between the main processor and the NCK2912 chip, and following a preset custom boot communication protocol, a communication session is established between the boot programs of both parties, and the firmware update data is transmitted from the main processor to the NCK2912 chip. The bootloader of the NCK2912 chip writes the received firmware update data into the application storage area of ​​the NCK2912 chip.

[0024] The customized bootstrap communication protocol includes session management, data block transmission, and session verification commands. The session verification command includes the target address, data length, data content, and the cyclic redundancy check (CRC) code for the data block.

[0025] The protocol employs a reliable transmission mechanism based on acknowledgment and retransmission. The step of writing firmware update data to the application storage area adopts a streaming burning method, that is: receiving a complete data block, verifying it, and then writing it to the corresponding storage address, without caching the entire firmware file in the NCK2912 chip's memory.

[0026] To ensure a reliable upgrade session, a custom boot communication protocol is required between the main MCU bootloader and the NCK2912 bootloader. Preferably, this protocol employs a command-response mechanism, and its core command set can be designed as follows: Session initialization command (INIT_PRG): Sent by the main bootloader to establish an upgrade session. After the NCK2912 bootloader replies with confirmation, it enters programming mode.

[0027] Data block transfer command (CMD_DATA): Sent cyclically by the main bootloader to transmit firmware data. Its payload includes the destination address, data length, data content, and block checksum (e.g., CRC16). The NCK2912 bootloader performs real-time verification on each packet; if successful, it replies with an ACK; otherwise, it replies with a NACK.

[0028] Session verification command (CMD_ACTIVATE): Sent by the main bootloader after all data has been sent, to trigger the final integrity check. After completing the check, the NCK2912 bootloader sets the boot flag based on the result.

[0029] Specifically, the data block transmission command may employ an automatic retransmission mechanism, that is, after receiving a negative acknowledgment from the receiver, the current data block is retransmitted.

[0030] The security upgrade session process is particularly suitable for firmware update scenarios where the controller is already installed in the vehicle or encased in a housing, including: Step S1: Session Establishment and Authentication. The main application of the main processor receives the update command through the diagnostic interface. After verification, it sets the McuBootMode parameter to "NCK2912 upgrade mode".

[0031] Step S2: Bootloader Switching. The main processor performs a soft reset. After the reset, the main boot confirms entry into upgrade mode and notifies NCK2912_App to jump to NCK2912_Boot via the communication bus (preferably SPI bus).

[0032] Step S3: Protocol Initialization. The master bootloader sends the INIT_PRG command to NCK2912_Boot. NCK2912_Boot replies with confirmation, and the session is established.

[0033] Step S4: Reliable data transmission. The main bootloader encapsulates the firmware data into a CMD_DATA command packet and sends it via the communication bus (preferably the SPI bus). The NCK2912_Boot performs real-time verification and replies with confirmation or negative confirmation, triggering necessary retransmissions.

[0034] Step S5: Streaming programming. NCK2912_Boot writes the verified data blocks to the corresponding address in the NCK2912_App area, without caching the entire firmware file.

[0035] Step S6: Final Verification and Activation. The main bootloader sends the CMD_ACTIVATE command. NCK2912_Boot performs a final integrity check. If successful, the NCK2912BootMode parameter is set to "Valid".

[0036] Step S7: System Recovery. The main bootloader resets McuBootMode to "Normal Startup" and triggers a system reset. After the system boots normally, the updated applications run.

[0037] The automotive RF processing chip-bridged dual-boot program update system is equipped with a main processor connected to the automotive RF processing chip. The automotive RF processing chip and the main processor are described in detail below: The main processor includes a main boot memory area and a main application memory area. The program in the main boot memory area is configured to receive update data and communicate with the NCK2912 bootloader via a communication bus according to the customized boot communication protocol. Specifically, it includes: Boot module: Upon receiving an update instruction, it controls the main processor to run the main processor's boot program; Receiving module: Receives firmware update data through the bootloader of the boot module; Communication module: Follows a preset custom boot communication protocol to establish a communication session with the automotive radio frequency processing chip; The main processor's system architecture and memory planning are divided into: main boot area, main application area, and NVM parameter area (storing McuBootMode, etc.).

[0038] The automotive radio frequency processing chip includes an NCK2912 boot memory area and an NCK2912 application memory area. The program in the NCK2912 boot memory area is configured to receive data, perform verification and programming operations through the communication bus according to the customized boot communication protocol. Specifically, it includes: Boot module: Upon receiving an update command, it controls the automotive RF processing chip to run its boot program. Communication module: Follows the preset custom boot communication protocol to establish a communication session with the main processor; Program storage area: Stores the automotive radio frequency processing chip program, as well as firmware update data that can be written.

[0039] The system architecture and memory planning of the automotive radio frequency processing chip are divided into: NCK2912_Boot area, NCK2912_App area, and internal EEPROM (storing NCK2912BootMode, etc.).

[0040] The present invention has been described above by way of example with reference to the accompanying drawings. Obviously, the specific implementation of the present invention is not limited to the above-described manner. Any non-substantial improvements made using the inventive concept and technical solution of the present invention, or the direct application of the inventive concept and technical solution of the present invention to other occasions without modification, are all within the protection scope of the present invention.

Claims

1. A bridged dual-boot program update method for automotive radio frequency processing chips, characterized in that, Includes the following steps: Step 1: In response to the update command for the automotive RF processing chip, control the main processor and the automotive RF processing chip to run their boot programs respectively; Step 2: Receive firmware update data through the main processor's bootloader; Step 3: The main processor and the automotive radio frequency processing chip establish a communication session between their respective boot programs via a communication bus, and the firmware update data is transmitted from the main processor to the automotive radio frequency processing chip. Step 4: The received firmware update data is written to the application storage area of ​​the automotive radio frequency processing chip through the boot program of the automotive radio frequency processing chip.

2. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 1, characterized in that: The bootloader includes session management, data block transmission, and session verification commands.

3. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 2, characterized in that: The session verification command includes the target address, data length, data content, and cyclic redundancy check code for the data block.

4. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 1, 2, or 3, characterized in that: In step 3, the communication session established by the communication bus adopts a command-response communication protocol. The communication protocol adopts an automatic retransmission mechanism, and after receiving a negative acknowledgment from the receiver, it retransmits the current data block.

5. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 4, characterized in that: The command set of the communication protocol includes: Session initialization command: sent by the main processor to establish an upgrade session. After the automotive RF processing chip replies with confirmation, it enters the programming state. Data block transmission command: sent cyclically by the main processor to transmit firmware data. The transmitted firmware data includes the target address, data length, data content and block checksum. The automotive RF processing chip performs real-time verification on each packet. If it passes, it replies with an acknowledgment; if it fails, it replies with a negative acknowledgment. Session verification command: Sent by the main processor after all data has been sent, it is used to trigger the final integrity verification. After the automotive RF processing chip completes the verification, it sets the start flag based on the result.

6. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 5, characterized in that: In step 3, the communication session method includes: Step S1: Session establishment and authentication. The main processor receives the update command through the diagnostic interface. After verification, the upgrade mode will be started. Step S2: Boot program switching, the main processor performs a soft reset. After the reset, the main Boot area enters upgrade mode and notifies the automotive RF processing chip to jump to the NCK2912_Boot area via the communication bus; Step S3: Protocol initialization, the main Boot area sends the INIT_PRG command to the NCK2912_Boot area, the NCK2912_Boot area replies with confirmation, and the session is established; Step S4: Reliable data transmission. The main boot encapsulates the firmware data into a CMD_DATA command packet and sends it through the communication bus. The NCK2912_Boot area performs real-time verification and replies with confirmation or negative confirmation, triggering necessary retransmissions. Step S5: Stream programming, the NCK2912_Boot area writes the verified data block to the corresponding address; Step S6: Final verification and activation. The main Boot area sends the CMD_ACTIVATE command, and the NCK2912_Boot area performs the final integrity verification. If it passes, the parameters of the automotive RF processing chip are set to "valid". Step S7: System recovery. The main boot area's heavy vehicle RF processing chip is set to "normal startup" and triggers a system reset. After the system starts normally, the updated application runs.

7. The program update method for bridged dual-boot automotive radio frequency processing chips according to claim 1 or 6, characterized in that: In step 4, the step of writing the firmware update data to the application storage area is performed using a streaming burning method.

8. A bridged dual-boot program update system for automotive radio frequency processing chips, the system comprising a main processor connected to the automotive radio frequency processing chip, characterized in that: The main processor includes: Boot module: Upon receiving an update instruction, it controls the main processor to run the main processor's boot program; Receiving module: Receives firmware update data through the bootloader of the boot module; Communication module: Follows a preset custom boot communication protocol to establish a communication session with the automotive radio frequency processing chip; The automotive radio frequency processing chip includes: Boot module: Upon receiving an update command, it controls the automotive RF processing chip to run its boot program. Communication module: Follows the preset custom boot communication protocol to establish a communication session with the main processor; Program storage area: Stores the automotive radio frequency processing chip program, as well as firmware update data that can be written.

9. The automotive radio frequency processing chip bridged dual-boot program update system according to claim 8, characterized in that: The main processor is an automotive electronic control unit; the flash memory of the main processor is divided into: a main boot area, a main app area, and an NVM parameter area; The automotive radio frequency processing chip is NXP's NCK2912 chip; the memory of the automotive radio frequency processing chip is divided into: NCK2912_Boot area, NCK2912_App area, and internal EEPROM.

10. The automotive radio frequency processing chip bridged dual-boot program update system according to claim 8 or 9, characterized in that: The upgrade session between the main processor and the automotive radio frequency processing chip follows a matching communication protocol between the main boot area of ​​the main processor and the NCK2912_Boot area of ​​the automotive radio frequency processing chip.

Images