Fault data acquisition method, processor, chip, device, medium and product

Abstract

The present disclosure relates to a fault data acquisition method, a processor, a chip, an equipment, a medium and a product. The acquisition method comprises: in response to receiving fault state information sent by a communication processor and the first transmission path between the communication processor being abnormal, determining a fault data acquisition command, the fault state information being used to represent that the communication processor is in a fault state; sending the fault data acquisition command to the communication processor through a second transmission path; and receiving fault data returned by the communication processor according to the fault data acquisition command through the second transmission path, the fault data being used to determine the reason why the communication processor is in the fault state. In the present disclosure, after receiving the fault state information reported by the communication processor and confirming that the first transmission path is abnormal, the fault data can be acquired through the second transmission path, thereby avoiding the destruction of the structure of the electronic equipment and improving the data acquisition efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of fault handling technology, and in particular to a method, processor, chip, device, medium and product for acquiring fault data. Background Technology

[0002] When the application processor (AP) and the communication processor (CP) are two different chips, if the communication processor fails and the first transmission path between the two is abnormal, the electronic device needs to be disassembled and the communication processor needs to be connected to an external debugging device by flying wires. This method not only damages the structure of the electronic device, but also takes time and is inefficient. Summary of the Invention

[0003] To overcome the problems existing in related technologies, this disclosure provides a method for acquiring fault data, a processor, a chip, a device, a medium, and a product.

[0004] According to a first aspect of the present disclosure, a method for acquiring fault data is provided, the method comprising: In response to receiving fault status information sent by the communication processor and the first transmission path between the communication processor and the communication processor being abnormal, a fault data acquisition command is determined, wherein the fault status information is used to characterize that the communication processor is in a fault state. The fault data acquisition command is sent to the communication processor via the second transmission path; The communication processor receives fault data returned by the fault data acquisition command through the second transmission path, wherein the fault data is used to determine the reason why the communication processor is in the fault state.

[0005] In this embodiment, after receiving the fault status information reported by the communication processor and confirming that the first transmission path is abnormal, the application processor can obtain the fault data through the second transmission path, which avoids damage to the electronic device structure and improves the data acquisition efficiency.

[0006] In some embodiments of this disclosure, the command to determine fault data acquisition includes: Parse the fault data acquisition file to determine the fault data acquisition command; The fault data acquisition file is pre-stored in the application processor, or the acquisition method further includes: in response to receiving the fault status information and the first transmission path being abnormal, receiving the fault data acquisition file sent by the first external device.

[0007] In this embodiment, the fault data acquisition file is easy to modify and maintain. By parsing the fault data acquisition file to determine the fault data acquisition command, the flexibility of acquiring fault data is improved.

[0008] In some embodiments of this disclosure, the command to determine fault data acquisition includes: In response to receiving the fault status information and the first transmission path being abnormal, the system receives the fault data acquisition command sent by the second external device.

[0009] In this embodiment, the fault data acquisition command can be directly determined without parsing the file, saving time and improving the efficiency of fault data acquisition.

[0010] In some embodiments of this disclosure, sending the fault data acquisition command to the communication processor via a second transmission path includes: The fault data acquisition command is encapsulated into a format corresponding to the second transmission path; The encapsulated fault data acquisition command is sent to the communication processor via the second transmission path.

[0011] In this embodiment, after the application processor determines the fault data acquisition command, it first encapsulates the fault data acquisition command and then sends the fault data acquisition command in the format corresponding to the second transmission path to the communication processor through the second transmission path, thereby improving the reliability of fault data acquisition.

[0012] In some embodiments of this disclosure, the fault data acquisition command includes multiple sub-acquisition commands. After the application processor sends one of the sub-acquisition commands to the communication processor and receives the sub-fault data returned by the communication processor according to the sub-acquisition command or after the sub-acquisition command is executed, it sends the next sub-acquisition command to the communication processor. The fault data includes the sub-fault data obtained through all the sub-acquisition commands.

[0013] In this embodiment, since the communication processor is already in a fault state, sending the next sub-acquisition command after the execution of one sub-acquisition command can reduce the processing burden of the communication processor and avoid further failures caused by excessive processing burden in the fault state.

[0014] In some embodiments of this disclosure, the plurality of sub-acquisition commands include at least one write command and at least one read command. The write command is used to make the storage area readable after the data contained in the write command is written to the storage area corresponding to the write command in the communication processor. The read command is used to read the data in the storage area corresponding to the read command in the communication processor.

[0015] In this embodiment, for storage areas that are not readable, data is first written to make them readable, and then complete fault data can be obtained, which improves the accuracy of subsequent fault diagnosis.

[0016] In some embodiments of this disclosure, the acquisition method further includes: In response to receiving the fault status information, the fault data is obtained through the first transmission path; In response to the inability to obtain the fault data through the first transmission path, it is determined that the first transmission path is abnormal.

[0017] In this embodiment, the application processor determines whether the first transmission path is abnormal by attempting to obtain fault data through the first transmission path. The method for determining whether the first transmission path is abnormal is simple and reduces the complexity of processing.

[0018] According to a second aspect of the present disclosure, an application processor is provided, the application processor comprising: A first data interface is used to be electrically connected to a communication processor and to receive fault status information sent by the communication processor, wherein the fault status information is used to indicate that the communication processor is in a fault state. A second data interface is used to be electrically connected to the communication processor to form a second transmission path; A processing device, electrically connected to both the first data interface and the second data interface, is configured to, in response to the first data interface receiving the fault status information and the first transmission path between the application processor and the communication processor being abnormal, determine a fault data acquisition command, and is further configured to send the fault data acquisition command to the communication processor via the second transmission path and receive fault data returned by the communication processor according to the fault data acquisition command, wherein the fault data is used to determine the reason why the communication processor is in the fault state.

