WO2025119074A1 - Data acquisition method, controller, and vehicle - Google Patents

Abstract

The present application provides a data acquisition method, a controller, and a vehicle, being capable of using a microcontroller unit (MCU) on a vehicle to acquire operation data of a system-on-chip (SoC), thereby achieving anomaly analysis of the SoC. In the method, an MCU and an SoC that are comprised in a controller of a vehicle are connected by means of a universal asynchronous receiver-transmitter (UART) interface, on this basis, the MCU can acquire operation data of the SoC by means of the UART interface, and then the MCU can forward the operation data to a first on-board component, thereby achieving anomaly analysis of the SoC.

Description

Data acquisition method, controller and vehicle

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on December 4, 2023, with application number 202311656437.6 and application name “Data Acquisition Method, Controller and Vehicle”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of computer technology, and in particular to a data acquisition method, a controller and a vehicle.

Background Art

With the rapid development of intelligent driving technology, more and more vehicles are using system-on-chip (SoC) to control the normal operation of the vehicle. Among them, SoC is a chip-level system formed by combining a series of integrated circuits with specific functions on a chip, which can realize the control of multiple electronic control units (ECU) on the vehicle. Generally speaking, after the SoC is powered on, various systems on the SoC will be started in order to ensure the normal operation of the SoC. When the SoC starts abnormally, by obtaining relevant data during the SoC startup process, the abnormality in the SoC startup process can be quickly located, and then the cause of the SoC startup abnormality can be analyzed.

Currently, during the SoC testing phase, relevant personnel can directly export relevant data during the SoC startup process to the detection equipment through the hardware interface on the SoC, so as to quickly analyze the cause of the SoC startup anomaly. However, in order to prevent the SoC information and functions from being leaked, the hardware interface is usually not retained on the SoC during mass production, and it is impossible to obtain relevant data during the SoC startup process through the hardware interface, resulting in the inability to effectively analyze the cause of the anomaly when the SoC subsequently experiences an abnormal startup.

Summary of the invention

The present application provides a data acquisition method, a controller and a vehicle, which can utilize a microcontroller unit MCU on a vehicle to acquire operating data of a system-on-chip SoC, thereby realizing abnormal analysis of the SoC.

In order to achieve the above purpose, this application adopts the following technical solutions:

In a first aspect, a data acquisition method is provided, which is applied to a microcontroller unit MCU in a controller of a vehicle, wherein the controller also includes a system-on-chip SoC, and the MCU is connected to the SoC via a universal asynchronous receiver/transmitter UART interface. The method includes: acquiring operating data of the SoC via the UART interface; and sending the operating data to a first vehicle-mounted component, wherein the operating data is used for abnormal analysis of the SoC.

In the solution of the first aspect above, for the vehicle controller including MCU and SoC, a new UART hardware path from SoC to MCU is added, so that MCU can obtain the operation data of SoC through the UART hardware path, and MCU sends the obtained operation data of SoC to the first vehicle-mounted component to realize the analysis and processing of the operation data. In this way, after the controller including MCU and SoC is mass-produced, if the SoC has a startup abnormality, the relevant personnel can also have a path to obtain the operation data of SoC and quickly analyze the cause of the startup abnormality of SoC.

In a possible implementation, after obtaining the operation data of the SoC through the UART interface, the method further includes: compressing the operation data to obtain compressed operation data; and sending the operation data to the first vehicle-mounted component, including: sending the compressed operation data to the first vehicle-mounted component. In this way, the MCU can use less memory space to store a large amount of operation data of the SoC.

In a possible implementation, after obtaining the operation data of the SoC through the UART interface, the method further includes: encrypting the operation data to obtain encrypted operation data; and sending the operation data to the first vehicle-mounted component, including: sending the encrypted operation data to the first vehicle-mounted component. In this way, the information security of the operation data of the SoC is guaranteed, and even if an attacker obtains the operation data of the SoC, the attacker cannot know the content and meaning thereof.

