A pluggable integrated debugging box for cockpit main unit

Abstract

This utility model relates to the field of conversion circuit technology, specifically to a pluggable integrated debugging box for cockpit main unit. This debugging box concentrates many debugging ports in the system onto a single PCIe interface. The cockpit main unit connects to the debugging box via its gold fingers, enabling flexible plugging and unplugging. It allows one interface to cover all debugging needs. Compared to traditional ADB, it also expands the native serial port, customizable debugging ports, and upgrades control, effectively solving the problems of scattered interfaces, complex operation, and limited expansion capabilities in traditional debugging methods. This significantly improves the convenience and flexibility of cockpit system debugging.

Description

Technical Field

[0001] This utility model belongs to the field of debugging box technology, specifically relating to a pluggable integrated debugging box for cockpit main unit. Background Technology

[0002] Currently, automotive electronics technology is developing rapidly, and the automotive cockpit system has become a core module integrating functions such as infotainment, human-machine interaction, and vehicle control. Its operational stability and functional integrity directly affect the vehicle's driving safety and user experience. Therefore, efficient debugging of the cockpit system is crucial in the research and development, production, and after-sales stages.

[0003] Currently, debugging of automotive cockpit systems largely relies on the ADB (Android Debug Bridge) tool. However, it is mainly suitable for basic debugging of upper-level applications and systems, and has limitations in scenarios involving deeper, lower-level drivers, hardware interactions, and complex fault localization. For such deep debugging needs, the industry typically relies on the serial port integrated by default in the SOC (System-on-a-Chip) for log tracing and command interaction.

[0004] However, traditional debugging methods have significant technical problems: First, the debugging interfaces are scattered, with ADB interfaces, SOC serial ports and other customized debugging interfaces often distributed independently, which requires frequent switching of connected devices during the debugging process, making the operation cumbersome; second, the expansion capabilities are insufficient, making it difficult to be compatible with diverse customized debugging needs and system upgrade control functions, thus limiting the improvement of debugging efficiency. Utility Model Content

[0005] To address the limitations and issues of current cockpit systems that rely on ADB tools for deep-level driver development, hardware interaction, and complex fault location, this invention consolidates numerous debugging ports within the system onto a single PCIe interface. The interface connects to the debugging box via the cockpit host's gold fingers, enabling flexible plugging and unplugging. All debugging can be performed through a single interface. Compared to traditional ADB, this invention expands upon native serial ports, customizable debugging ports, and upgrade controls, offering greater convenience and flexibility.

[0006] This utility model provides a pluggable integrated debugging box for a cockpit main unit, including a box body and functional modules disposed within the box body. The functional modules include a PCIe gold finger, a DIP switch circuit, a Type-A interface circuit, an LED indicator circuit, a Type-C interface circuit, a USB-to-UART module circuit, and an RS232-to-UART module circuit. The DIP switch circuit is connected to the PCIe gold finger, allowing manual setting of status parameters and unidirectional input of configuration signals to the PCIe gold finger. The Type-A interface circuit connects to the PCIe gold finger to achieve bidirectional communication with the PCIe interface. The USB-to-UART module has one end connected to the LED indicator circuit to drive the LED indicator to display system status, and the same side connected to the Type-C interface circuit for connecting USB-C devices. The other end connects to the PCIe gold finger to complete bidirectional conversion between USB and UART protocols. The RS232-to-UART module has two ends connected to a 5569 interface and the PCIe gold finger respectively, for completing bidirectional conversion between RS232 and UART protocols.

[0007] The aforementioned pluggable integrated debugging box for the cockpit main unit includes a DIP switch circuit comprising a 4-bit DIP switch J2, a pull-up resistor R2, and a pull-down resistor R1. The 4-bit DIP switch J2 internally comprises four independent switches, each connected to two pins. Switch 1, consisting of pins 1 and 8, controls GPIOB8_CTL. Pin 1 is connected to a 3.3V power supply via pull-up resistor R2, and pin 8 is connected to GPIOB8_CTL and connected in series with pull-down resistor R1 to ground (GND). Switch 2, consisting of pins 2 and 7, controls the GPIOB8_CTL. OB11_CTL, where pin 2 is connected to a 3.3V power supply via pull-up resistor R2, and pin 7 is connected to the signal GPIOB11_CTL; switch 3 consists of pins 3 and 6, used to configure MCU1_BOOT0, where pin 3 is connected to a 3.3V power supply via pull-up resistor R2, and pin 6 is connected to the BOOT0 pin of MCU1; switch 4 consists of pins 4 and 5, used to configure MCU2_BOOT0, where pin 4 is connected to a 3.3V power supply via pull-up resistor R2, and pin 5 is connected to the BOOT0 pin of MCU2.