[0019] In this embodiment, when the communication processor fails and the first transmission path is abnormal, the application processor can obtain fault data through the second transmission path, thus avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0020] In some embodiments of this disclosure, the processing apparatus includes a parsing unit, which is used to parse a fault data acquisition file to determine the fault data acquisition command; The fault data acquisition file is pre-stored in the application processor; or The application processor also includes: A third data interface is used to electrically connect to a first external device, wherein, in response to the first data interface receiving the fault status information and the first transmission path being abnormal, the third data interface is used to receive the fault data acquisition file sent by the first external device.

[0021] In this embodiment, the fault data acquisition command can be determined by parsing the fault data acquisition file. The fault data acquisition file is easy to modify and maintain, which improves the flexibility of acquiring fault data.

[0022] In some embodiments of this disclosure, the application processor further includes: A fourth data interface is provided, which is electrically connected to a second external device and to the processing device. In response to the first data interface receiving the fault status information and the first transmission path being abnormal, the fourth data interface is used to receive the fault data acquisition command sent by the second external device.

[0023] In this embodiment, the fault data acquisition command can be directly determined without parsing the file, saving time and improving the efficiency of fault data acquisition.

[0024] In some embodiments of this disclosure, the processing apparatus includes: An encapsulation unit is used to encapsulate the fault data acquisition command into a format corresponding to the second transmission path; A driving unit is configured to invoke the second data interface to send the encapsulated fault data acquisition command to the communication processor via the second transmission path.

[0025] In this embodiment, the fault data acquisition command is encapsulated and transmitted via the second transmission path, which ensures that the fault data acquisition command is successfully sent to the communication processor, thereby improving the reliability of fault data acquisition.

[0026] In some embodiments of this disclosure, the fault data acquisition command includes multiple sub-acquisition commands, and the processing device is further configured to send the next sub-acquisition command to the communication processor after sending one of the sub-acquisition commands to the communication processor and receiving sub-fault data returned by the communication processor according to the sub-acquisition command or after the sub-acquisition command is executed; The fault data includes the sub-fault data obtained through all the sub-acquisition commands.

[0027] In some embodiments of this disclosure, the plurality of sub-acquisition commands include at least one write command and at least one read command. The write command is used to make the storage area readable after the data contained in the write command is written to the storage area corresponding to the write command in the communication processor. The read command is used to read the data in the storage area corresponding to the read command in the communication processor.

[0028] In some embodiments of this disclosure, the processing apparatus is further configured to: In response to receiving the fault status information, the fault data is obtained through the first transmission path; In response to the inability to obtain the fault data through the first transmission path, it is determined that the first transmission path is abnormal.

[0029] According to a third aspect of the present disclosure, a communication processor is provided, the communication processor comprising: The fifth data interface is used to be electrically connected to the application processor and to send fault status information to the application processor, wherein the fault status information is used to indicate that the communication processor is in a fault state. A conversion device is configured to be electrically connected to the application processor to form a second transmission path, and to be electrically connected to multiple storage areas of the communication processor; the conversion device is configured to receive a fault data acquisition command sent by the application processor through the second transmission path, and to acquire fault data corresponding to the fault data acquisition command from the multiple storage areas according to the fault data acquisition command, and to return the fault data to the application processor through the second transmission path; The fault data is used to determine the reason why the communication processor is in the fault state.

[0030] In this embodiment, when the communication processor fails and the first transmission path is abnormal, the communication processor can receive the fault data acquisition command sent by the application processor through the second transmission path, and return the read fault data to the application processor after executing the fault data acquisition command, thereby avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0031] In some embodiments of this disclosure, the conversion device includes: The sixth data interface is used to be electrically connected to the application processor to form the second transmission path, and is used to receive the fault data acquisition command and return the fault data through the second transmission path; A seventh data interface is electrically connected to multiple storage areas and is used to obtain the fault data from the multiple storage areas. The conversion unit is used to convert the fault data acquisition command into a form that the seventh data interface can recognize and then transmit it to the seventh data interface, and to convert the fault data into a format corresponding to the second transmission path and then transmit it to the sixth data interface.

[0032] In this embodiment, the application processor can access the storage area of ​​the communication processor through a hardware connection and a software-implemented conversion unit to obtain fault data, which is used to determine the cause of the fault and handle the fault problem of the communication processor in a timely manner.

[0033] According to a fourth aspect of the present disclosure, an application processor chip is provided, including the application processor as described in the second aspect of the present disclosure.

[0034] According to a fifth aspect of the present disclosure, a communication processor chip is provided, including the communication processor as described in the third aspect of the present disclosure.

[0035] According to a sixth aspect of the present disclosure, an electronic device is provided, the electronic device including an application processor chip as described in the fourth aspect of the present disclosure and a communication processor chip as described in the fifth aspect of the present disclosure, or processor; Memory used to store the processor's executable instructions; The processor is configured to execute the fault data acquisition method described above.

[0036] According to a seventh aspect of the present disclosure, a non-transitory 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 the fault data acquisition method as described above.

[0037] According to an eighth aspect of the present disclosure, a computer program product is provided, including a computer program or instructions, which, when executed by a processor, implement the fault data acquisition method described above.

[0038] 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

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

[0040] Figure 1 This is a schematic diagram of the structure of an application processor according to an exemplary embodiment; Figure 2This is a schematic diagram illustrating data interaction between a processing device and a conversion unit according to an exemplary embodiment; Figure 3 This is a schematic diagram of the structure of a communication processor according to an exemplary embodiment; Figure 4 This is an application scenario diagram illustrating a method for acquiring fault data according to an exemplary embodiment; Figure 5 This is a flowchart illustrating a method for acquiring fault data according to an exemplary embodiment; Figure 6 This is a flowchart illustrating a method for acquiring fault data according to another exemplary embodiment; Figure 7 This is a block diagram of an electronic device according to an exemplary embodiment.