In a possible implementation, after the MCU obtains the operation data of the SoC through the UART interface, it can compress the operation data or encrypt the operation data. The application does not limit the order of execution of the compression process and the encryption process. For example, the operation data can be compressed first, and then the compressed operation data can be encrypted.

In a possible implementation, the above-mentioned acquisition of the operation data of the SoC through the UART interface includes: controlling the SoC to be in a power-on state; acquiring the operation data of the SoC through the UART interface during the system startup process of the SoC; and caching the operation data. In this way, after controlling the SoC to be powered on, the MCU can start to acquire the operation data of the SoC during the system startup process through the UART interface and cache it in the memory space of the MCU.

In a possible implementation, sending the operation data to the first vehicle-mounted component includes: sending the operation data to the first vehicle-mounted component when detecting that the startup of the SoC is abnormal. In this way, after the MCU obtains the operation data of the SoC, if it detects that the SoC is not started normally, the MCU can automatically send the operation data to the first vehicle-mounted component, so that relevant personnel can obtain the operation data to locate the abnormality of the SoC.

In a possible implementation, sending the operating data to the first vehicle-mounted component includes: sending the operating data to the first vehicle-mounted component in response to a first instruction from a user. In this way, after the MCU obtains the operating data of the SoC, if an enable instruction from the user is detected, the MCU can send the operating data to the first vehicle-mounted component, so that the user can understand the cause of the abnormal startup of the SoC.

In a possible implementation, the MCU is connected to the first vehicle-mounted component via a controller area network (CAN) bus, and sends operating data to the first vehicle-mounted component, including: dividing the operating data into multiple data slices; generating a CAN message corresponding to each of the multiple data slices; and sending the CAN message corresponding to each data slice to the first vehicle-mounted component via the CAN bus. In this way, when the MCU sends the operating data of the SoC via the CAN bus, since the CAN bus is relatively narrow, it is impossible to send all the operating data at once. Therefore, the operating data can be split and sent out multiple times.

In a possible implementation, the first vehicle-mounted component is a vehicle-mounted communication component, which is used to establish a communication connection with an external device of the vehicle, wherein: the operation data is used to instruct the vehicle-mounted communication component to send the operation data to the external device, and instruct the external device to analyze and process the operation data. In this way, the MCU can forward the operation data of the SoC to a component with communication capabilities on the vehicle, so that the operation data can be sent to the external device, making it easier for relevant personnel to view the operation data and analyze the cause of the abnormality.

In a possible implementation, the first vehicle-mounted component is a vehicle-mounted display device, wherein: the operation data is used to instruct the vehicle-mounted display device to analyze and process the operation data and display the analysis results. In this way, the MCU can forward the operation data of the SoC to a component on the vehicle with display and analysis capabilities, so that relevant personnel can directly view the cause of the abnormality through the component.

In a second aspect, a data acquisition device is provided, which is included in the MCU of the vehicle controller, and the device has the function of implementing the above-mentioned first aspect or any possible design method thereof. The function can be implemented by hardware, or by hardware executing corresponding software implementation. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions. For example, the data acquisition device may include an acquisition module and a sending module. The acquisition module is used to acquire the operating data of the SoC through the UART interface; the sending module is used to send the operating data to the first vehicle-mounted component, and the operating data is used to perform abnormal analysis of the SoC.

In a third aspect, a microcontroller unit MCU is provided, which is applied to a vehicle, and the MCU includes a processor, a memory and a universal asynchronous receiver/transmitter UART interface, wherein the UART interface is used to connect to a system-on-chip SoC, the memory is used to store a computer program or instruction, and the processor is used to run the computer program or instruction and execute the data acquisition method in any possible implementation of the first aspect above.

In a fourth aspect, a controller is provided, which includes the MCU and SoC of the third aspect.

In a fifth aspect, a vehicle is provided, comprising the controller according to the fourth aspect.

In a sixth aspect, a chip system is provided. The chip system includes one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected via a line. The interface circuit is used to receive a signal and send the signal to the processor, where the signal includes an instruction. The processor is used to run the instruction and execute the data acquisition method in any possible implementation of the first aspect.

