Camera firmware offline upgrading device and method

Abstract

The invention relates to the technical field of camera firmware upgrading, in particular to camera firmware offline upgrading equipment and method. The equipment comprises a built-in power supply assembly, a main controller, a local interaction assembly, a storage medium interface and a communication interface assembly, the built-in power supply assembly is used for supplying power to equipment; the main controller is connected with the built-in power supply assembly; the local interaction assembly is connected with the main controller and is used for providing a local operation interface; the storage medium interface is connected with the main controller and is used for accessing a removable storage medium in which firmware data is stored; the communication interface assembly is in communication connection with the main controller and is used for connecting a camera; the main controller is used for writing firmware data from the storage medium interface into the connected camera through the communication interface component; according to the equipment, independent power supply is achieved through the built-in power supply assembly, an offline operation interface is provided by means of the local interaction assembly, the equipment is suitable for outdoor and after-sales scenes without stable power supply, and the convenience and reliability of firmware upgrading of the camera are improved.

Description

Technical Field

[0001] This invention relates to the field of camera firmware upgrade technology, and specifically to a camera firmware offline upgrade device and method. Background Technology

[0002] As a core component of intelligent vehicle visual perception systems, automotive cameras are widely used in Advanced Driver Assistance Systems (ADAS) and autonomous driving technologies. Firmware upgrades are crucial for ensuring system safety and functional iteration. Currently, such as Figure 1 As shown, the industry generally uses PC-based host computer tools to upgrade camera firmware. This solution establishes a communication connection with the camera through professional development tool software. The development tool needs to be equipped with a dedicated power adapter and connected to a 220V AC power supply to realize the firmware burning and parameter configuration of the camera. The existing upgrade method relies on a PC host computer and dedicated debugging equipment, connecting the camera to the development tool through a coaxial cable, and completing firmware transmission and verification under the support of 220V power supply.

[0003] However, current firmware upgrades for vehicle cameras typically require a PC-based host computer tool and a dedicated debugging adapter. This upgrade process necessitates a 220V AC power supply and relies on the PC software environment to establish a communication link. Therefore, firmware upgrades are inconvenient in vehicle after-sales service locations, outdoors, or other scenarios lacking stable AC power and PC equipment. Summary of the Invention

[0004] This invention provides a device and method for offline firmware upgrade of cameras, which can solve the problems of existing camera firmware upgrades relying on PC host computers, dedicated debugging tools and complex environment setup, especially the lack of portability and power supply convenience in outdoor or after-sales scenarios.

[0005] To achieve the above objectives, the present invention provides the following technical solution: A first aspect of the present invention provides a camera firmware offline upgrade device, comprising: a built-in power supply component for powering the device; a main controller connected to the built-in power supply component; a local interaction component connected to the main controller for providing a local operation interface; a storage medium interface connected to the main controller for accessing a removable storage medium storing firmware data; and a communication interface component communicatively connected to the main controller for connecting a camera; the main controller is used to write firmware data from the storage medium interface to the connected camera via the communication interface component.

[0006] In one optional embodiment, the communication interface component includes at least two serial deserializer chips, which are connected to the main controller via a control bus and each supports different vehicle serial communication protocols.

[0007] In one alternative embodiment, different in-vehicle serial communication protocols include the GMSL protocol and the FPD-LINK protocol.

[0008] In one alternative embodiment, the control bus is an IIC bus.

[0009] In an optional embodiment, the main controller is further configured to: read a configuration file in a removable storage medium accessed by the storage medium interface, the configuration file including communication protocol type information of the target camera; Based on the communication protocol type information, perform at least one of the following operations: The local interaction component outputs guidance information instructing the camera to be connected to the corresponding protocol port in the communication interface component; or Automatically detect and confirm whether the camera is connected to a port that matches the communication protocol type information.

[0010] In an alternative embodiment, the main controller is further configured to verify the written data after the firmware data is written to the camera.

[0011] In one alternative embodiment, the verification is performed by sequentially reading back in blocks and performing cyclic redundancy check with the source data.

[0012] In one alternative embodiment, the firmware data block size for block readback is 1024 bytes.

[0013] In one alternative embodiment, the built-in power supply component includes a rechargeable battery and power management circuitry.

[0014] In one alternative embodiment, the built-in power supply component further includes a charging circuit and a power management integrated circuit, which converts the battery voltage into multiple operating voltages required by the main controller and communication interface components.

[0015] In one alternative embodiment, the local interaction component includes a display unit and an input unit.

[0016] In one alternative embodiment, the display unit includes a liquid crystal display screen, and the input unit includes physical buttons or a touch screen.

[0017] In one alternative embodiment, the local interaction component is configured to display the device's battery level, connection status with the camera, list of upgradable firmware, or firmware upgrade progress in real time.

[0018] In one alternative embodiment, the storage medium interface is an SD card interface.

[0019] In one alternative embodiment, the device further includes a housing for accommodating the built-in power supply components, main controller, local interaction components, storage medium interface, and communication interface components.

[0020] A second aspect of the present invention provides a method for firmware upgrade using a camera firmware offline upgrade device, comprising: connecting a removable storage medium storing firmware data to the storage medium interface of the device; connecting the camera to the communication interface component of the device; initiating an upgrade operation through the local interaction component of the device; and the main controller of the device responding to the upgrade operation by writing the firmware data from the storage medium interface to the connected camera through the communication interface component.