[0041] In the picture: 1-Application processor; 3-Communication processor; 11-First data interface; 12-Second data interface; 13-Processing device; 31-Fifth data interface; 32-Conversion device; 33-Storage area; 131-Parsing unit; 132-Packaging unit; 133-Driver unit; 134-Device file unit; 321-Conversion unit; 322-Sixth data interface; 700-Electronic device; 702-Processing component; 704-Memory; 706-Power supply component; 708-Multimedia component; 710-Audio component; 712-Input / output interface; 714-Sensor component; 716-Communication component; 720-Processor. Detailed Implementation

[0042] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. 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. It should also be understood that the term “and / or” as used in this disclosure refers to any or all possible combinations including one or more of the associated listed items.

[0043] When the application processor and communication processor are on two different chips, in response to receiving information from the communication processor indicating a fault state, the application processor can obtain fault data to determine the cause of the communication processor's fault state through the first transmission path between the application processor and the communication processor. This first transmission path can be a high-speed peripheral component interconnect (PCIe). If the first transmission path malfunctions, the application processor cannot obtain fault data through it. In this case, the electronic device needs to be disassembled, and the communication processor needs to be connected to external debugging equipment via jumper wires. The external debugging equipment then handles the communication processor's fault. This method not only damages the structure of the electronic device but also requires time and is inefficient.

[0044] Based on this, this disclosure provides an application processor and a communication processor, wherein a second data interface of the application processor and a sixth data interface of the conversion device of the communication processor are electrically connected to form a second transmission path. When the application processor receives fault status information sent by the communication processor and the first transmission path is abnormal, the application processor can obtain fault data through the second transmission path, avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0045] This disclosure provides an application processor, such as... Figure 1 As shown, the application processor 1 includes a first data interface 11, a second data interface 12, and a processing device 13. The first data interface 11 is electrically connected to the communication processor 3 and is used to receive fault status information sent by the communication processor 3. The fault status information indicates that the communication processor 3 is in a fault state. The second data interface 12 is electrically connected to the communication processor 3 to form a second transmission path. The processing device 13 is electrically connected to both the first data interface 11 and the second data interface 12, and is used to determine a fault data acquisition command in response to the first data interface 11 receiving fault status information and the first transmission path between the application processor 1 and the communication processor 3 being abnormal. It is also used to send the fault data acquisition command to the communication processor 3 through the second transmission path and receive fault data returned by the communication processor 3 based on the fault data acquisition command. The fault data is used to determine the cause of the communication processor 3 being in a fault state.

[0046] For example, the first data interface 11 can be electrically connected to the communication processor 3 via a first connection line, such as being electrically connected to the fifth data interface of the communication processor 3 via the first connection line. When the communication processor 3 is in a fault state, it can send fault state information to the first data interface 11, for example, by sending the fault state information to the first data interface 11 via an interrupt, so that the application processor 1 can quickly process the fault state of the communication processor 3.

[0047] For example, the second data interface 12 can be electrically connected to the communication processor 3 via a second connection line, for instance, to the sixth data interface of the conversion device of the communication processor 3 via the second connection line. Both the second data interface 12 and the sixth data interface of the conversion device of the communication processor 3 can be Serial Peripheral Interface (SPI).

[0048] For example, in response to receiving fault status information through the first data interface 11, the processing device 13 can obtain the fault status information through the first data interface 11 and obtain fault data for determining the cause of the communication processor 3's fault state through the first transmission path between the application processor 1 and the communication processor 3. The first transmission path is, for example, a high-speed peripheral component interconnect. In response to the inability to obtain fault data through the first transmission path, the processing device 13 can determine that the first transmission path is abnormal. At this time, the processing device can determine a fault data acquisition command and send the fault data acquisition command to the communication processor 3 through the second transmission path and receive the fault data returned by the communication processor 3.

[0049] For example, the processing device 13 can determine the fault data acquisition command by parsing a fault data acquisition file pre-stored in the application processor 1 or obtained from an external source, or it can directly obtain the fault data acquisition command from an external source. The fault data acquisition command may include at least one read command and at least one write command. The write command is used to write the data contained in the write command into the storage area corresponding to the write command in the communication processor 3, making the storage area readable. The read command is used to read the data in the storage area corresponding to the read command in the communication processor 3. After receiving the fault data acquisition command, the communication processor 3 performs read and write operations on the storage area corresponding to the fault data acquisition command, and returns the read fault data to the application processor 1 through the second transmission path. After obtaining the fault data from the second data interface 12, the processing device 13 can store the fault data in a corresponding file for subsequent use in fault cause analysis of the communication processor 3.

[0050] In this embodiment, when the communication processor fails and the first transmission path is abnormal, the application processor can obtain fault data through the second transmission path, thus avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0051] In one embodiment, such as Figure 2 As shown, the processing device 13 includes a parsing unit 131. The parsing unit 131 is used to parse the fault data acquisition file to determine the fault data acquisition command.

[0052] The fault data acquisition file is pre-stored in the application processor 1, or the application processor 1 further includes a third data interface for electrically connecting to the first external device. In response to the first data interface 11 receiving fault status information and the first transmission path being abnormal, the third data interface is used to receive the fault data acquisition file sent by the first external device.

[0053] For example, the parsing unit 131 can determine the fault data acquisition command by executing the parsing command for the fault data acquisition file.

[0054] For example, the third data interface may be a USB interface, and the first external device may be a computer. The third data interface can be electrically connected to the first external device via a third connection cable. A fault data acquisition file can be edited and generated on the first external device and sent to the third data interface of application processor 1 via the third connection cable.

