Display method of cabin instrument based on rendering right distribution and vehicle

Abstract

The invention provides a display method of a cabin instrument based on rendering right distribution and a vehicle. The display method of the cabin instrument comprises the following steps: initializing a main operating system and an auxiliary operating system of a target vehicle; controlling the main operating system to execute a first rendering task aiming at the first picture information, and controlling the auxiliary operating system to execute a second rendering task aiming at the second picture information; transferring the rendering right of part of the first picture information to the auxiliary operating system to execute a third rendering task; controlling the main operating system to obtain process information of the auxiliary operating system in real time, and judging whether the auxiliary operating system is in an abnormal state or not according to the process information; if yes, it is judged that the rendering right of the third rendering task is transferred to the main operating system. The technical problem that in the prior art, rendering tasks of a main operation system and an auxiliary operation system are distributed fixedly and cannot be dynamically adjusted according to the operation state of the auxiliary operation system, so that system resources are wasted or partial picture display is interrupted when the system is abnormal is solved.

Description

Technical Field

[0001] This invention relates to the field of vehicle instrument display technology, and more specifically, to a cockpit instrument display method and vehicle based on rendering rights allocation. Background Technology

[0002] Vehicle cockpit instruments are typically handled by a single operating system (such as Linux, QNX, or Android) that is responsible for rendering and displaying all screen information. To improve system real-time performance and security, some cockpit instruments adopt a master-slave operating system architecture, where the master operating system is responsible for the 2D rendering of critical instrument information (such as speed and RPM), while the slave operating system is responsible for rendering complex graphics (such as 3D navigation and entertainment interfaces).

[0003] However, the relevant technologies have at least one of the following problems: the rendering task allocation of the main and secondary operating systems is fixed in the existing technology and cannot be dynamically adjusted according to the running status of the secondary operating system, resulting in waste of system resources or interruption of part of the screen display when abnormal. Summary of the Invention

[0004] The technical problem solved by this invention is that in the prior art, the rendering task allocation of the main and secondary operating systems is fixed and cannot be dynamically adjusted according to the running status of the secondary operating system, resulting in waste of system resources or interruption of part of the screen display when abnormal.

[0005] To address the aforementioned problems, this invention provides a cockpit instrument display method based on rendering rights allocation. The cockpit instrument display method includes: Step S1: Initializing the main operating system and the secondary operating system of the target vehicle; Step S2: Controlling the main operating system to execute a first rendering task for first screen information, and controlling the secondary operating system to execute a second rendering task for second screen information; Step S3: Controlling the main operating system to obtain the running information of the secondary operating system and determining whether the secondary operating system is in a good running state; Step S4: If yes, determining that the rendering rights of part of the first screen information are transferred to the secondary operating system to execute a third rendering task; Step S5: Controlling the main operating system to obtain the process information of the secondary operating system in real time, and determining whether the secondary operating system is in an abnormal state based on the process information; Step S6: If yes, determining that the rendering rights of the third rendering task are transferred to the main operating system, and controlling the main operating system to execute an emergency command for the secondary operating system.

[0006] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: by initializing the main operating system and the secondary operating system and executing the first and second rendering tasks respectively, when the secondary operating system is running well, the rendering rights of some of the first screen information are dynamically transferred to the secondary operating system. When the secondary operating system is abnormal, the third rendering task rights are quickly switched back to the main operating system and emergency commands are executed. This realizes the dynamic allocation of rendering tasks and rapid recovery from abnormalities, and improves the smoothness, stability and safety of the cockpit instrument display.

[0007] In one embodiment of the present invention, the cockpit instrument includes an upper layer for displaying first screen information and a lower layer covered by the upper layer, the lower layer being used to display second screen information; wherein, when the secondary operating system executes a third rendering task, the first screen information rendered and output by the secondary operating system is displayed on the lower layer.

[0008] Compared with existing technologies, the technical effects achieved by this solution are as follows: By using an upper and lower layer superimposed display structure for the cockpit instruments, when the secondary operating system takes over the rendering of the first screen information, it is displayed on the lower layer. When the secondary operating system malfunctions, this first screen information returns to the upper layer, avoiding the influence of the secondary operating system's abnormal state, thus realizing the layered display and seamless integration of the rendering screens of the primary and secondary operating systems.

