Instrument function development method of electronic cabin chip

Abstract

The invention discloses an instrument function development method for an electronic cabin chip, and belongs to the technical field of cabin chip development. The invention aims to solve the problem that the existing low-cost intelligent cabin chip can not really realize product integration due to simple hardware combination of an instrument function and an IVI function. Comprising the steps that for an electronic cabin chip comprising an A core with an R core, a QTforMCU or LVGL loading instrument function framework is configured in an R core thread; a time division multiplexing mode is adopted, after the A core is initialized, the R core thread in the idle state runs an instrument application program, and instrument information is displayed through a configured LVDS display channel. According to the invention, the same resource is subjected to time division multiplexing, so that the chip resource is saved.

Description

Technical Field

[0001] The invention relates to an instrument function development method of an electronic cockpit chip, belonging to the technical field of cockpit chip development. Background Art

[0002] As the information interaction between the instrument and the in-vehicle entertainment system (IVI) increases, the market demand for integrated solution products is increasing. The concept of the smart cockpit integrates the full LCD instrument and IVI into one, which not only gives the instrument and IVI a natural advantage in interaction, but also reduces the production cost of the integrated product.

[0003] Currently, the main smart cockpit chips are mostly high-end chips with multiple A cores and multiple R cores to run Android (IVI) and Linux (instrument). Figure 1 As shown. The R core is responsible for safety domain management, fast reversing rear view and startup animation. It has strong performance and comprehensive functions, but the chip price is high. This cannot be applied to low-priced models.

[0004] For low-priced models, the IVI and instrument products currently used are completed with two traditional main control chips. One low-end main control A core chip runs IVI, and the other main control chip runs the full LCD instrument. The data interaction between the two chips is limited to external communication Uart or SPI hard link, such as Figure 2 and Figure 3 As shown. Although this method is low-cost, the degree of integration is not high and the amount of data interaction is limited. It is equivalent to simply combining two products of the traditional solution with hardware so that they share a hardware board. Summary of the invention

[0005] Aiming at the problem that the existing low-cost intelligent cockpit chip simply combines the instrument function and the IVI function by hardware and cannot truly achieve product integration, the present invention provides an instrument function development method for an electronic cockpit chip.

[0006] A method for developing instrument functions of an electronic cockpit chip of the present invention comprises:

[0007] For the electronic cockpit chip that includes an A core with an attached R core, QTforMCU or LVGL is configured in the R core thread to load the instrument function framework. By using time-sharing multiplexing, after the A core is initialized, the idle R core thread runs the instrument application and displays the instrument information through the configured LVDS display channel.

[0008] According to the instrument function development method of the electronic cockpit chip of the present invention, the A core and the R core exchange information using RPmsg.

[0009] According to the instrument function development method of the electronic cockpit chip of the present invention, the R core is adapted to the RTOS micro operating system.

[0010] According to the instrument function development method of the electronic cockpit chip of the present invention, QTforMCU or LVGL is adapted to the G2D display module.

[0011] According to the instrument function development method of the electronic cockpit chip of the present invention, the instrument application program and the instrument information display material are compiled, packaged and burned together with the R core firmware program. After the electronic cockpit chip is powered on, the R core initializes the chip resources to load the LD2 firmware, initializes the DDR and EMMC storage, and the R core copies the necessary resources for the A core operation to the DDR to reset the A core operation.

[0012] According to the instrument function development method of the electronic cockpit chip of the present invention, the R core configures the display interface and display screen of the electronic cockpit chip LVDS and MIPI-DSI, loads the firmware and instrument information display materials of QTforMCU or LVGL stored in the EMMC into DDR, and waits for the instrument application to run; the R core also reads the startup animation materials stored in the EMMC.

[0013] According to the instrument function development method of the electronic cockpit chip of the present invention, the R core uses G2D to play the boot animation and then initializes the camera and IO information;