[0008] The aforementioned pluggable integrated debugging box for the cockpit main unit includes a TYPE-A interface circuit comprising connector J3, capacitor C2, and capacitor C3. Connector J3 is a 6-pin USB debugging interface. Pin 1 of connector J3 is connected to USB1_DN_DBG, and pin 2 is connected to USB1_DP_DBG. Pins 1 and 2 form a data path for transmitting USB differential signals. Pins 4 and 6 of connector J3 are grounded. Pin 5 of connector J3 is connected to USB_VCC. One end of capacitors C2 and C3 is connected to the connection point between USB_VCC and pin 5 of J3, and the other end is grounded to GND. Capacitors C2 and C3 are connected in parallel between the USB_VCC power supply and ground, and share the same power node with the power supply pin of J3, for filtering the USB_VCC power supply.

[0009] The aforementioned pluggable integrated debugging box for the cockpit main unit has a USB 2.0 interface for its TYPE-A interface circuit.

[0010] The aforementioned pluggable integrated debugging box for the cockpit main unit includes a USB-to-UART module comprising a power system, a chip U2, a crystal oscillator circuit, and a reset circuit. The power system includes an input power supply VCC_3V3 and a filter capacitor module. The input power supply is a 3.3V DC power supply. The filter capacitor module includes capacitors C14, C15, C16, and C17 connected in parallel between VCC_3V3 and ground to filter out high-frequency power supply noise. The chip U2 is used to receive multiple UART serial port data and convert them to USB protocol output, while also supporting USB host commands to control the UART serial port. The crystal oscillator circuit includes crystal Y1 and capacitors C18 and C19. The two ends of crystal Y1 are connected to the TAL_IN and XTAL_OUT pins of U2, respectively. One end of capacitor C18 is connected to the connection point of Y1 and XTAL_IN, and the other end is connected to GND. One end of capacitor C19 is connected to the connection point of Y1 and XTAL_OUT, and the other end is connected to GND. The reset circuit includes resistor R34 and capacitor C20. One end of resistor R34 is connected to VCC_3V3, and the other end is connected to the RESET network of U2's reset pin. One end of capacitor C20 is connected to the RESET network of U2's reset pin, and the other end is grounded.

[0011] The aforementioned pluggable integrated debugging box for the cockpit main unit includes a TYPE-C interface circuit comprising a power input conditioning module, a diode D1, and a USB interface J6. The power input conditioning module includes an input power supply VCC_3V3, input filter capacitors C5 and C6, a voltage regulator U1, and output filter capacitors C7 and C8. The input power supply provides 3.3V as the power input for the entire interface circuit. Input filter capacitors C5 and C6 are connected in parallel between VCC_3V3 and ground. Output filter capacitors C7 and C8 are connected in parallel between pin 3 of U1 and ground. Pins 2 and 4 of the voltage regulator U1 are connected to the input power supply VCC_3V3, pin 3 is connected to VCC_3V3, and pin 1 is grounded. The power pins 1 and 2 of the USB interface J6 are connected to EXT_USB_VCC, data pins 6 and 7 are used to transmit USB signals, and pin 12 is grounded. Diode D1 is located between the power conditioning module and the USB interface J6 to prevent reverse current.

[0012] The aforementioned pluggable integrated debugging box for the cockpit main unit has a USB 2.0 interface for its TYPE-C interface circuit.

[0013] The aforementioned pluggable integrated debugging box for the cockpit main unit includes an RS232 to UART module circuit comprising a power charge pump module U3A and a signal conversion module U3B. The VCC pin of U3A is connected to DBG_3V3, and the GND pin is grounded. The C1+ and C1- pins of U3A are respectively connected to the two ends of the charge pump capacitor C9. The C2+ and C2- pins of U3A are respectively connected to the two ends of the charge pump capacitor C11. One end of C10 is connected to the V+ pin of U3A, and the other end is connected to GND. One end of C12 is connected to the V- pin of U3A, and the other end is connected to GND. The T1IN pin of U3B is connected to… Connect the MCU's DBG_TX and R1OUT12 pins to the TTL output. Connect one end of pull-up resistor R30 to DBG_3V3 and the other end to the R1OUT12 pin of U3B. Connect one end of pull-up resistor R31 to DBG_3V3 and the other end to the T1IN pin of U3B. Connect the R1IN pin to the RS232 input and the T1OUT pin to the RS232 output. Connect one end of R32 to pin 14 of U3B and the other end to the transmit signal pin of DB9 socket J7. Connect one end of R33 to the R1IN pin of U3B and the other end to the receive signal pin of DB9 socket J7.