[0009] In one embodiment of the present invention, controlling the main operating system to execute an emergency command for the secondary operating system includes: freezing the underlying output buffer of the secondary operating system, extracting the last frame of the second rendering task as a backup frame; displaying the backup frame at the lower layer, controlling the main operating system to issue a stop rendering command to the secondary operating system, and controlling the main operating system to restart the secondary operating system.

[0010] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: by specifying emergency commands including freezing the secondary operating system output buffer, extracting the last frame as a backup frame and displaying it in the lower layer, stopping rendering and restarting the secondary operating system, the screen "frame preservation" display and system fast restart are realized when the secondary operating system is abnormal, preventing black screen or information loss and improving the system's fault tolerance.

[0011] In one embodiment of the present invention, controlling the main operating system to restart the secondary operating system includes: controlling the main operating system to send a restart command to the secondary operating system and detecting the heartbeat signal of the secondary operating system within a preset time; if the heartbeat signal of the secondary operating system is detected, determining that the secondary operating system has escaped the abnormal state, controlling the secondary operating system to execute the second rendering task, and determining to return to step S3.

[0012] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: by detecting the heartbeat signal of the secondary operating system after restarting, confirming that it has returned to normal, the second rendering task is reallocated and the process returns to step S3, thus realizing automatic recovery after an anomaly and intelligent switching of rendering rights, further improving the system's self-healing ability and resource utilization efficiency.

[0013] In one embodiment of the present invention, controlling the main operating system to issue a restart command to the secondary operating system and detecting the heartbeat signal of the secondary operating system within a preset time includes: if no heartbeat signal of the secondary operating system is detected, determining that the current restart count T of the secondary operating system is T=T. ex +1, determine if the number of reboots T is greater than the reboot threshold T0; if yes, control the main operating system to stop sending reboot commands to the secondary operating system; if no, control the main operating system to resend reboot commands to the secondary operating system; where T ex This represents the number of restarts before the last restart, and T ex The initial value is 0.

[0014] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: by introducing a restart count mechanism and a restart threshold T0, the secondary operating system is prevented from falling into an infinite restart loop, system resources are prevented from being exhausted, and the security and reliability of exception handling are improved.

[0015] In one embodiment of the present invention, controlling the main operating system to obtain the running information of the secondary operating system and determine whether the secondary operating system is in a good running state includes: obtaining the running memory of the secondary operating system and determining whether the running memory is greater than a first threshold; if not, then determining that the secondary operating system is in a good running state.

[0016] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: by monitoring the running memory of the secondary operating system and comparing it with a first threshold, it can determine whether the system is in a good running state, providing an objective and quantifiable basis for determining the transfer of rendering rights, and improving the accuracy and rationality of dynamic allocation.

[0017] In one embodiment of the present invention, controlling the main operating system to obtain process information of the secondary operating system in real time, and determining whether the secondary operating system is in an abnormal state based on the process information, includes: controlling the main operating system to detect whether the heartbeat signal of the secondary operating system has timed out; if so, determining that the secondary operating system is in an abnormal state; or obtaining the running memory of the secondary operating system and determining whether the running memory is greater than a second threshold; if so, determining that the secondary operating system is in an abnormal state.

[0018] Compared with existing technologies, the technical effects achieved by this solution are as follows: by combining the dual judgment mechanism of heartbeat signal timeout and running memory exceeding the second threshold, the abnormal status of the secondary operating system is comprehensively evaluated, which improves the comprehensiveness and timeliness of anomaly detection and reduces the risk of misjudgment.

[0019] In one embodiment of the present invention, the cockpit instrument includes a non-transparent layer covering the upper layer, the non-transparent layer being used to display third-screen information; initializing the main operating system and the secondary operating system of the target vehicle includes: controlling the main operating system to execute a fourth rendering task for the third-screen information, controlling the main operating system to output the third-screen information to the non-transparent layer; controlling the main operating system to detect the heartbeat signal of the secondary operating system; if the heartbeat signal of the secondary operating system is detected, controlling the main operating system to stop executing the fourth rendering task.

[0020] Compared with existing technologies, the technical effects achieved by this solution are as follows: a non-transparent layer is introduced to display third-screen information, the main operating system temporarily renders the boot animation during the initialization phase, and stops after the secondary operating system is running normally, thus achieving a smooth transition during the startup phase.