[0055] In this embodiment, the fault data acquisition command can be determined by parsing the fault data acquisition file. The fault data acquisition file is easy to modify and maintain, which improves the flexibility of acquiring fault data.

[0056] In one embodiment, the application processor 1 further includes a fourth data interface for electrically connecting to a second external device and to the processing device 13. In response to the first data interface 11 receiving fault status information and the first transmission path being abnormal, the fourth data interface is used to receive a fault data acquisition command sent by the second external device.

[0057] For example, the fourth data interface can be a USB interface, and the second external device can be a computer. The fourth data interface can be electrically connected to the second external device via a fourth connection cable. A fault data acquisition command can be edited and generated on the second external device and sent to the fourth data interface of the application processor 1 via the fourth connection cable. The processing device 13 can obtain the fault data acquisition command from the fourth data interface for subsequent processing. The third data interface and the fourth data interface can be the same interface, the first external device and the second external device can be the same external device, and the third connection cable and the fourth connection cable can be the same connection cable.

[0058] In this embodiment, the fault data acquisition command can be directly determined without parsing the file, saving time and improving the efficiency of fault data acquisition.

[0059] In one embodiment, such as Figure 2 As shown, the processing device 13 includes an encapsulation unit 132 and a driving unit 133. The encapsulation unit 132 is used to encapsulate the fault data acquisition command into a format corresponding to the second transmission path. The driving unit 133 is used to invoke the second data interface 12 to send the encapsulated fault data acquisition command to the communication processor 3 through the second transmission path.

[0060] For example, the encapsulation unit 132 and the parsing unit 131 belong to the user mode, the driver unit 133 belongs to the kernel mode, and the processing device 13 also includes Figure 2 The device file unit 134, encapsulation unit 132, and driver unit 133 shown can access each other through the device file unit 134. The parsing unit 131, encapsulation unit 132, driver unit 133, and device file unit 134 can all be implemented in software.

[0061] In this embodiment, the fault data acquisition command is encapsulated and transmitted via the second transmission path, which ensures that the fault data acquisition command is successfully sent to the communication processor, thereby improving the reliability of fault data acquisition.

[0062] In one embodiment, the fault data acquisition command includes multiple sub-acquisition commands. The processing device 13 is further configured to send the next sub-acquisition command to the communication processor 3 after sending a sub-acquisition command to the communication processor 3 and receiving the sub-fault data returned by the communication processor 3 according to the sub-acquisition command or after the sub-acquisition command is executed. The fault data includes sub-fault data obtained through the full sub-acquisition command.

[0063] In one embodiment, the plurality of sub-acquisition commands include at least one write command and at least one read command. The write command is used to make the storage area readable after the data contained in the write command is written into the storage area corresponding to the write command in the communication processor 3. The read command is used to read the data in the storage area corresponding to the read command in the communication processor 3.

[0064] In one embodiment, the processing device 13 is further configured to: In response to receiving fault status information, fault data is obtained through the first transmission path; In response to the inability to obtain fault data through the first transmission path, it is determined that the first transmission path is abnormal.

[0065] This disclosure provides a communication processor, such as... Figure 3As shown, the communication processor 3 includes a fifth data interface 31 and a conversion device 32. The fifth data interface 31 is electrically connected to the application processor 1 and is used to send fault status information to the application processor 1. The fault status information indicates that the communication processor 3 is in a fault state. The conversion device 32 is electrically connected to the application processor 1 to form a second transmission path and is also electrically connected to multiple storage areas 33 of the communication processor 3. The conversion device 32 receives fault data acquisition commands sent by the application processor 1 through the second transmission path, and retrieves the fault data corresponding to the fault data acquisition command from the multiple storage areas 33 according to the fault data acquisition command, and returns the fault data to the application processor 1 through the second transmission path. The fault data is used to determine the cause of the communication processor 3 being in a fault state.

[0066] For example, the fifth data interface 31 can be electrically connected to the application processor 1 via the first connection line, such as being electrically connected to the first data interface 11 of the application processor 1 via the first connection line. When the communication processor 3 is in a fault state, it can send fault status information to the application processor 1 via the fifth data interface 31, for example, by sending the fault status information to the application processor 1 via an interrupt, so that the application processor 1 can quickly process the fault state of the communication processor 3.

[0067] For example, the conversion device 32 may include a sixth data interface, a seventh data interface, and a conversion unit. The sixth data interface can be electrically connected to the application processor 1 via a second connection line to form a second transmission path, for example, it can be electrically connected to the second data interface 12 of the application processor 1 via the second connection line. Both the sixth data interface and the second data interface 12 of the application processor 1 can be serial peripheral interfaces. The seventh data interface is, for example, an Advanced High-performance Bus (AHB) interface, which is electrically connected to multiple storage areas 33 via the AHB. Through this interface and bus, read and write operations corresponding to fault data acquisition commands can be performed on multiple storage areas 33 to acquire fault data. For example, if the fault data is distributed in multiple storage areas 33, and some storage areas 33 are in a non-readable state, the data contained in the write command in the fault data acquisition command can be written into the corresponding storage area 33 to make the storage area 33 readable. The data in the corresponding storage area 33 can be read by executing the read command in the fault data acquisition command, and the data read by executing all the read commands in the fault data acquisition command constitutes the fault data. The conversion unit can be used to convert the fault data acquisition command received from the application processor 1 into a form that the seventh data interface can recognize and then transmit it to the seventh data interface. It can also be used to convert the fault data transmitted from the storage area 33 to the seventh data interface into a format corresponding to the second transmission path and then transmit it to the sixth data interface.

