Automobile PMIC chip burner, burner system and burning method
The integrated automotive PMIC chip programmer solves the problems of complex equipment, high cost, poor versatility and low efficiency in existing technologies, and achieves efficient and reliable PMIC programming. It is suitable for automotive electronics production and field repair and meets automotive-grade quality standards.
Patent Information
- Application Number
- CN202511480677.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-16
- Publication Date
- 2026-01-09
AI Technical Summary
Existing PMIC programming technology suffers from problems such as high equipment costs, system complexity, poor versatility, low programming efficiency, insufficient reliability, and low level of production line automation, making it difficult to meet the stringent requirements of 'zero defects' in the automotive electronics field.
An automotive PMIC chip programmer was designed, employing a highly integrated control architecture. The main control unit coordinates the programming process, and combined with an interface conversion module, power management module, status indication module, and target connection interface, it achieves compatibility and automated programming for various chip models. It supports dual power input, monitors voltage and communication status in real time, and performs step-by-step data verification and functional testing.
It significantly reduces equipment complexity and cost, improves equipment versatility and production line automation, ensures the reliability and efficiency of programming, is suitable for automotive electronics production and on-site repair scenarios, and meets the stringent requirements of automotive-grade standards.
Smart Images

Figure CN121301254A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of automotive electronics manufacturing / chip programming technology, specifically relating to an automotive PMIC chip programmer, a programmer system, and a programming method. Background Technology
[0002] In the automotive electronics manufacturing industry, the programming of power management integrated circuits (PMICs) is a critical production step, as their reliability directly affects the safety and stability of the entire vehicle system. As the core power management module of an automotive electronic system, the PMIC needs to be programmed during production and maintenance to configure its operating parameters, voltage curves, and protection thresholds, ensuring perfect compatibility with different hardware platforms. Currently, the industry commonly uses programming solutions based on dedicated debugging interfaces (such as JTAG and SWD) or a secondary development model that indirectly programs the PMIC through the main control MCU. While these solutions meet basic programming requirements to some extent, they are designed for general electronics manufacturing scenarios, employing a "universal adapter" design philosophy, emphasizing protocol compatibility and flexibility, and supporting the programming of multiple chip types through complex protocol management modules. As automotive electronics develops towards intelligence and high integration, the functional complexity of automotive PMICs continues to increase, placing higher demands on the reliability, safety, and efficiency of the programming process. Existing general solutions are no longer sufficient to meet the stringent "zero-defect" quality standards of the automotive electronics field.
[0003] Existing PMIC programming technology suffers from the following prominent problems and limitations: First, in terms of equipment architecture, traditional programmers rely on expensive dedicated debugging tools or complex external circuits, resulting in high equipment costs and complex maintenance. Furthermore, different PMIC models require different programming tools, leading to poor system versatility and significant inconvenience for equipment management and use. Second, regarding the programming process, existing solutions mostly adopt a step-by-step collaborative mode, requiring the main control chip as an intermediate carrier for data transfer. This not only increases process complexity but also introduces additional uncertainties, making it difficult to guarantee the consistency and stability of the programming process. Simultaneously, programming efficiency is low, and automation support is lacking, failing to meet the high-efficiency production demands of modern production lines. Third, in terms of reliability assurance, existing solutions primarily focus on data verification and protocol compatibility, lacking comprehensive protection mechanisms for the complex operating environment of automotive electronics. In particular, they lack precise power management and comprehensive functional verification, resulting in insufficient power quality monitoring and a lack of real-time voltage detection and fault protection mechanisms. Under the power fluctuations common in automotive electronics, this can easily lead to programming failures or even chip damage. Finally, in terms of application adaptability, the existing solution relies heavily on PC online working mode and does not support offline programming function. It is neither suitable for the needs of automotive electronics production lines for efficient and automated production, nor can it meet the requirements for rapid deployment in on-site maintenance and after-sales environments, thus limiting its application scope and usage flexibility.
[0004] In view of this, the present invention is hereby proposed. Summary of the Invention
[0005] One objective of this invention is to address the problems of high system complexity and cost, low programming efficiency, insufficient reliability, lack of security, and low degree of production line automation in existing chip programming technologies, while also meeting the stringent requirements of "zero defects" for automotive-grade applications.
[0006] To achieve the above objectives, the present invention provides an automotive PMIC chip programmer, comprising:
[0007] The main control unit is used to control the burning process;
[0008] An interface conversion module, connected to the main control unit, is used to convert the programming protocol output by the main control unit into a standard communication protocol supported by the PMIC chip.
[0009] The power management module is used to provide a stable operating voltage for the PMIC chip to be programmed and the programmer itself. The power management module supports dual power input modes of external power input and USB power supply.
[0010] The target connection interface is used for physical connection to the PMIC chip to be programmed.
[0011] The status indicator module is used to display the burning status and error messages.
[0012] Furthermore, the power management module includes: an external power input circuit for receiving a wide voltage input of 5V~28V and providing a standard operating voltage to the PMIC under test through a DC-DC step-down circuit; a USB power supply circuit for receiving 5V voltage, powering the programmer itself and temporarily powering the low-power PMIC chip; the main control unit is configured to perform power-on timing control: start after a preset time delay to avoid power fluctuations; after startup, detect whether the VDD pin voltage of the target PMIC is stable within a first preset threshold range; if the voltage is abnormal, an alarm is triggered through the status indication module and the programming process is paused.
[0013] Furthermore, the main control unit is configured to perform a port and communication protocol detection process: it determines whether the PMIC has been correctly inserted into the programming socket through a dedicated detection pin. If it is not inserted or has poor contact, the status indicator module will indicate a connection error. If the connection is normal, it will sequentially enable the I²C, SPI, and UART interfaces to send standard probe commands to the target PMIC and listen for response data and timing. If a response with a valid data format is received within a preset response time, the protocol is considered to be successfully matched. If there is no response from any protocol, it will enter a deep diagnostic mode: reduce the communication rate and retry multiple times. If it still fails, it will indicate that the chip is not responding or is damaged.
[0014] Furthermore, the main control unit is configured to perform the original data erasure process: before erasure, it reads the PMIC internal status register to confirm whether the erasure operation is supported and queries the write protection bit status. If write protection is enabled, it attempts to remove it through a specific command sequence; it performs area erasure, supporting sector erasure, whole-area erasure, and erasure mode that retains key parameters; among them, the mode that retains key parameters skips the calibration data area to prevent the loss of factory calibration values; after erasure is completed, it sends a read command to verify whether the target address data is completely empty. If it is not completed, it retryes, and if the retry fails, it reports an error.
[0015] Furthermore, the main control unit is configured to perform the data writing and verification process: when writing data, it is written page by page, and the writing rate is adjustable; during the writing process, the ACK signal or BUSY signal is monitored in real time; the post-write verification includes: the first layer of byte-by-byte readback comparison verification and the second layer of CRC32 global verification; after the burning is completed, the main control unit calculates the CRC value of the actual written data and compares it with the original CRC value. If they do not match, an error is reported.
[0016] Furthermore, the main control unit is configured to perform functional tests after programming is completed, including: basic function test: using the programmer's built-in ADC to detect the actual output voltage of the PMIC and determine whether it is within the second preset threshold range; timing response test: sending control commands and measuring their turn-on delay time, comparing it with the target response time, and if the deviation is greater than the preset deviation value, it is considered abnormal; communication stability test: reading the device ID multiple times consecutively and counting the number of failures.
[0017] Furthermore, the automotive PMIC chip programmer also includes: a firmware storage unit for storing default configuration files or programming scripts to enable offline programming; and a communication interface for connecting to a host computer or mobile terminal.
[0018] Furthermore, the programming process includes power supply and initialization, port and communication protocol detection, original data erasure processing, programming data writing and verification, and functional testing after programming is completed.
[0019] In other embodiments, an automotive programmer system is provided, including a host computer or a mobile terminal and an automotive PMIC chip programmer as described above, which is communicatively connected to the host computer or the mobile terminal.
[0020] In some embodiments, a method for programming an automotive PMIC chip programmer is provided, which can be applied to the automotive programmer system described above. The method includes: a pre-programming preparation step: powering the PMIC chip and programmer through a power management module, and the main control unit performing power-on timing control and initialization; a port and communication protocol detection step: detecting physical connections and automatically probing and matching the communication protocol with the PMIC chip; an existing data erasure processing step: after confirming the erasure conditions, performing a region-by-region erasure operation and verifying the erasure results; a programming data writing and verification step: writing data to the PMIC chip page by page, and performing byte-by-byte readback and CRC global verification; and a post-programming functional testing step: testing and verifying the basic functions, timing response, and communication stability of the programmed PMIC chip.
[0021] Based on the foregoing description, those skilled in the art will understand that this invention, by constructing a highly integrated direct control architecture, allows the main control unit to directly coordinate and control the entire programming process, eliminating intermediate conversion steps and reducing system complexity and equipment costs. An interface conversion module converts the main control unit's general instructions into communication protocols supported by the PMIC chip, ensuring compatibility with various chip models. The power management module employs a dual-power input design, providing power to both the programmer itself and the PMIC to be programmed with a stable and adjustable operating voltage. The target connection interface ensures reliable physical and electrical connection with the PMIC chip. The status indication module provides real-time feedback on programming status and error information, enhancing the human-machine interface experience. By integrating power management, protocol conversion, process control, and status indication into one system, this invention solves the problems of complex equipment, high cost, and poor versatility in traditional programming solutions. It significantly improves equipment versatility and production line automation, offering a low-cost, highly compatible, and efficient programming system suitable for field deployment, while also meeting the stringent automotive-grade "zero-defect" requirements. Attached Figure Description
[0022] The accompanying drawings, as part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments and descriptions of the invention are used to explain the invention, but do not constitute an undue limitation of the invention. Obviously, the drawings described below are merely some embodiments, and those skilled in the art can obtain other drawings based on these drawings without creative effort. In the drawings:
[0023] Figure 1 This is a schematic diagram of the structure of an automotive PMIC chip programmer in some embodiments of the present invention. Explanation of reference numerals in the attached figures
[0024] 100. Programmer; 1. Main control unit; 2. Interface conversion module; 3. Power management module; 4. Target connection interface; 5. Status indicator module; 6. Firmware storage unit; 7. Communication interface. Detailed Implementation
[0025] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments will be clearly and completely described below with reference to the accompanying drawings. The following embodiments are used to illustrate the present invention, but are not intended to limit the scope of the present invention.
[0026] Those skilled in the art should understand that the embodiments described below are merely a part of the embodiments of the present invention, and not all of the embodiments of the present invention. These partial embodiments are intended to explain the technical principles of the present invention and are not intended to limit the scope of protection of the present invention. Based on the embodiments provided by the present invention, all other embodiments obtained by those skilled in the art without creative effort should still fall within the scope of protection of the present invention.
[0027] The following reference Figure 1 This document will provide a detailed description of the automotive PMIC chip programmer, programmer system, and programming method in some embodiments of the present invention. Figure 1 This is a schematic diagram of the structure of an automotive PMIC chip programmer in some embodiments of the present invention.
[0028] The core of the automotive PMIC chip programmer 100 of this invention lies in its highly integrated and automated design, enabling efficient and reliable programming of automotive power management chips. Specifically, the programmer 100 uses a microcontroller as the main control unit 1, responsible for coordinating and controlling the entire programming process. An interface conversion module 2 converts the general instructions of the main controller into specific standard communication protocols (such as I²C, SPI, UART) supported by the PMIC chip, thus ensuring compatibility with various chip models. The power management module 3 adopts a dual power input design (external wide-voltage power supply and USB), providing power to both the programmer 100 itself and the PMIC to be programmed with a stable and adjustable operating voltage. The target connection interface 4 ensures reliable physical and electrical connection with the PMIC chip. The status indication module 5 provides real-time feedback on programming status and error information, enhancing the human-machine interface experience. Through modular design, power management, protocol conversion, process control, and status indication are integrated into one unit, solving the problems of complex equipment, high cost, and poor versatility in traditional programming solutions, achieving efficient and flexible PMIC programming in automotive electronics production and repair scenarios.
[0029] like Figure 1As shown, in some embodiments of the present invention, an automotive PMIC chip programmer 100 is provided, including a main control unit 1, an interface conversion module 2, a power management module 3, a target connection interface 4, a status indicator module 5, a firmware storage unit 6, and a communication interface 7. The main control unit 1 controls the programming process. The interface conversion module 2 is connected to the main control unit 1 and converts the programming protocol output by the main control unit 1 into a standard communication protocol supported by the PMIC chip. The power management module 3 provides a stable operating voltage for the PMIC chip to be programmed and the programmer 100 itself; the power management module 3 supports dual power input modes: external power input and USB power supply. The target connection interface 4 physically connects to the PMIC chip to be programmed. The status indicator module 5 displays the programming status and error messages. The firmware storage unit 6 stores default configuration files or programming scripts for offline programming. The communication interface 7 connects to a host computer or mobile terminal.
[0030] The main control unit 1 (MCU) is responsible for precisely and automatically executing the programming algorithm, thereby completing the mission of implanting code into the target chip. In other words, the main control unit 1 controls the programming process. The main control unit 1 uses a microcontroller, which can decompose a complex programming task into multiple precise and controllable steps. It abstracts and encapsulates the underlying complexity of programming different target chips, allowing the PC software to focus only on upper-level logic (such as file selection and interface interaction) without needing to generate specific hardware signals for each chip. This effectively improves the versatility, reliability, and automation of the programmer 100.
[0031] The programming process includes power supply and initialization, port and communication protocol detection, original data erasure, programming data writing and verification, and functional testing after programming is completed.
[0032] The power-up and initialization process includes physical connection, power supply setup, signal initialization, and self-test of the main control unit 1. Physical connection: The programmer 100's socket, fixture, or probes are correctly connected to the corresponding pins of the target chip (or PCB board). Power supply setup: The programmer 100 accurately outputs the required power supply voltage (VCC / VDD) and programming voltage (VPP, if needed) according to the target chip's specifications (e.g., 1.8V, 2.5V, 3.3V, 5.0V); the main control unit 1 strictly controls the power-on sequence and voltage rise rate to avoid chip damage due to power-on surges. Signal initialization: All communication and control signal lines (e.g., RST, CLK, DATA, etc.) are placed in a known, idle initial state. Main control unit 1 self-test: The programmer 100 performs a rapid self-test to confirm that its hardware modules (e.g., power supply, interface conversion circuits) are functioning correctly. Through power supply and initialization processing, a basic working environment and stable communication are established for the programmer 100. At the same time, precise voltage control and power-on timing can avoid latch-up or other hardware damage caused by abnormal power supply, effectively preventing chip damage.
[0033] Port & Protocol Detection processing includes connection attempt, identifier reading, verification and confirmation, and protocol parameter adjustment. Connection attempt: The main control unit 1 of the programmer 100 begins sending "connect" or "identify" commands to the target chip according to several preset possible protocols (or specified by the host computer). For example, for an ARM chip, it will attempt to send a connection sequence specific to the SWD protocol. Identifier reading: Requesting the target chip to return its unique identifier (such as JTAG IDCODE), device ID, or part number. Verification and confirmation: Comparing the read ID with the chip model selected in the programming software. Protocol parameter adjustment: Fine-tuning parameters such as communication rate (baud rate, clock frequency) according to chip requirements to optimize communication quality. By detecting and processing the port and communication protocol, it can be ensured that the firmware to be burned is 100% compatible with the currently connected physical chip, thus avoiding major accidents such as burning the wrong chip from the source and playing a role in identity verification and error prevention. At the same time, it can automatically adapt, that is, automatically identify and adapt the correct communication protocol and parameters, reducing the technical requirements for operators and improving the degree of automation. Furthermore, it establishes reliable communication, that is, confirms that the "dialogue" channel between the main controller and the target chip is smooth and stable, preparing for subsequent large data transmission.
[0034] The existing data erasure process includes sending an erase command, waiting for the erasure to complete, and verifying a blank state. Sending the erase command: The programmer 100 sends an erase instruction to the target chip. Depending on the chip type, the erasure method varies, typically including: Chip Erase, Sector Erase, and Page Erase. Chip Erase: Erases the entire memory array (usually to 0xFF or 0x00). Sector Erase / Page Erase: Erases only the area where new data needs to be written, offering higher efficiency. Waiting for Erasure to Complete: The erasure operation takes a certain amount of time (ranging from milliseconds to seconds). The programmer 100 waits for the chip to return an "erasure complete" signal or performs a timeout check. Verifying a Blank State: The erased area is read to confirm that all memory cells are in a "blank" state (e.g., all 0xFF). Erasing existing data in most non-volatile memory (such as Flash) prepares the memory for writing new data. It also ensures security by completely erasing the original firmware, preventing the leakage of sensitive code or data and meeting security audit requirements. Furthermore, it also ensures writing quality by writing to blank media, which ensures the correctness and consistency of data and avoids errors caused by mixing old and new data.
[0035] The programming and verification process includes data writing (programming), on-the-spot verification (or final verification), and optional checksum verification. Data writing (programming): The programmer 100 reads the original firmware file (e.g., bin, hex file) from the cache, divides the data into small blocks (e.g., by page, by sector), and writes them to the target chip's memory cells in batches according to the chip's programming timing. After each block is written, it may wait for the chip to return a "programming complete" response. On-the-spot verification (or final verification): The newly written data is read back and compared byte by byte with the data in the original cache. If any byte does not match, an error is immediately marked, and the operation can be retried. Optional checksum verification: Some processes also calculate the checksum (e.g., CRC32) of the entire memory area and compare it with the ideal value as a secondary guarantee. The core steps of the programming function can be achieved through data writing and verification, which means that the goal of implanting program code into the chip is completed. At the same time, verification is used to verify that no bit flips, address misalignments or other unexpected errors have occurred during data transmission and programming, ensuring 100% correct programming. Furthermore, real-time error correction is possible, which can immediately detect errors and handle them in a timely manner on the production site (such as retrying or marking them as faults), preventing defective products from flowing into subsequent stages.
[0036] Post-Programming Functional Test (PPT) after programming includes resetting / starting the chip, applying stimuli, measuring the response, and judging the result. Resetting / starting the chip: The programmer 100 releases control over the chip (e.g., de-resets), allowing the chip to begin executing the newly programmed program. Applying stimuli: The programmer 100 (or its accompanying test fixture) sends pre-designed test signals to the chip or its PCB board via I / O ports, serial ports, ADC / DACs, etc. Examples include simulating an input signal, sending a test command, or changing a voltage value. Measuring the response: The response output of the chip or PCB is measured and captured. Examples include reading the level of an I / O port, receiving data from a serial port, or measuring a voltage value. Judging the result: The measured response is compared with the expected correct value to determine whether the test passes (PASS / FAIL). The functional testing process after programming not only verifies that the data has been written correctly, but also further verifies that the written program can run normally on the chip and achieve the expected function, thus achieving the final quality verification. At the same time, this step can also discover potential problems, namely some deeper problems, such as firmware version errors (the file is correct but the function is not correct), hidden damage to the chip itself, and faults in the peripheral circuits on the PCB board (such as soldering problems), which greatly reduces the cost and rework rate of subsequent testing stages.
[0037] Since PMICs typically lack standard debugging and programming interfaces such as JTAG / SWD, their configuration relies on a general-purpose communication bus. Therefore, an interface conversion module 2 is needed to perform protocol translation and electrical adaptation. Interface conversion module 2 acts as a "translator" and "bridge" between the main control unit 1 and the PMIC chip. Protocol translation converts high-level programming commands issued by the main control unit 1 (e.g., "write XX data to address YY") into waveforms and timing sequences of standard hardware-level communication protocols that the PMIC can recognize and execute. Electrical adaptation ensures that the logic level of the main control unit 1 (e.g., 3.3V) matches the logic level required by the PMIC (which may be 1.8V, 2.5V, etc.), providing necessary level conversion and drive capabilities to guarantee the stability and reliability of signal transmission.
[0038] Interface conversion module 2 is connected to main control unit 1. Interface conversion module 2 is used to convert the programming protocol output by main control unit 1 into the standard communication protocol supported by PMIC chip. The standard communication protocol includes, but is not limited to, I²C, SPI and UART, to be compatible with various chip models.
[0039] Interface conversion module 2 is configured such that power management module 3 supplies power to it. Interface conversion module 2 then begins self-testing and initialization to ensure it is in a stable and ready operating state. Master control unit 1 is configured to send initialization commands or advanced instructions to interface conversion module 2 via its interface (such as UART or SPI). Initialization commands include, but are not limited to, target protocol selection, protocol speed, and slave address. Specifically, for example, setting the target protocol to I²C, the I²C speed to 400kHz, and the output level to 1.8V. This configures the operating mode of interface conversion module 2, preparing it for accurate protocol conversion in subsequent programming commands. Then, master control unit 1 decomposes the programming process into discrete advanced instructions and sends them to interface conversion module 2 via its hardware interface (such as UART). Upon receiving the commands, interface conversion module 2 first parses the commands and then assembles protocol frames to complete the translation from application layer commands to link layer protocol data units. Hardware timing signals are then generated to control each high and low level change of the SCL clock line, ensuring data stability when SCL is high, thus producing electrical signals that the automotive PMIC physical interface can correctly recognize and respond to. The level conversion circuit (such as a level shifter) inside interface conversion module 2 converts the generated 3.3V logic signal into a 1.8V (or other voltage) signal required by the PMIC and enhances its driving capability to ensure reliable signal recognition by the PMIC, avoiding communication failures or device damage due to voltage mismatch. Finally, the reverse operation of the read process completes the closed loop of bidirectional data communication, enabling the main control unit 1 to verify the correctness of the write operation. Interface conversion module 2 is also configured to perform status feedback and error handling. After completing each command, interface conversion module 2 sends a status code to the main control unit 1, allowing the main control unit 1 to understand the success or failure of each underlying operation. If the interface module returns an error, the main control unit 1 can decide how many times to retry, abort the process, and report the error according to a preset strategy, thereby improving the robustness and reliability of the entire programming system.
[0040] The power management module 3 is used to provide a stable operating voltage for the PMIC chip to be programmed and the programmer 100 itself. The power management module 3 adopts a dual-channel independent power supply design, that is, the power management module 3 supports dual power input modes of external power input and USB power supply. Specifically, the power management module 3 includes an external power input circuit and a USB power supply circuit.
[0041] The external power input circuit receives a wide voltage input of 5V to 28V and provides a standard operating voltage to the PMIC under test via a DC-DC buck converter. The power management module 3 is configured to accept a wide-range DC voltage (5V-28V), which is then fed into a DC-DC buck converter. This converter, through feedback control, efficiently and accurately converts and stabilizes the fluctuating input voltage at a standard operating voltage (e.g., 3.3V, 1.8V, 5.0V, etc., depending on the PMIC under test), ensuring stable output even under high input voltage fluctuations.
[0042] The USB power supply circuit primarily powers the logic circuitry of the programmer 100 itself and can temporarily provide 5V power to the low-power PMIC. Specifically, the USB power supply circuit receives 5V voltage from a standard USB interface (such as Type-A or Type-C), and then divides the 5V power supply into two main paths. One path directly or through an LDO (low dropout linear regulator) powers the programmer 100's main control unit 1, logic circuitry, status indicator lights, etc.; the other path can provide temporary power to the low-power PMIC chip when needed through a switching circuit.
[0043] The target connection interface 4 is used for the physical connection of the PMIC chip to be programmed. The target connection interface 4 includes a programming socket, a probe bed / test clip, and a flexible circuit board (FPC) connector. The programming socket is used to program individual PMIC chips; the chip is precisely placed inside the socket, and internal probes contact each pin. The probe bed / test clip is used to program PMIC chips already soldered onto a PCB board, using a row of precision spring probes or dedicated clips to align and contact the PMIC pads on the PCB board. The flexible circuit board (FPC) connector is used to connect modules or PCBs of specific shapes. The operator physically mates the PMIC chip (or the PCB board with the PMIC soldered on) with the target connection interface 4 in the correct orientation and position. Preferably, the target connection interface 4 has a foolproof structure (such as a keyhole or positioning post) to prevent reverse insertion or incorrect insertion. Once the electrical signal path is successfully connected, the metal contacts inside the interface reliably connect to each relevant pin of the PMIC chip. Typically, the pins include power supply pins (e.g., VCC, VDD, GND), communication pins (e.g., SDA, SCL for I²C; SCLK, MOSI, MISO for SPI), and control pins (e.g., RESET, BOOT, POWER_EN). Power supply pins are used for power supply, communication pins for data transmission, and control pins for controlling the PMIC's state. This provides a stable and reliable physical connection, ensuring that all electrical signals (power, data, and control) can be transmitted without loss between the programmer 100 and the PMIC.
[0044] The status indicator module 5 is used to display the programming status and error messages. The status indicator module 5 is configured as an LED indicator, which conveys status information through color, brightness, and flashing mode. The main control unit 1 drives one or more LED indicators to present different visual modes based on the real-time status of the programming process. This invention uses a three-color LED (red / green / blue or red / green / yellow) as an example. Specifically: During the standby / ready stage of the programming process, the green LED is constantly lit. If the programmer 100 passes its power-on self-test and does not detect a chip or is waiting for a start command, the main control unit 1 is configured to control the GPIO output of the green LED to be high, keeping it constantly lit. During the detection / operation stage of the programming process, the blue or yellow LED flashes. If the programmer 100 has detected a chip and is performing a critical operation (such as communication protocol detection, erasure, programming, or verification), the main control unit 1 is configured to start a timer interrupt to switch the LED's on / off state at a fixed frequency (such as 1Hz or 5Hz), producing a flashing effect. During the programming process, if programming is successful, the green LED will flash several times and then remain constantly lit. If all programming and verification steps are successfully completed, the main control unit 1 is configured to control the green LED to flash rapidly 3-5 times (providing a strong "success" indication), and then return to a constant light, indicating that the system is ready and the chip can be removed. If an error occurs during the programming process, the red LED will flash in a specific pattern. If an error occurs at any stage of the process, such as a power failure, communication failure, verification error, or chip ID mismatch, the main control unit 1 will immediately pause the process and drive the red LED to flash in different coded patterns according to the error type. Different coded flashing patterns include: continuous fast flashing indicating a communication connection failure; two slow flashes followed by a pause indicating a verification error; and one fast flash followed by a pause indicating a power supply voltage abnormality. This intuitive physical and visual feedback mechanism ensures that the entire programming process is smooth, transparent, and easy to maintain.
[0045] Firmware storage unit 6 is used to store default configuration files or burning scripts, enabling offline burning. This allows the programmer 100 to complete burning tasks independently without relying on a real-time connected PC, making it particularly suitable for production line or field environments. The entire offline burning process can be divided into two stages: deployment and execution. After connecting to the host computer, the deployment stage begins, which includes file transfer and storage, and task configuration. File transfer and storage: The user selects the PMIC configuration files or compiled burning scripts to be batch-burned in the host computer software; the host computer software sends these files to the programmer 100 via communication interface 7 (such as USB or Type-C); the main control unit 1 of the programmer 100 receives these files and writes them into firmware storage unit 6 (such as an external SPI Flash or eMMC chip). Files are usually named or indexed for management. Task configuration: The user can set offline burning parameters through the host computer software, such as selecting the default configuration file to be used, setting the burning count counter, and naming the task set. This configuration information is also stored in firmware storage unit 6. After disconnecting from the host computer, the process enters the execution phase, which includes starting offline mode, reading and parsing, executing the programming, and recording the results. Starting offline mode: The programmer 100 is moved to the production line, allowing it to operate independently of the PC (either directly or via USB). The operator initiates the programming process via a button or sensor switch. Reading and parsing: The main control unit 1 reads the pre-stored configuration file or programming script from the firmware storage unit 6. It parses these files, converting them into a series of low-level commands ready for execution (e.g., writing data 0x8F to address 0x20 via I²C). Executing programming: The main control unit 1 begins executing the parsed command flow: connecting to the PMIC, erasing, writing data, verification, etc. This process is identical to online programming, but the commands originate from local storage instead of real-time PC input. Recording results: After programming is complete, the main control unit 1 writes the programming results (success / failure, error code, chip ID, programming time, etc.) to a specific area of the firmware storage unit 6 (e.g., a log file) and updates the task counter. By storing and executing configuration files locally through firmware storage unit 6, the automation level and production efficiency of the production line are greatly improved, the quality differences caused by external interference are completely eliminated, and the consistency and reliability of the burned content are absolutely guaranteed.
[0046] Communication interface 7 serves as the channel for the programmer 100 to exchange data and interact with the outside world. It connects to a host computer or mobile terminal, supports updating programming scripts, downloading programming data, and uploading programming process logs, facilitating remote monitoring and management and expanding the application modes of the programmer 100. Specifically, the steps for data exchange and command interaction via communication interface 7 include connection establishment, enumeration and identification, data transmission, and connection maintenance and disconnection. Specifically, connection establishment: The user connects the programmer 100 to the host computer (PC) or mobile terminal (phone / tablet) using a data cable (such as a USB cable) or wirelessly (such as Wi-Fi or Bluetooth). The main control unit 1 of the programmer 100 detects the connection event, initializes the communication protocol stack, and establishes a session with the software on the terminal. Enumeration and identification: The programmer 100 "introduces" itself to the connected terminal (USB enumeration process), informing the other party of its device type, supported communication protocols, etc. The host computer software identifies and loads the corresponding driver accordingly, enabling correct communication with the programmer 100. Data transmission (downlink: terminal -> programmer 100) includes sending programming files, sending control commands, and sending configuration parameters. Sending programming files: The user sends the configuration file / script from the host computer software to the programmer 100's storage unit. Sending control commands: When the user clicks buttons such as "Start Programming," "Stop," or "Read Chip ID," these commands are encapsulated into data packets and sent to the programmer 100's main control unit 1 for execution via communication interface 7. Sending configuration parameters: The user sets parameters such as voltage and timing and sends them to the programmer 100 via the interface. Data transmission (uplink: programmer 100 -> terminal) includes uploading status information, uploading data and logs, and responding to requests. Uploading status information: The programmer 100 returns real-time status ("Connecting," "Programming," "Verifying") to the host computer software for displaying progress bars and status prompts on the UI interface. Uploading data and logs: The programmer 100 sends the read internal chip data, programming results, error logs, and other data back to the host computer software for display, recording, and analysis. Request Response: When the host computer software requests to read the file list or logs stored internally by the programmer 100, the programmer 100 will package this data and upload it. Connection Maintenance and Disconnection: During long-term connections, both parties will maintain the validity of the connection through mechanisms such as heartbeat packets. After all operations are completed, the user can safely eject the device in the software and then physically disconnect the connection.
[0047] The main control unit 1 is configured to perform power-on timing control: start after a preset time delay to avoid power fluctuations; after startup, it checks whether the VDD pin voltage of the target PMIC is stable within a first preset threshold range; if the voltage is abnormal, it alarms through the status indication module 5 and suspends the programming process, effectively preventing programming failure or chip damage caused by power abnormalities. The preset time period can be set to 100ms, and the first preset threshold range can be set to a theoretical voltage fluctuation of 5%, i.e., within the allowable range (±5%).
[0048] The main control unit 1 is also configured to perform port and communication protocol detection: It uses a dedicated detection pin (ID_PIN) to determine if the PMIC is correctly inserted into the programming socket. If not inserted or making poor contact, the status indicator module 5 indicates a connection error, preventing subsequent operation failures due to poor contact. If the connection is normal, it sequentially uses the I²C, SPI, and UART interfaces to send standard probe commands (such as reading the device ID) to the target PMIC and listens for response data and timing. If a valid response with a valid data format is received within a preset response time, the protocol is considered to be successfully matched. If all protocols fail to respond, it enters deep diagnostic mode: reducing the communication rate and retrying multiple times to eliminate temporary communication failures caused by signal integrity or timing deviations, thereby accurately distinguishing between chip damage and communication configuration problems. If multiple retries still fail, it indicates that the chip is unresponsive or damaged.
[0049] The main control unit 1 is also configured to perform the original data erasure process, including: Step 1, since the write protection bit is a flag that controls whether a storage area can be modified, if it is set, it must first be deactivated through a specific command sequence. That is, before erasing, the PMIC internal status register is read to confirm whether the erase operation is supported and to query the write protection bit status. If write protection is enabled, it attempts to deactivate it through a specific command sequence. The write protection bit status refers to the current setting of a switch or flag used to control whether the storage medium or memory area is allowed to be modified (written). The write protection bit status includes two states: State 1, Enabled / Set; State 2, Disabled / Cleared. Enabled / Set indicates that write protection is enabled. At this time, data can only be read and cannot be modified, deleted, or formatted. Disabled / Cleared indicates that write protection is disabled. At this time, data can be read, modified, deleted, or formatted normally. Step two: The erase operation supports three modes: sector erase, full-chip erase, and retaining critical parameters. Sector erase targets the configuration area, full-chip erase is suitable for brand-new chips, and the retaining critical parameters mode skips the area storing factory calibration values to prevent chip performance degradation due to lost calibration data. Specifically, it performs area-by-area erase, supporting sector erase, full-chip erase, and retaining critical parameters erase modes; the retaining critical parameters mode skips the calibration data area to prevent loss of factory calibration values. Step three: After erasure, a read command is sent to verify whether the target address data is completely empty. If not, a retry is performed; if the retry fails, an error is reported, ensuring the thoroughness of the erase operation.
[0050] The main control unit 1 is also configured to execute the data writing and verification process: during data writing, data is written page by page, and the writing rate is adjustable to adapt to different chip performance. During the writing process, the ACK or BUSY signal is monitored in real time to ensure that each operation is correctly responded to by the chip. Post-write verification includes two layers: byte-by-byte readback comparison and CRC32 global verification. Specifically, the first layer, byte-by-byte readback comparison verification, directly verifies whether the data in each storage unit is consistent. The second layer, CRC32 global verification, after the programming is completed, the main control unit 1 calculates the CRC value of the actual written data and compares it with the original CRC value; if they do not match, an error is reported. This dual verification mechanism greatly reduces the probability of missed error detection; if either verification fails, an error is reported, ensuring the high reliability of the programmed data.
[0051] The main control unit 1 is also configured to perform functional tests after programming, including: basic function tests, timing response tests, and communication stability tests. The basic function test uses the programmer 100's built-in ADC to detect the actual output voltage of the PMIC and determines if it falls within a second preset threshold range, thus verifying its analog performance. The second preset threshold range is the theoretical output voltage ±2%. The timing response test sends control commands and measures their on-time delay, comparing it to the target response time. A deviation greater than a preset deviation value is considered abnormal, ensuring the chip's dynamic response performance meets requirements. The target response time is obtained from the chip datasheet, which is the chip's "instruction manual" and the sole authoritative standard for writing test programs, setting test parameters, and judging product quality. The preset deviation value can be set to 10%. The communication stability test reads the device ID multiple times consecutively and counts the number of failures to assess the long-term reliability of the interface connection.
[0052] In other embodiments of the present invention, the main control unit 1 is further configured to perform a reset and result reporting after the programming is completed and before the functional test is performed: Resetting the target chip: After programming and verification are all successful, the main control MCU sends a "reset" command to the target chip, causing it to exit the programming mode and allowing the target chip to start executing the newly programmed firmware from the starting address of the user program area. Result reporting: The main control MCU sends a "programming successful" signal to the host computer and drives the onboard green LED indicator to light up (or the buzzer sounds once). If any step fails (such as verification failure), the process is immediately terminated, an "error code" is sent, and the red LED flashes; at the same time, the main control MCU resets the interface status and waits for the next programming task.
[0053] The core control path is as follows: Communication interface 7 → Main control unit 1 → Interface conversion module 2 → Target connection interface 4 → PMIC chip to be programmed. Programming instructions and firmware data are transmitted from the host computer via communication interface 7, and received and processed by the main control unit 1 (usually an MCU). The main control unit 1 sends high-level instructions to the interface conversion module 2, which translates them into physical signals that the PMIC can understand (such as I²C and SPI timings), and finally transmits them to the PMIC chip via the target connection interface 4.
[0054] Power supply path: Power management module 3 → entire system → PMIC chip to be programmed. Power management module 3 provides stable operating voltage for all other modules (including main control unit 1, interface conversion module 2, status indicator module 5, and firmware storage module 6). At the same time, power management module 3 also provides precise and controllable programming power (VCC / VDD, VPP) to the PMIC chip to be programmed through target connection interface 4.
[0055] Storage and configuration pathway: Firmware storage unit 6 ↔ Main control unit 1. When the main control unit 1 needs to perform an offline burning task, it will read the pre-stored configuration file, burning script and firmware data from the firmware storage unit 6. Burning logs and results may also be written back to this storage unit, which is a two-way data interaction relationship.
[0056] Status feedback path: main control unit 1 → status indicator module 5. The main control unit 1 drives the status indicator module 5 (such as LED lights) according to the status of the entire burning process (such as "burning", "success", "error") to provide real-time feedback to the operator in a visual way. This is a one-way control relationship.
[0057] In some embodiments of the present invention, an automotive programmer system is provided, including a host computer or mobile terminal and an automotive PMIC chip programmer 100 as described above, which is communicatively connected to the host computer or mobile terminal. The automotive programmer system consists of a host computer or mobile terminal and one or more programmers 100, connected via a communication interface 7. The host computer is responsible for complex task management, such as batch programming task scheduling, programming script editing and distribution, data management, and result analysis, while the programmer 100 is responsible for executing specific programming operations. This architecture combines the powerful processing capabilities of the host computer with the dedicated execution capabilities of the programmer 100, making it suitable for application scenarios requiring centralized management and large-scale programming.
[0058] In some embodiments of the present invention, a programming method for an automotive PMIC chip programmer 100 is provided, which can be applied to the automotive PMIC chip programmer 100 described above and / or the automotive programmer system described above. The method includes:
[0059] Preparation steps before programming: Power supply module 3 supplies power to PMIC chip and programmer 100, and main control unit 1 performs power-on timing control and initialization.
[0060] The system employs a dual-power input mode. The external power input is converted to the standard operating voltage required by the PMIC under test via a DC-DC step-down circuit. The USB power supply powers the programmer 100 itself. After power-on, the main control MCU starts with a 100ms delay and then checks whether the VDD pin voltage of the target PMIC is stable within the allowable range. If the voltage is abnormal, an LED alarm is triggered and the process is paused. The dual-power input mode includes: an external power input range of 5V~28V, converted to 3.3V and 1.8V standard operating voltages via a DC-DC step-down circuit, with the voltage value automatically configured by the main control MCU according to the PMIC model; and a 5V USB power supply, used for the programmer 100 itself and providing temporary power to the low-power PMIC chip.
[0061] Port and Communication Protocol Detection Steps: The physical connection is detected, and the communication protocol matching the PMIC chip is automatically identified. The communication protocol detection steps include: determining whether the PMIC is correctly inserted via a dedicated detection pin; if not inserted or with poor contact, an LED flashes to indicate a connection error; the main controller sequentially sends standard probe commands to the target PMIC via the I²C, SPI, and UART interfaces, listening to the response data and timing, requiring a response time of less than 10ms and valid data format; if all protocols fail to respond, a deep diagnostic mode is entered, reducing the communication rate and retrying the probe operation; if it still fails, a message indicates that the chip is unresponsive or damaged. The deep diagnostic mode includes reducing the I²C communication rate from 400kHz to 100kHz and retrying the probe operation three times.
[0062] The original data erasure process is as follows: After confirming the erasure conditions, perform a segmented erasure operation and verify the erasure result. The data erasure steps include: reading the PMIC internal status register to confirm whether the erasure operation is supported, querying the write protection bit status, and removing the protection through a specific command sequence when enabled; three erasure modes are supported: sector erasure erases only the configuration area, whole-area erasure is suitable for the first programming, and the key parameter retention mode skips the calibration data area; after erasure is completed, the main control unit 1 sends a read command to verify whether the target address data is completely empty. If not, it will retry a maximum of 2 times.
[0063] Data writing and verification steps: Data is written to the PMIC chip page by page, and then read back byte by byte and perform a global CRC check. The data writing and verification steps include: writing data page by page, with the size of each page determined according to the PMIC specifications; monitoring the ACK or BUSY signal in real time during the writing process; after writing, performing two levels of verification: the first level performs a byte-by-byte readback comparison, and the second level performs a global CRC32 check, where the main controller calculates the CRC value of the actually written data and compares it with the original value.
[0064] Functional testing steps after programming: The programmed PMIC chip undergoes basic functional testing, timing response testing, and communication stability testing and verification. Functional testing steps include: using the programmer's built-in ADC to detect the actual output voltage of the PMIC with a detection accuracy of ±2%, determining whether the output voltage is within the allowable range; sending control commands and measuring the start-up delay time; a deviation exceeding 10% compared to the datasheet is considered abnormal; continuously reading the device ID 100 times and counting the number of communication failures.
[0065] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.
[0066] Those skilled in the art will understand that this invention, by constructing a highly integrated direct control architecture, directly coordinates and controls the entire programming process through the main control unit 1, eliminating intermediate conversion links and reducing system complexity and equipment costs; by innovatively integrating programming verification with functional testing, comprehensive functional testing, including output voltage accuracy detection, timing response testing, and communication stability verification, is performed immediately after data writing to ensure compliance with automotive-grade "zero-defect" quality requirements; by designing an intelligent dual-power supply system and a precise power-on timing control mechanism, real-time voltage monitoring and automatic protection functions are achieved, effectively preventing programming failures or chip damage caused by power supply abnormalities; through the built-in large-capacity firmware storage unit 6 and optimized human-machine interface, multiple communication protocols and offline programming modes are supported, significantly improving equipment versatility and production line automation, resulting in a low-cost, highly compatible, and efficient programming system suitable for field deployment.
[0067] Those skilled in the art will understand that modules in the device of the embodiments can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiments can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components. Except where at least some of such features and / or processes or units are mutually exclusive, any combination can be used to combine all features disclosed in this specification (including the accompanying claims, abstract, and drawings) and all processes or units of any method or device so disclosed. Unless expressly stated otherwise, each feature disclosed in this specification (including the accompanying claims, abstract, and drawings) may be replaced by an alternative feature that serves the same, equivalent, or similar purpose.
[0068] Furthermore, those skilled in the art will understand that although some embodiments herein include certain features included in other embodiments but not others, combinations of features from different embodiments are intended to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments can be used in any combination.
[0069] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-described technical content to create equivalent embodiments without departing from the scope of the present invention. The implementation schemes in the above embodiments can be further combined or replaced. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.
Claims
1. A car PMIC chip programmer (100), characterized in that, include: The main control unit (1) is used to control the burning process; The interface conversion module (2) is connected to the main control unit (1) and is used to convert the programming protocol output by the main control unit (1) into the standard communication protocol supported by the PMIC chip. The power management module (3) is used to provide a stable operating voltage for the PMIC chip to be programmed and the programmer (100) itself. The power management module (3) supports dual power input modes of external power input and USB power supply. The target connection interface (4) is used to physically connect to the PMIC chip to be programmed; The status indicator module (5) is used to display the burning status and error message.
2. The automotive PMIC chip programmer (100) according to claim 1, characterized in that, The power supply management module (3) includes: An external power input circuit is used to receive a wide voltage input of 5V~28V and provide a standard operating voltage to the PMIC under test through a DC-DC step-down circuit. The USB power supply circuit is used to receive 5V voltage, power the programmer (100) itself and temporarily power the low-power PMIC chip. The main control unit (1) is configured to perform power-on timing control: start after a preset time delay to avoid power fluctuations; after starting, detect whether the VDD pin voltage of the target PMIC is stable within the first preset threshold range; if the voltage is abnormal, alarm and suspend the burning process through the status indicator module (5).
3. The automotive PMIC chip programmer (100) according to claim 2, characterized in that, The main control unit (1) is configured to perform port and communication protocol detection process: The dedicated detection pin determines whether the PMIC has been correctly inserted into the programming socket. If it is not inserted or has poor contact, the status indicator module (5) indicates a connection error. If the connection is normal, the I²C, SPI, and UART interfaces will be enabled in sequence to send standard probe commands to the target PMIC, and the response data and response timing will be monitored. If a response with a valid data format is received within the preset response time, the protocol is considered to have matched successfully. If all protocols fail to respond, enter deep diagnostic mode: reduce the communication rate and retry multiple times; if it still fails, indicate that the chip is unresponsive or damaged.
4. The automotive PMIC chip programmer (100) according to claim 3, characterized in that, The main control unit (1) is configured to perform the original data erasure process: Before erasing, read the PMIC internal status register to confirm whether the erase operation is supported and check the write protection bit status. If write protection is enabled, try to remove it through a specific command sequence. Performs area-by-area erasure, supporting sector erasure, full-area erasure, and erasure mode that retains key parameters; among them, the mode that retains key parameters skips the calibration data area to prevent the loss of factory calibration values. After erasure is complete, a read command is sent to verify whether the target address data is completely empty. If not, a retry is performed, and an error is reported if the retry fails.
5. The automotive PMIC chip programmer (100) according to claim 4, characterized in that, The main control unit (1) is configured to perform the data writing and verification process: Data is written page by page with an adjustable write rate; the ACK or BUSY signal is monitored in real time during the writing process. Post-write verification includes: first-level byte-by-byte readback comparison verification and second-level CRC32 global verification; After the burning is completed, the main control unit (1) calculates the CRC value of the actual written data and compares it with the original CRC value. If they do not match, an error is reported.
6. The automotive PMIC chip programmer (100) according to claim 5, characterized in that, The main control unit (1) is configured to perform functional tests after the programming is completed, including: Basic function test: Use the built-in ADC of the programmer (100) to detect the actual output voltage of the PMIC and determine whether it is within the second preset threshold range; Timing response test: Send control commands and measure their start delay time, compare it with the target response time, and if the deviation is greater than the preset deviation value, it is considered abnormal; Communication stability test: Read the device ID multiple times consecutively and count the number of failures.
7. The automotive PMIC chip programmer (100) according to claim 1, characterized in that, Also includes: Firmware storage unit (6) is used to store default configuration files or burning scripts to enable offline burning; The communication interface (7) is used to connect to a host computer or mobile terminal.
8. The automotive PMIC chip programmer (100) according to claim 1, characterized in that, The programming process includes power supply and initialization, port and communication protocol detection, original data erasure, programming data writing and verification, and functional testing after programming is completed.
9. A car programmer system, characterized in that, Includes a host computer or mobile terminal and an automotive PMIC chip programmer (100) as described in claims 1 to 8 that is communicatively connected to the host computer or mobile terminal.
10. A method for programming an automotive PMIC chip programmer (100), characterized in that, The method can be applied to the automotive programmer system described in claim 9, characterized in that it includes: Preparation steps before programming: Power supply is provided to the PMIC chip and programmer (100) through the power management module (3), and the main control unit (1) performs power-on timing control and initialization; Port and communication protocol detection steps: Detect physical connections and automatically detect and match the communication protocol with the PMIC chip; Existing data erasure process: After confirming the erasure conditions, perform area-by-area erasure operations and verify the erasure results; Data writing and verification steps: Write the data to the PMIC chip page by page, and perform byte-by-byte readback and CRC global verification; Functional testing steps after programming: Perform basic function, timing response, and communication stability tests on the programmed PMIC chip.
Citation Information
Cited By
Variable-voltage multi-interface multi-scene communication chip burning method and device
CN121614157A
A variable voltage multi-interface multi-scene communication chip burning method and device
CN121614157B