It can be understood that the beneficial effects that can be achieved by the device of the second aspect, the microcontroller unit MCU of the third aspect, the controller of the fourth aspect, the vehicle of the fifth aspect and the chip system of the sixth aspect provided above can be referred to the beneficial effects of the first aspect and any possible implementation thereof, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a vehicle architecture provided in an embodiment of the present application;

FIG2 is a schematic diagram of a system architecture provided by the related art;

FIG3 is a schematic diagram of a system architecture provided by the related art;

FIG4 is a schematic diagram of a flow chart of a data acquisition method provided in an embodiment of the present application;

FIG5 is a schematic diagram of a system architecture provided in an embodiment of the present application;

FIG6 is a timing diagram of a data acquisition method provided in an embodiment of the present application;

FIG7 is a flow chart of a data acquisition method provided in an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a data acquisition device provided in an embodiment of the present application.

DETAILED DESCRIPTION

The embodiments of the present application are described in detail below with reference to the accompanying drawings.

As shown in FIG1 , an embodiment of the present application provides a schematic diagram of the architecture of a vehicle 100. The vehicle 100 may be a conventional vehicle or an autonomous driving vehicle for carrying personnel. An autonomous driving vehicle may also be referred to as an unmanned vehicle or an intelligent driving vehicle, etc., which may travel in a manual mode, a fully autonomous mode, or a partially autonomous mode. When configured to travel in a fully autonomous mode or a partially autonomous mode, the autonomous driving vehicle may travel autonomously in a geographic area with little or no control input from the driver.

Optionally, the vehicle 100 may be a ground-based vehicle, such as a car, a bus, a motorcycle, a locomotive, a subway, etc. The vehicle 100 may also be a water-based vehicle, such as a ship, a hovercraft, a submarine, etc. The vehicle 100 may also be a flying vehicle, such as an airplane, a helicopter, etc. The embodiment of the present application does not limit the specific type of the vehicle 100.

In the embodiment of the present application, the vehicle 100 may include at least one controller 110, which has a control function and a computing function, etc.

In some embodiments, the controller 110 may be an electronic control unit (ECU). Different ECUs may implement different functions to control the normal operation of the vehicle. For example, the air conditioning ECU may control the temperature in the vehicle, and the engine ECU may control the air intake, fuel injection, and ignition timing of the engine to control the speed of the vehicle.

Among them, various ECUs can be connected through the in-vehicle bus to realize data communication between ECUs. Among them, the bus can be a controller area network (CAN) bus, or an Ethernet bus, a local interconnect network (LIN) bus, a media oriented system transport (MOST) bus, a FlexRay and other wired communication lines, or a line generated by a wireless communication module such as wireless fidelity (Wi-Fi), Bluetooth, ZigBee, etc.

In some embodiments, a vehicle may be divided into a plurality of different domains according to functions, each domain including at least one domain controller, and each domain controller is used to manage a plurality of ECUs connected to one or more CAN buses within the domain.

The controller 110 may also be a domain controller. The domain controller may be a cockpit domain controller (CDC), or a smart cockpit platform, for controlling a smart cockpit. The domain controller may also be a vehicle domain controller (VDC), or a vehicle control platform, for controlling vehicle power. The domain controller may also be a mobile data center (MDC), or a smart driving platform, for controlling smart driving. The embodiments of the present application do not limit the type of domain controller.

The controller 110 may include a microcontroller unit (MCU) 111 and a SoC 112. The SoC 112 includes a universal asynchronous receiver/transmitter (UART) interface, which is a universal serial data bus for asynchronous communication. In the SoC, the UART interface can be used for data transmission, debug indication and debug information output. In the embodiment of the present application, the MCU 111 and the SoC 112 can be connected via the UART interface. The MCU 111 is used to obtain the operating data of the SoC 112 through the UART interface.

In the embodiment of the present application, the power supply of SoC 112 is controlled by MCU 111, and MCU 111 is responsible for detecting the working status of SoC 112 and performing operations such as powering on SoC 112, powering off SoC 112, and abnormal recovery. Among them, after MCU 111 powers on SoC 112, SoC 112 will periodically transmit a frame of heartbeat signal data packets to MCU 111, and MCU 111 will perform timing processing on the heartbeat signal. If the next one or more heartbeat signals are not received within the specified time, it is considered that SoC 112 is abnormal and restart is performed.