[0014] After receiving the instruction that the A core has started, the R core releases the MIPI-DSI display content resources to the A core; after confirming that the A core has started to run the display content resources, the R core loads QTforMCU or LVGL into the thread to run the instrument application.

[0015] Beneficial effects of the present invention: The method of the present invention transplants QTforMCU or LVGL to mid- and low-end electronic cockpit chips for the development of low-cost instrument programs, and can replace the low-cost IVI instrument built with traditional two main control chips at a lower cost price to obtain a highly integrated intelligent cockpit solution.

[0016] The method of the present invention transplants QTforMCU to the security domain MCU, so that the R core that originally does not have the instrument function development can use the G2D display unit more efficiently, and can render the display effect required by ordinary instruments. It enables a low-end cockpit chip to run IVI and instrument programs at the same time, with a high degree of integration, good communication effect, and greatly reduced costs.

[0017] The method of the present invention improves the utilization rate of the R-core CPU and the 2D display module in the chip security domain, performs time-division multiplexing on the same resource, saves chip resources, and reduces costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 This is the principle block diagram of the existing intelligent cockpit chip using high-end chips with multiple A cores and multiple R cores;

[0019] Figure 2 This is a schematic diagram of the current low-priced models using Uart for data interaction;

[0020] Figure 3 This is a schematic diagram of the current low-priced models using SPI for data exchange;

[0021] Figure 4 It is a principle block diagram of the instrument function development method of the electronic cockpit chip of the present invention;

[0022] Figure 5 This is a block diagram of the operation principle of existing mid- and low-end electronic cockpit chips; DSI in the figure is mipi-DSI, which is a type of display interface; DC1 is the first display unit inside the SOC chip, and DC2 is the second display unit inside the SOC chip, and its full name is Display Controller;

[0023] Figure 6 It is a flow chart of the instrument function development method of the electronic cockpit chip described in the present invention. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0025] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0026] The present invention will be further described below in conjunction with the accompanying drawings and specific embodiments, but they are not intended to limit the present invention.

[0027] Specific implementation method 1. Combination Figures 4 to 6 As shown, the present invention provides a method for developing instrument functions of an electronic cockpit chip, comprising:

[0028] For the electronic cockpit chip that includes an A core with an attached R core, QTforMCU or LVGL is configured in the R core thread to load the instrument function framework. By using time-sharing multiplexing, after the A core is initialized, the idle R core thread runs the instrument application and displays the instrument information through the configured LVDS display channel.

[0029] When designing mid- and low-end A-core chips, an R-core is always included to be responsible for the security domain. The R-core can generally be used for fast reversing and boot animations. Because the A-core boots slowly and takes much longer to load the system than the R-core, when the chip starts running, the configuration of the screen display and hardware operations that need to run quickly are generally completed by the R-core. After the startup is completed, it is handed over to the A-core to handle subsequent requirements. Therefore, after the A-core is initialized, the R-core is basically idle.

[0030] In this implementation, the A core and the R core exchange information using RPmsg.

[0031] In this implementation, after the R core is initialized, while starting to play the boot animation, QTforMCU or LVGL is ported to load the complete display function framework, and the instrument program is run in the R core thread. The R core is configured with an LVDS display channel to output the display image, so that the CPU and G2D display unit, which should be in an idle state, can run the instrument application. This implementation utilizes low-end A core chips, and allows the security domain R core to run QTforMCU to run the instrument program while running the Android (IVI) system. Releasing the R core computing power increases the utilization rate of the R core CPU and G2D in the security domain from 5% to 80%. The R core and the A core use RPmsg for inter-core communication and information exchange, and the information transmission efficiency crushes traditional Uart communication.

[0032] Low-end and mid-range electronic cockpit chips generally have more external resources, and are only used for IVI infotainment systems with a single screen, which often leave some resources unused. To facilitate hardware development and customized boot animation and other hardware resources, the R core is adapted to the RTOS micro-operating system. The boot animation and camera can run in the RTOS system thread.