[0014] The aforementioned pluggable integrated debugging box for the cockpit main unit includes an LED indicator circuit comprising a power supply VCC_3V3 and four LEDs: LED1A, LED1B, LED2A, and LED2B. LED1A's anode is connected to a current-limiting resistor R19, and its cathode is grounded. LED1B's anode is connected to a current-limiting resistor R20, then to VCC_3V3, and its cathode is connected to ACT / CFG / DCD3. LED2A's anode is connected to a current-limiting resistor R21, then to VCC_3V3, and its cathode is connected to TX_LED / RI3. LED2B's anode is connected to a current-limiting resistor R22, then to VCC_3V3, and its cathode is connected to RX_LED / DSR3.

[0015] The aforementioned pluggable integrated debugging box for the cockpit main unit has LED1A as a power indicator, which is constantly lit when VCC_3V3 is powered; LED1B as a Link indicator, which is constantly lit during normal configuration; LED2A as a serial port data transmission indicator, which flashes when data is being transmitted from the serial port; and LED2B as a serial port data reception indicator, which flashes when data is being received from the serial port.

[0016] Compared with the prior art, the beneficial effects of this utility model are:

[0017] This utility model provides a pluggable integrated debugging box for cockpit main unit. The debugging box concentrates many debugging ports in the system onto a single PCIe interface. It connects to the debugging box via the gold fingers of the cockpit main unit, enabling flexible plugging and unplugging. This allows a single interface to cover all debugging needs. Compared to traditional ADB, it also expands the native serial port, customizable debugging ports, and upgrade control, effectively solving the problems of scattered interfaces, complex operation, and limited expansion capabilities in traditional debugging methods. This significantly improves the convenience and flexibility of cockpit system debugging. Attached Figure Description

[0018] Figure 1 This is a circuit connection system diagram of the debugging box of this utility model;

[0019] Figure 2 This is the circuit diagram of the 4-channel DIP switch of this utility model;

[0020] Figure 3 This is the circuit diagram of the TYPE-A interface of this utility model;

[0021] Figure 4 This is the circuit diagram of the USB 2.0 to UART module of this utility model;

[0022] Figure 5 This is the circuit diagram of the TYPE-C interface of this utility model;

[0023] Figure 6 This is the circuit diagram of the LED indicator light of this utility model;

[0024] Figure 7 This is the circuit diagram of the RS232 to UART module of this utility model;

[0025] Figure 8 This is a schematic diagram of the appearance of the debugging box of this utility model.

[0026] In the diagram, 1 is a DIP switch, 2 is a TYPE-A interface, 3 is an LED indicator, 4 is a TYPE-C interface, 5 is a 5569 interface, and 6 is a PCIe gold finger interface. Detailed Implementation

[0027] To address the limitations and problems of current cockpit systems relying on ADB tools in deep-level driver, hardware interaction, and complex fault location scenarios, this invention provides a pluggable integrated debugging box for the cockpit main unit. This debugging box centralizes multiple debugging ports within the system onto a single PCIe interface, connecting to the debugging box via the cockpit main unit's gold fingers, enabling flexible plugging and unplugging and allowing a single interface to cover all debugging needs. The invention will be further described and illustrated below with reference to the accompanying drawings and specific embodiments.

[0028] Example: This example provides a pluggable integrated debugging box for cockpit main unit, such as... Figure 1 As shown, the box contains functional modules, including a PCIe gold finger, a DIP switch circuit, a TYPE-A interface circuit, an LED indicator circuit, a TYPE-C interface circuit, a USB to UART module circuit, a 5569 interface circuit, and an RS232 to UART module circuit. The PCIe gold finger is the core module of this debugging box. It serves as the physical interface between the entire system and the host. It is inserted into the host's PCIe slot and is responsible for data transmission, command interaction, and power supply. It connects with other circuits through the PCIe gold finger to realize communication between the various functional module circuits and the host.

