Method and system for recovering touch anomaly of vehicle-mounted display screen, electronic device, and medium

Abstract

Disclosed in the present invention are a method and system for recovering a touch anomaly of a vehicle-mounted display screen, a device, and a medium. The method comprises: when it is detected that a touch anomaly occurs in a vehicle-mounted display screen, acquiring a user operation instruction and judging whether a central control system can normally respond to the user operation instruction; if the central control system can normally respond to the user operation instruction, determining that a touch drive of the vehicle-mounted display screen fails to be loaded; monitoring whether a backup camera drive is successfully loaded, and when it is monitored that the backup camera drive fails to be loaded, performing reloading by means of a communication bus corresponding to the backup camera drive; and when the number of reloading times reaches a preset number, releasing an occupied resource by means of the communication bus corresponding to the backup camera drive, so that the central control system resets and reloads the touch drive, wherein the backup camera drive and the central control system communicate with an in-vehicle infotainment system by means of different communication buses. The present invention ensures stable operation of the vehicle-mounted display screen and improves the driving safety and driving experience of users, and thus can be applied to the technical field of vehicle control.

Description

Method, system, electronic device and medium for recovering abnormal touch of vehicle display screen Technical Field

[0001] The present invention relates to the field of vehicle control technology, and in particular to a method, system, electronic device and medium for recovering from touch anomaly on a vehicle display screen. Background Art

[0002] Currently, automobiles are developing towards connectivity, automation, sharing, and electrification, all of which are oriented towards intelligence. Intelligence revolutionized the mobile phone industry 15 years ago and is now repeating itself in the automotive industry, making the automotive industry the world's most dynamic market. A key manifestation of automotive intelligence is the smart cockpit. This significantly enhances the intelligent experience and is becoming a key factor influencing car purchases. As consumers increasingly prioritize smart cockpits, their penetration into the automotive market is accelerating, and they are expected to become standard features in smart cars. Data shows that the global penetration rate of new cars equipped with smart cockpit technology will increase from 38.4% in 2019 to 59.4% in 2025, with the penetration rate in my country even higher, reaching 75.9% by 2025. The evolution of smart cockpits will also accelerate the advancement of automotive intelligence and drive the continued development of the in-vehicle display market. As vehicles become more intelligent, in-vehicle display panels are becoming higher in resolution, larger in size, and more numerous, with designs becoming more diverse, technologies more diverse, and functionally integrated.

[0003] In-vehicle displays are human-computer interaction devices. When a user touches the screen, it identifies the touch point, movement direction, and speed, and transmits the signal to the vehicle computer, enabling interaction between the user and the vehicle computer. In-vehicle displays should feature smooth touch and timely response, allowing users to drive more safely. However, in actual driving scenarios, occasional touch failures or abnormalities are inevitable (such as abnormal AVM driver loading, resulting in touch failure and non-recovery), which greatly affects the user's driving safety and experience.

[0004] Explanation of terms:

[0005] Bootloader: A boot program (also called a boot loader or boot program) located on a computer or other computer application. It is the program that boots the operating system. The boot program startup method and program vary depending on the application model. Simply put, the bootloader is a small program that runs before the operating system kernel runs. Through this small program, we can initialize hardware devices and establish a memory space map, thus bringing the system's hardware and software environment to a suitable state, preparing the correct environment for the final call to the operating system kernel.

[0006] Kernel: It is the most basic part of the operating system and the core of the operating system. It is the first layer of software expansion based on hardware, providing the most basic functions of the operating system. It is the foundation of the operating system and is also responsible for managing the system's processes, memory, kernel architecture, device drivers, files, and network systems, determining the system's performance and stability.

[0007] Hypervisor: A layer of software that runs between the physical server and the operating system, allowing multiple operating systems and applications to share a set of underlying physical hardware. A hypervisor can be considered the "meta" operating system in a virtual environment, coordinating access to all physical devices and virtual machines on the server, hence its name (virtual machine monitor). The hypervisor is the core of all virtualization technologies, and its fundamental function is to support the non-interruptive migration of multiple workloads. When a server boots up and executes the hypervisor, it allocates an appropriate amount of memory, CPU, network, and disk resources to each virtual machine and loads the client operating systems of all virtual machines.

[0008] DDR: Double data rate synchronous dynamic random access memory.

[0009] GPIO: General Purpose I / O Ports, which are general-purpose input / output ports. In layman's terms, these are pins that can output high and low levels or read the status of the pins - whether it is a high level or a low level.