[0021] In one embodiment of the present invention, the first screen information is a 2D screen; and / or the second screen information is a 3D screen.

[0022] Compared with existing technologies, the technical effects achieved by adopting this technical solution are: it conforms to the typical application scenarios of cockpit instruments, allows the main operating system to focus on lightweight real-time rendering, and the secondary operating system to process complex graphics, thereby improving the rationality of task allocation and performance optimization.

[0023] On the other hand, the present invention also provides a vehicle, including: a cockpit instrument display method based on rendering rights allocation as in any of the above examples; a main operating system being a Linux system or a QNX system; and / or a secondary operating system being an Android system.

[0024] Compared with existing technologies, the technical effects achieved by adopting this technical solution are as follows: it can achieve the technical effects corresponding to any of the above examples, which will not be elaborated here.

[0025] By adopting the technical solution of the present invention, the following technical effects can be achieved: (1) By initializing the main operating system and the secondary operating system and executing the first rendering task and the second rendering task respectively, when the secondary operating system is running well, the rendering rights of some of the first screen information are dynamically transferred to the secondary operating system. When the secondary operating system is abnormal, the third rendering task rights are quickly switched back to the main operating system and an emergency command is executed. This realizes the dynamic allocation of rendering tasks and rapid recovery from abnormalities, and improves the smoothness, stability and safety of the cockpit instrument display. (2) After restarting, the heartbeat signal of the secondary operating system is detected. After confirming that the system has returned to normal, the second rendering task is reallocated and the process returns to step S3. This achieves automatic recovery after an anomaly and intelligent switching of rendering rights, further improving the system's self-healing ability and resource utilization efficiency. (3) A non-transparent layer covering the upper layer is introduced to display the third screen information. During the initialization phase, the main operating system temporarily renders the boot animation, which stops after the secondary operating system is normal, thus achieving a smooth transition during the startup phase. Attached Figure Description

[0026] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. Figure 1 This is a flowchart illustrating a cockpit instrument display method based on rendering rights allocation, provided as an embodiment of the present invention. Detailed Implementation

[0027] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0028] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0029] It should be noted that relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0030] This invention provides a cockpit instrument display method based on rendering rights allocation. The cockpit instrument display method includes the following steps: See Figure 1 As shown, step S1: Initialize the main operating system and the secondary operating system of the target vehicle; Preferably, the main operating system is a Linux system or a QNX system, serving as a stable rendering module and a control decision-making module; the secondary operating system is an Android system, serving as a controlled rendering coprocessor.

[0031] Step S2: Control the main operating system to execute the first rendering task for the first screen information, and control the secondary operating system to execute the second rendering task for the second screen information; Preferably, the first screen information is an easily rendered screen such as a normal or 2D screen, including instrument speed, warning lights, pop-ups, and other 2D animations; the second screen information is a difficult-to-render screen such as a complex animation or a 3D interface, such as dynamic lane lines and 3D car model animations.

[0032] Step S3: Control the main operating system to obtain the running information of the secondary operating system and determine whether the secondary operating system is running well; Step S4: If yes, then determine to transfer the rendering rights of part of the first screen information to the secondary operating system to execute the third rendering task; Preferably, after some initial screen information is transferred to the secondary operating system, such as vehicle speed and hazard lights, important information is rendered by a stable Linux / QNX system. Meanwhile, rendering rights for pop-ups or other 2D animations can be temporarily granted to Android via IPC communication. After Android finishes rendering, the data is directly overlaid onto the virtual screen. This minimizes the load on the Linux / QNX system and ensures reliable operation of the underlying communication.

[0033] Step S5: Control the main operating system to obtain the process information of the secondary operating system in real time, and determine whether the secondary operating system is in an abnormal state based on the process information; Step S6: If yes, then determine that the rendering rights of the third rendering task are transferred to the main operating system, and control the main operating system to execute emergency commands for the secondary operating system.