[0033] This implementation method is implemented in a time-sharing multiplexing manner under the condition of fixed hardware resources. The R core uses the RTOS system to further integrate low-end electronic cockpit chip resources, and the IVI infotainment system with a single screen does not utilize the specified resources. The original Android system GPU rendering 3D effect remains unchanged. After the boot animation is completed, the unused G2D module and screen display interface, as well as the remaining CPU computing power of the R core, are combined together and can be used for the instrument program development solution of the second product.

[0034] This implementation directly transplants the QTforMCU display framework into the security domain compilation framework of mid- and low-end chips, and QTforMCU or LVGL adapts to the G2D display module.

[0035] Furthermore, the instrument application program and the instrument information display material are compiled, packaged and burned together with the R core firmware program. After the electronic cockpit chip is powered on, the R core initializes the chip resources to load the LD2 firmware, initializes the DDR and EMMC storage, and the R core copies the necessary resources for the A core operation to the DDR to reset the A core operation.

[0036] The R core also configures the LVDS and MIPI-DSI display interfaces and display screens inside the electronic cockpit chip, loads the QTforMCU or LVGL firmware and instrument information display materials stored in the EMMC into the DDR, and waits for the instrument application to run; the R core also reads the boot animation materials stored in the EMMC.

[0037] The R core uses G2D to play the boot animation, and then initializes the camera and IO information; if a reversing signal is received, the screen directly displays the camera image;

[0038] After receiving the instruction that the A core has started, the R core releases the MIPI-DSI display content resources to the A core, which is then handed over to the Android GPU to draw the image. After confirming that the A core has started running the display content resources, the R core loads QTforMCU or LVGL into the thread to run the instrument application.

[0039] Although the present invention is described herein with reference to specific embodiments, it should be understood that these embodiments are merely examples of the principles and applications of the present invention. It should therefore be understood that many modifications may be made to the exemplary embodiments and that other arrangements may be devised without departing from the spirit and scope of the present invention as defined by the appended claims. It should be understood that the various dependent claims and features described herein may be combined in a manner different from that described in the original claims. It should also be understood that the features described in conjunction with a single embodiment may be used in other described embodiments.

Claims

1. A method for developing instrument functions for an electronic cockpit chip, characterized in that: include: For the electronic cockpit chip including the A core with R core, configure QTforMCU or LVGL in the R core thread to load the instrument function framework; By using time-sharing multiplexing, after the A core is initialized, the idle R core thread runs the instrument application and displays the instrument information through the configured LVDS display channel.

2. The instrument function development method of the electronic cockpit chip according to claim 1 is characterized in that: The A core and the R core use RPmsg to exchange information.

3. The instrument function development method of the electronic cockpit chip according to claim 2 is characterized in that: The R core is adapted to the RTOS micro operating system.

4. The instrument function development method of the electronic cockpit chip according to claim 3 is characterized in that: QTforMCU or LVGL is adapted to the G2D display module.

5. The instrument function development method of the electronic cockpit chip according to claim 4 is characterized in that: The instrument application program and instrument information display material are compiled, packaged and burned together with the R core firmware program. After the electronic cockpit chip is powered on, the R core initializes the chip resources to load the LD2 firmware, initializes the DDR and EMMC storage, and the R core copies the necessary resources for the A core to run into the DDR to reset the A core to run.

6. The instrument function development method of the electronic cockpit chip according to claim 5 is characterized in that: The R core configures the electronic cockpit chip LVDS and MIPI-DSI display interface and display screen, loads the QTforMCU or LVGL firmware and instrument information display materials stored in the EMMC into the DDR, and waits for the instrument application to run; the R core also reads the boot animation materials stored in the EMMC.

7. The instrument function development method of the electronic cockpit chip according to claim 6 is characterized in that: The R core uses G2D to play the boot animation and then initializes the camera and IO information; After receiving the instruction that the A core has started, the R core releases the MIPI-DSI display content resources to the A core; after confirming that the A core has started to run the display content resources, the R core loads QTforMCU or LVGL into the thread to run the instrument application.

Images