In the embodiment of the present application, after SoC 112 is powered on, various systems on SoC 112 will be started in order, such as the basic input output system (BIOS), Bootloader, operating system (OS), etc.

In some embodiments, the vehicle may also include an on-board communication component 120 with a communication function, such as a gateway, an on-board communication terminal, a vehicle computer, etc. Among them, the on-board communication terminal is also called a vehicle-mounted telecommunication box (telematics-box, T-box). The on-board T-box is a box with a communication function in the vehicle, which can provide a remote communication interface for the vehicle 100 and is usually hidden in the vehicle. The on-board T-box is mainly used to communicate with the background system (such as a server)/electronic equipment to realize the vehicle information display and vehicle control on the electronic equipment side. Among them, the electronic device can be a mobile phone, a tablet computer, a wearable device, etc. In a possible implementation, the on-board T-box can read the data of each ECU in the vehicle through the CAN bus, and send the data to the background system (such as a server) or electronic equipment through the network for users to view.

In some embodiments, the vehicle may also include a vehicle-mounted display component 130 with a display function, such as a vehicle-mounted computer. The vehicle-mounted computer is also called a vehicle-mounted computer or a vehicle-mounted navigation. The vehicle-mounted computer may include a host and a display screen, and the host and the display screen of the vehicle-mounted computer may be arranged together or separately. The vehicle-mounted computer is usually installed in the center console. The center console refers to a workbench in front of the driver and co-driver seats in the vehicle 100, which is usually a carrier of devices such as an instrument panel, air conditioner, audio panel, storage box, and airbags. Optionally, the vehicle-mounted computer can be connected to sensors in the vehicle, and the vehicle-mounted computer can control the vehicle based on data from the sensors. Sensors in the vehicle may include, but are not limited to, temperature sensors, speed sensors, and image sensors.

In some embodiments, the controller 110 may be connected to the vehicle-mounted communication component 120 and the vehicle-mounted display component 130 via a bus to achieve data communication.

In some embodiments, the above-mentioned vehicle computer and vehicle-mounted communication terminal may also be an ECU in the vehicle.

It is understood that the embodiments of the present application do not limit the structure of the vehicle, and the vehicle may include more components or devices. The methods in the following embodiments may be implemented in a vehicle or controller having the above hardware structure.

Generally, when the SoC startup is abnormal, relevant personnel can quickly locate the abnormality in the SoC startup process by obtaining relevant data during the SoC startup process, and then analyze the cause of the SoC startup abnormality.

At present, during the test phase of SoC, as shown in Figure 2, relevant personnel can directly connect a data line from the hardware UART interface on the SoC to connect the detection equipment, so that the relevant data during the SoC startup process can be exported to the detection equipment, and then the cause of the SoC startup abnormality can be quickly analyzed. However, in order to ensure that the SoC information and functions are not leaked, the hardware UART interface is usually not retained on the SoC during mass production of SoC, and relevant personnel cannot obtain the relevant data during the SoC startup process by accessing the hardware UART interface, resulting in the inability to effectively analyze the cause of the abnormality when the subsequent SoC startup abnormality occurs.

In the field of information and communications technology (ICT) servers, as shown in Figure 3, although a baseboard management controller (BMC) can be attached to the UART interface of the server's SoC to export the SoC's operating data through the UART interface, in the vehicle field, if a BMC is attached to the SoC in each controller in the vehicle, not only the hardware cost and software adaptation cost are increased, but also there is an information security problem.

Therefore, in order to solve the above problems, the embodiment of the present application provides a data acquisition method, which uses the functional safety MCU on the vehicle to replace the BMC in the ICT field, and adds a UART hardware path from the SoC to the MCU, so that the MCU can obtain the operating data of the SoC through the UART hardware path, and the MCU sends the obtained operating data of the SoC to realize the analysis and processing of the abnormal operation of the SoC. In this way, there is no need to increase additional hardware costs. After mass production of controllers containing MCU and SoC, if the SoC has a startup abnormality, relevant personnel can also have a path to obtain the operating data of the SoC and quickly analyze the cause of the abnormal startup of the SoC.