[0021] This invention provides a camera firmware offline upgrade device and method. This solution achieves independent power supply capability through a built-in power component, avoiding dependence on external power and solving the problem of power acquisition difficulties in outdoor scenarios. A complete local operation interface is provided through a local interaction component, allowing users to complete the upgrade operation without connecting to a PC, simplifying the environment setup process and improving operational convenience. A removable storage medium is connected via a storage medium interface, enabling offline storage and transmission of firmware data, ensuring the reliability of on-site upgrades. A direct connection is established with the camera through a communication interface component, and the main controller coordinates the firmware data writing process, achieving a plug-and-play upgrade mode, significantly improving after-sales maintenance efficiency. This design not only highly integrates power supply, control, interaction, and communication functions, forming a lightweight and portable upgrade device, but also significantly lowers the technical threshold for camera firmware upgrades through hardware integration and an offline operation mechanism, providing a reliable solution for outdoor and after-sales scenarios, with significant practical value and market prospects. Attached Figure Description

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention. It is obvious that the drawings described below are merely some embodiments of the invention, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0023] In the attached diagram: Figure 1 This is a schematic diagram of the device connection for upgrading the camera firmware prior to the improvements of this invention; Figure 2 This is a schematic diagram showing the connection between the camera firmware offline upgrade device and the camera in one embodiment of the present invention; Figure 3 This is a hardware architecture block diagram of a camera firmware offline upgrade device provided in one embodiment of the present invention; Figure 4This is a software architecture block diagram of a camera firmware offline upgrade device provided in one embodiment of the present invention; Figure 5 This is a schematic diagram of the user interface of a camera firmware offline upgrade device provided in one embodiment of the present invention; The attached diagram is labeled as follows: Camera firmware offline upgrade device 100, built-in power supply component 1, charging circuit 11, power management integrated circuit 12, main controller 2, local interaction component 3, display unit 31, input unit 32, storage medium interface 4, removable storage medium 41, communication interface component 5, serializer chip 51, control bus 6, camera 200. Detailed Implementation

[0024] The following specific examples illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments. Various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0025] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. The drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0026] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the invention. However, it will be apparent to those skilled in the art that embodiments of the invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the invention.

[0027] In the accompanying diagram of the instruction manual: Figure 2 The demonstration shows an application scenario where the camera firmware offline upgrade device 100 (powered by the built-in power supply component 1) establishes a communication connection with the camera 200 using the corresponding protocol through its communication interface component 5 (such as a physical interface supporting the GMSL protocol and the FPD-LINK protocol), thereby performing interactive operations such as firmware upgrades.

[0028] Figure 3 The specific composition and electrical connections of each component in the hardware solution of the camera firmware offline upgrade device 100 are illustrated below: Built-in power supply component 1: Composed of a rechargeable battery (such as a lithium battery pack), a charging circuit 11, and a power management integrated circuit 12. An external 5V DC power supply can charge the battery, and the battery output is converted into multiple stable voltages (e.g., 3.3V, 1.8V, 1.1V) by the power management integrated circuit 12 to power system components such as the main controller 2 and the serializer / deserializer chip 51 in the communication interface component 5.

[0029] Storage medium interface 4: It is a TF card slot (compatible with SD card), which is connected to the main controller 2 through the SDIO interface and is used to access the removable storage medium 41 (SD card) that stores the upgrade firmware package.

[0030] Main Controller 2: The core is a microcontroller (MCU), which serves as the connection and control center for all modules.

[0031] Local interaction component 3 includes input unit 32 (such as physical buttons for power on, select, confirm, etc., which are directly connected to the GPIO of the main controller 2) and display unit 31 (such as a TFT LCD screen, which is connected to the main controller 2 and connected to a power source to display information such as battery level, camera 200 connection status, firmware file list, and upgrade progress).

[0032] Communication interface component 5: The block diagram example includes two serial deserializer chips 51. One serial deserializer chip 51 is connected to the GMSL interface, and the other serial deserializer chip 51 is connected to the FPD-LINK interface. Both are connected to the main controller 2 via the control bus 6. The main controller 2 configures the serial deserializer chips 51 via the control bus 6 to establish a high-speed serial communication link with the camera 200. The high-speed serial communication link includes a data channel for transmitting firmware data and an embedded control channel for accessing the internal registers of the camera 200. The main controller 2 accesses the non-volatile memory inside the camera 200 through the embedded control channel.

[0033] Figure 4 The software layering structure running on the main controller 2 is demonstrated, with a real-time operating system (RTOS) as the system scheduling core, and is divided into: Hardware driver layer: including serial port driver, TFT display driver, file system driver, SDIO driver, control bus 6 driver, ADC driver, GPIO driver, etc., responsible for interaction with the underlying hardware.

[0034] Application layer: includes several key functional tasks, such as display interaction UI tasks, firmware upgrade tasks, power management tasks, button handling tasks, system debugging tasks, and SD card (i.e., removable storage medium 41) data processing tasks. These tasks work together to realize all the functions of the camera firmware offline upgrade device 100.

[0035] System layer: Centered on RTOS, it is responsible for task scheduling, synchronization, and communication between layers.

[0036] Figure 5 (User interface diagram) This diagram illustrates a user interface layout example for the display unit 31 in the local interaction component 3, including three core information display areas: Top area: The left side displays the "connected / not connected" status indicators for the camera firmware offline upgrade device 100 and the camera 200; the middle is the status display area for the camera firmware offline upgrade device 100; and the right side is the battery level display area for the built-in power component 1.

[0037] The middle area is for selecting and displaying a list of upgradable firmware. For example, the list displays different versions of firmware files such as "camera_firmware_V1.0", "camera_firmware_V1.1", and "camera_firmware_V1.2" for the user to select through input unit 32.

[0038] Bottom area: This is the firmware upgrade status display area, used to dynamically display the current camera firmware version (e.g., V1.1), the target firmware version to be upgraded (e.g., V1.2), and the real-time upgrade progress (e.g., "Upgrading..." prompt and 70% progress bar).

[0039] Example 1: The current firmware upgrade method for the Camera 200 primarily relies on PC-based host computer software in conjunction with dedicated debugging equipment. This solution requires the use of a communication adapter developed by the original manufacturer or a third party, and a separate power adapter. The communication link is typically established via USB, JTAG, or a dedicated interface, and complex protocol stack configuration and driver installation are required between the debugging tool and the Camera 200. This method suffers from several drawbacks, including complex environment setup, reliance on a PC host and a stable AC power supply, unsuitability for on-site upgrade scenarios without fixed power supply, such as outdoor or vehicle-mounted locations, and large and inaccessible equipment, making it difficult to meet the needs of rapid after-sales response and operation by non-technical personnel.

[0040] like Figure 2-4 As shown, the present invention provides a camera firmware offline upgrade device 100, including a built-in power supply component 1, a main controller 2, a local interaction component 3, a storage medium interface 4, and a communication interface component 5; Built-in power supply component 1 is used to power the camera firmware offline upgrade device 100; main controller 2 is connected to built-in power supply component 1; local interaction component 3 is connected to main controller 2 and is used to provide a local operation interface; storage medium interface 4 is connected to main controller 2 and is used to access removable storage medium 41 storing firmware data; communication interface component 5 is connected to main controller 2 for communication and is used to connect to camera 200; main controller 2 is used to write firmware data from storage medium interface 4 to the connected camera 200 through communication interface component 5.