[0010] I2C: Integrated Circuit Bus, which is a serial communication bus mainly used for communication transmission.

[0011] Summary of the Invention

[0012] The purpose of the present invention is to solve one of the technical problems existing in the prior art to at least a certain extent.

[0013] To this end, one purpose of an embodiment of the present invention is to provide a method for recovering touch abnormalities of a vehicle display screen. The method can quickly and automatically repair the vehicle display screen when it detects that the touch abnormality is caused by abnormal touch drive loading, thereby ensuring the stable operation of the vehicle display screen and improving the user's driving safety and driving experience.

[0014] Another object of an embodiment of the present invention is to provide a vehicle-mounted display screen touch abnormality recovery system.

[0015] In order to achieve the above technical objectives, the technical solutions adopted by the embodiments of the present invention include:

[0016] In one aspect, an embodiment of the present invention provides a method for recovering from touch abnormality of a vehicle display screen, comprising the following steps:

[0017] When a touch abnormality is detected on the vehicle display screen, the user operation instruction is obtained and it is determined whether the central control system can normally respond to the user operation instruction;

[0018] When the central control system can respond to the user operation instruction normally, it is determined that the touch driver loading of the vehicle display screen fails;

[0019] Monitoring whether the reversing image driver is loaded successfully, and when monitoring that the reversing image driver fails to load, retrying the loading through the communication bus corresponding to the reversing image driver;

[0020] When the loading retry reaches a preset number of times, the occupied resources are released through the communication bus corresponding to the reversing image driver, so that the central control system resets and reloads the touch driver;

[0021] The reversing image driver and the central control system communicate with the vehicle system via different communication buses.

[0022] Furthermore, in one embodiment of the present invention, the step of obtaining the user operation instruction and determining whether the central control system can normally respond to the user operation instruction specifically includes:

[0023] Acquiring a user operation instruction, where the user operation instruction includes at least one of a voice instruction, a steering wheel instruction, and a key instruction;

[0024] Inputting the user operation instruction into the central control system and obtaining a response action of the central control system;

[0025] The response action is compared with the user operation instruction, and it is determined whether the central control system can normally respond to the user operation instruction based on the comparison result.

[0026] Furthermore, in one embodiment of the present invention, the step of monitoring whether the reversing image driver is loaded successfully and retrying the loading through the communication bus corresponding to the reversing image driver when the reversing image driver fails to load is monitored specifically includes:

[0027] Obtaining a preset monitoring period, monitoring the reversing image driver according to the monitoring period, and determining whether the reversing image driver is loaded successfully;

[0028] When it is determined that the reversing image driver fails to load, a retry instruction of the vehicle system is received through the communication bus corresponding to the reversing image driver, and the reversing image driver is loaded and retried.

[0029] Furthermore, in one embodiment of the present invention, when the number of loading retries reaches a preset number, the step of releasing occupied resources via the communication bus corresponding to the reversing image driver so that the central control system resets and reloads the touch driver specifically includes:

[0030] Counting the loading retries of the reversing image driver;

[0031] When the reversing image driver's loading retries reach the preset number of times, the communication resources of the vehicle system occupied are released through the communication bus corresponding to the reversing image driver, and then the serial deserializer is initialized and the touch driver is reset and reloaded through the central control system.

[0032] Furthermore, in one embodiment of the present invention, the vehicle-mounted display screen touch abnormality recovery method further includes a step of starting the vehicle-mounted display screen, which specifically includes:

[0033] The microcontroller detects a power-on signal and outputs an enable signal to a system-side power supply when the power-on signal is detected, so that the system-side power supply supplies power to the system on chip;

[0034] The system on chip is started, and a boot program is loaded and run through the system on chip to initialize the vehicle display screen, thereby establishing a memory space mapping diagram.

[0035] Furthermore, in one embodiment of the present invention, the step of loading and running the startup program specifically includes:

[0036] Initialize the hardware code;

[0037] Reserving a first readable and writable RAM space, and testing an address of the first RAM space;

[0038] Set the stack pointer and modify the register address to the first RAM space;

[0039] Check the memory map of the vehicle system and load the kernel hardware and root file system;

[0040] Initializing the double data rate synchronous dynamic random access memory by the boot program and loading a program into the double data rate synchronous dynamic random access memory;

[0041] Start the Linux Kernel and mount system files;

[0042] Starting the system driver of the central control system and loading the reversing image driver;