The following will take the controller in Figure 1 as an example to introduce a data acquisition method provided by an embodiment of the present application. Wherein, the controller includes an MCU and a SoC, as shown in Figure 4, the data acquisition method may include:

S410, MCU obtains the operation data of SoC through the UART interface.

It can be understood that since the MCU and the SoC are connected via the UART interface, the MCU can directly obtain the operating data of the SoC through the UART channel.

The operation data of the SoC may refer to a series of startup data after the SoC is powered on, and the series of startup data may facilitate the subsequent abnormal analysis of the startup of the SoC. For example, the operation data of the SoC may include a series of code data and instructions executed when the BIOS is started, a series of code data executed when the Bootloader is started, and a series of code data executed when the OS is started.

In some embodiments, the operation data of the SoC may also refer to the execution data when the SoC implements various functions after startup. This series of execution data may facilitate subsequent abnormal analysis of the operation functions of the SoC.

S420. The MCU sends the operating data to the first vehicle-mounted component, where the operating data is used to perform abnormality analysis on the SoC.

In an embodiment of the present application, after the MCU obtains the operating data of the SoC, it can send the operating data of the SoC so that relevant personnel can obtain the operating data of the SoC, and parse the operating data through a matching parsing script to analyze and locate the cause of the abnormality of the SoC.

In the embodiment of the present application, the MCU can send the operation data of the SoC to the first vehicle-mounted component in the vehicle through the vehicle internal bus. The first vehicle-mounted component can be any component, device, etc. in the vehicle.

As a method, the first vehicle-mounted component can be a vehicle-mounted communication component with communication function, such as a vehicle-mounted gateway, a vehicle-mounted T-box, etc. After the MCU sends the operation data of the SoC to such vehicle-mounted communication components, the vehicle-mounted communication components can send the operation data of the SoC to external devices of the vehicle, such as a server in the vehicle-to-cloud system, a detection device with data detection and analysis capabilities, etc., so that relevant personnel can view the operation data and analyze the cause of the abnormality.

As shown in FIG5 , after MCU 111 obtains the operating data of SoC 112 through the UART channel, it can forward the operating data of SoC to the vehicle communication component through the vehicle bus, and the vehicle communication component reports the operating data to the server 200 of the vehicle cloud system. Therefore, relevant personnel can read the operating data from the server and perform abnormal analysis of SoC.

Optionally, the vehicle-mounted communication component may also have data detection and analysis capabilities, so that after receiving the operating data of the SoC, the vehicle-mounted communication component may also analyze and process the operating data, and after obtaining the analysis results, send them to the vehicle's external devices.

As another method, the first vehicle-mounted component can be a vehicle-mounted display component with a display function, such as a vehicle computer. After the MCU sends the operation data of the SoC to such a vehicle-mounted display component, the vehicle-mounted display component can analyze and process the operation data, and after obtaining the analysis result, display the analysis result. In this way, relevant personnel can directly view the cause of the abnormality through the component.

In some embodiments, due to the limited memory space of the MCU, it may not be able to carry a large amount of operating data of the SoC. Therefore, after the MCU obtains the operating data of the SoC, it can also compress the operating data to obtain the compressed operating data, and then forward it to the first vehicle-mounted component. In this way, the MCU can use less memory space to store a large amount of SoC operating data. Among them, the compression algorithm can be any compression algorithm in the relevant technology, and the embodiments of the present application are not limited to this. For example, the Lz77 compression algorithm is used.

In some embodiments, since broadcasting the operating data of the SoC on the CAN network may face the risk of information security and system hacking, after the MCU obtains the operating data of the SoC, it can also encrypt the operating data to obtain the encrypted operating data, and then forward it to the first vehicle-mounted component. In this way, the information security of the operating data of the SoC is guaranteed, and even if the attacker obtains the operating data of the SoC, the attacker cannot know its content and meaning. Among them, the encryption algorithm can be any encryption algorithm in the relevant technology, and the embodiments of the present application are not limited to this.