[0034] By initializing the main operating system and the secondary operating system and executing the first and second rendering tasks respectively, the rendering rights of some first-screen information are dynamically transferred to the secondary operating system when the secondary operating system is running well. When the secondary operating system malfunctions, the rendering rights of the third rendering task are quickly switched back to the main operating system and emergency commands are executed. This achieves dynamic allocation of rendering tasks and rapid recovery from anomalies, improving the smoothness, stability and safety of the cockpit instrument display.

[0035] Furthermore, the cockpit instruments include an upper layer for displaying first screen information and a lower layer covered by the upper layer, the lower layer for displaying second screen information; wherein, when the secondary operating system executes a third rendering task, the first screen information rendered and output by the secondary operating system is displayed on the lower layer.

[0036] Preferably, the cockpit instrument panel is divided into an upper layer and a lower layer. The animation of the upper layer will cover the animation of the lower layer. When the animation of the lower layer cannot be displayed, it will not affect the important animations on the upper layer, such as vehicle speed and warning lights.

[0037] By utilizing a superimposed upper and lower layer display structure for the cockpit instruments, when the secondary operating system takes over the rendering of the first screen information, it is displayed on the lower layer. When the secondary operating system malfunctions, this first screen information returns to the upper layer, avoiding the impact of the secondary operating system's abnormal state. This achieves layered display and seamless integration of the rendering screens of the primary and secondary operating systems.

[0038] Further, step S6 includes: Step S61: Freeze the underlying output buffer of the secondary operating system and extract the last frame of the second rendering task as a backup frame; Step S62: Output the backup frame and display it in the lower layer. Control the main operating system to send a stop rendering command to the secondary operating system, and control the main operating system to restart the secondary operating system.

[0039] By specifying emergency commands, including freezing the secondary operating system's output buffer, extracting the last frame as a backup frame and displaying it in the lower layer, stopping rendering and restarting the secondary operating system, the system achieves frame-saving display and rapid system restart when the secondary operating system malfunctions, preventing black screens or information loss and improving the system's fault tolerance.

[0040] Further, step S62 includes: Step S621: Control the main operating system to send a restart command to the secondary operating system, and detect the heartbeat signal of the secondary operating system within a preset time. Preferably, in this embodiment of the application, the preset time is set to 30 seconds.

[0041] Step S622: If a heartbeat signal of the secondary operating system is detected, it is determined that the secondary operating system has escaped the abnormal state, the secondary operating system is controlled to execute the second rendering task, and it is determined to return to step S3.

[0042] Preferably, the heartbeat signal is detected by means of a watchdog process set on the Linux / QNX side that detects the Android system.

[0043] Preferably, backup frames are continuously displayed before the Android system renders the first frame.

[0044] After restarting, the system detects the heartbeat signal of the secondary operating system, confirms that it has returned to normal, reallocates the second rendering task, and returns to step S3. This achieves automatic recovery after an anomaly and intelligent switching of rendering rights, further improving the system's self-healing ability and resource utilization efficiency.

[0045] Further, step S621 includes: Step S6211: If no heartbeat signal is detected from the secondary operating system, determine that the current number of restarts of the secondary operating system is T=T. ex +1, determine if the number of restarts T is greater than the restart threshold T0; Preferably, in this embodiment of the application, the restart threshold is 3 times.

[0046] Step S6212: If yes, then control the main operating system to stop sending reboot commands to the secondary operating system; Step S6213: If not, control the main operating system to resend the restart command to the secondary operating system; Among them, T ex This represents the number of restarts before the last restart, and T ex The initial value is 0.

[0047] By introducing a restart count mechanism and a restart threshold T0, the secondary operating system is prevented from falling into an infinite restart loop, thus preventing system resource exhaustion and improving the security and reliability of exception handling.

[0048] Further, step S3 includes: Step S31: Obtain the running memory of the secondary operating system and determine whether the running memory is greater than the first threshold; Preferably, the running memory includes the CPU and memory, and in this embodiment of the application, the first threshold is preferably 60%.

[0049] Step S32: If not, then the secondary operating system is determined to be in good working order.

[0050] By monitoring the secondary operating system's running memory and comparing it with a first threshold, it determines whether the system is in a good running state, providing an objective and quantifiable basis for rendering right transfer judgment, thus improving the accuracy and rationality of dynamic allocation.

[0051] Further, step S5 includes: Step S51: Control the main operating system to detect whether the heartbeat signal of the secondary operating system has timed out; Preferably, a timeout is determined when no heartbeat signal is received for 500 consecutive ms.