[0041] It should be noted that the built-in power supply component 1 is the basic unit that ensures the camera firmware offline upgrade device 100 can operate independently without an external power supply environment. Its function is not limited to power supply, but also needs to support multi-voltage rail output, charge and discharge management, power monitoring and overvoltage / overcurrent / overtemperature protection. This component can be implemented using a rechargeable lithium battery pack in conjunction with the power management integrated circuit 12, such as a lithium polymer battery pack with a nominal voltage of 7.4V and a capacity of not less than 5000mAh. After conversion by the power management integrated circuit 12, it outputs multiple stable DC voltages such as 3.3V (for the main controller 2 and logic circuits), 1.8V (for the serializer chip 51 I / O), and 1.1V (for the core of the main controller 2).

[0042] The main controller 2 is a microcontroller (MCU), such as a chip with an integrated ARM Cortex-M series core or RISC-V core. It needs to have necessary peripheral interface resources such as SDIO, IIC, and GPIO to reduce power consumption and cost while ensuring complete functionality. The main controller 2 is connected to the built-in power supply component 1 through a power input pin and an ADC sampling channel to obtain the operating voltage and read the battery voltage and current information in real time to estimate the remaining power.

[0043] The local interaction component 3 is the key interface for users to establish an operational loop with the camera firmware offline upgrade device 100. Its role is to replace the PC graphical interface and command line tools, and realize the full-process visual interaction of upgrade preparation, target selection, process monitoring and result confirmation. The local interaction component 3 includes at least two parts: a display unit 31 and an input unit 32, both of which are electrically connected to the main controller 2. The display unit 31 can be a TFT LCD screen, an OLED screen, or a segment LCD, used to display battery level, camera 200 connection status, firmware file list in TF card, current / target firmware version number, upgrade progress bar, and error message. The input unit 32 can be a physical button (such as a power button, up / down selection buttons, and confirmation button, directly connected to the GPIO pins of the main controller 2), a touch screen (resistive or capacitive), a rotary encoder, or a capacitive touch button, used to receive user commands and trigger corresponding functions. When a physical button solution is used, it has strong anti-electromagnetic interference capability and high operational reliability, making it suitable for industrial environments such as vehicle repair. When the display unit 31 is omitted, key status feedback can be achieved through a combination of multi-color LED indicator lights (such as a solid green light indicating successful connection and a flashing red light indicating verification failure) combined with a buzzer tone.

[0044] Storage medium interface 4 is the localized carrier access channel for firmware data. Its design must balance compatibility, stability, and anti-misinsertion mechanisms. Storage medium interface 4 can be a TF card (MicroSD) interface conforming to the SD 3.0 specification or a standard SD card interface, connected to the main controller 2 via the SDIO bus, supporting FAT32 or exFAT file systems. The TF card is used to pre-store signed and authenticated firmware binary files (.bin), configuration files (.cfg), and verification digests (.sha256). The main controller 2 reads and verifies their integrity through the file system driver. The interface structure can be equipped with a latch detection switch and a hot-plug protection circuit to prevent hot-plugging from causing the main controller 2 to reset or data corruption.

[0045] The communication interface component 5 serves as the physical and protocol channel for establishing a data path between the camera firmware offline upgrade device 100 and the camera 200. It needs to support hardware-level interfacing with the mainstream high-speed serial communication protocols of the vehicle-mounted camera 200. The communication interface component 5 includes at least one physical interface and its matching protocol conversion circuit, which can establish a reliable connection with camera 200 modules compatible with GMSL (Gigabit Multimedia Serial Link) or FPD-LINK (Flat Panel Display Link) protocols. The communication interface component 5 and the main controller 2 communicate via a standard control bus 6 (such as IIC, SPI, or LVDS control channel) for register configuration, status query, and command issuance. The communication interface component 5 can adopt a discrete design, i.e., each physical interface corresponds to an independent serial deserializer chip 51; or it can adopt a multiplexed design, supporting multiple protocols on a single interface through automatic protocol identification and dynamic switching circuits. The interface can be a FAKRA connector (commonly used for GMSL), an HSD (High Speed ​​Data) connector, or a customized vehicle wiring harness interface, with EMC shielding and mechanical locking structures to ensure a stable connection under vehicle vibration conditions.

[0046] Through the above technical solution, this invention achieves the following: in a restricted field environment without a PC, mains power, or network connection, the entire firmware upgrade process of the vehicle-mounted camera 200 can be initiated and completed simply by inserting a removable storage medium 41 containing firmware, connecting the target camera 200, and triggering local operation commands. Because the built-in power supply component 1 provides independent power supply, it solves the technical problem of not being able to obtain stable AC power in outdoor and after-sales scenarios; because the main controller 2 integrates protocol parsing and data scheduling capabilities, combined with the hardware compatibility design of the communication interface component 5, it solves the upgrade compatibility problem caused by different vehicle-mounted cameras 200 using heterogeneous protocols such as GMSL or FPD-LINK; because the local interaction component 3 provides graphical guidance and status feedback, it lowers the operation threshold, enabling non-technical personnel to accurately complete the upgrade task; because the storage medium interface 4 supports offline firmware loading, it avoids network transmission risks and dependence on host computer tools, improving the controllability of firmware sources and the security of the upgrade process. Therefore, this embodiment achieves a plug-and-play, offline autonomous, protocol-compatible, and user-friendly portable firmware upgrade effect, effectively improving the maintenance efficiency and responsiveness of the vehicle-mounted camera 200 throughout its lifecycle.

[0047] Optionally, after reading the firmware data, the main controller 2 is also used to verify the digital signature of the firmware data according to a preset verification key, and to perform a write operation after the verification is successful.

[0048] Example 2: like Figure 3As shown, as an optional embodiment of this case, this embodiment further provides: the communication interface component 5 includes at least two serial deserializer chips 51, the serial deserializer chips 51 are connected to the main controller 2 through the control bus 6, and each supports different vehicle serial communication protocols.

