A method and system for communication between a domain controller and an ARHUD

Abstract

This invention belongs to the field of vehicle information processing and provides a method and system for communication between a domain controller and an ARHUD. The communication method includes: connecting the domain controller and the ARHUD via an LVDS cable; using the IIC protocol as a framework to implement a handshake between the domain controller and the ARHUD; after a successful handshake, the domain controller sends a HUD function configuration command to the ARHUD, and the ARHUD receives and responds to the command to configure its functions.

Description

Technical Field

[0001] This invention belongs to the field of vehicle information processing, and particularly relates to a communication method and system between a domain controller and an ARHUD. Background Technology

[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.

[0003] With the advancement of automotive technology, customer demands for displays in smart cockpits are becoming increasingly diverse. ARHUD (Augmented Reality HUD), as a new type of display in smart cockpits, is changing customers' perception of traditional WHUD (Windshield-HUD). ARHUD not only integrates navigation functions with real-world views to enhance the driving experience, but it can also integrate with ADAS (Advanced Driver Assistance System) to provide a real-world display solution for autonomous driving. As is well known, the real-world fusion function of ARHUD, a core feature distinguishing it from ordinary HUDs (Head-Up Displays), relies on the system's hardware performance for its implementation. For example, AR (Augmented Reality) algorithms require SOC (System-on-Chip) computing power, AR image processing requires GPU (Graphics Processing Unit) computing power, and data storage requires eMMC (Embedded Multi Media Card) storage space. Based on these requirements, ARHUDs need to incorporate an AR Creator (AR algorithm control center) in their hardware design. The AR Creator is responsible for the parsing and fusion of information related to AR algorithms, coordinate transformation, coordinate calibration, and image generation. Its hardware includes core electronic components such as the SOC, MCU (Microcontroller Unit), and eMMC. Currently, there are two technical forms of AR Creator in the industry: one where the ARHUD itself has an integrated AR Creator, allowing the HUD to independently acquire data and output video for display. Another approach adopts a hardware-software separation design concept, eliminating the hardware (ARcreator) in traditional designs. The core algorithm is integrated into the domain controller as software, with the ARHUD itself acting only as a display, receiving and displaying the video signal processed by the AR algorithm. In this hardware-software separation design, the ARcreator is integrated into the domain controller as a software package, and the ARHUD only functions as a display. Implementing local settings and software upgrades for the ARHUD based on the first technology is relatively complex. Firstly, the ARHUD display needs CAN functionality. When communicating with the ARcreator via CAN signals, the signal must first be sent to the vehicle's CAN bus, and then relayed to the ARHUD. This long communication link poses a signal delay risk and increases the load on all vehicle nodes. Additionally, the ARHUD needs its own CAN (Controller Area Network) chip, further increasing costs. Summary of the Invention

[0004] To address the technical problems existing in the background art, the present invention provides a domain controller and ARHUD communication method and system, which is used to realize data transmission between ARHUD and domain controller, and can realize functions such as ARHUD status setting (user ID, HUD on / off status, height, brightness, language) and software upgrade.

[0005] To achieve the above objectives, the present invention adopts the following technical solution:

[0006] The first aspect of the present invention provides a method for communication between a domain controller and an ARHUD.

[0007] A method for communication between a domain controller and an ARHUD, comprising:

[0008] The domain controller and ARHUD are connected via an LVDS cable;

[0009] The IIC protocol is used as a framework to implement the handshake between the domain controller and the ARHUD;

[0010] After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to ARHUD. ARHUD accepts and responds to the command to complete the ARHUD function configuration or refresh.

[0011] As one implementation method, the domain controller IIC uses a high-speed 400kHz speed.

[0012] As one implementation, if the data read by the domain controller fails to verify the data, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

[0013] As one implementation, during the process of the ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

[0014] In one implementation, when the ARHUD has data to send, the display that communicates with the domain controller pulls the interrupt request signal IRQ low and notifies the domain controller to read it.

[0015] As one implementation, if the domain controller fails to read data for a set time period after the interrupt request signal IRQ is pulled low, the ARHUD discards the frame data, and the interrupt request signal IRQ returns to a high level.

[0016] In one implementation, when the address sent by the domain controller for IIC read is consistent with the address of the ARHUD slave, the ARHUD pulls the interrupt request signal IRQ high and keeps it high until the stop bit of the domain controller's IIC read operation ends, then returns to idle, and the interrupt request signal IRQ is high.

[0017] A second aspect of the present invention provides a domain controller and ARHUD communication system.

[0018] A domain controller and ARHUD communication system includes: a domain controller and an ARHUD connected via an LVDS cable;

[0019] The domain controller and ARHUD use the IIC protocol as a framework for handshaking. After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to the ARHUD. The ARHUD accepts and responds to the command to configure or refresh its functions.

[0020] As one implementation, if the data read by the domain controller fails to verify the data, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

[0021] As one implementation, during the process of the ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

[0022] Compared with the prior art, the beneficial effects of the present invention are:

[0023] This invention employs a technical solution that uses an LVDS line to directly transmit communication between the ARHUD and the domain controller. It uses the IIC protocol as a framework to realize the handshake between the domain controller and the ARHUD, as well as the function configuration or refresh of the ARHUD. This reduces the need for the CAN chip built into the HUD, and at the same time, direct internal communication between controllers achieves the effects of cost saving and fast communication control.

[0024] Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0025] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.