[0029] Specifically, the DIP switch circuit is unidirectionally connected to the PCIe gold finger. Status parameters are manually set via the DIP switch, and configuration signals are transmitted unidirectionally to the PCIe gold finger. Figure 2 As shown, the DIP switch circuit is used to manually control GPIO signals and MCU startup mode. Its core component J2 (HAD-04HWAG-2) is a 4-bit DIP switch, which is connected to a manual closing / opening switching circuit to change the signal level. Internally, it contains 4 sets of independent switches, each set connected to two pins. Specifically:

[0030] Pins 1 and 8 form switch 1, which controls GPIOB8_CTL. Pin 1 is connected to a 3.3V power supply via pull-up resistor R2, ensuring that pin 1 remains high by default when the switch is open. Pin 8 is connected to GPIOB8_CTL and connected in series with pull-down resistor R1 to ground (GND), ensuring that GPIOB8_CTL remains low by default when the switch is open. In this switch, when the switch is closed, GPIOB8_CTL is pulled to 3.3V, controlling GPIOB8 to enter the enable or mode switching state; when the switch is open, GPIOB8_CTL is pulled down to 0V by pull-down resistor R1, and GPIOB8 returns to the default state.

[0031] Pins 2 and 7 form switch 2, which controls GPIOB11_CTL. Pin 2 is the same as pin 1, and is pulled up to 3.3V through pull-up resistor R2. Pin 7 is connected to the signal GPIOB11_CTL, and controls the state of GPIOB11 by switching the level.

[0032] Pins 3 and 6 form switch 3, configuring MCU1_BOOT0. Pin 3 is pulled up to 3.3V via pull-up resistor R2, and pin 6 is connected to the BOOT0 pin of MCU1. In this switch, when the switch is closed, MCU1_BOOT0 is at a high level of 3.3V, and MCU1 enters programming / debugging mode; when the switch is open, MCU1_BOOT0 is at a low level, and normal startup occurs.

[0033] Pins 4 and 5 form switch 4, which configures MCU2_BOOT0. Pin 4 is pulled up to 3.3V via pull-up resistor R2, and pin 5 is connected to the BOOT0 pin of MCU2. The logic is the same as MCU1_BOOT0.

[0034] In this DIP switch circuit, pull-up resistor R2 and pull-down resistor R1 eliminate uncertain levels and ensure signal stability when the switch is open. The four switches cover two GPIO controls and two MCU startup configurations. The system behavior can be flexibly adjusted by hardware DIP switches without modifying the code. For example, during the debugging phase, the MCU can be switched to start the debugging mode by DIP switches. During the running phase, the peripheral enable can be turned on or off as required by GPIO levels.

[0035] The TYPE-A interface circuit connects to the PCIe gold fingers to enable bidirectional communication with the PCIe terminal, used to connect USB-A devices and achieve high-speed data exchange, such as... Figure 3As shown, the TYPE-A interface circuit includes connector J3, a 6-pin USB debug interface. Pin 1 connects to USB1_DN_DBG, and pin 2 connects to USB1_DP_DBG, forming a data path for transmitting USB differential signals. Pins 4 and 6 are grounded, enhancing anti-interference capability and reducing grounding impedance to ensure USB communication reliability. Pin 5 connects to USB_VCC. One end of capacitors C2 and C3 is connected to the connection point between USB_VCC and pin 5 of J3, and the other end is connected to GND. C2 and C3 are connected in parallel between the USB_VCC power supply and ground, sharing the same power node with the power supply pin (pin 5) of J3, for filtering the USB_VCC power supply and eliminating high-frequency noise. The parallel design also expands the filtering frequency band. The USB_VCC power supply, filtered by C2 and C3, provides power to pin 5 of J3, forming a power path to power external devices / debuggers. This TYPE-A interface circuit ensures that USB_VCC is free of noise through the filtering capacitors, avoiding interference with the USB differential signals.

[0036] The USB to UART module connects to the LED indicator circuit on one end to drive the LED indicator to display the system status, and connects to the TYPE-C interface circuit on the same side to connect USB-C devices. The other end connects to the PCIe gold fingers to complete the bidirectional conversion between USB and UART protocols.