[0049] It should be noted that the communication interface component 5 includes at least two serial deserializer chips 51, which are used to achieve physical layer and link layer interfacing with vehicle cameras 200 that use different high-speed serial communication protocols. The serial deserializer chips 51 are connected to the main controller 2 through the control bus 6, so that the main controller 2 can control the register configuration, status reading, fault diagnosis and protocol switching of each serial deserializer chip 51. The serial deserializer chips 51 support different vehicle serial communication protocols, so that the same camera firmware offline upgrade device 100 can cover the heterogeneous communication standards adopted by mainstream vehicle cameras 200, and can be adapted to multiple vehicle platforms without replacing hardware or external adapter modules.

[0050] Based on the type of the actually connected camera 200, the main controller 2 selectively activates the corresponding serial deserializer chip 51 through the control bus 6, and uses the built-in protocol engine of the chip to complete physical layer docking, link establishment and EEPROM access operations. Since each serial deserializer chip 51 natively supports GMSL and FPD-LINK protocols, there is no need for software to simulate the protocol stack or add an external protocol conversion bridge chip, which fundamentally avoids problems such as communication failure, firmware writing interruption or EEPROM erase / write abnormality caused by protocol incompatibility. This solves the technical problem in the background technology that "a single communication interface cannot be compatible with the different high-speed serial communication protocols used by various vehicle cameras 200, resulting in poor universality of the camera firmware offline upgrade device 100 and frequent adapter replacements on site", and achieves the technical effects of expanding the protocol coverage of the camera firmware offline upgrade device 100, improving cross-platform adaptability and reducing the complexity of after-sales maintenance.

[0051] Example 3: like Figure 2-3 As shown, as an optional embodiment of this case, this embodiment further provides: different vehicle serial communication protocols including the GMSL protocol and the FPD-LINK protocol.

[0052] It should be noted that GMSL protocol refers to Gigabit Multimedia Serial Link protocol, and FPD-LINK protocol refers to Flat Panel Display Link protocol. In this embodiment, GMSL and FPD-LINK protocols are two independent vehicle serial communication protocols that are incompatible at both the physical and link layers. They are mapped to the physical channels corresponding to two independent serial deserializer chips 51 in the communication interface component 5. That is, one serial deserializer chip 51 is dedicated to the encoding and decoding and link management of the GMSL protocol stack, while the other serial deserializer chip 51 is dedicated to the frame synchronization, CRC check, and reverse IIC channel parsing of the FPD-LINK protocol stack. The two are physically isolated in hardware, and in software, they are accessed by the main controller 2 through the same control bus with 6-fold time-division addressing. This ensures that protocol switching does not require hardware replacement, does not introduce signal crosstalk, and can support the firmware upgrade needs of multiple brands and generations of vehicle cameras 200 in parallel.

[0053] The GMSL protocol can be implemented using MAX96705, MAX96711, or a serial deserializer chip 51 compatible with GMSL2 / GMSL3 standards; the FPD-LINK protocol can be implemented using DS90UB953, DS90UB960, or a serial deserializer chip 51 supporting FPD-Link III / IV; both types of chips are connected to the main controller 2 through a standard IIC interface (SCL / SDA), with configurable addresses, supporting the main controller 2 to dynamically identify the device type, read the protocol identifier register in the camera 200 EEPROM, and automatically load the corresponding protocol driver module accordingly. Because both protocols natively support the reverse IIC control channel, the main controller 2 can directly access the non-volatile storage unit inside the camera 200, avoiding the limitation of relying on the pre-installed upgrade service program in the camera 200 MCU firmware in traditional solutions. This allows the underlying firmware to be rewritten even when the camera 200 is powered off or in an abnormal state. As a result, in limited environments with no PC, no stable power supply, and time sensitivity, such as outdoor maintenance, rapid recovery of accident sites, and batch upgrades after sales, the success rate, universality, and engineering implementation efficiency of firmware upgrade operations are improved.

[0054] Example 4: like Figure 3 As shown, as an optional embodiment of this case, this embodiment further provides that: the control bus 6 is an IIC bus.

[0055] It should be noted that control bus 6 is an IIC bus, meaning that IIC (Inter-Integrated Circuit) is used as the control communication channel between the main controller 2 and multiple serial deserializer chips 51. This significantly reduces hardware resource consumption and system interconnection complexity while ensuring reliable configuration and status interaction. Specifically, because the IIC bus has the advantages of fewer pins, mature protocols, strong multi-device support capabilities, and low hardware and software implementation costs, in an architecture where multiple serial deserializer chips 51 coexist, the main controller 2 only needs to occupy two general-purpose I / O pins to complete the register configuration and status monitoring of all serial deserializer chips 51, effectively alleviating the pin resource shortage problem of the embedded main controller 2. At the same time, the standardized interface of the IIC bus lowers the replacement threshold for serial deserializer chips 51 from different manufacturers, enhancing hardware design flexibility and supply chain robustness. This solves the practical problems in the background technology, such as high hardware integration difficulty, decreased system reliability, and increased maintenance costs caused by complex control links, achieving the technical effects of simplified circuit design, improved multi-protocol adaptation efficiency, and guaranteed stability for field upgrades.

[0056] Example 5: like Figure 3-4 As shown, as an optional embodiment of this case, this embodiment further provides that: the main controller 2 is also configured to: automatically identify or guide the user to connect to the camera 200 that matches the configuration file according to the configuration file in the removable storage medium 41 accessing the storage medium interface 4; wherein, the configuration file includes at least the communication protocol type information adopted by the target camera 200, and is used to guide the user to connect the camera 200 to the corresponding physical port on the communication interface component 5.

[0057] like Figure 3-4 As shown, as an optional embodiment of this case, this embodiment further provides that: the main controller 20 is also configured to: read the configuration file in the removable storage medium 41 connected to the storage medium interface 4, the configuration file including the communication protocol type information of the target camera; Based on the communication protocol type information, perform at least one of the following operations: The local interaction component 3 outputs guidance information instructing the camera 200 to be connected to the corresponding protocol port in the communication interface component 5; or Automatically detect and confirm whether the camera 200 is connected to a port that matches the communication protocol type information.

