Diagnostic method, device and electronic equipment for a vehicle system

Abstract

The present disclosure provides a diagnostic method and device of a vehicle-mounted system and an electronic device, and relates to the field of vehicle-mounted system diagnosis. The specific steps are: establishing the connection between a diagnostic instrument and a vehicle controller through the diagnostic instrument interface of a vehicle; controlling the SOC corresponding to the vehicle-mounted system through the vehicle controller, so that the SOC enters a diagnostic mode; and diagnosing the SOC through the diagnostic instrument. The present disclosure controls the vehicle controller by connecting the diagnostic instrument to the diagnostic instrument interface of the vehicle, so as to diagnose the fault of the vehicle controller, realizes the diagnosis of the vehicle controller, avoids the disassembly and damage of the vehicle structure during diagnosis, and improves the diagnosis efficiency of the vehicle.

Description

Technical Field

[0001] This disclosure relates to the field of vehicle system diagnostics, and more particularly to a method, apparatus and electronic device for diagnosing vehicle systems. Background Technology

[0002] In related technologies, the method for diagnosing a vehicle's onboard system involves removing the interior trim panels and connecting the vehicle's infotainment system to its Universal Serial Bus (USB) interface, then using the USB's diagnostic port for diagnostics. However, the USB port is not a standard diagnostic port for vehicles and cannot be directly exposed outside the vehicle for diagnosis. Therefore, each diagnostic requires removing the infotainment system from the vehicle body, which can easily damage the vehicle's overall structure. Summary of the Invention

[0003] This disclosure provides a diagnostic method, apparatus, and electronic device for an in-vehicle system, to at least solve the problem of vehicle disassembly and structural damage during diagnostics in related technologies. The technical solution of this disclosure is as follows:

[0004] According to a first aspect of the present disclosure, a diagnostic method for an in-vehicle system is provided, comprising:

[0005] Establish a connection between the diagnostic tool and the vehicle's infotainment system controller via the vehicle's diagnostic tool interface;

[0006] The vehicle controller controls the system-on-a-chip (SOC) corresponding to the vehicle system, causing the SOC to enter diagnostic mode.

[0007] The SOC is diagnosed using the diagnostic tool.

[0008] Optionally, before establishing the connection between the diagnostic tool and the vehicle's infotainment system controller via the vehicle's diagnostic tool interface, the method further includes:

[0009] The diagnostic tool is security verified by the hardware security module (HSM), and after the diagnostic tool passes the security verification, a connection is established between the diagnostic tool and the vehicle controller.

[0010] Optionally, controlling the SOC corresponding to the vehicle system through the vehicle controller to put the SOC into diagnostic mode includes:

[0011] The vehicle control unit is instructed to stop heartbeat detection of the SOC.

[0012] The vehicle control unit controls the SOC to restart and enters Fastboot mode, wherein the SOC is diagnosed in Fastboot mode.

[0013] Optionally, the diagnostic tool and the vehicle controller are connected via Ethernet.

[0014] Optionally, diagnosing the SOC using the diagnostic tool includes:

[0015] Send the Fastboot command to the SOC to cause the search SOC to perform the export partition.

[0016] According to a second aspect of the present disclosure, a diagnostic device for an in-vehicle system is provided, comprising:

[0017] The connection module is used to establish a connection between the diagnostic tool and the vehicle's infotainment system controller via the vehicle's diagnostic tool interface;

[0018] The control module is used to control the SOC corresponding to the vehicle system through the vehicle controller, so that the SOC enters the diagnostic mode;

[0019] A diagnostic module is used to diagnose the SOC using the diagnostic tool.

[0020] According to a third aspect of the present disclosure, an electronic device is provided, comprising:

[0021] processor;

[0022] Memory used to store the processor's executable instructions;

[0023] The processor is configured to execute the instructions to implement the diagnostic method for the vehicle system as described in any of the first aspects above.

[0024] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein when instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to perform a diagnostic method for an in-vehicle system as described in any one of the first aspects above.

[0025] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the diagnostic method for an in-vehicle system according to any one of the first aspects described above.

[0026] The technical solutions provided by the embodiments of this disclosure have at least the following beneficial effects:

[0027] By connecting the diagnostic tool to the vehicle's diagnostic interface to control the vehicle's infotainment system controller, fault diagnosis of the vehicle's infotainment system is achieved, avoiding the need to disassemble and damage the vehicle's structure during diagnosis, and improving the efficiency of vehicle diagnosis.

[0028] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0029] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure, and are not intended to unduly limit this disclosure.

[0030] Figure 1 This is a flowchart illustrating a diagnostic method for an in-vehicle system according to an exemplary embodiment.

[0031] Figure 2 This is a flowchart illustrating a diagnostic method for an in-vehicle system according to an exemplary embodiment.

[0032] Figure 3 This is a schematic diagram of a vehicle diagnostic device according to an exemplary embodiment.

[0033] Figure 4 This is a schematic diagram of a vehicle diagnostic device according to an exemplary embodiment.

[0034] Figure 5 This is a flowchart illustrating a diagnostic method in Fastboot mode according to an exemplary embodiment.

[0035] Figure 6 This is a block diagram illustrating a diagnostic device for an in-vehicle system according to an exemplary embodiment.

[0036] Figure 7 This is a block diagram illustrating an apparatus according to an exemplary embodiment.

[0037] Figure 8 This is a block diagram illustrating an apparatus according to an exemplary embodiment. Detailed Implementation

[0038] To enable those skilled in the art to better understand the technical solutions of this disclosure, the technical solutions in the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0039] It should be noted that the terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this disclosure described herein can be implemented in orders other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0040] It should be noted that the user information involved in this disclosure (including but not limited to user device information, user personal information, etc.) is all information authorized by the user or fully authorized by all parties.

[0041] With the advancement of computer technology, vehicles are becoming increasingly intelligent, and most vehicles are now equipped with in-vehicle infotainment (IVI) systems. IVI systems utilize a dedicated onboard central processing unit, based on the vehicle's bus system and internet services, to form a comprehensive in-vehicle information processing system. IVI can realize a range of applications including 3D navigation, real-time traffic information, interactive IPTV, driver assistance, fault detection, vehicle information, vehicle control, mobile office, wireless communication, and online entertainment functions and content (Telematics Service Provider, TSP) services, greatly enhancing the vehicle's electronic, networked, and intelligent levels. Functionally, in-vehicle infotainment systems enable information communication between people and vehicles, and between vehicles and the outside world (vehicle-to-vehicle communication).

[0042] MCU: Microcontroller Unit (MCU), also known as a single-chip microcomputer or microcontroller, is a chip-level computer that integrates a central processing unit (CPU) with a reduced frequency and specifications. It combines memory, timer, USB, analog-to-digital (A / D) converter, universal asynchronous receiver / transmitter (UART) and other peripheral interfaces, and even LCD driver circuitry, all onto a single chip. This allows for different control combinations for various applications. The in-vehicle infotainment system includes the MCU, which processes data and sends commands to control the vehicle.

[0043] Current in-vehicle infotainment system (IVR) troubleshooting processes require a USB connection. Specifically, this involves inserting a USB flash drive to retrieve the IVR's operational logs or connecting a computer to the IVR via USB for diagnostics. However, since USB is not a standard diagnostic port for vehicles, it cannot be directly exposed outside the vehicle for diagnosis. Therefore, each diagnostic requires removing the IVR from the vehicle body, which can easily damage the vehicle's structural integrity and lead to additional problems.

[0044] Figure 1 This is a flowchart illustrating a diagnostic method for an in-vehicle system according to an exemplary embodiment, such as... Figure 1 As shown, the method includes the following steps.

[0045] Step 101: Establish a connection between the diagnostic tool and the vehicle's infotainment system controller via the vehicle's diagnostic tool interface;

[0046] It should be noted that the method in the embodiments of this application can be executed by a host computer. Optionally, the host computer is a computer that directly issues control commands, such as a personal computer (PC), host computer, master computer, etc.

[0047] In this embodiment, when a fault occurs in the vehicle's infotainment system, a diagnostic tool (MDB) is used to diagnose the fault. The MDB is a computer-based tool. Faults in the vehicle's infotainment system can be detected and troubleshooted through the OBD interface, an international standard automotive communication interface. The computer is connected to the OBD interface, and the MDB in the computer can be connected to the vehicle's infotainment controller (XCU) via the OBD interface to debug the System-on-Chip (SOC). SOC is an abbreviation for System on Chip, also known as a system-on-a-chip, meaning it is a product, a dedicated integrated circuit containing a complete system and all embedded software.