[0026] Figure 1 This is a communication framework diagram between the domain controller and ARHUD according to an embodiment of the present invention;

[0027] Figure 2This is a block diagram of the AR-HUD MCU-side software upgrade structure according to an embodiment of the present invention;

[0028] Figure 3(a) is a flowchart of the HUD APP (i.e., domain controller) software upgrade process according to an embodiment of the present invention;

[0029] Figure 3(b) is a flowchart of the AR-HUD MCU software upgrade process according to an embodiment of the present invention;

[0030] Figure 4 This is a flowchart of a domain controller and ARHUD communication method according to an embodiment of the present invention. Detailed Implementation

[0031] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0032] It should be noted that the following detailed description is illustrative and intended to provide further explanation of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0033] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0034] Example 1

[0035] When using a hardware / software separation scheme, the domain controller and ARHUD are connected via LVDS (Low-Voltage Differential Signaling) lines, requiring the definition of a communication protocol to achieve data communication between them. The domain controller and ARHUD are connected via LVDS lines, and the IIC (Inter-Integrated Circuit) protocol is used as the framework. This defines how ARHUD settings (user ID, HUD on / off status, height, brightness, language, etc.) and software upgrades are implemented through the IIC protocol.

[0036] IIC (Inter-Integrated Circuit) is short for IIC Bus, which is an integrated circuit bus and a type of serial communication bus.

[0037] Figure 1 The communication framework diagram between the domain controller and ARHUD in this embodiment is given; Figure 1 In this system, the domain controller has an embedded operating system. The domain controller communicates with each other in sequence through a serializer, two video signal connectors, a deserializer, and a microcontroller. The video signal connector, which is directly connected to the deserializer, is also connected to the video processing chip, and the video processing chip is connected to the HUD display.

[0038] Reference Figure 4 A method for communication between a domain controller and an ARHUD is presented, which includes:

[0039] Step 1: Connect the domain controller and ARHUD using an LVDS cable;

[0040] Step 2: Use the IIC protocol as a framework to implement the handshake between the domain controller and ARHUD;

[0041] Step 3: After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to ARHUD. ARHUD accepts and responds to the command to complete the ARHUD function configuration or refresh.

[0042] Preferably, the domain controller IIC uses a high-speed 400KHz speed.

[0043] If the data read by the domain controller fails to verify, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

[0044] During the process of ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

[0045] When ARHUD has data to send, the display that communicates with the domain controller will pull the interrupt request signal IRQ low and notify the domain controller to read it.

[0046] If the interrupt request signal IRQ is pulled low and no data is read by the domain controller within a set time period, ARHUD discards the data frame and the interrupt request signal IRQ returns to a high level.

[0047] When the address sent by the domain controller for IIC read matches the address of the ARHUD slave, the ARHUD will pull the interrupt request signal IRQ high and keep it high until the stop bit of the domain controller's IIC read operation ends, at which point it will return to idle and the interrupt request signal IRQ will be high again.

[0048] Specifically, ARHUD status settings:

[0049] HUD to domain controller:

[0050]

[0051]

[0052] Domain controller to HUD:

[0053]

[0054] The data is an event-driven signal, for example:

[0055]

[0056]

[0057] Based on the above protocol, ARHUD and the domain controller can perform a handshake. After a successful handshake, HUD function settings (on / off, brightness, height, language, display content, etc.) can be configured.

[0058] Recommended timing for IIC domain controller read / write operations:

[0059] Domain Controller IIC Read Display Operation Timing:

[0060]

[0061] Note: STOP and RESTART are not required between Slave Addr and data1.

[0062] Domain Controller IIC Write Display Operation Timing:

[0063] Start SlaveAddr W ACK CMD_ID ACK Datel ACK … DateN ACK Ext_Length ACK CheckSum ACK Stop

[0064] ARHUD is located in the address specified in the protocol "Slave Address: Remote IIC Slave".

[0065] It is recommended that the domain controller IIC be set to a high speed of 400kHz.

[0066] If the data read by the domain controller fails verification, the same read operation can be attempted again before the next IRQ interrupt.

[0067] ARHUD Interrupt Request Signal IRQ for Reading Data from Domain Controller: Explanation

[0068] 1. IRQ is high when idle;

[0069] 2. When the ARHUD has data to send, the display will pull the IRQ low to notify the domain controller to read it as soon as possible;

[0070] 3. If the domain controller does not read data for more than 100ms after the IRQ is pulled low (the timeout is adjustable; see instructions 0x12 and 0x82 for details), the ARHUD will discard the data frame and the IRQ will return to the high level.

[0071] 4. When the address sent by the domain controller for IIC read is consistent with the address of the ARHUD slave, the ARHUD will pull the IRQ high and keep it high until the stop bit of the domain controller's IIC read operation ends;

[0072] 5. Return to idle state, IRQ is high.