[0058] It should be noted that the configuration file settings enable the main controller 20 to determine the communication protocol type required by the target camera before performing a firmware upgrade. Based on this, the main controller 20 can execute corresponding control logic to assist or verify the physical connection process. Specifically, the main controller 20 obtains explicit protocol identification information by reading and parsing the configuration file, and can then coordinate the initialization behavior of the hardware interface or generate user guidance instructions accordingly. This method pre-embeds the protocol differences between different cameras in the configuration file, reducing the requirements for protocol recognition capabilities of on-site operators, avoiding physical connection errors caused by protocol incompatibility from the source, thereby improving the device's adaptability to cameras with different protocols and the reliability of the entire upgrade process.

[0059] Based on the communication protocol type information, the main controller 20 can primarily perform two cooperative operations. The first is a guided mode: the main controller 20 outputs visual or auditory guidance information to the user through the local interaction component 3 (e.g., its display unit) to instruct the user to connect the camera 200 to the physical port on the communication interface component 5 that matches the protocol type. The second is an automatic identification and verification mode. In this mode, the main controller 20 sequentially accesses each serializer / deserializer chip 51 in the communication interface component 5 via the control bus (e.g., I²C bus), queries whether there is a camera response at the corresponding physical port, and reads the protocol identification information of the responding camera. The main controller 20 compares the actual protocol identification read with the target protocol type recorded in the configuration file. If a camera response is detected only at a certain port, and its protocol identification matches the configuration file, the connection is determined to be correct, and the system automatically enters the subsequent upgrade preparation process; if no valid response is detected at any port, or the detected protocol identification does not match the configuration file, the connection is determined to be abnormal, and an error message is output through the local interaction component 3.

[0060] The physical ports on the communication interface component 5 are typically interfaces with independent mechanical and electrical identifiers, supported by different serializer / deserializer chips 51. As an alternative hardware implementation, the physical ports of the communication interface component 5 can be designed as adaptive multiplexing interfaces. In this design, the device has only one physical connector, but its rear end is connected to multiple parallel serializer / deserializer chips 51. The main controller 20 is connected to these deserializer chips 51 via a control bus and simultaneously controls an analog switch or signal multiplexer. Based on the protocol type determined in the configuration file, the main controller 20 controls this switch to select which protocol's signal from the physical connector is routed to the corresponding protocol's serializer / deserializer chip 51, thereby achieving time-division multiplexing compatibility of a single physical interface for multiple protocols. This design, through clear pre-defined guidance, eliminates the need for operators to manually determine the correspondence between protocols and ports, effectively avoiding connection errors and simplifying on-site operations.

[0061] Example 6: As an optional embodiment of this case, this embodiment further provides that the main controller 2 is also configured to verify the written data after writing the firmware data to the camera 200.

[0062] This embodiment aims to address the issue that during the firmware writing process, factors such as momentary interruption of the communication link, fluctuations in EEPROM programming voltage, timing offset of the serial deserializer chip 51, or failure to erase or write the storage unit may cause some data to be incorrectly burned into the non-volatile memory (such as EEPROM or Flash) inside the camera 200, thereby leading to functional failures such as camera 200 startup failure, image abnormalities, and protocol handshake timeouts. After the main controller 2 completes the physical writing of firmware data to the camera 200, it automatically initiates data consistency verification without external intervention. By directly reading back the actual storage content inside the camera 200 and comparing it with the source data, it effectively identifies hidden write errors caused by communication jitter, power drops, or EEPROM unit failure. Since the verification action occurs at a deterministic point in time after the writing is completed, and the comparison object is the actual storage state of the camera 200 rather than the transmission buffer or intermediate register, it can accurately locate the specific address range of the write failure, avoiding the implementation of erroneous firmware. This improves the success rate of a single upgrade, reduces the after-sales rework rate, and ensures the reliability and traceability of the firmware upgrade process in restricted environments such as the field and vehicles without PC assistance.

[0063] Example 7: As an optional embodiment of this case, this embodiment further provides a verification method in which the verification is performed by sequentially reading back in blocks and performing cyclic redundancy verification with the source data.

[0064] It should be noted that by dividing the firmware data into fixed-length data blocks, reading the corresponding blocks sequentially from the camera's 200 storage unit, and synchronously performing cyclic redundancy check (CRC) on the data blocks at the same location in the original firmware file locally, the CRC values ​​calculated twice are compared to see if they match, thus completing the write correctness verification. This method avoids the memory resource bottleneck caused by loading the entire firmware into the main controller's 2 RAM for a one-time comparison, and is particularly suitable for resource-constrained embedded main control environments (such as ARM Cortex-M series MCUs or RISC-V architecture microcontrollers), balancing verification reliability, memory usage efficiency, and real-time response capabilities.

[0065] The main controller 2 coordinates the data reading rhythm of the storage medium interface 4, the command issuance timing of the communication interface component 5, and the allocation of local CRC calculation resources; the storage medium interface 4 provides a stable, low-latency supply of firmware source data; the communication interface component 5 ensures accurate delivery of readback commands and receipt of valid responses; and the CRC verification logic is embedded as a quality gate node in the entire data flow path, forming a closed-loop verification chain of write-readback-comparison-feedback. This coordination does not rely on external device intervention and is entirely completed autonomously by the internal modules of the camera firmware offline upgrade device 100.

[0066] Despite the limited RAM resources of the main controller, it can still perform high-confidence write verification on vehicle camera 200 firmware (such as the GMSL camera 200, whose common firmware size is 2MB-8MB) in the several MB range. Because it adopts a sequential block processing mechanism, each verification only needs to cache one piece of data and its CRC value (e.g., 1024 bytes + 4 bytes CRC), resulting in peak memory usage of less than 2KB, which is lower than the full loading scheme. Due to the use of the CRC algorithm, it can effectively identify common anomalies such as data misalignment and bit flipping caused by power fluctuations, signal interference, poor contact, or errors in the serial deserializer chip 51 link during firmware burning. Because the verification logic is deeply integrated with the main controller's runtime system, it can combine RTOS task priority scheduling to insert verification subtasks into the upgrade task, ensuring that the main thread (such as UI refresh and progress reporting) is not blocked while ensuring that each piece of data is verified in a timely manner. Therefore, without increasing hardware costs, it improves the robustness and field applicability of firmware upgrade operations, effectively solving the technical contradiction of balancing verification completeness and resource adaptability in embedded portable devices without PC assistance.

[0067] Example 8: As an optional embodiment of this case, this embodiment further provides that the firmware data block size for block readback is 1024 bytes.