[0068] In this embodiment, when the communication processor fails and the first transmission path is abnormal, the communication processor can receive the fault data acquisition command sent by the application processor through the second transmission path, and return the read fault data to the application processor after executing the fault data acquisition command, thereby avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0069] In one embodiment, the conversion device 32 includes a sixth data interface, a seventh data interface, and Figure 2 The conversion unit 321 is shown. The sixth data interface is electrically connected to the application processor 1 to form a second transmission path, and is used to receive fault data retrieval commands and return fault data through the second transmission path. The seventh data interface is electrically connected to multiple storage areas 33, and is used to retrieve fault data from the multiple storage areas 33. The conversion unit 321 is used to convert the fault data retrieval command into a form recognizable by the seventh data interface and transmit it to the seventh data interface, and to convert the fault data into a format corresponding to the second transmission path and transmit it to the sixth data interface.

[0070] For example, the sixth data interface can be electrically connected to the application processor 1 via the second connection line to form a second transmission path, such as being electrically connected to the second data interface 12 of the application processor 1 via the second connection line. Both the sixth data interface and the second data interface 12 of the application processor 1 can be serial peripheral interfaces. The sixth data interface can receive fault data acquisition commands sent by the application processor 1, or return fault data corresponding to the fault data acquisition command to the application processor 1.

[0071] For example, the seventh data interface is, for instance, an Advanced High-Performance Bus (AHS) interface, which is electrically connected to multiple storage areas 33 via an AHS bus. Through this interface and bus, read and write operations corresponding to fault data retrieval commands can be executed on the multiple storage areas 33 to obtain fault data. For example, if the fault data is distributed across multiple storage areas 33, and some storage areas 33 are in a non-readable state, the data contained in the write command of the fault data retrieval command can be written into the corresponding storage area 33, making that storage area 33 readable. Data in the corresponding storage area 33 can be read by executing the read command in the fault data retrieval command; the data read by all the read commands in the fault data retrieval command constitutes the fault data.

[0072] For example, the conversion unit 321 can be implemented in software.

[0073] In this embodiment, the application processor can access the storage area of ​​the communication processor through a hardware connection and a software-implemented conversion unit to obtain fault data, which is used to determine the cause of the fault and handle the fault problem of the communication processor in a timely manner.

[0074] To facilitate understanding, the application scenarios of the fault data acquisition method disclosed herein are first described. The fault data acquisition method disclosed herein can be applied to... Figure 4 The application processor 1 is shown. (e.g.) Figure 4 As shown, application processor 1 includes a first data interface 11 and a second data interface 12. Communication processor 3 includes a fifth data interface 31 and a conversion device 32, the conversion device 32 including a sixth data interface 322. The first data interface 11 is electrically connected to the fifth data interface 31. The second data interface 12 is electrically connected to the sixth data interface 322, forming a second transmission path. For example, if the second data interface 12 and the sixth data interface 322 are electrically connected via a second connecting line, then the second transmission path includes the second data interface 12, the sixth data interface 322, and the second connecting line. Figure 4 As shown, the second data interface 12 includes a first pin CS1, a second pin CLK1, a third pin DI1, and a fourth pin DO1. The sixth data interface 322 includes a fifth pin CS2, a sixth pin CLK2, a seventh pin DI2, and an eighth pin DO2. The first pin CS1 is electrically connected to the fifth pin CS2 and is used to transmit a signal from the application processor 1 to the communication processor 3. The second pin CLK1 is electrically connected to the sixth pin CLK2 and is used to transmit a clock signal sent by the application processor 1 to the communication processor 3 to achieve clock synchronization. The third pin DI1 is electrically connected to the eighth pin DO2 and is used to transmit data sent from the communication processor 3 to the application processor 1, such as fault data. The fourth pin DO1 is electrically connected to the seventh pin DI2 and is used to transmit data sent from the application processor 1 to the communication processor 3, such as a fault data retrieval command.

[0075] This disclosure provides a method for obtaining fault data, such as... Figure 5 As shown, the acquisition methods include: S100: In response to receiving fault status information sent by the communication processor and the first transmission path between the communication processor being abnormal, a fault data acquisition command is determined.

[0076] Fault status information is used to characterize the communication processor in a fault state.

[0077] For example, when the communication processor 3 is in a fault state, it can send fault state information to the first data interface 11 of the application processor 1 through the fifth data interface 31, for example, by sending the fault state information to the first data interface 11 through an interrupt, so that the application processor 1 can quickly process the fault state of the communication processor 3.

[0078] For example, in response to receiving fault status information, application processor 1 can obtain fault data to determine the cause of the fault state of communication processor 3 via a first transmission path with communication processor 3, such as a high-speed peripheral component interconnect. In response to the inability to obtain fault data via the first transmission path, application processor 1 can determine that the first transmission path is abnormal, and at this time application processor 1 can determine a fault data acquisition command.

[0079] For example, application processor 1 can determine the fault data acquisition command by parsing a fault data acquisition file pre-stored by application processor 1 or obtained from an external source, or it can directly obtain the fault data acquisition command from an external source.

[0080] S200: The fault data acquisition command is sent to the communication processor via the second transmission path.

[0081] For example, application processor 1 can first encapsulate the fault data acquisition command into a format corresponding to the second transmission path, and then send the encapsulated fault data acquisition command to communication processor 3 through the second transmission path.

[0082] S300: Receive fault data returned by the communication processor based on the fault data acquisition command through the second transmission path.

[0083] Fault data is used to determine the cause of a fault in the communication processor.

[0084] For example, the fault data acquisition command may include at least one read command and at least one write command. The write command is used to write the data contained in the write command into the storage area corresponding to the write command in the communication processor 3, making the storage area readable. The read command is used to read the data in the storage area corresponding to the read command in the communication processor 3. After receiving the fault data acquisition command, the communication processor 3 performs read and write operations on the storage area corresponding to the communication processor 3 according to the fault data acquisition command, and returns the read fault data to the application processor 1 through the second transmission path. After receiving the fault data through the second transmission path, the application processor 1 can store the fault data in the corresponding file for subsequent use in fault cause analysis of the communication processor 3.