[0043] Load the touch driver, start the application, and read and write the system log.

[0044] Furthermore, in one embodiment of the present invention, the step of initializing the hardware code specifically includes:

[0045] Shield all interrupt services;

[0046] Set the CPU operating speed and clock frequency;

[0047] Initialize the random access memory and close the instruction cache and data cache inside the CPU.

[0048] On the other hand, an embodiment of the present invention provides a vehicle-mounted display screen touch abnormality recovery system, comprising:

[0049] The central control system response judgment module is used to obtain user operation instructions and judge whether the central control system can respond normally to the user operation instructions when a touch abnormality is detected on the vehicle display screen;

[0050] a touch driver loading judgment module, configured to determine that the touch driver loading of the vehicle display screen has failed when the central control system can normally respond to the user operation instruction;

[0051] A reversing image driver monitoring module is used to monitor whether the reversing image driver is loaded successfully. When it is monitored that the reversing image driver fails to load, the reversing image driver is reloaded through the communication bus corresponding to the reversing image driver.

[0052] A touch driver reset loading module, configured to release occupied resources via the communication bus corresponding to the reversing image driver when a preset number of loading retries is reached, so that the central control system resets and reloads the touch driver;

[0053] The reversing image driver and the central control system communicate with the vehicle system via different communication buses.

[0054] On the other hand, an embodiment of the present invention provides an electronic device, which includes a memory, a processor, a program stored on the memory and runnable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the vehicle display screen touch abnormality recovery method as described above is implemented.

[0055] On the other hand, an embodiment of the present invention also provides a storage medium, which is a computer-readable storage medium for computer-readable storage. The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the vehicle display screen touch abnormality recovery method as described above.

[0056] The advantages and benefits of the present invention will be described in part in the following description and will become apparent from the following description or learned through practice of the present invention:

[0057] When an embodiment of the present invention detects a touch anomaly on the vehicle display screen, it obtains user operation instructions and determines whether the central control system can respond to the user operation instructions normally. When the central control system can respond to the user operation instructions normally, it determines that the touch driver loading of the vehicle display screen has failed, and then monitors whether the reversing image driver has been loaded successfully. When it is monitored that the reversing image driver has failed to load, it retry the loading through the communication bus corresponding to the reversing image driver. When the number of loading retries reaches a preset number, the occupied resources are released through the communication bus corresponding to the reversing image driver, so that the central control system resets and reloads the touch driver. The embodiment of the present invention can quickly and automatically repair the vehicle display screen touch anomaly caused by the abnormal loading of the touch driver, thereby ensuring the stable operation of the vehicle display screen and improving the user's driving safety and driving experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following introduction is made to the drawings required for use in the embodiments of the present invention. It should be understood that the drawings introduced below are only for the convenience of clearly describing some embodiments of the technical solutions of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative work.

[0059] FIG1 is a flowchart of a method for recovering from touch abnormality of a vehicle display screen provided by an embodiment of the present invention;

[0060] FIG2 is a flowchart of step S101 according to an embodiment of the present invention;

[0061] FIG3 is a flowchart of step S103 provided by an embodiment of the present invention;

[0062] FIG4 is a flowchart of step S104 provided by an embodiment of the present invention;

[0063] FIG5 is a flowchart of steps for starting a vehicle display screen according to an embodiment of the present invention;

[0064] FIG6 is a flowchart of step S202 according to an embodiment of the present invention;

[0065] FIG7 is a flowchart of step S2021 according to an embodiment of the present invention;

[0066] FIG8 is a schematic diagram of the communication connection between the AVM controller, central control display, instrument display and host according to an embodiment of the present invention;

[0067] FIG9 is a schematic structural diagram of a vehicle display screen touch abnormality recovery system provided by an embodiment of the present invention;

[0068] FIG10 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention;

[0069] FIG11 is a schematic diagram of the structure of a storage medium provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0070] The embodiments of the present invention are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements with the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present application, and are not to be construed as limitations on the present application. It should be noted that, although the functional modules are divided in the system schematic and the logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in a different order than the module division in the system schematic or the order in the flow chart. For the step numbers in the following embodiments, they are only provided for the convenience of explanation, and no limitation is placed on the order between the steps. The execution order of each step in the embodiment can be adaptively adjusted according to the understanding of those skilled in the art.