[0073] AR-HUD software upgrade

[0074] Upgrade method:

[0075] 1. Upgrade the AR-HUD MCU software via LVDS line and IIC communication.

[0076] 2. The AR-HUD is a slave device.

[0077] Frame format: Read frame format:

[0078]

[0079]

[0080] Write frame format:

[0081]

[0082] Upgrade Instructions

[0083]

[0084]

[0085] like Figure 2 As shown in Figures 3(a) and 3(b), the upgrade process is as follows: the upgrade communication is between the HUD APP (Application software, referring to the AR software integrated in the domain controller) and the HUD MCU.

[0086] Step 1: Click the upgrade button on the HMI (Human Machine Interface). The domain controller will check if the provisioning code and upgrade package name match the information displayed on the HUD. If they do not match, the upgrade process will be exited.

[0087] Step 2: The HUD APP sends a notification to the HUD MCU to perform a setting process, and the HUD itself sets its own display upgrade flag. There is no hard-wired signal; it is output via the IIC protocol.

[0088] Step 3: The HUD APP queries the current MCU working status, and the HUD MCU replies with the current working status.

[0089] Step 4: The HUD APP sends the Flash Driver file information; the HUD MCU receives and responds.

[0090] Step 5: The HUD APP sends the Flash Driver file – this involves multiple transmissions.

[0091] Step 6: The HUD APP reads the sending status; the HUD MCU replies with the receiving status.

[0092] Step 7: The HUD APP has completed sending the Flash Driver file.

[0093] Step 8: HUD MCU confirms the status of the Flash Driver file.

[0094] Step 9: HUD MCU erases the APP area.

[0095] Step 10: HUD APP notification sends upgrade file information.

[0096] Step 11: HUD APP sends upgrade file – multiple transmissions are possible.

[0097] Step 12: The HUD APP reads the sending status; the HUD MCU replies with the receiving status.

[0098] Step 13: The HUD APP has completed sending the upgrade file.

[0099] Step 14: HUD MCU confirms the status of the upgrade file.

[0100] Step 15: HUD MCU Reset (used to detect whether the HUD display upgrade is complete; a normal reset indicates a successful reset, while no response indicates a successful reset).

[0101] Step 16: Upgrade successful. Clear the HUD upgrade flag.

[0102] In one or more embodiments, a domain controller and ARHUD communication system is also provided, comprising: a domain controller and an ARHUD connected via an LVDS line;

[0103] The domain controller and ARHUD use the IIC protocol as a framework for handshaking. After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to the ARHUD. The ARHUD accepts and responds to the command to configure or refresh its functions.

[0104] If the data read by the domain controller fails to verify, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

[0105] During the process of ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

[0106] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A method for communication between a domain controller and an ARHUD, characterized in that, include: The domain controller and ARHUD communicate directly via an LVDS cable connection. The IIC protocol is used as a framework to implement the handshake between the domain controller and the ARHUD; After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to ARHUD. ARHUD accepts and responds to the command to realize the function configuration or refresh of ARHUD. When ARHUD has data to send, the display that communicates with the domain controller will pull the interrupt request signal IRQ low and notify the domain controller to read it; If the domain controller fails to read data for a set time period after the interrupt request signal IRQ is pulled low, ARHUD discards the data frame, and the interrupt request signal IRQ returns to a high level.

2. The domain controller and ARHUD communication method as described in claim 1, characterized in that, The domain controller IIC uses a high-speed 400KHz speed.

3. The domain controller and ARHUD communication method as described in claim 1, characterized in that, If the data read by the domain controller fails to verify, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

4. The domain controller and ARHUD communication method as described in claim 1, characterized in that, During the process of ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

5. The domain controller and ARHUD communication method as described in claim 1, characterized in that, When the address sent by the domain controller for IIC read matches the address of the ARHUD slave, the ARHUD will pull the interrupt request signal IRQ high and keep it high until the stop bit of the domain controller's IIC read operation ends, at which point it will return to idle and the interrupt request signal IRQ will be high again.

6. A domain controller and ARHUD communication system, characterized in that, include: Domain controllers and ARHUDs are connected via LVDS cables; The domain controller and ARHUD use the IIC protocol as a framework for handshaking. After the domain controller and ARHUD successfully handshake, the domain controller sends a HUD function configuration or refresh command to ARHUD. ARHUD accepts and responds to the command to realize the function configuration or refresh of ARHUD. When ARHUD has data to send, the display that communicates with the domain controller will pull the interrupt request signal IRQ low and notify the domain controller to read it; If the domain controller fails to read data for a set time period after the interrupt request signal IRQ is pulled low, ARHUD discards the data frame, and the interrupt request signal IRQ returns to a high level.

7. The domain controller and ARHUD communication system as described in claim 6, characterized in that, If the data read by the domain controller fails to verify, the same read operation can be attempted again before the next interrupt request signal (IRQ) interrupts.

8. The domain controller and ARHUD communication system as described in claim 6, characterized in that, During the process of ARHUD requesting the domain controller to read data via the interrupt request signal IRQ, the interrupt request signal IRQ is high when idle.

Images