[0068] It should be noted that this technical solution addresses the performance balance issue encountered in the verification process during embedded firmware upgrades: When firmware readback verification is performed in blocks, if the size of a single data block is too large, it will significantly increase the RAM usage pressure on the main controller 2, especially on resource-constrained MCU platforms, easily triggering memory overflow or interrupt delays; if the size of a single block is too small, multiple IIC reads, CRC calculations, and comparisons need to be initiated frequently, leading to a surge in the number of bus transactions, frequent CPU context switching, and an extended overall verification time, reducing upgrade efficiency. Specifically, block readback refers to the main controller 2 initiating a reverse read request to the connected camera 200 through the communication interface component 5 after the firmware is written. It sequentially reads the written data segments from the non-volatile memory inside the camera 200 according to a preset fixed length and performs consistency verification with the data blocks at the corresponding positions of the original firmware source data. This process does not rely on external PCs or network feedback and is entirely completed locally in a closed loop by the camera firmware offline upgrade device 100. Firmware data blocks specifically refer to a continuous sequence of bytes participating in a single verification operation. Their boundaries are strictly aligned to integer multiples of byte offset addresses to ensure that read operations comply with the physical constraints of memory page erase / write units; the size is 1024 bytes, meaning each data block precisely includes 1024 consecutive bytes (i.e., 2¹). 0 The value (in bytes) is not arbitrarily chosen, nor is it solely for programming convenience; rather, it is determined based on the typical storage architecture and real-time constraints of embedded systems.

[0069] Without introducing additional hardware resources, changing the communication protocol stack architecture, or relying on external computing units, closed-loop readback and CRC32 verification are performed on the firmware data written to camera 200 in 1024-byte units. Because this block length is aligned with the EEPROM physical page structure, the number of cross-page accesses is reduced, lowering the probability of 6 retries on the control bus. Because it is compatible with the on-chip RAM capacity of the main controller 2, it avoids the uncertainty and potential leakage risks caused by dynamic memory allocation. Furthermore, because it achieves a balance between computation frequency and single-processing volume, the overall verification time is shortened compared to the 512-byte block scheme, and the peak memory usage is reduced compared to the 2048-byte block scheme.

[0070] Example 9: like Figure 3 As shown, as an optional embodiment of this case, this embodiment further provides: the built-in power supply component 1 includes a rechargeable battery and a power management circuit.

[0071] It should be noted that by integrating a rechargeable battery as an energy carrier and setting up a power management circuit within the camera firmware offline upgrade device 100, the device achieves the self-sufficiency required for full-function operation. The rechargeable battery provides continuous and stable DC power output, while the power management circuit handles core management functions such as battery charging and discharging control, voltage conversion, current distribution, overvoltage / overcurrent / overtemperature protection, and system power supply status monitoring. Through this combined structure, the camera firmware offline upgrade device 100 eliminates its dependence on external AC power or a PC USB port, enabling it to independently complete firmware upgrades in restricted environments such as vehicle environments without mains power, repair shops, accident scenes, and outdoor roads, thus improving on-site responsiveness and operational freedom. The rechargeable battery is either a lithium-ion battery or a lithium polymer battery. The power management circuit includes a charging management unit, a battery protection unit, and a multi-channel DC-DC voltage conversion module. The rechargeable battery and the power management circuit are electrically and mechanically connected through a dedicated battery connector and a flexible printed circuit board (FPC) with fuse function. The rechargeable battery provides basic electrical energy reserves as an energy source, while the power management circuit, as the energy dispatching hub, completes the adaptation of electrical energy form and system-level safety control. The two constitute a closed-loop energy subsystem, ensuring that the main controller 2, communication interface component 5, storage medium interface 4, and local interaction component 3 all receive stable, clean, and controlled power supply support under different load conditions.

[0072] Example 10: like Figure 3 As shown, as an optional embodiment of this case, this embodiment further provides that: the built-in power supply component 1 also includes a charging circuit 11 and a power management integrated circuit 12, the power management integrated circuit 12 being used to convert the battery voltage into multiple operating voltages required by the main controller 2 and the communication interface component 5.

[0073] It should be noted that the charging circuit 11 is responsible for the safe access and intelligent charging of the energy input terminal; the lithium battery serves as an energy buffer and reserve unit, smoothing out the impact of instantaneous large current; the power management integrated circuit 12 serves as the energy dispatching center, allocating differentiated voltages according to the functional requirements of the modules, and ensuring that the main controller 2 is powered on and initialized before driving the communication interface component 5 to power on and handshake through precise timing control, avoiding the serial deserializer chip 51 from locking up or the control bus 6 from conflicting due to power supply timing disorder; the voltage rails are isolated by physical wiring and the magnetic bead filtering design to suppress cross-module noise coupling and improve communication reliability, thereby realizing the provision of customized, highly stable, and low-interference multi-channel DC power supply for heterogeneous functional modules under the premise of a single rechargeable battery power supply. Because it incorporates a power management integrated circuit 12 with multiple DC-DC and LDO output capabilities, and is equipped with an integrated charging circuit 11, it can efficiently and controllably convert the original output voltage of the lithium battery into the core logic voltage (such as 3.3V) required by the main controller 2 and the protocol-specific voltage (such as 1.8V for GMSL I / O and 1.1V for FPD-LINK core) required by the communication interface component 5. This solves the technical problem in the background technology that "ordinary battery output cannot directly meet the power supply requirements of various different voltage levels required by modules such as the main controller 2 and the communication interface component 5", thereby achieving the technical effects of optimizing the power architecture, extending the battery life of the camera firmware offline upgrade device 100, and improving the system's operational stability and anti-interference capabilities.

[0074] Example 11: like Figure 3-4 As shown, as an optional embodiment of this case, this embodiment further provides: the local interaction component 3 includes a display unit 31 and an input unit 32.

[0075] It should be noted that the display unit 31 is used to visually output the operating status and related information of the camera firmware offline upgrade device 100 to the user. Its functions cover, but are not limited to, battery level, physical connection status of the camera 200 (such as GMSL link lock, FPD-LINK clock synchronization), list of recognizable firmware files, target camera 200 model and current firmware version, confirmation interface before the upgrade task starts, real-time upgrade progress bar, verification result prompts and abnormal alarm information; the display unit 31 can be a liquid crystal display (LCD). The input unit 32 is used to receive user operation commands for the camera firmware offline upgrade device 100, including but not limited to power on / wake up, firmware selection, camera 200 protocol type confirmation, upgrade start, upgrade stop, and menu navigation; its physical implementation includes physical buttons, touch screen, rotary encoder, or capacitive touch buttons.