In some embodiments, after the MCU obtains the operating data of the SoC, it may also first compress the operating data of the SoC, and after obtaining the compressed operating data, encrypt the compressed operating data to obtain the encrypted operating data.

In some embodiments, after the MCU obtains the operating data of the SoC, it may also first encrypt the operating data of the SoC, obtain the encrypted operating data, and then compress the encrypted operating data to obtain compressed operating data. The embodiments of the present application do not limit the order of execution of encryption and compression.

The data acquisition method provided in the embodiment of the present application adds a UART hardware path from SoC to MCU for a vehicle controller including MCU and SoC, so that MCU can obtain the operation data of SoC through the UART hardware path, and MCU sends the obtained operation data of SoC to the first vehicle-mounted component to realize the analysis and processing of the operation data. In this way, even if the SoC has a startup abnormality after the controller including MCU and SoC is mass-produced, the relevant personnel can also have a path to obtain the operation data of SoC and quickly analyze the cause of the abnormal startup of SoC.

Please refer to FIG. 6 and FIG. 7 . FIG. 6 shows a timing diagram of a data acquisition method provided in an embodiment of the present application, and FIG. 7 shows a flow chart of a data acquisition method provided in an embodiment of the present application. The data acquisition method may include:

S510, MCU controls the SoC to be in a power-on state.

In the embodiment of the present application, when the SoC is in the ordering state, if the SoC needs to be started, the MCU can power on the SoC so that the SoC is in the power-on state. After the SoC is in the power-on state, the SoC can start various systems on the SoC in an orderly manner. During the startup process, the startup data of the SoC can be forwarded to the MCU through the UART interface.

S520: During the system startup process of the SoC, the MCU obtains the operation data of the SoC through the UART interface.

In the embodiment of the present application, after the MCU powers on the SoC, the MCU can obtain the operating data of the SoC through the UART interface.

S530, MCU compresses and encrypts the operation data.

In the embodiment of the present application, after the MCU obtains the operating data of the SoC, it can compress and encrypt the operating data of the SoC, which can not only ensure data security but also save the memory space of the MCU.

S540, MCU caches running data.

In the embodiment of the present application, after compressing and encrypting the running data, the MCU may temporarily store the compressed and encrypted running data and wait for a subsequent determination as to whether to send it out.

S550: When the MCU detects that the startup of the SoC is abnormal, it sends the operation data to the vehicle communication component.

In the embodiment of the present application, after the MCU powers on the SoC, the SoC will periodically transmit a heartbeat signal data packet to the MCU, and the MCU will perform timing processing on the heartbeat signal. If the heartbeat signal is not received within a specified time, such as one minute, it is considered that the SoC has a startup abnormality. At this time, the MCU can send the compressed and encrypted operating data to the vehicle-mounted communication component.

Optionally, when the MCU sends the operating data of the SoC via the CAN bus, since the CAN bus is relatively narrow, it is not possible to send all the operating data at once, so the operating data can be split and sent out multiple times. The MCU divides the operating data of the SoC into multiple data slices, generates a CAN message corresponding to each of the multiple data slices, and then cyclically sends the CAN message corresponding to each data slice to the vehicle-mounted communication component via the CAN bus.

Optionally, when the MCU detects that the SoC is abnormally started, the MCU may also send the operation data to the vehicle-mounted display component, so that the vehicle-mounted display device can analyze and process the operation data and display the analysis results.

In some embodiments, the MCU may also send the operation data to the vehicle-mounted communication component or the vehicle-mounted display component in response to the user's first instruction. In this way, after the MCU obtains the operation data of the SoC, if it detects the user's enable instruction, the MCU may also send the operation data to the first vehicle-mounted component, so that the user can understand the reason for the abnormal startup of the SoC.

Optionally, when the MCU detects a startup anomaly of the SoC, it can instruct the vehicle display component to display an abnormality prompt and display an abnormality analysis option (such as an icon or a drop-down menu). When the user selects the abnormality analysis option, the MCU responds to the click operation and can send the temporarily stored SoC operation data to the vehicle display component, which analyzes and processes the operation data and displays the analysis results.