[0071] In the description of the present invention, the meaning of "a plurality" is two or more. If there is a description of "first" or "second", it is only used to distinguish technical features and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features. In addition, unless otherwise defined, all technical and scientific terms used in this document have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used in this document are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0072] The vehicle display screen touch anomaly recovery method provided in the embodiments of the present application can be applied to a terminal, can be applied to a server side, and can also be software running on a terminal or a server side. In some embodiments, the terminal can be a smartphone, a tablet computer, a laptop computer, a desktop computer, a set-top box, etc.; the server side can be configured as an independent physical server, or as a server cluster or distributed system consisting of multiple physical servers, or as a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms; the software can be an application that implements the vehicle display screen touch anomaly recovery method, etc., but is not limited to the above forms.

[0073] The present application can be used in many general or special computer system environments or configurations. For example: personal computers, server computers, handheld or portable devices, tablet devices, multi-processor systems, microprocessor-based systems, set-top boxes, programmable consumer electronic devices, network PCs, minicomputers, mainframe computers, distributed computing environments including any of the above systems or devices, and the like. The present application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present application can also be practiced in distributed computing environments in which tasks are performed by remote processing devices connected via a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.

[0074] It should be noted that in each specific embodiment of the present application, when it comes to the need to perform relevant processing based on data related to the user's identity or characteristics, such as user information, user behavior data, user historical data, and user location information, the user's permission or consent will be obtained first, and the collection, use, and processing of such data will comply with the relevant laws, regulations, and standards of the relevant countries and regions. In addition, when the embodiment of the present application needs to obtain the user's sensitive personal information, the user's separate permission or consent will be obtained through a pop-up window or by jumping to a confirmation page. After clearly obtaining the user's separate permission or consent, the necessary user-related data for the normal operation of the embodiment of the present application will be obtained.

[0075] The embodiment of the present invention can solve the problem of touch abnormality that occurs when users use the car display screen. When the car computer detects that the display screen touch abnormality is caused by the failure of touch driver loading, the system will perform self-recovery and restore the touch function of the screen within a few seconds, avoiding the user experience and driving safety affected by the screen touch problem.

[0076] FIG1 is a flowchart of a method for recovering a vehicle display screen from a touch abnormality according to an embodiment of the present invention. Referring to FIG1 , an embodiment of the present invention provides a method for recovering a vehicle display screen from a touch abnormality, specifically comprising the following steps:

[0077] S101: When a touch abnormality is detected on the vehicle display screen, a user operation instruction is obtained and it is determined whether the central control system can respond to the user operation instruction normally.

[0078] FIG2 is a flowchart of step S101 according to an embodiment of the present invention. Referring to FIG2 , as an optional embodiment, the step of obtaining a user operation instruction and determining whether the central control system can normally respond to the user operation instruction specifically includes:

[0079] S1011. Obtaining a user operation instruction, where the user operation instruction includes at least one of a voice instruction, a steering wheel instruction, and a key instruction;

[0080] S1012: Input the user operation instruction into the central control system and obtain the response action of the central control system;

[0081] S1013: Compare the response action with the user operation instruction, and determine whether the central control system can normally respond to the user operation instruction based on the comparison result.

[0082] Specifically, when a touch abnormality occurs on the screen, we must first determine whether the central control system can respond normally to the user's commands, such as voice commands and related command actions of the steering wheel buttons. If it can be recognized normally, it means that the vehicle system is normal and it is determined to be a touch abnormality problem.

[0083] S102: When the central control system can normally respond to the user's operation instruction, it is determined that the touch driver loading of the vehicle display screen fails.

[0084] Specifically, if a screen touch anomaly is detected, in an actual vehicle project (E115), the touch anomaly is primarily caused by an abnormal loading of the AVM driver (reversing image driver), resulting in touch failure. The actual vehicle system logs indicate that during the AVM driver loading process, the remote serializer cannot be accessed, affecting the initialization timing of the serializer-deserializer chip, resulting in a failure in touch driver loading.

[0085] During the loading process of the touch driver, the touch reset needs to be controlled because the touch reset control pin is controlled by the GPIO (through the IO port) of the deserializer. If the touch driver is loaded while the deserializer is still in the initialization process, it will result in the inability to apply for the GPIO (through the IO port) control resource for touch reset, causing the touch driver loading to fail.

[0086] Since the AVM controller and the central control / passenger driver serial deserializer chips are mounted on the same I2C bus, when an exception occurs in the AVM controller and an access exception occurs, the I2C will perform a retry process, which will occupy this part of the resources and affect the initialization timing of the central control and passenger driver serial deserializers, thereby causing screen touch abnormalities.