[0048] Optionally, the computer is connected to the OBD interface via Ethernet, and the OBD interface is connected to the vehicle control domain via Ethernet.

[0049] Step 102: Control the system-on-a-chip (SOC) corresponding to the vehicle system through the vehicle controller, so that the SOC enters the diagnostic mode.

[0050] In this embodiment, during diagnostics, the SOC corresponding to the vehicle system needs to be in a suitable state for diagnostics, i.e., the diagnostic mode. The diagnostic mode process is implemented by the MDB controlling the SOC through the XCU. The XCU operates the SOC in different modes by connecting to the SOC's input / output I / O pins such as PS_HOLD RESET_N and the power key. These modes include power-on mode, reboot mode, and diagnostic mode.

[0051] Step 103: Diagnose the SOC using the diagnostic tool.

[0052] In this embodiment of the application, after the SOC enters the diagnostic mode, the MDB can obtain data from the SOC to analyze the cause of the SOC failure and debug the SOC to resolve the failure.

[0053] Optional, Figure 1 Step 101, prior to establishing the connection between the MDB and the XCU via the vehicle's OBD interface, further includes:

[0054] The MDB is securely verified via HSM, wherein after the MDB passes the security verification, a connection is established between the MDB and the XCU.

[0055] In this embodiment, an HSM (Hardware Smart Controller) is a hardware device used to protect and manage keys used by a strong authentication system, while also providing related cryptographic operations. HSMs are typically connected directly to a computer or network server via an expansion card or external device. HSMs offer two types of tamper protection: tamper evidence / proof and tamper resistance. The former ensures that tampering leaves a trace, while the latter causes the HSM to destroy protected information such as keys. Each HSM includes one or more security coprocessors to prevent tampering or bus probing. Many HSM systems provide reliable key backup mechanisms, allowing confidential data to be securely processed or transferred via smart cards or other devices. Since HSMs are often part of critical infrastructure such as public key infrastructure or online banking, multiple HSMs are typically used simultaneously to achieve high availability. Some HSMs feature dual power supplies and designs that allow for component replacement without downtime (e.g., cooling fans) to ensure high availability requirements in environments such as data centers.

[0056] To protect the vehicle's infotainment system from malicious software connections, the MDB must be verified for security via HSM before being connected to the XCU. Only after security is confirmed can the connection between the MDB and the XCU be established.

[0057] In this embodiment, the XCU is controlled by connecting the MDB to the vehicle's OBD interface to perform fault diagnosis on the XCU. This achieves vehicle system diagnosis, avoids disassembling the vehicle and damaging its structure during diagnosis, and improves the efficiency of vehicle diagnosis.

[0058] Figure 2 This is a flowchart illustrating a diagnostic method for an in-vehicle system according to an exemplary embodiment, such as... Figure 2 As shown, Figure 1 Step 102 specifically includes the following steps:

[0059] Step 201: Control the vehicle controller to stop performing heartbeat detection on the SOC;

[0060] In this embodiment, the XCU is not required to perform heartbeat detection on the SOC during the diagnostic process. Therefore, before the diagnostic process, a control (Command, CMD) command is first sent to stop the XCU from performing heartbeat detection on the SOC. Heartbeat detection is used to determine whether the SOC is operating normally, and generally involves sending simple communication packets at regular intervals. If no response is received from the other party within a specified time period, it is determined that the SOC has crashed. This is also used to detect abnormal disconnections of the Transmission Control Protocol (TCP).

[0061] The fundamental reason for performing heartbeat detection is that the XCU cannot effectively determine whether the SOC is online; in other words, the XCU cannot distinguish whether the SOC has been idle for an extended period or has been disconnected. A heartbeat is essentially the SOC periodically sending simple messages to the XCU to inform it that the SOC is still running.

[0062] The code sends a fixed message to the XCU every few minutes, and the XCU replies with a fixed message upon receiving it. If the XCU does not receive the SOC message within a few minutes, it considers the SOC disconnected. For example, some communication software, if not used for a long time, requires heartbeat packets to determine its online or offline status, involving periodic packet sending and receiving.

[0063] Step 202: Control the vehicle controller to restart the SOC and perform a fastboot mode, wherein the SOC is diagnosed in the fastboot mode.