S560. The vehicle-mounted communication component sends the operating data to the server.

In the embodiment of the present application, after receiving the CAN message, the vehicle communication component can report the CAN message to the server, so that the relevant personnel can pull the CAN message from the server and parse the CAN message through the supporting parsing script tool to obtain the original SoC operation data before encryption and compression. Then the relevant personnel can analyze the startup abnormality of the SoC based on the parsed original SoC operation data.

It is understandable that, in order to realize the above functions, the above controller or MCU etc. includes hardware structures and/or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

It should be noted that the division of modules in the embodiments of the present invention is schematic and is only a logical function division. There may be other division methods in actual implementation. For example, a controller or MCU may include a memory, a processor, a communication interface, and a bus. Among them, the memory, the processor, and the communication interface are connected to each other through the bus.

The present application also provides a data acquisition device, which can be applied to the controller or MCU mentioned above. The device is used to execute the functions or steps executed by the controller or MCU in the method embodiment mentioned above.

The embodiment of the present application can divide the functional modules of the above-mentioned data acquisition device etc. according to the above-mentioned method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional module.

As an example, please refer to FIG. 8, which shows a schematic diagram of the structure of a data acquisition device provided in an embodiment of the present application. As shown in FIG. 8, the data acquisition device 800 includes an acquisition module 801 and a sending module 802. Among them, the acquisition module 801 is used to obtain the operation data of the SoC through the UART interface. The sending module 802 is used to send the operation data to the first vehicle-mounted component, and the operation data is used to perform abnormal analysis of the SoC.

In a possible implementation, the data acquisition device 800 further includes a compression processing module, which is used to compress the operation data to obtain compressed operation data. A sending module 802 is used to send the compressed operation data to the first vehicle-mounted component.

In a possible implementation, the data acquisition device 800 further includes an encryption processing module, which is used to encrypt the operation data to obtain the encrypted operation data. The sending module 802 is used to send the encrypted operation data to the first vehicle-mounted component.

In a possible implementation, the acquisition module 801 is used to: control the SoC to be in a power-on state; during the system startup process of the SoC, acquire the operating data of the SoC through the UART interface; and cache the operating data.

In a possible implementation, the sending module 802 is configured to send the operating data to the first vehicle-mounted component when a startup abnormality of the SoC is detected.

In a possible implementation, the sending module 802 is configured to send the operating data to the first vehicle-mounted component in response to a first instruction from a user.

In a possible implementation, the MCU is connected to the first vehicle-mounted component via a controller area network CAN bus, and a sending module 802 is used to divide the operating data into multiple data slices; generate a CAN message corresponding to each data slice in the multiple data slices; and send the CAN message corresponding to each data slice to the first vehicle-mounted component via the CAN bus.

In a possible implementation, the first vehicle-mounted component is a vehicle-mounted communication component, which is used to establish a communication connection with an external device of the vehicle, wherein: the operating data is used to instruct the vehicle-mounted communication component to send the operating data to the external device and instruct the external device to analyze and process the operating data.

In a possible implementation, the first vehicle-mounted component is a vehicle-mounted display device, wherein: the operating data is used to instruct the vehicle-mounted display device to analyze and process the operating data and display the analysis result.

It should be noted that the information interaction, execution process, etc. between the modules in the data acquisition device 800 provided in Figure 8 are based on the same concept as the method embodiment corresponding to Figure 4 in the present application. The specific content can be found in the description of the method embodiment shown in the previous part of the present application, and will not be repeated here.

An embodiment of the present application also provides a microcontroller unit MCU, which is applied to a vehicle. The MCU includes a processor, a memory and a universal asynchronous receiver/transmitter UART interface. The UART interface, the memory and the processor are coupled, wherein the UART interface is used to connect to a system-on-chip SoC, the memory is used to store a computer program or instruction, and the processor is used to run the computer program or instruction. The various functions or steps performed by the MCU in the above method embodiment.