[0085] In this embodiment, after receiving the fault status information reported by the communication processor and confirming that the first transmission path is abnormal, the application processor can obtain the fault data through the second transmission path, which avoids damage to the electronic device structure and improves the data acquisition efficiency.

[0086] In one embodiment, determining the fault data acquisition command in step S100 includes: parsing the fault data acquisition file to determine the fault data acquisition command.

[0087] The fault data acquisition file is pre-stored in the application processor, or the acquisition method further includes: in response to receiving fault status information and the first transmission path being abnormal, receiving the fault data acquisition file sent by the first external device.

[0088] For example, the fault data acquisition command can be determined by executing a parsing command on the fault data acquisition file.

[0089] For example, application processor 1 can be electrically connected to a first external device to receive a fault data acquisition file sent by the first external device. The first external device can be a computer, which can edit and generate the fault data acquisition file before sending it to application processor 1.

[0090] In this embodiment, the fault data acquisition file is easy to modify and maintain. By parsing the fault data acquisition file to determine the fault data acquisition command, the flexibility of acquiring fault data is improved.

[0091] In one embodiment, determining the fault data acquisition command in step S100 includes: in response to receiving fault status information and the first transmission path being abnormal, receiving a fault data acquisition command sent by a second external device.

[0092] For example, application processor 1 can be electrically connected to a second external device to receive a fault data acquisition command sent by the second external device. The second external device can be a computer, and the fault data acquisition command can be edited and generated on the second external device before being sent to application processor 1. The first external device and the second external device can be the same external device.

[0093] In this embodiment, the fault data acquisition command can be directly determined without parsing the file, saving time and improving the efficiency of fault data acquisition.

[0094] In one embodiment, sending the fault data acquisition command to the communication processor via the second transmission path in step S200 includes: S210. Encapsulate the fault data acquisition command into a format corresponding to the second transmission path.

[0095] S220: The encapsulated fault data acquisition command is sent to the communication processor via the second transmission path.

[0096] For example, application processor 1 may include Figure 2 The encapsulation unit 132, driver unit 133, and device file unit 134 shown can all be implemented in software. After encapsulating the fault data acquisition command into the format corresponding to the second transmission path, the encapsulation unit 132 accesses the driver unit 133 through the device file unit 134, causing the driver unit 133 to call the second data interface 12 and send the encapsulated fault data acquisition command to the communication processor 3 through the second transmission path.

[0097] In this embodiment, after the application processor determines the fault data acquisition command, it first encapsulates the fault data acquisition command and then sends the fault data acquisition command in the format corresponding to the second transmission path to the communication processor through the second transmission path, thereby improving the reliability of fault data acquisition.

[0098] In one embodiment, the fault data acquisition command includes multiple sub-acquisition commands. After the application processor sends a sub-acquisition command to the communication processor and receives sub-fault data returned by the communication processor based on that sub-acquisition command, or after the sub-acquisition command has been executed, it sends the next sub-acquisition command to the communication processor. The fault data includes sub-fault data acquired through all the sub-acquisition commands.

[0099] For example, fault data can be stored in multiple storage areas of the communication processor 3. A sub-acquisition command can be a read command or a write command for a storage area. If the sub-acquisition command is a read command, after receiving the sub-fault data returned by the communication processor 3 according to the sub-acquisition command, the application processor 1 can send the next sub-acquisition command to the communication processor 3. If the sub-acquisition command is a write command, after the application processor 1 sends the sub-acquisition command to the communication processor 3, it can consider the sub-acquisition command to be completed and continue to send the next sub-acquisition command to the communication processor 3.

[0100] The fault data includes sub-fault data obtained through the all-sub-acquire command, and may include sub-fault data read through the read command in the all-sub-acquire command.

[0101] In this embodiment, since the communication processor is already in a fault state, sending the next sub-acquisition command after the execution of one sub-acquisition command can reduce the processing burden of the communication processor and avoid further failures caused by excessive processing burden in the fault state.

[0102] In one embodiment, the plurality of sub-acquisition commands include at least one write command and at least one read command. The write command is used to make the storage area readable after the data contained in the write command is written to the storage area corresponding to the write command in the communication processor. The read command is used to read the data in the storage area corresponding to the read command in the communication processor.

[0103] For example, fault data is distributed across multiple storage areas of the communication processor 3. Some of these storage areas are currently unreadable. Data contained in a write command can be written into the corresponding storage area, making that area readable. Data in the corresponding storage area can be read by executing a read command. The fault data is composed of data read from all sub-read commands of the read command.

[0104] In this embodiment, for storage areas that are not readable, data is first written to make them readable, and then complete fault data can be obtained, which improves the accuracy of subsequent fault diagnosis.

[0105] In one embodiment, the acquisition method further includes: S400: In response to receiving fault status information, fault data is obtained through the first transmission path.

[0106] S500: In response to the inability to obtain fault data through the first transmission path, determine that the first transmission path is abnormal.

[0107] For example, application processor 1 first attempts to obtain fault data through a first transmission path. If it is unable to obtain fault data through the first transmission path, it determines that the first transmission path is abnormal and then obtains fault data through a second transmission path.

[0108] In this embodiment, the application processor determines whether the first transmission path is abnormal by attempting to obtain fault data through the first transmission path. The method for determining whether the first transmission path is abnormal is simple and reduces the complexity of processing.

[0109] This disclosure provides a method for obtaining fault data, such as... Figure 6 As shown, the acquisition methods include: S601. In response to receiving fault status information sent by the communication processor, fault data is obtained through the first transmission path.