[0037] like Figure 4 As shown, the USB to UART module, based on U2, converts multiple UART serial ports to USB protocols. It receives data from multiple UART serial ports, packages it into USB data packets, and sends them to the host via USB_DP / USB_DM. Simultaneously, it receives instructions from the USB host and forwards them to the corresponding UART serial port. It includes a power system, chip U2, crystal oscillator circuit, reset circuit, and signal interface. The power system includes an input power supply VCC_3V3 and a filter capacitor module. The input power supply is a 3.3V DC power supply. The filter capacitor module includes capacitors C14, C15, C16, and C17 connected in parallel between VCC_3V3 and ground to filter out high-frequency noise from the power supply and ensure stable operation of the chip.

[0038] Chip U2 is a CH348 series chip used to receive multiple UART serial port data and convert them into USB protocol output, while also supporting USB host commands to control UART serial port transmission and reception.

[0039] The crystal oscillator circuit includes crystal Y1 and capacitors C18 and C19. The two ends of crystal Y1 are connected to the TAL_IN and XTAL_OUT pins of U2, respectively. One end of capacitor C18 is connected to the connection point of Y1 and XTAL_IN, and the other end is connected to GND. One end of capacitor C19 is connected to the connection point of Y1 and XTAL_OUT, and the other end is connected to GND. Each of the two capacitors is connected to one pin of the crystal oscillator to ground, forming a symmetrical AC loop to ensure symmetrical attenuation of the AC signal at both ends of the crystal oscillator and avoid phase deviation that could lead to unstable oscillation.

[0040] The reset circuit includes resistor R34 and capacitor C20. Through the RESET network, R34 provides a high-level hold, and C20 implements a low-level delay upon power-on, jointly controlling the reset / startup of U2. One end of resistor R34 is connected to VCC_3V3, and the other end is connected to the RESET network of U2's reset pin. One end of capacitor C20 is connected to the RESET network of U2's reset pin, and the other end is grounded. The two are connected to the RESET node as a common connection point. R34 is pulled up to the power supply, and C20 is pulled down to ground to absorb high-frequency noise on the RESET pin and avoid false reset, forming a charging and discharging path of power supply-R34-RESET-C20-ground.

[0041] The signal interfaces include a UART serial port and a USB differential port. CH348_TXD4 and CH348_RXD4 correspond to the UART4 channel. CH348_TXD4 is connected to pin 40 of chip U2 after being connected in series with R23, and CH348_RXD4 is connected to pin 41 of chip U2 after being connected in series with R24. CH348_TXD5 and CH348_RXD5 correspond to the UART5 channel. CH348_TXD5 is connected to pin 44 of chip U2 after being connected in series with R26, and CH348_RXD5 is connected to pin 46 of chip U2 after being connected in series with R29. Current limiting or impedance matching of resistors R23, R24, R27, and R29 protects the chip pins and improves the serial port's anti-interference capability. USB_DP and USB_DM connect to external USB interfaces (such as TYPE-C and TYPE-A) to transmit USB 2.0 differential data.

[0042] like Figure 5As shown, the TYPE-C interface circuit includes a power input conditioning module, diode D1, and USB interface J6. The power input conditioning module includes an input power supply VCC_3V3, input filter capacitors C5 and C6, a voltage regulator U1, and output filter capacitors C7 and C8. The input power supply provides 3.3V as the power input for the entire interface circuit. Input filter capacitors C5 and C6 are connected in parallel between VCC_3V3 (the power input of U1) and ground to filter out noise from the input power supply. Output filter capacitors C7 and C8 are connected in parallel between pin 3 of U1 (VIN, which is actually the output terminal of U1) and ground to filter out ripple from the output of U1. Pins 2 and 4 of the voltage regulator U1 are connected to the input power supply VCC_3V3, and pin 3 is also connected to VCC_3V3 to ensure stable power supply. Pin 1 is grounded.

[0043] The power pins 1 and 2 of the USB interface J6 are connected to EXT_USB_VCC, the data pins 6 and 7 are used to transmit USB signals, and the 12 pin is grounded to provide a loop.

[0044] Diode D1 is a Schottky diode located between the power conditioning module and the USB interface J6 to prevent reverse current. When an external USB device attempts to supply power in reverse, the diode is reverse-biased and cut off, protecting U1 and the system power from reverse flow. The TYPE-C interface circuit stabilizes the power supply through U1, diode D1 prevents reverse power supply, and the capacitor filters out noise to ensure power quality.