[0052] If so, the secondary operating system is determined to be in an abnormal state; Alternatively, step S52: Obtain the running memory of the secondary operating system and determine whether the running memory is greater than the second threshold; Preferably, in this embodiment of the application, the second threshold is 75%.

[0053] If so, the secondary operating system is determined to be in an abnormal state.

[0054] By combining the heartbeat signal timeout and the second threshold for running memory to make a dual judgment mechanism, the abnormal status of the secondary operating system is comprehensively evaluated, which improves the comprehensiveness and timeliness of anomaly detection and reduces the risk of misjudgment.

[0055] Furthermore, the cockpit instruments include a non-transparent layer covering the upper layer, the non-transparent layer being used to display third-view information; step S1 includes: Step S11: Control the main operating system to execute the fourth rendering task for the third screen information, and control the main operating system to output the third screen information to the non-transparent layer; Preferably, the third screen information is the boot animation.

[0056] Preferably, during the startup phase of the main operating system and the secondary operating system, the Linux / QNX system can start immediately, while the Android system is not yet ready. At this time, the rendering rights of the boot animation are forcibly allocated to the Linux / QNX system; the Linux / QNX system quickly loads and plays the boot animation stored locally in a high-efficiency format (such as PNG sequence, RGB565raw, etc.).

[0057] Preferably, the non-transparent layer completely covers the upper and lower layers, so that when the non-transparent layer displays the third screen information, the first screen information and the second screen information cannot be displayed.

[0058] Step S12: Control the main operating system to detect the heartbeat signal of the secondary operating system; Step S13: If a heartbeat signal from the secondary operating system is detected, control the primary operating system to stop executing the fourth rendering task.

[0059] A non-transparent layer is introduced to display third-screen information. During the initialization phase, the main operating system temporarily renders the boot animation, which stops after the secondary operating system is running normally, thus achieving a smooth transition during the startup phase.

[0060] Furthermore, the first screen information is a 2D screen; and / or the second screen information is a 3D screen.

[0061] It aligns with typical cockpit instrument application scenarios, allowing the main operating system to focus on lightweight real-time rendering while the secondary operating system handles complex graphics, thus improving the rationality of task allocation and performance optimization.

[0062] On the other hand, the present invention also provides a vehicle, including: a cockpit instrument display method based on rendering rights allocation as in any of the above examples; a main operating system being a Linux system or a QNX system; and / or a secondary operating system being an Android system.

[0063] The technical effects that can be achieved in any of the above examples will not be elaborated here.

[0064] For ease of understanding, this application provides a dynamic rendering management embodiment based on the Qualcomm platform, which details the specific implementation of dynamically allocating rendering rights on demand between Linux / QNX as the master control terminal and the Android system on the Hypervisor virtualization cockpit platform of Qualcomm SA8775 SoC, as follows: During the startup phase within 3 seconds of system power-on, the Linux system starts first, detects that the Android system is not ready, forcibly assigns rendering rights to Linux / QNX for rendering, and displays the Linux-rendered boot animation on the instrument panel (DRM card0).

[0065] In normal operating mode, the GPU on the Android side completes the 3D scene rendering and overlays some 2D interface rendering; the 3D scene rendered by Android and the overlaid 2D interface are displayed on the lower layer of the instrument panel; the 2D instrument panel rendered by Linux is output to the upper layer of the instrument panel.

[0066] The Android system is monitored in three aspects, as follows: Heartbeat monitoring: First, the heartbeat signal is monitored through the watchdog process of the Linux system, with a timeout threshold set to 500ms; Process monitoring: Detects the status of the SurfaceFlinger process in the Android system (polling once per second) and checks for process crashes; Resource monitoring: Continuously monitor Android CPU / memory usage, with a second threshold set at 75%.

[0067] Emergency switchover procedure when an Android system anomaly is detected: Stop Android rendering and use a static spare frame as the base image; and trigger Linux to render the entire 2D instrument interface; the entire switching process is completed within 2 frame cycles (<32ms), and the user perceives a brief lag or no lag.

[0068] Then, an Android exception notification is sent to the user (displayed via a status bar icon).