[0110] Fault status information is used to characterize the communication processor in a fault state.

[0111] S602. In response to the inability to obtain fault data through the first transmission path, determine that the first transmission path is abnormal.

[0112] Fault data is used to determine the cause of a fault in the communication processor.

[0113] S603. In response to an anomaly in the first transmission path, parse the fault data acquisition file to determine the fault data acquisition command, or receive the fault data acquisition command sent by the second external device.

[0114] The fault data acquisition file is pre-stored in the application processor or sent to the application processor by the first external device.

[0115] S604. Encapsulate the fault data acquisition command into a format corresponding to the second transmission path.

[0116] S605, The encapsulated fault data acquisition command is sent to the communication processor via the second transmission path.

[0117] S606: Receive fault data returned by the communication processor based on the fault data acquisition command through the second transmission path.

[0118] This disclosure provides an application processor chip, including any of the application processors described in the above embodiments. In this embodiment, because the application processor chip includes the application processors described in the above embodiments, in the event of a communication processor failure and an abnormal first transmission path, fault data can be obtained through a second transmission path, avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0119] This disclosure provides a communication processor chip, including any of the communication processors described in the above embodiments. In this embodiment, because the communication processor chip includes the communication processors described in the above embodiments, in the event of a communication processor failure and an abnormal first transmission path, the communication processor can receive a fault data acquisition command sent by the application processor through a second transmission path, and after executing the fault data acquisition command, return the read fault data to the application processor, thus avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0120] This disclosure provides an electronic device including an application processor chip and a communication processor chip as described in the above embodiments. In this embodiment, because the electronic device includes the application processor chip and the communication processor chip as described in the above embodiments, in the event of a communication processor failure and an abnormal first transmission path between the application processor and the communication processor, the application processor can obtain the communication processor's fault data through a second transmission path, thus avoiding damage to the electronic device structure and improving data acquisition efficiency.

[0121] This disclosure provides an electronic device, such as a mobile phone, laptop computer, tablet computer, and wearable device.

[0122] refer to Figure 7As shown, the electronic device 700 may include one or more of the following components: processing component 702, memory 704, power supply component 706, multimedia component 708, audio component 710, input / output (I / O) interface 712, sensor component 714, and communication component 716.

[0123] Processing component 702 typically controls the overall operation of electronic 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 fault data acquisition method 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.

[0124] Memory 704 is configured to store various types of data to support the operation of electronic device 700. Examples of this data include instructions for any application or method operating on electronic device 700, contact data, phonebook data, messages, pictures, videos, etc. Memory 704 can be implemented by any type of volatile or non-volatile storage terminal 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.

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

[0126] Multimedia component 708 includes a screen that provides an output interface between electronic device 700 and 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 touch or swipe actions but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 708 includes a front-facing camera module and / or a rear-facing camera module. When electronic device 700 is in an operating mode, such as shooting mode or video mode, the front-facing camera module and / or rear-facing camera module may receive external multimedia data. Each front-facing camera module and rear-facing camera module may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0127] 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 electronic 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.

[0128] 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.

[0129] Sensor assembly 714 includes one or more sensors for providing state assessments of various aspects of electronic device 700. For example, sensor assembly 714 may detect the on / off state of electronic device 700, the relative positioning of components such as the display and keypad of electronic device 700, changes in position of electronic device 700 or a component of electronic device 700, the presence or absence of user contact with electronic device 700, orientation or acceleration / deceleration of electronic device 700, and temperature changes of electronic 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, gyroscope, magnetometer, pressure sensor, or temperature sensor.

[0130] Communication component 716 is configured to facilitate wired or wireless communication between electronic device 700 and other terminals. Electronic device 700 can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G, 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.

[0131] In an exemplary embodiment, the electronic device 700 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing terminals (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the fault data acquisition method shown in the above embodiments or combinations thereof.

[0132] This disclosure provides a non-transitory computer-readable storage medium including instructions, such as a memory 704 including instructions, which can be executed by a processor 720 of an electronic device 700 to perform the fault data acquisition method shown in the above embodiments or combinations thereof. For example, the non-transitory computer-readable storage medium may be a ROM, CD-ROM, magnetic tape, floppy disk, and optical data storage terminal, etc. When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the fault data acquisition method shown in the above embodiments or combinations thereof.

[0133] This disclosure provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the fault data acquisition method described above.

[0134] 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 disclosure 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 claims.

[0135] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of this disclosure. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0136] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this disclosure, "a plurality of" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0137] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this disclosure can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and this is not limited herein.

[0138] The specific embodiments described above do not constitute a limitation on the scope of protection of this disclosure. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this disclosure should be included within the scope of protection of this disclosure.

[0139] 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 disclosure 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 claims.

[0140] 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.

[0141] The examples in this document may involve user data, data acquisition, and / or use. All of these aspects comply with relevant laws, regulations, and rules. In the examples, all data collection, acquisition, processing, manipulation, forwarding, and use are conducted with the user's knowledge and confirmation. Accordingly, when implementing each example, the type, scope of use, and usage scenarios of any data or information that may be involved should be communicated to the user and their authorization obtained through appropriate means, in accordance with relevant laws and regulations. The specific methods of notification and / or authorization can vary depending on the actual situation and application scenario; the scope of the solution is not limited in this regard.

[0142] In this manual and the sample solutions, any processing of personal information will be conducted only under legal grounds (such as obtaining the consent of the data subject or being necessary for the performance of a contract) and will only be carried out within the scope stipulated or agreed upon. A user's refusal to process personal information beyond what is necessary for basic functions will not affect the user's use of basic functions.

Claims