[0087] Based on the problems described above, the embodiments of the present invention are optimized as follows:

[0088] 1) Modify the I2C communication line of the AVM controller (i.e., the reversing image driver) and configure a separate communication line for the AVM controller so as not to occupy the communication link of the deserializer of other screens;

[0089] 2) Add a monitoring mechanism to monitor the touch driver loading success every 1 second. If loading failure is detected, the touch driver is reloaded. The I2C will retry three times. After the number of retries is reached, the occupied resources will be released to avoid touch anomalies caused by resource occupation during the initialization sequence of the serial deserializer.

[0090] S103 , monitoring whether the reversing image driver is loaded successfully. When monitoring that the reversing image driver fails to load, retrying the loading via the communication bus corresponding to the reversing image driver.

[0091] FIG3 is a flowchart of step S103 according to an embodiment of the present invention. Referring to FIG3 , as an optional embodiment, monitoring whether the reversing image driver is loaded successfully, and when monitoring that the reversing image driver fails to load, retrying the reversing image driver through the communication bus corresponding to the reversing image driver is performed, which specifically includes:

[0092] S1031, obtaining a preset monitoring period, monitoring the reversing image driver according to the monitoring period, and determining whether the reversing image driver is loaded successfully;

[0093] S1032: When it is determined that the reversing image driver fails to load, a retry instruction from the vehicle system is received through a communication bus corresponding to the reversing image driver, and the reversing image driver is loaded and retried.

[0094] S104: When the number of loading retries reaches a preset number, the communication bus corresponding to the reversing image driver releases occupied resources, so that the central control system resets and reloads the touch driver;

[0095] Among them, the reversing image drive and central control system communicate with the vehicle system through different communication buses.

[0096] FIG4 is a flowchart of step S104 according to an embodiment of the present invention. Referring to FIG4 , as an optional embodiment, when the number of loading retries reaches a preset number, the communication bus corresponding to the reversing image driver releases occupied resources, so that the central control system resets and reloads the touch driver. The steps specifically include:

[0097] S1041. Counting the number of reload retries of the reversing image driver.

[0098] S1042. When the reversing image driver's loading retries reach a preset number, the communication resources of the vehicle system occupied by the reversing image driver are released through the communication bus corresponding to the reversing image driver, and then the serial deserializer is initialized and the touch driver is reset and reloaded through the central control system.

[0099] Specifically, when it is clear that the screen touch is abnormal, during the loading of the AVM driver, due to the inability to access the remote serializer, which affects the initialization timing of the serial deserialization chip, a monitoring mechanism for exception handling is added, and when it cannot be recovered after 3 retries, the self-recovery mechanism is started to restore the screen touch abnormality; for when multiple controllers are on the same I2C bus, the embodiment of the present invention avoids the AVM controller and the display screen being on the same bus in design, and the AVM image has a separate I2C channel at the initial design stage to avoid abnormal access occupying resources.

[0100] As shown in Figure 8, this is a schematic diagram of the communication connection between the AVM controller, central control display, instrument display and host provided in an embodiment of the present invention. It can be seen that the AVM controller and the on-board display screen of the central control / instrument in the embodiment of the present invention use different communication buses to communicate with the host of the vehicle system, avoiding resource occupation.

[0101] FIG5 is a flowchart of a step of starting a vehicle display screen according to an embodiment of the present invention. Referring to FIG5 , as an optional embodiment, the vehicle display screen touch abnormality recovery method further includes the step of starting the vehicle display screen, which specifically includes:

[0102] S201, detecting a power-on signal by a microcontroller, and when the power-on signal is detected, outputting an enable signal to a system-side power supply, so that the system-side power supply supplies power to the system on chip;

[0103] S202 , starting the system on chip, and loading and running a boot program through the system on chip to initialize the vehicle display screen, and then establishing a memory space mapping diagram.

[0104] Specifically, first, after the microcontroller MCU detects the power-on signal, it outputs an enable signal to turn on the power supply on the system side and supply power to the system on chip SOC; after the SOC detects the power supply, the SOC starts to start; the Bootloader is loaded and run, the hardware devices are initialized, and a mapping map of the memory space is established.

[0105] FIG6 is a flowchart of step S202 according to an embodiment of the present invention. Referring to FIG6 , as an optional embodiment, the step of loading and running the startup program specifically includes:

[0106] S2021. Initialize the hardware code;

[0107] S2022: reserve a first readable and writable RAM space, and test the address of the first RAM space;

[0108] S2023, set the stack pointer and modify the register address to the first RAM space;

[0109] S2024: Detect the memory map of the vehicle system and load the kernel hardware and root file system;

[0110] S2025, initializing the double data rate synchronous dynamic random access memory by starting the boot program, and loading the program into the double data rate synchronous dynamic random access memory;

[0111] S2026. Start the Linux Kernel and mount system files.

[0112] S2027. Start the system driver of the central control system and load the reversing image driver;

[0113] S2028. Load the touch driver, start the application, and read and write the system log.

[0114] Specifically, loading the Bootloader is divided into two stages, as follows:

[0115] 1) Phase 1:

[0116] 1. First initialize the hardware code:

[0117] 2. After hardware initialization, reserve readable and writable RAM space for loading phase 2, and test the read and write RAM space addresses

[0118] 3. Set the stack pointer and jump to the Bootloader stage 2 by modifying the PC register to point to the appropriate address.

[0119] 2) Phase 2:

[0120] 1. In order to output I / O information to the end user, it is also necessary to initialize hardware devices such as timers;

[0121] 2. Check the memory map within the vehicle system and load the kernel hardware and root file system;

[0122] 3. Set the kernel startup parameters and call it;

[0123] 4. Bootloader initializes DDR and loads the program into DDR;

[0124] 5. After DDR is loaded successfully, start the Hypervisor;

[0125] 6. Start the Linux Kernel and mount system files;

[0126] 7. Start the serial / deserializer drivers for the central control, instrument panel, and co-pilot panel, and load the AVM (reversing image) driver at the same time;

[0127] 8. Load the touch drivers for the central control and co-pilot screens, start applications, and read and write system logs.

[0128] FIG7 is a flowchart of step S2021 according to an embodiment of the present invention. Referring to FIG7 , as an optional implementation, the step of initializing the hardware code specifically includes:

[0129] S20211, shield all interrupt services;

[0130] S20212. Set the CPU operating speed and clock frequency;

[0131] S20213. Initialize the random access memory and close the instruction cache and data cache inside the CPU.

[0132] Specifically, the specific process of initializing the hardware code is as follows:

[0133] a. Shield all interrupts: The BootLoader execution process does not have to respond to any interrupts. It is usually the responsibility of the operating system driver to provide interrupt services. Interrupt shielding can be done by writing to the CPU's interrupt mask register or status register.

[0134] b. Set the CPU speed and clock frequency.

[0135] c. RAM initialization: Correctly set the function registers of the system memory controller.

[0136] d. Disable the CPU internal instruction / data cache.

[0137] The above describes the method steps of the embodiment of the present invention. It is understandable that the embodiment of the present invention can quickly and automatically repair the abnormal touch of the vehicle display screen when it detects abnormal touch driver loading, thereby ensuring the stable operation of the vehicle display screen and improving the user's driving safety and driving experience.

[0138] FIG9 is a schematic diagram of the structure of a vehicle display screen touch abnormality recovery system provided by an embodiment of the present invention. Referring to FIG9 , an embodiment of the present invention provides a vehicle display screen touch abnormality recovery system, comprising:

[0139] The central control system response judgment module is used to obtain user operation instructions and determine whether the central control system can respond normally to user operation instructions when a touch abnormality is detected on the vehicle display screen;

[0140] The touch driver loading judgment module is used to determine that the touch driver loading of the vehicle display screen has failed when the central control system can respond to user operation instructions normally;

[0141] The reversing image driver monitoring module is used to monitor whether the reversing image driver is loaded successfully. When it is detected that the reversing image driver fails to load, the reversing image driver is reloaded through the communication bus corresponding to the reversing image driver.

[0142] The touch driver reset loading module is used to release the occupied resources through the communication bus corresponding to the reversing image driver when the loading retry reaches the preset number of times, so that the central control system can reset and reload the touch driver;

[0143] Among them, the reversing image drive and central control system communicate with the vehicle system through different communication buses.

[0144] The contents of the above method embodiments are all applicable to the present system embodiments. The functions specifically implemented by the present system embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0145] An embodiment of the present invention further provides an electronic device comprising: a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for enabling communication between the processor and the memory. When the program is executed by the processor, the aforementioned method for recovering from an abnormal touch screen condition on a vehicle display screen is implemented. The electronic device can be any intelligent terminal, including a tablet computer and an in-vehicle computer.