[0064] In this embodiment of the application, Fastboot mode is the diagnostic mode. After stopping the heartbeat detection of XCU, the SOC can be restarted by using XCU and then enter Fastboot mode by connecting a specific IO pin for diagnosis.

[0065] Optionally, diagnosing the SOC through the MDB includes:

[0066] Send the Fastboot command to the SOC to cause the search SOC to perform the export partition.

[0067] In this embodiment of the application, the MDB sends a Fastboot command to cause the SOC to perform an export partition for analysis and diagnosis of the cause of the fault.

[0068] Figure 3 This is a schematic diagram illustrating a vehicle diagnostic device according to an exemplary embodiment. Figure 3 As shown, the MDB in the computer (PC) is connected to the OBD interface via Ethernet, the diagnostic instrument interface is connected to the XCU via Ethernet, and the eth-switch is a module in the XCU that contains multiple high-speed Ethernet interfaces and multiple dual-mode Ethernet transceivers (PHYs). The eth-switch can be configured to use the Virtual LAN (VLAN) function, supporting multiple 802.1Q VLANs and port-based VLAN segmentation. The MDB module in the eth-switch can control the MCU to control the corresponding SOC (8155-F and 8155-R).

[0069] Figure 4 This is a schematic diagram illustrating a vehicle diagnostic device according to an exemplary embodiment. Figure 4 As shown, omitting the data transmission process, it can be seen that the MDB in the PC controls the MCU via Ethernet to operate the SOC in different modes through IO pins such as PS_HOLD RESET_N and Powerkey, and transmits data through the SOC's UART to obtain data for fault analysis.

[0070] Figure 5 This is a flowchart illustrating a diagnostic method in Fastboot mode according to an exemplary embodiment. Figure 5 As shown, the MDB in the PC first sends a CMD command to disable the MCU's heartbeat detection for the two 8155F / R SOCs. After disabling heartbeat detection, the MCU sends a completion message (Response: ok) back to the MDB. At this point, the MDB sends a CMD command to instruct the MCU to control the SOCs to enter Fastboot mode for diagnostics. Upon receiving the command, the MCU powers on the SOCs via the RESET_N interface. Powering on is the process from power-on to system stability and operation. Then, the SOCs are put into Fastboot mode. The MDB can then send a fastboot command via Ethernet to search for and export partitions from the SOCs for diagnostics.

[0071] Figure 6This is a block diagram illustrating a diagnostic device for an in-vehicle system according to an exemplary embodiment. (Refer to...) Figure 6 The device includes a connection module 610, a control module 620, and a diagnostic module 630.

[0072] The connection module 610 is used to establish a connection between the diagnostic tool and the vehicle's infotainment controller via the vehicle's diagnostic tool interface;

[0073] The control module 620 is used to control the SOC corresponding to the vehicle system through the vehicle controller, so that the SOC enters the diagnostic mode;

[0074] The diagnostic module 630 is used to diagnose the SOC using the diagnostic tool.

[0075] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0076] Figure 7 This is a block diagram illustrating an apparatus 700 according to an exemplary embodiment. For example, apparatus 700 may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness equipment, personal digital assistant, etc.

[0077] Reference Figure 7 The device 700 may include one or more of the following components: a processing component 702, a memory 704, a power component 706, a multimedia component 708, an audio component 710, an input / output (I / O) interface 712, a sensor component 714, and a communication component 716.

[0078] Processing component 702 typically controls the overall operation of device 700, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 702 may include one or more processors 720 to execute instructions to complete all or part of the steps of the methods described above. Furthermore, processing component 702 may include one or more modules to facilitate interaction between processing component 702 and other components. For example, processing component 702 may include a multimedia module to facilitate interaction between multimedia component 708 and processing component 702.

[0079] Memory 704 is configured to store various types of data to support the operation of device 700. Examples of this data include instructions for any application or method operating on device 700, contact data, phonebook data, messages, pictures, videos, etc. Memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0080] Power supply assembly 706 provides power to various components of device 700. Power supply assembly 706 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 700.

[0081] Multimedia component 708 includes a screen that provides an output interface between the device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 708 includes a front-facing camera and / or a rear-facing camera. When the device 700 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0082] Audio component 710 is configured to output and / or input audio signals. For example, audio component 710 includes a microphone (MIC) configured to receive external audio signals when device 700 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 704 or transmitted via communication component 716. In some embodiments, audio component 710 also includes a speaker for outputting audio signals.