[0045] like Figure 6 As shown, the LED indicator circuit includes a power supply VCC_3V3 and four LEDs: LED1A, LED1B, LED2A, and LED2B. LED1A is the power indicator, which is always on when VCC_3V3 is powered; LED1B is the Link indicator, which is always on during normal configuration; LED2A is the serial port data transmission indicator, which flashes when data is being transmitted via the serial port; and LED2B is the serial port data reception indicator, which flashes when data is being received via the serial port. The anodes of the four LEDs are connected to VCC_3V3 via current-limiting resistors R19, R20, R21, and R22, respectively. The cathodes are grounded or connected to a control signal. Specifically, LED1A's anode is connected to current-limiting resistor R19 / cathode grounded; LED1B's anode is connected to current-limiting resistor R20 and then to VCC_3V3, with its cathode connected to ACT / CFG / DCD3; LED2A's anode is connected to current-limiting resistor R21 and then to VCC_3V3, with its cathode connected to TX_LED / RI3; LED2B's anode is connected to current-limiting resistor R22 and then to VCC_3V3, with its cathode connected to RX_LED / DSR3. All LED anodes are connected to the power supply, and the lighting is controlled by the cathode's voltage level (GND or a control signal). The current-limiting resistors ensure LED safety.

[0046] The RS232 to UART module connects to a 5569 interface and a PCIe gold finger at both ends, respectively, to complete the bidirectional conversion between RS232 and UART protocols. The 5569 interface is a multi-pin connector used to connect to customized serial port devices. It transmits bidirectionally with the RS232 to UART module, enabling bidirectional transmission between customized serial port devices and the PCIe gold finger.

[0047] like Figure 7 As shown, the RS232 to UART module circuit uses the SP3232EEN chip solution. Chip U3 is an RS232 transceiver, which is multi-channel and includes a power charge pump module U3A and a signal conversion module U3B. U3A converts 3.3V (DBG_3V3) to the standard ± voltage of RS232 through an internal charge pump circuit. Its VCC (pin 16) is connected to DBG_3V3, and GND (pin 15) is grounded. Pins 1 (C1+) and 3 (C1-) of U3A are connected to the two ends of the charge pump capacitor C9, respectively. Pins 4 (C2+) and 5 (C2-) of U3A are connected to the two ends of the charge pump capacitor C11, respectively. Capacitors C9 and C11, together with the internal circuit of the chip, form a boost-negative voltage generation loop: C9 participates in the generation of positive voltage (V+), and C11 participates in the generation of negative voltage (V-). Through high-frequency switching, the 3.3V is boosted to the required positive and negative high voltages. The V+ (positive high voltage) and V- (negative high voltage) signals generated by the charge pump have high-frequency ripple. This is smoothed using filter capacitors C10 and C12. One end of C10 is connected to pin 6 of U3A (V+, positive high voltage output), and the other end is connected to GND (ground). One end of C12 is connected to pin 7 of U3A (V-, negative high voltage output), and the other end is connected to GND. These filter capacitors remove high-frequency noise from V+ and V-, ensuring a stable RS232 signal level.

[0048] Connect U3B's T1IN (pin 11) to the MCU's DBG_TX, and R1OUT (pin 12) to the TTL output. Pull-up resistor R30 is connected at one end to DBG_3V3 and at the other end to U3B's R1OUT (pin 12). Pull-up resistor R31 is also connected at one end to DBG_3V3 and at the other end to U3B's T1IN (pin 11). These pull-up resistors ensure the stability of the serial port signal level. R1IN (pin 13) is connected to the RS232 input, and T1OUT (pin 14) is connected to the RS232 output. Connect one end of R32 to U3B's pin 14 and at the other end to pin 3 of DB9 socket J7 (transmit signal pin). Connect one end of R33 to U3B's R1IN (pin 13) and at the other end to pin 2 of DB9 socket J7 (receive signal pin). R32 and R33 are connected in series with U3B's RS232... The transmit output (T1OUT), receive input (R1IN) and external DB9 interface serve to limit current and protect the U3B chip.

[0049] After assembling each functional module into the debugging box, its appearance is as follows: Figure 8 As shown, the PCIe interface is located on the right side wall of the enclosure and is used to interface with the cockpit main unit. The DIP switch and the TYPC-C interface are located on the front side wall of the enclosure. The DIP switch is used to assign high and low states to the specified GPIOs of the cockpit, and the TYPC-C interface utilizes its standard USB 2.0 to UART converter, supporting reversible insertion. The 5569 interface, the TYPE-A interface, and four LED indicators are located on the left side wall of the enclosure. The 5569 interface is defined as an RS232 interface, and the four LED indicators are used to detect the serial data stream of the USB to UART converter. The TYPE-A interface pulls out the native USB port of the cockpit main unit, which can be used as an ADB interface.