[0146] FIG10 is a schematic diagram of the hardware structure of an electronic device provided by an embodiment of the present invention. Referring to FIG10 , an embodiment of the present invention provides an electronic device, including:

[0147] The processor 1001 may be implemented as a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is configured to execute relevant programs to implement the technical solutions provided by the embodiments of the present invention.

[0148] The memory 1002 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 1002 and is called by the processor 1001 to execute the vehicle display screen touch abnormality recovery method of the embodiment of the present invention;

[0149] Input / output interface 1003, used to implement information input and output;

[0150] Communication interface 1004, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);

[0151] Bus 1005 , which transmits information between various components of the device (e.g., processor 1001 , memory 1002 , input / output interface 1003 , and communication interface 1004 );

[0152] The processor 1001 , the memory 1002 , the input / output interface 1003 and the communication interface 1004 are connected to each other in communication within the device via a bus 1005 .

[0153] As shown in Figure 11, it is a structural schematic diagram of the storage medium provided by an embodiment of the present invention. Referring to Figure 11, an embodiment of the present invention also provides a storage medium, which is a computer-readable storage medium used for computer-readable storage. The storage medium stores one or more programs 1101, and the one or more programs 1101 can be executed by one or more processors to implement the above-mentioned vehicle display screen touch abnormality recovery method.

[0154] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0155] Embodiments of the present invention further disclose a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the method shown in FIG1 .

[0156] In some optional embodiments, the function / operation mentioned in the block diagram may not occur in the order mentioned in the operation diagram. For example, depending on the function / operation involved, the two boxes shown in succession can actually be executed substantially simultaneously or the above-mentioned boxes can sometimes be executed in reverse order. In addition, the embodiment presented and described in the flow chart of the present invention is provided in an exemplary manner for the purpose of providing a more comprehensive understanding of the technology. The disclosed method is not limited to the operation and logic flow presented herein. Optional embodiments are contemplated in which the order of the various operations is changed and the sub-operations described as a part of a larger operation are performed independently.

[0157] In addition, although the present invention is described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the above-mentioned functions and / or features can be integrated into a single physical device and / or software module, or one or more functions and / or features can be implemented in separate physical devices or software modules. It is also understood that a detailed discussion of the actual implementation of each module is not necessary for understanding the present invention. More specifically, given the properties, functions, and internal relationships of the various functional modules in the devices disclosed herein, the actual implementation of the module will be understood within the routine skills of an engineer. Therefore, a person skilled in the art can implement the present invention set forth in the claims using ordinary skills without undue experimentation. It is also understood that the specific concepts disclosed are merely illustrative and are not intended to limit the scope of the present invention, which is determined by the full scope of the appended claims and their equivalents.

[0158] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the above methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, and other media that can store program code.

[0159] The logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing the logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device). For purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0160] More specific examples (a non-exhaustive list) of computer-readable media include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk cartridge (magnetic devices), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable media on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, deciphering, or processing in another suitable manner as necessary, and then stored in a computer memory.

[0161] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above-described embodiments, multiple steps or methods can be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one of the following technologies known in the art or a combination thereof can be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application-specific integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0162] In the above description of this specification, reference to the terms "one embodiment / example," "another embodiment / example," or "certain embodiments / examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0163] While embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions, and variations may be made to the embodiments without departing from the principles and spirit of the invention, and that the scope of the invention is defined by the claims and their equivalents.

[0164] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without violating the spirit of the present invention. These equivalent modifications or substitutions are all included in the scope defined by the claims of this application.

Claims

1. A method for recovering from abnormal touch of a vehicle display screen, characterized in that: The following steps are involved: When a touch abnormality is detected on the vehicle display screen, the user operation instruction is obtained and it is determined whether the central control system can normally respond to the user operation instruction; When the central control system can respond to the user operation instruction normally, it is determined that the touch driver loading of the vehicle display screen fails; Monitoring whether the reversing image driver is loaded successfully, and when monitoring that the reversing image driver fails to load, retrying the loading through the communication bus corresponding to the reversing image driver; When the loading retry reaches a preset number of times, the occupied resources are released through the communication bus corresponding to the reversing image driver, so that the central control system resets and reloads the touch driver; The reversing image driver and the central control system communicate with the vehicle system via different communication buses.