[0076] Example 12: like Figure 3-4As shown, as an optional embodiment of this case, this embodiment further provides: the display unit 31 includes a liquid crystal display screen, and the input unit 32 includes physical buttons or a touch screen, realizing the autonomous guidance and status control of the entire firmware upgrade process by the local interaction component 3 without PC intervention. Since the liquid crystal display screen can intuitively present multi-dimensional status information (such as protocol type, connection quality, and remaining battery power) in a graphical manner, and the physical buttons maintain stable triggering characteristics under harsh conditions such as humidity, low temperature, and wearing gloves, the combination of the two significantly reduces the probability of user misoperation; at the same time, the touch screen, as an optional alternative, expands the operational adaptability of the camera firmware offline upgrade device 100 to different user groups. Therefore, in a limited field environment where no external computing device and stable AC power are required, this display and input configuration effectively supports the core function of the camera firmware offline upgrade device 100 as "plug and play, one-click upgrade," solving the problems of high after-sales upgrade failure rate and high operation threshold caused by the single interaction method and poor environmental adaptability in the background technology.

[0077] Example 13: like Figure 3-4 As shown, as an optional embodiment of this case, this embodiment further provides: the local interaction component 3 is configured to display in real time the battery level of the camera firmware offline upgrade device 100, the connection status with the camera 200, the list of upgradable firmware, or the firmware upgrade progress.

[0078] The local interaction component 3 serves as the most direct information interaction channel between the user and the camera firmware offline upgrade device 100. Its core function is to dynamically present the key operating status collected, analyzed, and integrated by the main controller 2 in a visual manner, thereby eliminating information blind spots during the operation process and ensuring the controllability and predictability of the upgrade behavior. This configuration is not simply a superposition of multiple display items, but rather achieves synchronous, hierarchical, and context-related presentation of multi-dimensional status information through the periodic collection, formatting, and interface scheduling of multi-source heterogeneous status data by the main controller 2, improving human-machine collaboration efficiency and operational fault tolerance. Thus, without relying on external computing devices and network connections, the local interaction component 3 of the camera firmware offline upgrade device 100 itself can provide users with a transparent view of the entire lifecycle status covering four key dimensions: energy supply, communication link, upgrade resources, and execution process. Because the main controller 2 continuously collects and integrates multi-source status signals from the power management circuit, communication interface component 5, and storage medium interface 4, and drives the display unit 31 to organize, render, and update the interface content according to preset logic, it solves the technical problem that users cannot keep track of the real-time operation of the camera firmware offline upgrade device 100 in restricted environments such as the field or after-sales without PC assistance, and are prone to misoperation or upgrade failure due to missing information; thus achieving the technical effects of improving operational certainty, reducing human error rate, and enhancing the professional credibility and on-site response reliability of the camera firmware offline upgrade device 100.

[0079] Example 14: like Figure 3-4 As shown, as an optional embodiment of this case, this embodiment further provides that: the storage medium interface 4 is an SD card interface.

[0080] It should be noted that by using a standardized SD card or TF card interface as the firmware data input channel, users can directly use consumer-grade memory cards pre-installed with firmware, without the need for a dedicated programmer or PC conversion tools. Because SD / TF cards possess industrial-grade temperature adaptability, high shock resistance, and ultra-long insertion / removal lifespan, the camera firmware offline upgrade device 100 ensures stable firmware reading in complex environments such as vehicle chassis and repair pits. The open interface protocol and mature drivers significantly reduce the software development difficulty of the main controller 2, while also reserving a compatibility foundation for future expansion with new functions such as USB Host interface and Bluetooth firmware push. SD / TF cards offer advantages such as high capacity, low cost, and portability, perfectly meeting the needs of portable devices.

[0081] Example 15: As an optional embodiment of this case, this embodiment further provides that the camera firmware offline upgrade device 100 also includes a housing for accommodating the built-in power supply component 1, the main controller 2, the local interaction component 3, the storage medium interface 4, and the communication interface component 5.

[0082] Example 16: This invention provides a method for firmware upgrade using a camera firmware offline upgrade device 100, comprising: connecting a removable storage medium 41 storing firmware data to the storage medium interface 4 of the camera firmware offline upgrade device 100; connecting a camera 200 to the communication interface component 5 of the camera firmware offline upgrade device 100; initiating an upgrade operation through the local interaction component 3 of the camera firmware offline upgrade device 100; and the main controller 2 of the camera firmware offline upgrade device 100 responding to the upgrade operation by writing the firmware data from the storage medium interface 4 to the connected camera 200 through the communication interface component 5.

[0083] In one optional embodiment of this case, if the upgrade fails, the main controller 2 can control the automatic restoration to the previous available firmware version.

[0084] In one optional embodiment of this case, after reading the firmware data, the main controller 2 is also used to verify the digital signature of the firmware data according to the verification key preset in the device's secure storage area; only after the verification is successful will the subsequent write operation be performed.

[0085] The following will describe in detail the working process of the camera firmware offline upgrade device 100: First, prepare by storing the firmware upgrade package and corresponding configuration file of camera 200 in the root directory of removable storage medium 41 (e.g., TF card), and then inserting the storage medium into the storage medium interface 4 of camera firmware offline upgrade device 100.

[0086] Subsequently, the camera firmware offline upgrade device 100 is powered on and starts up. The built-in power supply component 1 begins to supply power to the camera firmware offline upgrade device 100, and the main controller 2 initializes. The display unit 31 of the local interaction component 3 displays information such as the battery level of the camera firmware offline upgrade device 100, and displays the camera 200 as "not connected" by default. The main controller 2 reads data from the storage medium, prioritizing the configuration file (e.g., an .ini format file). This configuration file includes serializer model information and serializer information corresponding to the target camera 200, used to instruct the user to connect the camera 200 to which physical port on the communication interface component 5.