The embodiment of the present application further provides a controller, which includes the above data acquisition device, or includes the above MCU. Optionally, the controller is a domain controller or an electronic control unit ECU.

The embodiment of the present application also provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected through a line. The interface circuit can read the instruction stored in the memory and send the instruction to the processor. When the instruction is executed by the processor, the chip system can execute the various functions or steps performed by the MCU in the above method embodiment. Of course, the chip system can also include other discrete devices, which is not specifically limited in the embodiment of the present application.

The embodiment of the present application also provides a computer program product. When the computer program product runs on an MCU, the MCU executes each function or step executed by the MCU in the above method embodiment.

Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules or units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be covered within the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (13)

A data acquisition method, characterized in that it is applied to a microcontroller unit MCU in a controller of a vehicle, the controller also includes a system-on-chip SoC, the MCU is connected to the SoC via a universal asynchronous receiver-transmitter UART interface, and the method comprises: Acquire the operation data of the SoC through the UART interface; The operation data is sent to a first vehicle-mounted component, where the operation data is used to perform abnormality analysis on the SoC. The method according to claim 1, characterized in that after acquiring the operating data of the SoC through the UART interface, the method further comprises: compressing the operation data to obtain compressed operation data; The sending the operation data to the first vehicle-mounted component comprises: The compressed operation data is sent to the first vehicle-mounted component. The method according to claim 1 or 2, characterized in that after acquiring the operation data of the SoC through the UART interface, the method further comprises: Encrypting the operation data to obtain encrypted operation data; The sending the operation data to the first vehicle-mounted component comprises: The encrypted operation data is sent to the first vehicle-mounted component. The method according to any one of claims 1 to 3, characterized in that the obtaining the operation data of the SoC through the UART interface comprises: Controlling the SoC to be in a power-on state; During the system startup process of the SoC, obtaining the operation data of the SoC through the UART interface; The operating data is cached. The method according to any one of claims 1 to 4, characterized in that the sending of the operating data to the first vehicle-mounted component comprises: When a startup abnormality of the SoC is detected, the operation data is sent to a first vehicle-mounted component. The method according to any one of claims 1 to 4, characterized in that the sending of the operating data to the first vehicle-mounted component comprises: In response to a first instruction from a user, the operation data is sent to a first vehicle-mounted component. The method according to any one of claims 1 to 6, characterized in that the MCU is connected to the first vehicle-mounted component via a controller area network (CAN) bus, and the sending of the operating data to the first vehicle-mounted component comprises: Splitting the operating data into a plurality of data slices; Generate a CAN message corresponding to each data slice in the multiple data slices; The CAN message corresponding to each data piece is sent to the first vehicle-mounted component via the CAN bus. The method according to any one of claims 1 to 7, characterized in that the first vehicle-mounted component is a vehicle-mounted communication component, and the vehicle-mounted communication component is used to establish a communication connection with an external device of the vehicle, wherein: The operating data is used to instruct the vehicle-mounted communication component to send the operating data to the external device, and to instruct the external device to analyze and process the operating data. The method according to any one of claims 1 to 7, characterized in that the first vehicle-mounted component is a vehicle-mounted display device, wherein: The operating data is used to instruct the vehicle-mounted display device to analyze and process the operating data and display the analysis result. A microcontroller unit MCU, characterized in that it is applied to a vehicle, the MCU comprises a processor, a memory and a universal asynchronous receiver-transmitter UART interface, the UART interface, the memory and the processor are coupled, wherein the UART interface is used to connect a system-on-chip SoC, the memory is used to store a computer program or instruction, and the processor is used to run the computer program or instruction and execute the method as described in any one of claims 1 to 9. A controller, characterized in that the controller comprises the MCU as claimed in claim 10 and the SoC. A vehicle, characterized in that the vehicle comprises the controller as claimed in claim 11. A chip, characterized in that the chip includes an interface circuit and a processor, the interface circuit and the processor are interconnected through a line, the interface circuit is used to receive a signal, the signal includes an instruction, and the processor is used to run the instruction to execute the method according to any one of claims 1 to 9.