[0069] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A method for displaying cockpit instruments based on rendering rights allocation, characterized in that, The cockpit instrument display method includes: Step S1: Initialize the main operating system and secondary operating system of the target vehicle; Step S2: Control the main operating system to execute the first rendering task for the first screen information, and control the secondary operating system to execute the second rendering task for the second screen information; Step S3: Control the main operating system to obtain the running information of the secondary operating system and determine whether the secondary operating system is in a good running state; Step S4: If yes, then determine that the rendering rights of part of the first screen information will be transferred to the secondary operating system to execute the third rendering task; Step S5: Control the main operating system to obtain the process information of the secondary operating system in real time, and determine whether the secondary operating system is in an abnormal state based on the process information; Step S6: If yes, then determine that the rendering rights of the third rendering task are transferred to the main operating system, and control the main operating system to execute emergency commands for the secondary operating system.

2. The display method according to claim 1, characterized in that, The cockpit instrument panel includes an upper layer for displaying first screen information and a lower layer covered by the upper layer, wherein the lower layer is used to display second screen information; When the secondary operating system executes the third rendering task, the first screen information rendered and output by the secondary operating system is displayed on the lower layer.

3. The display method according to claim 2, characterized in that, The control of the primary operating system to execute emergency commands for the secondary operating system includes: Freeze the underlying output buffer of the secondary operating system and extract the last frame of the second rendering task as a backup frame; The backup frame is output and displayed in the lower layer, the main operating system is controlled to issue a stop rendering command to the secondary operating system, and the main operating system is controlled to restart the secondary operating system.

4. The display method according to claim 3, characterized in that, The control of the primary operating system to restart the secondary operating system includes: The main operating system is controlled to send a restart command to the secondary operating system, and the heartbeat signal of the secondary operating system is detected within a preset time. If a heartbeat signal of the secondary operating system is detected, it is determined that the secondary operating system has escaped the abnormal state, and the secondary operating system is controlled to execute the second rendering task, and it is determined to return to step S3.

5. The display method according to claim 4, characterized in that, The process of controlling the main operating system to send a restart command to the secondary operating system and detecting the heartbeat signal of the secondary operating system within a preset time includes: If no heartbeat signal is detected from the secondary operating system, then the current number of restarts of the secondary operating system is determined to be T=T. ex +1, determine whether the number of restarts T is greater than the restart threshold T0; If so, then the main operating system will stop sending restart commands to the secondary operating system; If not, then control the main operating system to resend the restart command to the secondary operating system; Among them, T ex This represents the number of restarts before the last restart, and T ex The initial value is 0.

6. The display method according to claim 1, characterized in that, The step of controlling the main operating system to obtain the running information of the secondary operating system and determining whether the secondary operating system is in a good running state includes: Obtain the running memory of the secondary operating system and determine whether the running memory is greater than a first threshold; If not, the secondary operating system is determined to be in good working order.

7. The display method according to claim 6, characterized in that, The step of controlling the main operating system to obtain the process information of the secondary operating system in real time, and determining whether the secondary operating system is in an abnormal state based on the process information, includes: The main operating system is controlled to detect whether the heartbeat signal of the secondary operating system has timed out. If so, the secondary operating system is determined to be in an abnormal state; or Obtain the running memory of the secondary operating system and determine whether the running memory is greater than a second threshold; If so, the secondary operating system is determined to be in an abnormal state.

8. The display method according to claim 2, characterized in that, The cockpit instrument panel includes a non-transparent layer covering the upper layer, the non-transparent layer being used to display third-view information; The initialization of the target vehicle's main operating system and secondary operating system includes: The main operating system is controlled to execute a fourth rendering task for the third screen information, and the main operating system is controlled to output the third screen information to the non-transparent layer; The main operating system is controlled to detect the heartbeat signal of the secondary operating system. If a heartbeat signal from the secondary operating system is detected, the primary operating system is controlled to stop executing the fourth rendering task.

9. The display method according to claim 1, characterized in that, The first image information is a 2D image; and / or The second image is a 3D image.

10. A vehicle, wherein the vehicle employs a cockpit instrument display method based on rendering rights allocation as described in any one of claims 1 to 9, characterized in that, The main operating system is a Linux system or a QNX system; and / or The secondary operating system is Android.

Images