[0087] Next, the target camera 200 is connected. Following the instructions in the configuration file, the user connects the camera 200 to the corresponding physical port on the communication interface component 5 via a cable. The main controller 2 automatically controls the corresponding serializer / deserializer chip 51 to establish a communication connection with the camera 200 based on the configuration file. Upon successful connection, the display status of the local interaction component 3 is updated to "Connected". Simultaneously, the main controller 2 continues to read firmware files (e.g., .bin format files) from the storage medium and displays a list of identified firmware versions on the local interaction component 3 for the user to select via the input unit 32.

[0088] Then, the firmware upgrade operation is performed. After the user selects and confirms the firmware version to be upgraded through the local interaction component 3, the main controller 2 first reads and displays the existing firmware version information in the camera 200, and simultaneously displays the target version information to be upgraded. Subsequently, the main controller 2 writes the firmware data from the storage medium interface 4 to the connected camera 200 through the communication interface component 5. During the upgrade process, the local interaction component 3 displays the upgrade progress bar in real time.

[0089] After the upgrade is completed, a verification process is executed. The main controller 2 reads back the written firmware data from the camera 200's memory and compares it with the source firmware data in the storage medium. The specific verification method is as follows: starting from the starting address, a fixed-size (e.g., 1024 bytes) data block is read back from the camera 200 sequentially, and a cyclic redundancy check (CRC32) calculation is performed on each data block; simultaneously, the same verification calculation is performed on the source data block at the same location in the storage medium; the verification results are compared to see if they match, and this process is repeated until the entire firmware package is verified. If all data blocks are verified to be consistent, the upgrade is considered successful; otherwise, an upgrade failure message is displayed.

[0090] Finally, once the verification is successful, the firmware upgrade process is complete.

[0091] This method addresses the dependence of traditional upgrade methods on personal computers, specialized tools, and fixed power supplies. Its principle lies in achieving a self-contained firmware delivery and writing system through the collaboration and structured local operation of various modules within a portable device. Implementing this method enables plug-and-play offline upgrades, significantly simplifying operations and lowering the technical barrier; the device operates using a built-in battery, completely eliminating the limitation of fixed power supplies and expanding application scenarios; it integrates multi-protocol interfaces and intelligent guidance, ensuring compatibility with mainstream automotive cameras 200, improving versatility and success rate; and localized status feedback and data verification mechanisms ensure the transparency of the upgrade process and the high reliability of the results.

[0092] In this case, by directly storing the verified correct firmware in the removable storage medium 41 (such as a TF card or SD card) and reading it through the storage medium interface 4, complete offline writing (i.e. burning) is achieved, ensuring the singleness and immutability of the firmware source and guaranteeing the uniqueness of the firmware from the physical carrier.

[0093] The camera firmware offline upgrade device 100 focuses on firmware writing (upgrade). After power-on, the main controller 2 can automatically complete the protocol configuration of the communication interface component 5 and the connected camera 200 based on the configuration file in the storage medium, which simplifies the operation process and enables users to quickly initiate and complete the upgrade through the local interaction component 3, making the operation convenient and efficient.

[0094] The camera firmware offline upgrade device 100 has a built-in power supply component 1 (including a rechargeable battery and a power management circuit), which completely eliminates its dependence on a fixed external power source, broadens the application environment, and is especially suitable for scenarios that require mobile operation, such as after-sales maintenance and on-site problem diagnosis.

[0095] The camera firmware offline upgrade device 100 integrates a local interactive component 3 (including a display unit 31 and an input unit 32), which can display key information such as battery level, connection status with camera 200, list of upgradable firmware, and upgrade progress in real time and intuitively. It provides users with clear operation feedback and process monitoring, fundamentally ensuring the visibility, controllability, and reliability of the upgrade process.

[0096] The above embodiments are merely illustrative of the principles and effects of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of the present invention. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in the present invention should still be covered by the claims of the present invention.

Claims

1. A camera firmware offline upgrade device, characterized in that, include: Built-in power supply component for powering the device; The main controller is electrically connected to the built-in power supply component; A local interaction component, connected to the main controller, is used to provide a local operation interface; A storage medium interface, connected to the main controller, is used to access a removable storage medium storing firmware data; A communication interface component, which communicates with the main controller, is used to connect to the camera; The main controller is used to write firmware data from the storage medium interface to the connected camera through the communication interface component.

2. The camera firmware offline upgrade device according to claim 1, characterized in that, The communication interface component includes at least two serial deserializer chips, which are connected to the main controller via a control bus and each supports different vehicle serial communication protocols.

3. The camera firmware offline upgrade device according to claim 2, characterized in that, The different in-vehicle serial communication protocols include the GMSL protocol and the FPD-LINK protocol.

4. The camera firmware offline upgrade device according to claim 2, characterized in that, The control bus is the IIC bus.

5. The camera firmware offline upgrade device according to claim 1, characterized in that, The main controller is also configured to: read a configuration file in a removable storage medium connected to the storage medium interface, the configuration file including communication protocol type information of the target camera; Based on the communication protocol type information, perform at least one of the following operations: The local interaction component outputs guidance information instructing the camera to be connected to the corresponding protocol port in the communication interface component; or Automatically detect and confirm whether the camera is connected to a port that matches the communication protocol type information.

6. The camera firmware offline upgrade device according to claim 1, characterized in that, The main controller is also configured to verify the written data after writing the firmware data to the camera.

7. The camera firmware offline upgrade device according to claim 6, characterized in that, The verification method is a sequential block readback and cyclic redundancy check with the source data, and the size of the firmware data block readback is a preset fixed length.

8. The camera firmware offline upgrade device according to claim 1, characterized in that, The built-in power supply components include a rechargeable battery and power management circuitry.

9. The camera firmware offline upgrade device according to claim 1, characterized in that, The local interactive component includes a display unit and an input unit; The local interaction component is configured to display the device's battery level, connection status with the camera, list of upgradable firmware, or firmware upgrade progress in real time.

10. A method for upgrading firmware of a portable camera, characterized in that, The method of performing a firmware upgrade using the camera firmware offline upgrade device according to any one of claims 1-9 includes the following steps: Connect a removable storage medium containing firmware data to the storage medium interface of the device. A communication interface component that connects the camera to the device; Initiate the upgrade operation through the device's local interaction component; In response to the upgrade operation, the main controller of the device writes firmware data from the storage medium interface to the connected camera via the communication interface component.

Images