2. The method for recovering from touch abnormality of an in-vehicle display screen according to claim 1, characterized in that: The step of obtaining the user operation instruction and determining whether the central control system can normally respond to the user operation instruction specifically includes: Acquiring a user operation instruction, where the user operation instruction includes at least one of a voice instruction, a steering wheel instruction, and a key instruction; Inputting the user operation instruction into the central control system and obtaining a response action of the central control system; The response action is compared with the user operation instruction, and it is determined whether the central control system can normally respond to the user operation instruction based on the comparison result.

3. The method for recovering from touch abnormality of an in-vehicle display screen according to claim 1, characterized in that: The step of monitoring whether the reversing image driver is loaded successfully and retrying the loading through the communication bus corresponding to the reversing image driver when the reversing image driver fails to load is monitored specifically includes: Obtaining a preset monitoring period, monitoring the reversing image driver according to the monitoring period, and determining whether the reversing image driver is loaded successfully; When it is determined that the reversing image driver fails to load, a retry instruction of the vehicle system is received through the communication bus corresponding to the reversing image driver, and the reversing image driver is loaded and retried.

4. The method for recovering from touch abnormality of an in-vehicle display screen according to claim 1, characterized in that: When the loading retry reaches a preset number of times, the communication bus corresponding to the reversing image driver releases occupied resources so that the central control system resets and reloads the touch driver. This step specifically includes: Counting the loading retries of the reversing image driver; When the reversing image driver's loading retries reach the preset number of times, the communication resources of the vehicle system occupied are released through the communication bus corresponding to the reversing image driver, and then the serial deserializer is initialized and the touch driver is reset and reloaded through the central control system.

5. A method for recovering from touch abnormality of an in-vehicle display screen according to any one of claims 1 to 4, characterized in that: The vehicle-mounted display screen touch abnormality recovery method further includes the step of starting the vehicle-mounted display screen, which specifically includes: The microcontroller detects a power-on signal and outputs an enable signal to a system-side power supply when the power-on signal is detected, so that the system-side power supply supplies power to the system on chip; The system on chip is started, and a boot program is loaded and run through the system on chip to initialize the vehicle display screen, thereby establishing a memory space mapping diagram.

6. The method for recovering from touch abnormality of an in-vehicle display screen according to claim 5, characterized in that: The step of loading and running the startup program specifically includes: Initialize the hardware code; Reserving a first readable and writable RAM space, and testing an address of the first RAM space; Set the stack pointer and modify the register address to the first RAM space; Check the memory map of the vehicle system and load the kernel hardware and root file system; Initializing the double data rate synchronous dynamic random access memory by the boot program and loading a program into the double data rate synchronous dynamic random access memory; Start the Linux Kernel and mount system files; Starting the system driver of the central control system and loading the reversing image driver; Load the touch driver, start the application, and read and write the system log.

7. The method for recovering from touch abnormality of an in-vehicle display screen according to claim 6, characterized in that: The step of initializing the hardware code specifically includes: Shield all interrupt services; Set the CPU operating speed and clock frequency; Initialize the random access memory and close the instruction cache and data cache inside the CPU.

8. A vehicle-mounted display screen touch abnormality recovery system, characterized in that: include: The central control system response judgment module is used to obtain user operation instructions and judge whether the central control system can respond normally to the user operation instructions when a touch abnormality is detected on the vehicle display screen; a touch driver loading judgment module, configured to determine that the touch driver loading of the vehicle display screen has failed when the central control system can normally respond to the user operation instruction; A reversing image driver monitoring module is used to monitor whether the reversing image driver is loaded successfully. When it is monitored that the reversing image driver fails to load, the reversing image driver is reloaded through the communication bus corresponding to the reversing image driver. A touch driver reset loading module, configured to release occupied resources via the communication bus corresponding to the reversing image driver when a preset number of loading retries is reached, so that the central control system resets and reloads the touch driver; The reversing image driver and the central control system communicate with the vehicle system via different communication buses.

9. An electronic device, characterized in that: The electronic device includes a memory, a processor, a program stored in the memory and executable on the processor, and a data bus for realizing connection and communication between the processor and the memory. When the program is executed by the processor, the steps of the vehicle display screen touch abnormality recovery method as described in any one of claims 1 to 7 are implemented.

10. A storage medium, which is a computer-readable storage medium and is used for computer-readable storage, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the steps of the vehicle display screen touch abnormality recovery method according to any one of claims 1 to 7.

Images