A Xilinx SoC-based boot component-based update system
By implementing a fine-grained partitioning design and decoupling of responsibilities for the QSPI Flash of Xilinx SoC, independent component-level updates and rollbacks of Xilinx SoC are achieved. This solves the problems of coarse update granularity, poor flexibility, and weak system recoverability in existing technologies, thereby improving update efficiency and system reliability.
Patent Information
- Application Number
- CN202610803791.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-05
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2046-06-05
AI Technical Summary
Existing Xilinx Zynq SoC update solutions suffer from issues such as coarse update granularity, lack of flexibility, weak system recoverability, and low operation and maintenance efficiency. In particular, they cannot achieve independent updates of individual components or efficient version management.
The system adopts a component-based update system, which decouples the responsibilities of FSBL and U-Boot by performing fine partitioning design on the QSPI Flash of Xilinx SoC, and implements FPGA loading in U-Boot. It supports independent updates and rollbacks at the component level, and enables remote management and secure updates in conjunction with the ODC operation and maintenance platform.
It enables fine-grained component update management, improves update flexibility and system recoverability, reduces the risk of update failure, and enhances operation and maintenance efficiency and system reliability.
Smart Images

Figure CN122331925B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of embedded system firmware and hardware configuration updates, and more specifically to the field of boot component updates. Background Technology
[0002] In the field of embedded systems, Xilinx Zynq SoCs are widely used due to their integration of FPGA and processor architectures. Their firmware and hardware configuration update mechanisms are a critical aspect of system design, directly determining upgrade efficiency, hardware compatibility, and operational stability. However, existing update solutions for this architecture employ an integrated design in pursuit of deployment convenience, thus creating a fixed technical implementation path and leading to corresponding application limitations.
[0003] The current common update approach for Xilinx Zynq SoCs is the BOOT.bin overall update scheme. This scheme packages the three core components—the first-level bootloader (FSBL), the FPGA configuration bitstream file (.bit), and the second-level bootloader (U-Boot)—into a single image file named BOOT.bin, and then burns it into non-volatile memory such as QSPI Flash using an SD card or JTAG tool. This existing technical solution has the following main drawbacks: The update granularity is coarse and lacks flexibility: any minor modification to a component (such as fixing a bug in the FSBL or upgrading FPGA functionality) requires repackaging and replacing the entire BOOT.bin file, lacking an effective rollback mechanism. Independent updates for individual components are not possible; if the BOOT.bin file is corrupted due to power outages, data errors, or other reasons, the entire boot chain will fail, potentially rendering the device unusable, increasing the risk of update errors and workload. Existing solutions lack hardware and software mechanisms for automatically and reliably reverting to a previous usable version after an update failure.
[0004] Rigid boot process: The standard FSBL requires loading and configuring the FPGA during boot, resulting in a strong coupling between the application processor (ARM) startup and FPGA configuration process. This prevents the implementation of a flexible boot mode that prioritizes system status checks or communication before configuring the FPGA as needed, leading to slow update speeds and low efficiency.
[0005] The system has poor recoverability: when the FPGA bitstream file is corrupted or incompatible with the software, the system will fail to start during the FSBL stage and will be unable to enter any available command line or recovery environment for troubleshooting.
[0006] Low operational efficiency: Version information for all components is mixed together, making fine-grained version management and dependency management difficult. Remote updates require transferring the entire large image, resulting in low efficiency.
[0007] In summary, existing embedded system update technologies suffer from problems such as coarse update granularity, lack of flexibility, weak system recoverability, and low operation and maintenance efficiency. Summary of the Invention
[0008] This invention alleviates the problems of existing embedded system update technologies, such as coarse update granularity, lack of flexibility, weak system recoverability, and low operation and maintenance efficiency. This invention provides the following solution: A component-based boot update system based on Xilinx SoC, the component-based boot update system includes an ODC operation and maintenance platform, a device-side update module, and a device-side QSPI Flash module; The device-side QSPI Flash module includes an FSBL main partition, an FSBL backup partition, an FPGA bitstream main partition, an FPGA bitstream backup partition, a U-Boot main partition, and a U-Boot backup partition; The ODC operation and maintenance platform is used to send a local security update command to the device-side update module after receiving the "packet verification successful" status. The device-side update module is used to receive the local security update instruction, and, taking the update package as an example, write the FPGA main partition to the FPGA backup partition, write the update package to the FPGA main partition, and obtain a hash value based on the current FPGA main partition; The device-side QSPI Flash module is used to verify the hash value. If the verification is successful, update the metadata of the QSPI Flash module on the device side and report the "local write successful" status to the ODC operation and maintenance platform; Otherwise, the FPGA backup partition in the QSPI Flash module of the driver device is written to the FPGA main partition, and the "write failed, rolled back" status is reported to the ODC operation and maintenance platform; The metadata includes a version number and a hash value.
[0009] Furthermore, in one embodiment of the present invention, the guided component update system further includes a device-side application service module.
[0010] Furthermore, in one embodiment of the present invention, the ODC operation and maintenance platform is also used to send component update packages to the device-side application service module; and is also used to receive a "ready" status. The device-side application service module is also used to receive the component update package and send the update instruction to the device-side update module; The device-side update module is also used to receive the update instruction and to send the "ready" status to the ODC operation and maintenance platform.
[0011] Furthermore, in one embodiment of the present invention, the ODC operation and maintenance platform is also used to send the encrypted signature update package to the device-side update module after receiving the "ready" status instruction; The device-side update module is also used to decrypt and verify the encrypted signature update package. If the verification is successful, it sends a "package verification successful" status to the ODC operation and maintenance platform and sends the update package obtained by decrypting the encrypted signature update package to the device-side QSPI Flash module; otherwise, it sends a "package verification failed" status to the ODC operation and maintenance platform.
[0012] Furthermore, in one embodiment of the present invention, the ODC operation and maintenance platform is also used to receive the "local write successful" status and the "write failed, rolled back" status, and send a device restart command to the device-side update module; The device-side update module is also used to receive the device restart command, restart the system, and report the system status to the ODC operation and maintenance platform. The system status includes component version and update status.
[0013] Furthermore, in one embodiment of the present invention, the device-side QSPI Flash module further includes a Linux kernel, an env partition, a boot partition, and a Ramdisk recovery partition.
[0014] Furthermore, in one embodiment of the present invention, in the device-side QSPI Flash module: FSBL Lightweight Bootstrap Phase: The env partition is used to store partition entries and expected hash values; The FSBL primary partition is used to read U-Boot partition entries from the env partition; it is also used to obtain the hash value of the U-Boot image based on the U-Boot partition entries; and it is further used to perform integrity verification by comparing the hash value of the U-Boot image with the expected hash value. If the verification fails, the U-Boot backup partition is written to the U-Boot main partition, and the hash value of the current U-Boot main partition is compared with the expected hash value for integrity verification. If the verification fails, the error is recorded to Flash; otherwise, the U-Boot main partition is started. Otherwise, start the U-Boot primary partition; U-Boot Decision and Dynamic Loading Phase: The U-Boot primary partition is used to read the boot flag from the boot partition. If the boot flag is recovery, the Linux kernel is used as the kernel image; otherwise, the Ramdisk recovery partition is used as the kernel image.
[0015] Furthermore, in one embodiment of the present invention, the FSBL primary partition occupies 1MB of space; the FSBL backup partition occupies 1MB of space.
[0016] Furthermore, in one embodiment of the present invention, the FPGA bitstream main partition occupies 4MB of space and the FPGA bitstream backup partition occupies 4MB of space.
[0017] Furthermore, in one embodiment of the present invention, the space occupied by the U-Boot primary partition is 1MB; the space occupied by the U-Boot backup partition is 1MB.
[0018] The present invention discloses a component-based boot update system based on Xilinx SoC, which effectively addresses the problems of existing embedded system update technologies, such as coarse update granularity, lack of flexibility, weak system recoverability, and low operation and maintenance efficiency. Specific beneficial effects include: 1. The component-based boot update system described in this invention provides a component-based, secure, and remotely manageable boot update solution. Through innovative partitioning design of the storage hardware and deep collaborative modification of the boot software (FSBL and U-Boot), the coupled responsibilities of the traditional FSBL ("loading FPGA + loading U-Boot") are decoupled. The modified FSBL is dedicated solely to loading U-Boot; while the FPGA loading responsibility is postponed and transferred to U-Boot, breaking the fixed order of the boot process, improving update flexibility, and enabling fine-grained update management and highly reliable rollback.
[0019] 2. The component-based update system described in this invention, with independent management of component versions, is clear and concise. Remote "one-click" updates significantly reduce on-site maintenance costs and the risk of human error. Maintenance personnel can individually fix FSBL vulnerabilities, upgrade FPGA functionality, or update U-Boot without affecting other components, providing fine-grained updates and risk isolation. It supports a mode of "starting the ARM for network communication and status checks first, then configuring the FPGA," suitable for complex system initialization. The U-Boot command line can be accessed without configuring the FPGA, facilitating low-level debugging.
[0020] This invention is applicable to the remote, secure, and independent updating of core components such as bootloaders, FPGA logic, and operating system kernels in embedded devices (such as industrial controllers, communication gateways, autonomous driving domain controllers, robots, etc.). Attached Figure Description
[0021] The above and / or additional aspects and advantages of the present invention will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a flowchart of the component-based update system described in Implementation Method 1; Figure 2 This is a flowchart of the device-side QSPI Flash module described in Embodiment Seven; Figure 3 This is a flowchart of the U-Boot decision-making and dynamic loading stage as described in Implementation Method Seven; Figure 4 This is a diagram showing the space occupied by the component-based update system described in Implementation Method 8. Detailed Implementation
[0022] Various embodiments of the present invention will now be clearly and completely described with reference to the accompanying drawings. The embodiments described with reference to the drawings are exemplary and intended to explain the present invention, and should not be construed as limiting the present invention.
[0023] Implementation Method 1: This implementation method describes a boot component-based update system based on a Xilinx SoC, such as... Figure 1 As shown, the component-based update system includes an ODC operation and maintenance platform, a device-side update module, and a device-side QSPIFlash module; The device-side QSPI Flash module includes an FSBL main partition, an FSBL backup partition, an FPGA bitstream main partition, an FPGA bitstream backup partition, a U-Boot main partition, and a U-Boot backup partition; The ODC operation and maintenance platform is used to send a local security update command to the device-side update module after receiving the "packet verification successful" status. The device-side update module is used to receive the local security update instruction, and, taking the update package as an example, write the FPGA main partition to the FPGA backup partition, write the update package to the FPGA main partition, and obtain a hash value based on the current FPGA main partition; The device-side QSPI Flash module is used to verify the hash value. If the verification is successful, update the metadata of the QSPI Flash module on the device side and report the "local write successful" status to the ODC operation and maintenance platform; Otherwise, the FPGA backup partition in the QSPI Flash module of the driver device is written to the FPGA main partition, and the "write failed, rolled back" status is reported to the ODC operation and maintenance platform; The metadata includes a version number and a hash value.
[0024] In this embodiment, the boot component update system is implemented based on a Xilinx Zynq SoC (such as Zynq-7000 or UltraScale+ MPSoC) hardware platform. The hardware platform includes: Zynq SoC connects directly to a QSPI NOR Flash chip (such as the Winbond W25Q series) with a capacity of at least 32Mb through its dedicated QSPI controller interface. This Flash is the core medium for storing all boot components and implementing partition management.
[0025] The Zynq SoC connects to DDR SDRAM via a DDR controller for program execution and data caching.
[0026] The Zynq SoC connects to the eMMC chip or SD card slot via the SD / SDIO controller as a temporary storage area for downloading update packages.
[0027] Zynq SoC provides a network channel for remote operation and maintenance by connecting an external PHY chip via its built-in GigE MAC or by connecting a 4G communication module (such as Quectel EC20 series) via a USB / SDIO interface.
[0028] All of the above hardware is integrated on the same PCB board and electrically interconnected through various controller interfaces of the Zynq SoC.
[0029] In this embodiment, the cloud-based ODC operation and maintenance platform is connected to the device via the Internet.
[0030] The cloud-deployed ODC operation and maintenance platform provides a web management interface, allowing administrators to upload update packages for specific components, select one or more target devices, and after the administrator performs a "one-click update" operation, the cloud-deployed ODC operation and maintenance platform sends update instructions to the target devices.
[0031] The device uses the aforementioned component-based update system to complete the entire update process and reports the progress, success / failure status, and logs to the cloud-deployed ODC operation and maintenance platform in real time.
[0032] The cloud-deployed ODC operation and maintenance platform displays the update status, and the administrator can remotely trigger a rollback operation for a specific component.
[0033] Connect to the cloud-based operations and maintenance center (ODC) via onboard Ethernet or 4G communication hardware to support remote initiation, monitoring, and management of the aforementioned component-level updates and rollback operations.
[0034] In this embodiment, it is preferable that the daemon running on the device receives update instructions and encrypted signature update packages from the cloud ODC via Ethernet or 4G module, and temporarily stores them to the eMMC / SD card.
[0035] In this embodiment, the verification preferably uses an encryption / decryption engine independently developed by the Linux application layer, such as AES, SHA, or RSA, to decrypt and sign the update package, ensuring that its source is trustworthy and has not been tampered with.
[0036] In this implementation, the component-based update system employs an update and rollback mechanism: based on module division, a set of independent update processes at the component level is established. Before updating any component, the current main partition content is forcibly backed up to the corresponding backup partition. If verification fails after the update or the system fails to start, the boot process can automatically roll back to the backup version. This implementation combines "forced backup before update" with "automatic backup switching if verification fails during boot," forming a secure closed loop that requires no manual intervention, greatly reducing the risk of system bricking and constituting a unique method for ensuring system reliability.
[0037] The component-based update system for boot components described in this embodiment is based on the core principles of "storage isolation, decoupling of responsibilities, and post-decision decision-making." It employs a refined partitioning scheme for the QSPI Flash of the Zynq SoC. By dividing the system into FSBL, FPGA bitstream, U-Boot, kernel, environment variable and partition table, and boot flag and configuration modules, it physically isolates each boot component, enabling independent access and updates. This provides a unique hardware storage layout for component-level independent updates and rollbacks.
[0038] Implementation Method 2: This implementation method further defines the component-based update system described in Implementation Method 1. In this implementation method, the component-based update system also includes a device-side application service module.
[0039] Implementation Method 3: This implementation method further defines the component-based update system described in Implementation Method 2. In this implementation method, the ODC operation and maintenance platform is also used to send the component update package to the device-side application service module; and is also used to receive the "ready" status. The device-side application service module is also used to receive the component update package and send the update instruction to the device-side update module; The device-side update module is also used to receive the update instruction and to send the "ready" status to the ODC operation and maintenance platform.
[0040] Implementation Method 4: This implementation method further defines the component-based update system described in Implementation Method 1. In this implementation method, the ODC operation and maintenance platform is also used to send the encrypted signature update package to the device-side update module after receiving the "ready" status instruction. The device-side update module is also used to decrypt and verify the encrypted signature update package. If the verification is successful, it sends a "package verification successful" status to the ODC operation and maintenance platform and sends the update package obtained by decrypting the encrypted signature update package to the device-side QSPI Flash module; otherwise, it sends a "package verification failed" status to the ODC operation and maintenance platform.
[0041] In this embodiment, after receiving the "package verification failed" status, the ODC operation and maintenance platform prompts that the upgrade package verification has failed and stops the upgrade operation.
[0042] Implementation Method 5: This implementation method further defines the component-based update system described in Implementation Method 1. In this implementation method, the ODC operation and maintenance platform is also used to receive the "local write successful" status and the "write failed, rolled back" status, and send a device restart command to the device-side update module. The device-side update module is also used to receive the device restart command, restart the system, and report the system status to the ODC operation and maintenance platform. The system status includes component version and update status.
[0043] Implementation Method Six: This implementation method further defines the boot component update system described in Implementation Method One. In this implementation method, the device-side QSPI Flash module also includes a Linux kernel, an env partition, a boot partition, and a Ramdisk recovery partition.
[0044] Implementation Method Seven: This implementation method further defines the component-based update system described in Implementation Method Six. In this implementation method, as... Figure 2 As shown, in the device-side QSPI Flash module: FSBL Lightweight Bootstrap Phase: The env partition is used to store partition entries and expected hash values; The FSBL primary partition is used to read U-Boot partition entries from the env partition; it is also used to obtain the hash value of the U-Boot image based on the U-Boot partition entries; and it is further used to perform integrity verification by comparing the hash value of the U-Boot image with the expected hash value. If the verification fails, the U-Boot backup partition is written to the U-Boot main partition, and the hash value of the current U-Boot main partition is compared with the expected hash value for integrity verification. If the verification fails, the error is recorded to Flash; otherwise, the U-Boot main partition is started. Otherwise, start the U-Boot primary partition; U-Boot Decision and Dynamic Loading Phase: The U-Boot primary partition is used to read the boot flag from the boot partition. If the boot flag is recovery, the Linux kernel is used as the kernel image; otherwise, the Ramdisk recovery partition is used as the kernel image.
[0045] This implementation modifies the FSBL source code, removing its function of loading the FPGA bitstream and instead loading and verifying the U-Boot image from a separate partition, thus achieving physical separation of FPGA configuration in the initial boot stage. This lightweight FSBL boot process differs from existing FSBL boot processes in the following ways: (1) Different FPGA loading logic: The FSBL lightweighting finds and removes or comments out the code segment that calls the XFsbl_LoadBitStream() function and related flags in the initialization process of the xfsbl_main.c file to ensure that FSBL completely skips the FPGA configuration process.
[0046] (2) Reconstruct partition loading logic: Modify the partition parsing logic in files such as xfsbl_partition_load.c, and no longer look for "device image" type partitions containing bitstreams, but only look for partition entries with the type identifier "U-Boot".
[0047] (3) Direct loading and verification of U-Boot: Based on the partition table information, the U-Boot image (u-boot.elf) is read to the predetermined loading address (e.g., 0x10000000). Then, the hash value of the image (e.g., SHA256) is calculated and compared with the expected hash value of the partition stored in partition 8 to complete the integrity verification.
[0048] (4) Jump Execution: After successful verification, FSBL jumps directly to the entry address of U-Boot in memory and transfers control. At this point, FSBL execution ends, without involving the FPGA.
[0049] In this embodiment, the U-Boot decision-making and dynamic loading process is as follows: Figure 3 As shown, the U-Boot decision-making and dynamic loading differ from existing technologies in that: (1) Add a boot flag reading module: In the early initialization stage of U-Boot (e.g., before the board_init_r function), add a read_boot_flag() function, which reads the boot flag and the contents of the boot_flag file in the configuration module through the QSPI Flash driver.
[0050] (2) Add an FPGA dynamic loading module: Add a new command or function fpga_load() in U-Boot. This function uses the FPGA driver related to the Zynq platform (such as fpga or zynqpl driver) to read the .bit file from the FPGA bitstream module. Through hardware interfaces such as the PCAP (Processor Configuration Access Port) inside the Zynq chip, the bitstream data is configured into the FPGA programmable logic.
[0051] (3) Reconstruct the boot decision process: Modify the default boot command (bootcmd) or main initialization sequence of U-Boot. After U-Boot starts, it calls read_boot_flag() to obtain the flag.
[0052] If the flag is "recovery": the kernel image is set to the Ramdisk recovery system submodule image, and then the system boots directly into the recovery environment without executing fpga_load().
[0053] If the flag is "main" (or the default): First, the fpga_load() function is called to dynamically load and configure the FPGA. After successful configuration, the kernel image is set to the Linux kernel submodule image, and the normal Linux kernel boot process continues.
[0054] The U-Boot decision-making and dynamic loading mechanism employs an enhanced U-Boot module, which adds a boot flag reading module and an FPGA dynamic loading module. After U-Boot starts, it first reads the boot flag, determines the boot path (main system or recovery system) based on the flag, and dynamically loads and configures the FPGA from an independent partition only when needed. This allows the system to flexibly select the boot path based on externally set flags (which can be remotely modified), inserting a "software-configurable decision point" into the boot process and achieving software configurability of the boot path.
[0055] Implementation Method 8: The Xilinx SoC-based boot component update system used in this implementation method is based on the Xilinx SoC-based boot component update system described in Implementation Method 1, combined with the boot component update systems optimized in Implementation Methods 2 to 7.
[0056] In this embodiment, a Xilinx Zynq-7020 SoC and a 256Mbit (16MB) WinbondW25Q128JV QSPI Flash are used.
[0057] In this embodiment, such as Figure 4 As shown, the space occupied by the component-based update system is as follows: FSBL module: 2 × 1MB FPGA bitstream module: 2 × 4MB U-Boot module: 2 × 1MB Kernel module: 6MB Environment Variables and Partition Table Module: 2KB Startup Flags and Configuration Module: 1KB Ramdisk system recovery submodule: 5.7MB When only FPGA logic needs to be upgraded, traditional solutions require transferring and burning the entire BOOT.bin file (approximately 6MB or more). This implementation only requires transferring a bitstream file of approximately 4MB, reducing network transmission time by approximately 33% and Flash write time by approximately 33%.
[0058] FPGA update compatibility issues caused system startup failures. After FSBL successfully verified U-Boot (unmodified), U-Boot would get stuck or the system would crash while loading the new FPGA bitstream. After power-on, because the main FPGA partition verification failed (or the watchdog timeout mechanism failed), the system could automatically boot from the backup FPGA partition to boot the old version. The device would be available again within seconds, and error logs could be reported through ODC, achieving "zero bricking after update failure".
Claims
1. A component-based boot update system based on Xilinx SoC, characterized in that, The component-based update system includes an ODC operation and maintenance platform, a device-side update module, and a device-side QSPI Flash module. The device-side QSPI Flash module includes an FSBL main partition, an FSBL backup partition, an FPGA bitstream main partition, an FPGA bitstream backup partition, a U-Boot main partition, and a U-Boot backup partition; The ODC operation and maintenance platform is used to send a local security update command to the device-side update module after receiving the "packet verification successful" status. The device-side update module is used to receive the local security update instruction, and when the update package is an FPGA update package, write the data of the FPGA bitstream main partition to the FPGA bitstream backup partition, write the update package to the FPGA bitstream main partition, and obtain a hash value based on the current FPGA bitstream main partition; The device-side QSPI Flash module is used to verify the hash value. If the verification is successful, update the metadata of the QSPI Flash module on the device side and report the "local write successful" status to the ODC operation and maintenance platform; Otherwise, the data of the FPGA bitstream backup partition in the QSPI Flash module on the driver side is written to the FPGA bitstream main partition, and the "write failed, rolled back" status is reported to the ODC operation and maintenance platform; The metadata includes a version number and a hash value; The device-side QSPI Flash module also includes a Linux kernel, an env partition, a boot partition, and a Ramdisk recovery partition; In the device-side QSPI Flash module: FSBL Lightweight Bootstrap Phase: The env partition is used to store partition entries and expected hash values; The FSBL primary partition is used to read U-Boot partition entries from the env partition; it is also used to obtain the hash value of the U-Boot image based on the U-Boot partition entries. It is also used to perform integrity verification by comparing the hash value of the U-Boot image with the expected hash value. If the verification fails, the data of the U-Boot backup partition is written to the U-Boot main partition, and the hash value of the current U-Boot main partition is compared with the expected hash value for integrity verification. If the verification fails, the error is recorded to Flash; otherwise, the U-Boot main partition is started. Otherwise, start the U-Boot primary partition; U-Boot Decision and Dynamic Loading Phase: The U-Boot primary partition is used to read the boot flag from the boot partition. If the flag is "recovery": the kernel image is set to the Ramdisk recovery system submodule image, and then the kernel is started directly without executing fpga_load(); If the flag is "main", the fpga_load() function is called first to dynamically load and configure the FPGA. After successful configuration, the kernel image is set to the Linux kernel submodule image, and the Linux kernel boot process continues.
2. The component-based update system for bootstrapping according to claim 1, characterized in that, The component-based update system also includes a device-side application service module.
3. The component-based update system for bootstrapping according to claim 2, characterized in that, The ODC operation and maintenance platform is also used to send component update packages to the device-side application service module; and to receive the "ready" status. The device-side application service module is also used to receive the component update package and send the update instruction to the device-side update module; The device-side update module is also used to receive the update instruction and to send the "ready" status to the ODC operation and maintenance platform.
4. The component-based update system for bootstrapping according to claim 1, characterized in that, The ODC operation and maintenance platform is also used to send the encrypted signature update package to the device-side update module after receiving the "ready" status instruction; The device-side update module is also used to decrypt and verify the encrypted signature update package. If the verification is successful, it sends the "package verification successful" status to the ODC operation and maintenance platform and sends the update package obtained by decrypting the encrypted signature update package to the device-side QSPI Flash module. Otherwise, the "packet verification failed" status will be sent to the ODC operation and maintenance platform.
5. The component-based update system for bootstrapping according to claim 1, characterized in that, The ODC operation and maintenance platform is also used to receive the "local write successful" status and the "write failed, rolled back" status, and send a device restart command to the device-side update module; The device-side update module is also used to receive the device restart command, restart the system, and report the system status to the ODC operation and maintenance platform. The system status includes component version and update status.
6. The component-based update system for bootstrapping according to claim 1, characterized in that, The FSBL primary partition occupies 1MB of space; the FSBL backup partition occupies 1MB of space.
7. The component-based update system for bootstrapping according to claim 1, characterized in that, The FPGA bitstream main partition occupies 4MB of space, and the FPGA bitstream backup partition occupies 4MB of space.
8. The component-based update system for bootstrapping according to claim 1, characterized in that, The U-Boot primary partition occupies 1MB of space; The U-Boot backup partition occupies 1MB of space.
Citation Information
Patent Citations
Method for on-line upgrading of FPGA (Field Programmable Gate Array) configuration item file
CN118394394A
Vehicle-mounted entertainment system upgrading method and system based on Flash CAN
CN119415125A
Dual-backup starting and integrity verification method and system for vehicle-mounted bus
CN121560359A