1. A method for acquiring fault data, characterized in that, The acquisition method includes: In response to receiving fault status information sent by the communication processor and the first transmission path between the communication processor and the communication processor being abnormal, a fault data acquisition command is determined, wherein the fault status information is used to characterize that the communication processor is in a fault state. The fault data acquisition command is sent to the communication processor via the second transmission path; The communication processor receives fault data returned by the fault data acquisition command through the second transmission path, wherein the fault data is used to determine the reason why the communication processor is in the fault state.

2. The method for acquiring fault data according to claim 1, characterized in that, The command to determine fault data acquisition includes: Parse the fault data acquisition file to determine the fault data acquisition command; The fault data acquisition file is pre-stored in the application processor, or the acquisition method further includes: in response to receiving the fault status information and the first transmission path being abnormal, receiving the fault data acquisition file sent by the first external device.

3. The method for acquiring fault data according to claim 1, characterized in that, The command to determine fault data acquisition includes: In response to receiving the fault status information and the first transmission path being abnormal, the system receives the fault data acquisition command sent by the second external device.

4. The method for acquiring fault data according to claim 1, characterized in that, Sending the fault data acquisition command to the communication processor via the second transmission path includes: The fault data acquisition command is encapsulated into a format corresponding to the second transmission path; The encapsulated fault data acquisition command is sent to the communication processor via the second transmission path.

5. The method for acquiring fault data according to claim 1, characterized in that, The fault data acquisition command includes multiple sub-acquisition commands. After the application processor sends one of the sub-acquisition commands to the communication processor and receives the sub-fault data returned by the communication processor according to the sub-acquisition command or after the sub-acquisition command is executed, it sends the next sub-acquisition command to the communication processor. The fault data includes the sub-fault data obtained through all the sub-acquisition commands.

6. The method for acquiring fault data according to claim 5, characterized in that, The plurality of sub-acquisition commands include at least one write command and at least one read command. The write command is used to make the storage area readable after the data contained in the write command is written to the storage area corresponding to the write command in the communication processor. The read command is used to read the data in the storage area corresponding to the read command in the communication processor.

7. The method for acquiring fault data according to claim 1, characterized in that, The acquisition method further includes: In response to receiving the fault status information, the fault data is obtained through the first transmission path; In response to the inability to obtain the fault data through the first transmission path, it is determined that the first transmission path is abnormal.

8. An application processor, characterized in that, The application processor includes: A first data interface is used to be electrically connected to a communication processor and to receive fault status information sent by the communication processor, wherein the fault status information is used to indicate that the communication processor is in a fault state. A second data interface is used to be electrically connected to the communication processor to form a second transmission path; A processing device, electrically connected to both the first data interface and the second data interface, is configured to, in response to the first data interface receiving the fault status information and the first transmission path between the application processor and the communication processor being abnormal, determine a fault data acquisition command, and is further configured to send the fault data acquisition command to the communication processor via the second transmission path and receive fault data returned by the communication processor according to the fault data acquisition command, wherein the fault data is used to determine the reason why the communication processor is in the fault state.

9. The application processor according to claim 8, characterized in that, The processing device includes a parsing unit, which is used to parse the fault data acquisition file to determine the fault data acquisition command. The fault data acquisition file is pre-stored in the application processor; or The application processor also includes: A third data interface is used to electrically connect to a first external device, wherein, in response to the first data interface receiving the fault status information and the first transmission path being abnormal, the third data interface is used to receive the fault data acquisition file sent by the first external device.

10. The application processor according to claim 8, characterized in that, The application processor also includes: A fourth data interface is provided, which is electrically connected to a second external device and to the processing device. In response to the first data interface receiving the fault status information and the first transmission path being abnormal, the fourth data interface is used to receive the fault data acquisition command sent by the second external device.

11. The application processor according to claim 8, characterized in that, The processing device includes: An encapsulation unit is used to encapsulate the fault data acquisition command into a format corresponding to the second transmission path; A driving unit is configured to invoke the second data interface to send the encapsulated fault data acquisition command to the communication processor via the second transmission path.

12. A communication processor, characterized in that, The communication processor includes: The fifth data interface is used to be electrically connected to the application processor and to send fault status information to the application processor, wherein the fault status information is used to indicate that the communication processor is in a fault state. A conversion device is configured to be electrically connected to the application processor to form a second transmission path, and to be electrically connected to multiple storage areas of the communication processor; the conversion device is configured to receive a fault data acquisition command sent by the application processor through the second transmission path, and to acquire fault data corresponding to the fault data acquisition command from the multiple storage areas according to the fault data acquisition command, and to return the fault data to the application processor through the second transmission path; The fault data is used to determine the reason why the communication processor is in the fault state.

13. The communication processor according to claim 12, characterized in that, The conversion device includes: The sixth data interface is used to be electrically connected to the application processor to form the second transmission path, and is used to receive the fault data acquisition command and return the fault data through the second transmission path; A seventh data interface is electrically connected to multiple storage areas and is used to obtain the fault data from the multiple storage areas. The conversion unit is used to convert the fault data acquisition command into a form that the seventh data interface can recognize and then transmit it to the seventh data interface, and to convert the fault data into a format corresponding to the second transmission path and then transmit it to the sixth data interface.

14. An application processor chip, characterized in that, Includes the application processor as described in any one of claims 8 to 11.

15. A communication processor chip, characterized in that, Includes the communication processor as described in any one of claims 12 to 13.

16. An electronic device, characterized in that, The electronic device includes the application processor chip as described in claim 14 and the communication processor chip as described in claim 15, or processor; Memory used to store the processor's executable instructions; The processor is configured to perform the fault data acquisition method as described in any one of claims 1 to 7.

17. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform the fault data acquisition method as described in any one of claims 1 to 7.

18. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are executed by the processor, the method for acquiring fault data as described in any one of claims 1 to 7 is implemented.

Images