[0083] I / O interface 712 provides an interface between processing component 702 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0084] Sensor assembly 714 includes one or more sensors for providing status assessments of various aspects of device 700. For example, sensor assembly 714 may detect the on / off state of device 700, the relative positioning of components such as the display and keypad of device 700, changes in the position of device 700 or a component of device 700, the presence or absence of user contact with device 700, the orientation or acceleration / deceleration of device 700, and temperature changes of device 700. Sensor assembly 714 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 714 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 714 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0085] Communication component 716 is configured to facilitate wired or wireless communication between device 700 and other devices. Device 700 can access wireless networks based on communication standards, such as WiFi, carrier networks (such as 2G, 3G, 4G, or 5G), or combinations thereof. In one exemplary embodiment, communication component 716 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 716 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0086] In an exemplary embodiment, the apparatus 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0087] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory 704 including instructions, which can be executed by a processor 720 of the device 700 to perform the above-described method. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device.

[0088] Figure 8This is a block diagram illustrating an apparatus 800 for... according to an exemplary embodiment. For example, apparatus 800 may be provided as a server. (Refer to...) Figure 8 The apparatus 800 includes a processing component 822, which further includes one or more processors, and memory resources represented by memory 832 for storing instructions, such as application programs, that can be executed by the processing component 822. The application programs stored in memory 832 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 822 is configured to execute instructions to perform the methods described above.

[0089] Device 800 may also include a power supply component 826 configured to perform power management of device 800, a wired or wireless network interface 850 configured to connect device 800 to a network, and an input / output (I / O) interface 858. Device 800 can operate on an operating system stored in memory 832, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0090] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0091] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A diagnostic method for an in-vehicle system, characterized in that, include: Establish a connection between the diagnostic tool and the vehicle's XCU (X-code unit) through the vehicle's diagnostic tool interface; The vehicle control unit (XCU) controls the system-on-a-chip (SOC) corresponding to the vehicle system, causing the SOC to enter diagnostic mode. The SOC is diagnosed using the diagnostic tool; The step of controlling the system-on-a-chip (SOC) corresponding to the vehicle system via the vehicle control unit (XCU) to enable the SOC to enter diagnostic mode includes: The vehicle control unit (XCU) is controlled to stop heartbeat detection of the SOC. The vehicle control unit (XCU) controls the restart of the system operating system (SOC) and performs fastboot mode, wherein the SOC is diagnosed in the fastboot mode. The diagnostic process for the SOC using the diagnostic tool includes: Send the Fastboot command to the SOC to cause the search SOC to perform the export partition.

2. The method as described in claim 1, characterized in that, Before establishing the connection between the diagnostic tool and the vehicle's XCU via the vehicle's diagnostic tool interface, the following is also included: The diagnostic tool is security verified by the hardware security module (HSM), and after the diagnostic tool passes the security verification, a connection is established between the diagnostic tool and the vehicle control unit (XCU).

3. The method as described in claim 1, characterized in that, The diagnostic tool and the vehicle infotainment unit (XCU) are connected via Ethernet.

4. A diagnostic device for an in-vehicle system, characterized in that, include: The connection module is used to establish a connection between the diagnostic tool and the vehicle's XCU (X-unit control unit) via the vehicle's diagnostic tool interface. The control module is used to control the SOC corresponding to the vehicle system through the vehicle controller XCU, so that the SOC enters the diagnostic mode; A diagnostic module is used to diagnose the SOC using the diagnostic tool; The control module is specifically used for: The vehicle control unit (XCU) is controlled to stop heartbeat detection of the SOC. The vehicle control unit (XCU) controls the restart of the system operating system (SOC) and performs fastboot mode, wherein the SOC is diagnosed in the fastboot mode. The diagnostic module is specifically used for; Send the Fastboot command to the SOC to cause the search SOC to perform the export partition.

5. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the diagnostic method for the vehicle system as described in any one of claims 1 to 3.

6. A computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform a diagnostic method for an in-vehicle system as described in any one of claims 1 to 3.

7. A computer program product comprising a computer program that, when executed by a processor, implements the diagnostic method for an in-vehicle system according to any one of claims 1-3.

Images