[0050] This utility model obtains bandwidth and power by connecting to the host via a PCIe gold finger, flexibly configures hardware parameters through DIP switches, provides intuitive feedback on system status through LED indicators, adapts to different serial port protocols via USB to UART and RS232 to UART, reducing the complexity of protocol processing on the PCIe side, and covers a variety of peripheral interfaces through YPE-A, TYPE-C, and 5569, thus broadening its applicability. This debugging box achieves comprehensive debugging capabilities by concentrating numerous debugging ports within the system onto a single PCIe interface, allowing for flexible plug-and-play functionality. Compared to traditional ADB, it also expands upon native serial ports and customizable debugging ports, upgrades control, etc., effectively solving the problems of scattered interfaces, complex operation, and limited expansion capabilities in traditional debugging methods, significantly improving the convenience and flexibility of cockpit system debugging.

[0051] The above description is only a preferred embodiment of the present utility model and does not limit the present utility model. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present utility model should be included within the protection scope of the present utility model.

Claims

1. A pluggable integrated debugging box for a cockpit main unit, comprising a box body and functional modules disposed within the box body, characterized in that: The functional modules include a PCIe gold finger, a DIP switch circuit, a TYPE-A interface circuit, an LED indicator circuit, a TYPE-C interface circuit, a USB to UART module circuit, and an RS232 to UART module circuit. The DIP switch circuit is connected to the PCIe gold finger and allows manual setting of status parameters and one-way input of configuration signals to the PCIe gold finger. The TYPE-A interface circuit is connected to the PCIE gold fingers to enable bidirectional communication with the PCIE terminal. The USB to UART module is connected to an LED indicator circuit on one end to drive the LED indicator to display the system status, and to a TYPE-C interface circuit on the same side for connecting USB-C devices. The other end is connected to the PCIe gold fingers to complete the bidirectional conversion between USB and UART protocols. The RS232 to UART module is connected to a 5569 interface and a PCIe gold finger at both ends, respectively, to complete the bidirectional conversion between RS232 and UART protocols.

2. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The DIP switch circuit includes a 4-bit DIP switch J2, a pull-up resistor R2, and a pull-down resistor R1. The 4-bit DIP switch J2 internally includes 4 sets of independent switches, each set connected to two pins. Switch 1 consists of pin 1 and pin 8, and is used to control GPIOB8_CTL. Pin 1 is connected to a 3.3V power supply via pull-up resistor R2, and pin 8 is connected to GPIOB8_CTL and connected in series with pull-down resistor R1 to ground (GND). Switch 2 consists of pin 2 and pin 7, and is used to control GPIOB11_CTL. Pin 2 is connected to a 3.3V power supply via pull-up resistor R2, and pin 7 is connected to the signal GPIOB11_CTL. Switch 3 consists of pin 3 and pin 6, and is used to configure MCU1_BOOT0. Pin 3 is connected to the 3.3V power supply via pull-up resistor R2, and pin 6 is connected to the BOOT0 pin of MCU1. Switch 4 consists of pins 4 and 5, and is used to configure MCU2_BOOT0. Pin 4 is connected to the 3.3V power supply via pull-up resistor R2, and pin 5 is connected to the BOOT0 pin of MCU2.

3. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The TYPE-A interface circuit includes connector J3, capacitor C2, and capacitor C3. Connector J3 is a 6-pin USB debugging interface. Pin 1 of connector J3 is connected to USB1_DN_DBG, and pin 2 is connected to USB1_DP_DBG. Pins 1 and 2 form a data path for transmitting USB differential signals. Pins 4 and 6 of connector J3 are grounded. Pin 5 of connector J3 is connected to USB_VCC. One end of capacitors C2 and C3 is connected to the connection point between USB_VCC and pin 5 of J3, and the other end is grounded to GND. Capacitors C2 and C3 are connected in parallel between the USB_VCC power supply and ground, and share the same power node with the power supply pin of J3, for filtering the USB_VCC power supply.

4. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The TYPE-A interface circuit has a USB 2.0 interface.

5. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The USB-to-UART module includes a power supply system, a chip U2, a crystal oscillator circuit, and a reset circuit. The power supply system includes an input power supply VCC_3V3 and a filter capacitor module. The input power supply is a 3.3V DC power supply. The filter capacitor module includes capacitors C14, C15, C16, and C17 connected in parallel between VCC_3V3 and ground to filter out high-frequency power supply noise. Chip U2 is used to receive multiple UART serial port data and convert them to USB protocol output, while also supporting USB host commands to control UART serial port transmission and reception. The crystal oscillator circuit includes... Crystal oscillator Y1 and capacitors C18 and C19 are connected. The two ends of crystal oscillator Y1 are connected to the TAL_IN and XTAL_OUT pins of U2, respectively. One end of capacitor C18 is connected to the connection point of Y1 and XTAL_IN, and the other end is connected to GND. One end of capacitor C19 is connected to the connection point of Y1 and XTAL_OUT, and the other end is connected to GND. The reset circuit includes resistor R34 and capacitor C20. One end of resistor R34 is connected to VCC_3V3, and the other end is connected to the RESET network of U2's reset pin. One end of capacitor C20 is connected to the RESET network of U2's reset pin, and the other end is grounded.

6. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The TYPE-C interface circuit includes a power input conditioning module, diode D1, and USB interface J6. The power input conditioning module includes an input power supply VCC_3V3, input filter capacitors C5 and C6, a voltage regulator U1, and output filter capacitors C7 and C8. The input power supply provides 3.3V as the power input for the entire interface circuit. Input filter capacitors C5 and C6 are connected in parallel between VCC_3V3 and ground. Output filter capacitors C7 and C8 are connected in parallel between pin 3 of U1 and ground. Pins 2 and 4 of the voltage regulator U1 are connected to the input power supply VCC_3V3, pin 3 is connected to VCC_3V3, and pin 1 is grounded. The power pins 1 and 2 of the USB interface J6 are connected to EXT_USB_VCC, the data pins 6 and 7 are used to transmit USB signals, and the 12 pin is grounded; the diode D1 is located between the power conditioning module and the USB interface J6 to prevent reverse current.

7. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The TYPE-C interface circuit interface is a USB 2.0 interface.

8. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The RS232 to UART module circuit includes a power charge pump module U3A and a signal conversion module U3B. The VCC pin of U3A is connected to DBG_3V3, and the GND pin is grounded. The C1+ and C1- pins of U3A are respectively connected to the two ends of the charge pump capacitor C9. The C2+ and C2- pins of U3A are respectively connected to the two ends of the charge pump capacitor C11. One end of C10 is connected to the V+ pin of U3A, and the other end is connected to GND. One end of C12 is connected to the V- pin of U3A, and the other end is connected to GND. The U3B's T1IN pin is connected to the MCU's DBG_TX pin, and the R1OUT12 pin is connected to the TTL output. One end of pull-up resistor R30 is connected to DBG_3V3, and the other end is connected to the U3B's R1OUT12 pin. One end of pull-up resistor R31 is connected to DBG_3V3, and the other end is connected to the U3B's T1IN pin. The R1IN pin is connected to the RS232 input, and the T1OUT pin is connected to the RS232 output. One end of R32 is connected to the U3B's pin 14, and the other end is connected to the transmit signal pin of DB9 socket J7. One end of R33 is connected to the U3B's R1IN pin, and the other end is connected to the receive signal pin of DB9 socket J7.

9. The pluggable integrated debugging box for cockpit main unit according to claim 1, characterized in that: The LED indicator circuit includes a power supply VCC_3V3 and four LEDs, namely LED1A, LED1B, LED2A, and LED2B. LED1A's anode is connected to a current-limiting resistor R19 and its cathode is grounded. LED1B's anode is connected to a current-limiting resistor R20 and then to VCC_3V3, and its cathode is connected to ACT / CFG / DCD3. LED2A's anode is connected to a current-limiting resistor R21 and then to VCC_3V3, and its cathode is connected to TX_LED / RI3. LED2B's anode is connected to a current-limiting resistor R22 and then to VCC_3V3, and its cathode is connected to RX_LED / DSR3.

10. The pluggable integrated debugging box for cockpit main unit according to claim 9, characterized in that: LED1A is a power indicator, which is always on when VCC_3V3 is powered; LED1B is a Link indicator, which is always on during normal configuration; LED2A is a serial port data transmission indicator, which flashes when there is data being transmitted through the serial port; LED2B is a serial port data reception indicator, which flashes when there is data being received through the serial port.

Images