CN116662096A

CN116662096A - Fault debugging method and electronic equipment

Info

Publication number: CN116662096A
Application number: CN202211596704.0A
Authority: CN
Inventors: 陈彦桦
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-12-12
Filing date: 2022-12-12
Publication date: 2023-08-29
Anticipated expiration: 2042-12-12
Also published as: CN116662096B

Abstract

The embodiment of the application is suitable for the technical field of data processing, and provides a fault debugging method and electronic equipment.

Description

Fault debugging method and electronic equipment

Technical Field

The present application relates to the field of data processing, and more particularly, to a fault debugging method and an electronic device.

Background

During the use of an electronic device, failures often occur due to errors in the operation of programs installed in the electronic device. To address these failures, it is often necessary to obtain information about the program's running time, and analyze the information to resolve the failure. At present, for some terminal devices (such as a bluetooth headset or a smart bracelet) with weaker processing capability, the related information of the fault cannot be obtained when the fault occurs, so that a new system version needs to be obtained from a server, and after the new system version is operated, the related information of the fault can be obtained if the same fault occurs again. The new system version is a system version for acquiring relevant information of faults when the faults occur in the electronic equipment.

However, after the terminal device runs a new system version, the same fault may not occur, resulting in failure to acquire relevant information of the fault, and thus failure to solve the type of fault.

Based on this, how to solve the faults occurring in the terminal device becomes a problem to be solved in the case that the same faults do not occur after the terminal device runs a new system version.

Disclosure of Invention

The application provides a fault debugging method which can solve the problem of faults in terminal equipment under the condition that the same faults do not occur after the terminal equipment operates a new system version.

In a first aspect, a fault debugging method is provided, the method is applied to a first electronic device, the first electronic device is connected with a second electronic device, and the method includes:

receiving first information sent by second electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed;

storing address information to a register in the first electronic device;

when the first electronic equipment operates to an address indicated by the address information, acquiring target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment of the first electronic equipment operating to the address information as an end point;

And sending the target data to the second electronic device so that the second electronic device processes the fault of the first electronic device based on the target data.

The fault debugging method provided by the embodiment of the application is applied to the first electronic equipment, the first electronic equipment is connected with the second electronic equipment, the first electronic equipment receives the second electronic equipment and sends first information, the address information is stored in the register, target data are acquired when the first electronic equipment runs to the address indicated by the address information, then the target data are sent to the second electronic equipment, so that the second electronic equipment can debug the fault of the first electronic equipment based on the target data, wherein the first information comprises the address information corresponding to the fault to be debugged, the target data comprise a system log of the first electronic equipment in a preset period, the preset period is a period taking the moment that the first electronic equipment runs to the address indicated by the address information as an end point, and because the address information is the address information corresponding to the fault to be debugged, when the first electronic equipment runs to the address indicated by the address information, the occurrence probability of the fault to be debugged is higher, the system log (target data) of the first electronic equipment in the period can reflect the fault condition of the fault to be debugged, and the second electronic equipment can process the fault of the first electronic equipment according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

With reference to the first aspect, in an embodiment of the first aspect, when the first electronic device runs to an address indicated by the address information, obtaining the target data includes: and when the first electronic equipment runs to the address indicated by the address information, acquiring target data according to the type of the register.

With reference to the first aspect, in one embodiment of the first aspect, the target register includes a flash patch and an FPB register corresponding to the interrupt FPB module, and when the first electronic device runs to an address indicated by the address information, obtaining the target data according to a type of the register includes:

and stopping the running program of the first electronic equipment to acquire target data under the condition that the address indicated by the address information of the running first electronic equipment and the register is an FPB register.

In the embodiment of the application, when the first electronic equipment runs to the address indicated by the address information and the address information is stored in the FPB register, the running program of the first electronic equipment is stopped, and the target data is acquired, so that when the target data is acquired, no other running program exists in the first electronic equipment, the acquired target data can more accurately indicate the field information of the fault to be debugged, and the accuracy of debugging the fault based on the target data is improved.

With reference to the first aspect, in one embodiment of the first aspect, the target register includes a DWT register corresponding to the data monitoring point and the trace DWT module, and when the first electronic device runs to an address indicated by the address information, acquiring the target data according to a type of the register includes:

and running the running program of the first electronic equipment and acquiring target data under the condition that the address indicated by the address information of the running first electronic equipment and the target register is a DWT register.

In the embodiment of the application, when the first electronic equipment runs to the address indicated by the address information and the address information is stored in the DWT register, the running program of the first electronic equipment is run to acquire the target data, so that the normal running of the running program of the first electronic equipment is not influenced in the process of acquiring the target data, the first electronic equipment can still continue to execute the currently executed function, the currently used function of the user is not influenced by the acquired target data, the normally used function can still be realized, and the user experience is improved.

With reference to the first aspect, in an embodiment of the first aspect, the first information further includes register information, where the register information is used to indicate a register corresponding to the first information.

In an embodiment of the present application, the first information further includes register information, where the register information is used for a register corresponding to the first information. That is, whether the first information is stored in the DWT register or the FPB register is determined by the second electronic device, and the second electronic device packages the register information in the first information and transmits it to the first electronic device. It should be understood that the first electronic device generally refers to an electronic device with a relatively weak processing power and the second electronic device has a relatively strong processing power. Therefore, the second electronic device with relatively strong processing capability determines that the first information exists in the register, and the first electronic device with relatively weak processing capability does not need to determine the register for storing the first information, so that the situation that the first electronic device cannot perform similar processing is avoided. In addition, the type of the register is related to the mode of acquiring the target data, and the mode of acquiring the target data is determined by the second electronic equipment, so that the processing load of the first electronic equipment can be further reduced, and the situation that the first electronic equipment cannot perform similar processing is avoided.

With reference to the first aspect, in an embodiment of the first aspect, the first information further includes return information, where the return information is used to indicate a time when the target data is sent to the second electronic device.

In the embodiment of the application, the time when the first electronic device sends the target data to the second electronic device can be determined according to the return information included in the first information, so that the time when the target data is returned to the second electronic device is more flexible. In addition, when the return information indicates that the time of sending the target data to the second electronic device is not the current time, the target data and other data reported by the first electronic device to the second electronic device can be sent to the second electronic device together, and the target data does not need to be sent to the second electronic device independently, so that the convenience of sending the target data to the second electronic device is improved.

With reference to the first aspect, in an embodiment of the first aspect, the first information further includes log information, where the log information is used to indicate a data amount of the target data.

With reference to the first aspect, in an embodiment of the first aspect, the first electronic device includes a bluetooth headset and a smart band.

In a second aspect, a fault debugging method is provided, the method is applied to a second electronic device, and a first electronic device is connected with the second electronic device, the method includes:

sending first information to first electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed;

Receiving target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by address information as an end point;

and processing the fault of the first electronic device based on the target data.

The fault debugging method provided by the embodiment of the application is applied to the second electronic equipment, the second electronic equipment is connected with the first electronic equipment, the second electronic equipment sends first information to the first electronic equipment, wherein the first information comprises address information corresponding to a fault to be debugged, and receives target data, the target data comprises a system log of the first electronic equipment in a preset period, the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by the address information as an end point, and the fault of the first electronic equipment is processed based on the target data. Because the target data is a system log of the moment when the first electronic device runs to the address indicated by the address information, and the address information is the address information corresponding to the fault to be debugged, the target data can reflect the fault condition of the fault to be debugged, and the second electronic device can process the fault of the first electronic device according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

With reference to the second aspect, in one embodiment of the second aspect, the first information further includes register information, where the register information is used to indicate a register corresponding to the first information.

With reference to the second aspect, in an embodiment of the second aspect, the first information further includes return information, where the return information is used to indicate a time when the target data is sent to the second electronic device.

With reference to the second aspect, in an embodiment of the second aspect, the first information further includes log information, where the log information is used to indicate a data amount of the target data.

With reference to the second aspect, in one embodiment of the second aspect, the second electronic device includes a cloud server.

In a third aspect, a fault-commissioning system is provided, the system comprising a first electronic device and a second electronic device, the first electronic device and the second electronic device being connected;

the second electronic equipment sends first information to the first electronic equipment, wherein the first information comprises address information corresponding to a fault to be debugged;

the first electronic device stores address information into a register;

when the first electronic equipment runs to an address indicated by the address information, acquiring target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment when the first electronic equipment runs to the address indicated by the address information as an end point;

The first electronic device sends target data to the second electronic device;

the second electronic device debugs the failure of the first electronic device based on the target data.

According to the fault debugging system provided by the embodiment of the application, the second electronic equipment sends first information to the first electronic equipment, the first electronic equipment stores address information into the register, when the address indicated by the address information is operated, target data are acquired, then the second electronic equipment sends the target data to the second electronic equipment, the second electronic equipment debugs the fault of the first electronic equipment based on the target data, wherein the first information comprises address information corresponding to the fault to be debugged, the target data comprise a system log of the first electronic equipment in a preset period, the preset period is a period taking the moment when the first electronic equipment is operated to the address indicated by the address information as an end point, and because the address information is the address information corresponding to the fault to be debugged, when the first electronic equipment is operated to the address indicated by the address information, the occurrence probability of the fault to be debugged is higher, the system log (target data) of the first electronic equipment in the period can reflect the fault condition of the fault to be debugged, and therefore the second electronic equipment can process the fault of the first electronic equipment according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

With reference to the third aspect, in one embodiment of the third aspect, the system further includes a third electronic device, the first electronic device is connected to the second electronic device through the third electronic device,

the second electronic device sending first information to the first electronic device, comprising:

the second electronic device sends the first information to the third electronic device;

the third electronic device sends first information to the first electronic device;

the first electronic device sending target data to the second electronic device, comprising:

the first electronic device sends target data to the third electronic device;

the third electronic device sends the target data to the second electronic device.

According to the fault debugging method provided by the embodiment of the application, under the condition that the first electronic equipment and the second electronic equipment cannot be directly connected, the second electronic equipment firstly transmits first information to the third electronic equipment, the third electronic equipment transmits the first information to the first electronic equipment, then the first electronic equipment stores address information to a register, when the address indicated by the address information is reached, target data is acquired, then the target data is transmitted to the third electronic equipment, and the target data is transmitted to the second electronic equipment through the third electronic equipment, so that the second electronic equipment processes the fault of the first electronic equipment based on the target data. In the embodiment of the application, under the condition that the first electronic equipment and the second electronic equipment cannot be directly connected, after the address information corresponding to the fault to be debugged is determined by the second electronic equipment, the first information comprising the address information corresponding to the fault to be debugged is sent to the first electronic equipment through the third electronic equipment, then after the first electronic equipment acquires the target data, the target data is sent to the second electronic equipment through the third electronic equipment, so that the second electronic equipment processes the fault of the first electronic equipment based on the target data, which is equivalent to the condition that the third electronic equipment is used for processing the fault of the first electronic equipment through the second electronic equipment under the condition that the first electronic equipment is not restarted, and further the condition that the running environment is damaged due to restarting and then the fault cannot be reproduced and cannot be processed is avoided.

With reference to the third aspect, in an embodiment of the third aspect, the third electronic device comprises a terminal device.

In a fourth aspect, a fault-debugging device is provided, comprising means for performing any one of the methods of the first or second aspects. The device can be a server, terminal equipment or a chip in the terminal equipment. The apparatus may include an acquisition unit and a processing unit.

When the apparatus is a terminal device, the processing unit may be a processor, and the acquiring unit may be a communication interface; the terminal device may further comprise a memory for storing computer program code which, when executed by the processor, causes the terminal device to perform any of the methods of the first or second aspects.

When the device is a chip in the terminal equipment, the processing unit may be a processing unit inside the chip, and the obtaining unit may be an output interface, a pin, a circuit, or the like; the chip may also include memory, which may be memory within the chip (e.g., registers, caches, etc.), or memory external to the chip (e.g., read-only memory, random access memory, etc.); the memory is for storing computer program code which, when executed by the processor, causes the chip to perform any one of the methods of the first or second aspects.

In one possible implementation, the memory is used to store computer program code; a processor executing the computer program code stored in the memory, the processor, when executed, configured to perform: receiving first information sent by second electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed; storing address information to a register in the first electronic device; when the first electronic equipment operates to an address indicated by the address information, acquiring target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment of the first electronic equipment operating to the address information as an end point; and sending the target data to the second electronic device so that the second electronic device processes the fault of the first electronic device based on the target data.

In one possible implementation, the memory is used to store computer program code; a processor executing the computer program code stored in the memory, the processor, when executed, configured to perform: sending first information to first electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed; receiving target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by address information as an end point; and processing the fault of the first electronic device based on the target data.

In a fifth aspect, there is provided a computer readable storage medium storing computer program code which, when run by a troubleshooting device, causes the troubleshooting device to perform either the troubleshooting method of the first or second aspects.

In a sixth aspect, there is provided a computer program product comprising: computer program code which, when run by a troubleshooting device, causes the troubleshooting device to perform any one of the device methods of the first or second aspects.

According to the fault debugging method and the electronic device provided by the embodiment of the application, the second electronic device sends the first information to the first electronic device, the first electronic device stores the address information into the register, when the first electronic device runs to the address indicated by the address information, the target data is acquired, then the second electronic device sends the target data to the second electronic device, the second electronic device debugs the fault of the first electronic device based on the target data, wherein the first information comprises the address information corresponding to the fault to be debugged, the target data comprises a system log of the first electronic device in a preset period, the preset period is a period taking the moment that the first electronic device runs to the address indicated by the address information as an end point, and because the address information is the address information corresponding to the fault to be debugged, when the first electronic device runs to the address indicated by the address information, the occurrence probability of the fault to be debugged is higher, the system log (target data) of the first electronic device in the period can reflect the fault condition of the fault to be debugged, and the second electronic device can process the fault of the first electronic device according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

Drawings

FIG. 1 is a schematic diagram of a hardware system suitable for use in an electronic device of the present application;

fig. 2 is a schematic diagram of an application scenario provided in an embodiment of the present application;

fig. 3 is a schematic diagram of an application scenario provided in an embodiment of the present application;

fig. 4 is a schematic flow chart of a fault debugging method according to an embodiment of the present application;

fig. 5 is a schematic software structure of an electronic device according to an embodiment of the present application;

fig. 6 is a schematic flow chart of a fault debugging method according to an embodiment of the present application;

fig. 7 is a schematic flow chart of a fault debugging method according to an embodiment of the present application;

FIG. 8 is a schematic flow chart of a fault debugging method according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a fault-commissioning device provided by the present application;

FIG. 10 is a schematic diagram of a fault-commissioning device provided by the present application;

fig. 11 is a schematic diagram of an electronic device for fault debugging provided by the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. Wherein, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B; "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.

The terms "first," "second," "third," and the like, are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", or a third "may explicitly or implicitly include one or more such feature.

At present, during the use of the electronic device, faults often occur due to running errors of programs installed in the electronic device. To address these failures, it is often necessary to obtain information about the program's running time, and analyze the information to resolve the failure. In one possible scenario, some electronic devices have weak processing power and cannot analyze the fault. Among these electronic devices are bluetooth headsets, smart bracelets, etc.

In one possible case, during the development process of the bluetooth headset, a debug line can be independently led out from the bluetooth headset, connected with the testing machine, and the fault is determined through debug software on the testing machine. The debugging software comprises a Jlink debugging simulator, IAR, keil, ozone and the like. However, the following problems may exist in debugging by using a wired connection:

1. The original sequential logic of the Bluetooth headset can be destroyed when the wired connection method is used for fault debugging, the Bluetooth headset breaks down when in normal operation, and a testing machine is connected for debugging, so that the fault is not repeated.

2. The CPU of the Bluetooth headset is suspended by fault debugging in a wired connection method, so that the CPU cannot respond to external Bluetooth information, and external equipment of the Bluetooth headset is interrupted, and a fault site cannot be simulated truly.

3. A malfunctioning bluetooth headset is an electronic device that has been used by a user, and thus a debug line cannot be drawn from the bluetooth headset for debugging.

In order to solve the fault of the electronic device, for example, to verify whether a branch of the program runs is misplaced or not, or to take the value of a variable in an abnormal scene, a system version needs to be newly generated, so that when the electronic device runs a new system version, whether the score of the program running is misplaced or not can be recorded in a system log, or the value of a variable in the abnormal scene is taken. In this way, a new system version is usually pushed to the electronic device by a wireless transmission mode, after the electronic device installs the new system version, the relevant information recorded in the fault recovery is recorded in the system log, the system log is exported, and the exported system log is sent to the tester. The whole process is complex and requires a long time.

In addition, typically after the electronic device installs a new system version, a reboot is required to validate the new system version. However, after the electronic device is restarted, the operating environment of the electronic device is changed. In this way, some faults with low occurrence probability may not be reproduced, so that the electronic device cannot acquire relevant information corresponding to the faults, and the type of faults cannot be solved.

In view of this, the embodiment of the present application provides a fault debugging method, a second electronic device sends first information to a first electronic device, where the first electronic device stores address information into a register, and obtains target data when running to an address indicated by the address information, and then sends the target data to the second electronic device, where the second electronic device debugs a fault of the first electronic device based on the target data, the first information includes address information corresponding to the fault to be debugged, the target data includes a system log of the first electronic device in a preset period, the preset period is a period taking a time when the first electronic device runs to the address indicated by the address information as an end point, and because the address information is the address information corresponding to the fault to be debugged, when the first electronic device runs to the address indicated by the address information, the occurrence probability of the fault to be debugged is higher, and the system log (target data) of the first electronic device in this period can reflect a fault condition of the fault to be debugged, so that the second electronic device can process the fault of the first electronic device according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

The fault debugging method provided by the embodiment of the application can be applied to electronic equipment. Optionally, the electronic device includes a terminal device, which may also be referred to as a terminal (terminal), a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), and so on. The terminal device may be a mobile phone, a smart television, a wearable device, a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned driving (self-driving), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), or the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the terminal equipment.

By way of example, fig. 1 shows a schematic diagram of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller may be a neural hub and a command center of the electronic device 100, among others. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The charge management module 140 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive a charging input of a wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive wireless charging input through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140 and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be configured to monitor battery capacity, battery cycle number, battery health (leakage, impedance) and other parameters. In other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charge management module 140 may be disposed in the same device.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement photographing functions through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously learn itself. Applications such as intelligent awareness of the electronic device 100 may be implemented through the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The processor 110 executes various functional applications of the electronic device 100 and data processing by executing instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.

The electronic device 100 may implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or a portion of the functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music, or to hands-free conversations, through the speaker 170A.

A receiver 170B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When electronic device 100 is answering a telephone call or voice message, voice may be received by placing receiver 170B in close proximity to the human ear.

Microphone 170C, also referred to as a "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 170C through the mouth, inputting a sound signal to the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to enable collection of sound signals, noise reduction, identification of sound sources, directional recording functions, etc.

The earphone interface 170D is used to connect a wired earphone. The headset interface 170D may be a USB interface 130 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, a american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 180F for measuring a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, the electronic device 100 may range using the distance sensor 180F to achieve quick focus.

The proximity light sensor 180G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The electronic device 100 emits infrared light outward through the light emitting diode. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object in the vicinity of the electronic device 100. When insufficient reflected light is detected, the electronic device 100 may determine that there is no object in the vicinity of the electronic device 100. The electronic device 100 can detect that the user holds the electronic device 100 close to the ear by using the proximity light sensor 180G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 180G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to unlock the fingerprint, access the application lock, photograph the fingerprint, answer the incoming call, etc.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

The touch sensor 180K, also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key, a volume key, etc. The keys 190 may be mechanical keys. Or may be a touch key. The electronic device 100 may receive key inputs, generating key signal inputs related to user settings and function controls of the electronic device 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration alerting as well as for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also correspond to different vibration feedback effects by touching different areas of the display screen 194. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, may be used to indicate a state of charge, a change in charge, a message indicating a missed call, a notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195, or removed from the SIM card interface 195 to enable contact and separation with the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support Nano SIM cards, micro SIM cards, and the like. The same SIM card interface 195 may be used to insert multiple cards simultaneously. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, the electronic device 100 employs esims, i.e.: an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

It should be noted that any of the electronic devices mentioned in the embodiments of the present application may include more or fewer modules in the electronic device 100.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture.

The application scenario provided by the embodiment of the application is described below with reference to the accompanying drawings.

Fig. 2 is a schematic diagram of an application scenario of the fault debugging method provided in an embodiment of the present application, where, as shown in fig. 2, a bluetooth headset is connected to a tester through bluetooth. And after the Bluetooth headset fails, sending a system log to the testing machine, and processing the failure of the Bluetooth headset by the testing machine based on the system log. Compared with the traditional method, the Bluetooth headset does not need to be restarted in the process of processing the failure of the Bluetooth headset.

It should be understood that the embodiment of the application is also applicable to fault debugging of the smart band. For example, the smart band is connected with the testing machine through Bluetooth. And after the intelligent bracelet fails, sending a system log to the testing machine. The testing machine processes faults of the intelligent bracelet based on the system log.

The above processing procedure for the fault is not limited to the bluetooth headset or the smart band. The Bluetooth headset (or the intelligent bracelet) and the testing machine are not limited to be connected through Bluetooth, and can be connected through other wireless transmission modes.

Fig. 3 is an application scenario schematic diagram of a fault debugging method according to an embodiment of the present application. In one possible scenario, when the bluetooth headset is used by a user. In general, when a bluetooth headset fails, a user does not want to return the bluetooth headset to a factory for repair. Therefore, as shown in fig. 3, the bluetooth headset may transmit the system log to a mobile phone connected to the bluetooth headset, and transmit the system log to the server through the mobile phone, so that the server processes the failure of the bluetooth headset based on the system log. Also, in handling the failure of the bluetooth headset, the bluetooth headset does not need to be restarted.

It should be understood that the embodiment of the application is also applicable to fault debugging of the smart band. For example, bluetooth connection is performed between the smart band and the server through a mobile phone. And after the intelligent bracelet fails, sending the system log to the mobile phone, and sending the system log to the server through the mobile phone. And the server processes faults of the intelligent bracelet based on the system log.

The above processing procedure for the fault is not limited to the bluetooth headset or the smart band. The Bluetooth headset (or the intelligent bracelet) and the mobile phone are not limited to be connected through Bluetooth, and can be connected through other wireless transmission modes.

It should be understood that the foregoing is illustrative of an application scenario, and is not intended to limit the application scenario of the present application in any way.

The fault debugging method provided by the embodiment of the application is described in detail below with reference to fig. 4 to 8.

Fig. 4 is a schematic flow chart of a fault debugging method provided by the embodiment of the present application, as shown in fig. 4, where a first electronic device is connected to a second electronic device, and the first electronic device may be a bluetooth headset or an intelligent bracelet. The second electronic device may be a testing machine or a terminal device (such as a mobile phone), which is not limited in this embodiment of the present application. The first electronic device and the second electronic device may be connected through bluetooth, or may be connected through other wireless communication manners, which is not limited in the embodiment of the present application. As shown in fig. 4, the method includes:

s101, the second electronic device sends first information to the first electronic device. The first information comprises address information corresponding to the fault to be debugged.

For ease of understanding, the following description will be given taking the first electronic device as a bluetooth headset and the second electronic device as a tester (terminal device).

In the process of software engineering construction of the Bluetooth headset, debugging information can be compiled, wherein the debugging information refers to the corresponding relation between code line information and instruction information. The lst file generated by the construction software engineering comprises the debugging information. It should be understood that the failure of the bluetooth headset is usually caused by a branch running error of the program or abnormal value of a certain variable. Therefore, the failure correspondence of the bluetooth headset corresponds to one code line information. That is, the user may determine the code line information corresponding to the failure of the bluetooth headset based on the failure phenomenon and the lst file. Wherein each code line has its corresponding address.

Based on the above, the testing machine may acquire corresponding address information based on the code line information, that is, address information corresponding to the fault to be debugged, and send the address information to the first electronic device through the first information.

In one possible scenario, the content of the lst file portion in the constructed software project may be as follows:

/>

here, the address information corresponding to 484 lines is "c0190cc", the address information corresponding to 494 lines is "c1090d0", and the address information corresponding to 495 lines is "c1090d4". The tester may send the address information to the first electronic device via the first information.

In one possible scenario, the address information may also be obtained through a map file. And searching the memory address corresponding to the global variable sign of the fault to be debugged in the map file, namely the address information corresponding to the fault to be debugged. And then the address information is transmitted to the Bluetooth headset through the first information. Illustratively, part of the content of the map file is as follows:

/>

the global variable "g_record_set_a2dp_volume_ind" corresponds to an address of "0x0000000020075ca4"; the global variable "g_record_set_device_record_allow" corresponds to an address of "0x0000000020075ca8"; the global variable "g_record_set_device_recovery_reflection" corresponds to an address of "0x0000000020075cac"; the global variable "g_record_set_ hfp _volume_ind" corresponds to an address of "0x0000000020075cb0".

When the testing machine obtains the address information corresponding to the fault to be debugged, the address information can be packaged in the first information, and the first information is sent to the Bluetooth headset.

S102, the first electronic device stores address information into a register.

Among other things, a chip employing an arm architecture may be included in a bluetooth headset (first electronic device), which may include an external debugger External debugger, a flash patch and interrupt unit (Flash Patch and Break unit, FPB), N FPB registers, a data monitoring point and trace unit (Data Watchpoint and Trace unit, DWT), N DWT registers, and an exception debug monitor (DebugMonitor exception), as shown in fig. 5. It should be appreciated that the number of FPB registers and the number of DWT registers may be the same or different, as the embodiments of the present application are not limited in this respect.

After receiving the first information, the bluetooth headset may store the address information in the first information to the FPB register or may store the address information in the DWT register.

S103, the first electronic device acquires target data when running to the address indicated by the address information.

The target data comprises a system log of the first electronic device in a preset period, and the preset period is a period taking the moment when the first electronic device runs to an address indicated by the address information as an end point.

And when the Bluetooth headset runs to the address indicated by the address information, acquiring target data.

It should be appreciated that during the procedure that the bluetooth headset is running, the running address is typically compared to the addresses stored in the registers (including the FPB register and DWT register), and if so, the bluetooth headset is running to the address indicated by the address information. When the Bluetooth headset runs to the address indicated by the address information, debugMonitor exception can be called by External debugger to collect and store the site information, and the site information is stored in a system log. Corresponding to the acquisition of target data by DebugMonitor exception.

Alternatively, the bluetooth headset may select how to acquire the target data according to the register type.

For example, if the address information is stored in the FPB register, the bluetooth headset may stop running the program currently running and acquire the target data. The method is equivalent to that the Bluetooth headset interrupts the currently running program to acquire the target data.

For example, if the address information is stored in the DWT register, the bluetooth headset runs the program currently running, and obtains the target data. The method is equivalent to that the Bluetooth headset continues to operate the currently operated program to acquire the target data.

In one possible scenario, the second electronic device may package an indication of which type of register to use in the first information, and send the first information to the first electronic device to cause the first electronic device to select to store address information in the corresponding register based on the register type.

Optionally, the first information further includes register information, where the register information is used to indicate a register corresponding to the first information.

For example, if the register information included in the first information indicates that the register corresponding to the first information is an FPB register, the bluetooth headset stores address information in the FPB register. When the running address of the bluetooth headset is the address indicated by the address information stored in the FPB register, the bluetooth headset can stop running the currently running program to acquire the target data.

For example, if the register information included in the first information indicates that the register corresponding to the first information is a DWT register, the bluetooth headset stores the address information in the DWT register. When the running address of the Bluetooth headset is the address indicated by the address information stored in the DWT register, the Bluetooth headset can continue to run the currently running program to acquire target data.

In one possible case, the second electronic device may further package the size of the data amount of the target data to be acquired in the first information, and send the first information to the first electronic device, so that the first electronic device determines the size of the acquired target data based on the size of the data amount.

Optionally, the first information includes log information, the log information being used to indicate a data amount of the target data.

The testing machine packages the data amount of the target data to be acquired into the first information and sends the first information to the Bluetooth headset. And the Bluetooth headset acquires a system log within a preset duration based on the data quantity of the target data, and takes the system log as the target data. The preset duration corresponds to the data quantity of the target data. For example. The data size of the target data is 100KB, and the corresponding data size of the system log of 10S is 100KB, that is, the preset duration corresponding to the data size of 100KB of the target data is 10S. The bluetooth headset acquires a system log of 10S ending at the current time as target data.

S104, the first electronic device sends the target data to the second electronic device.

The first electronic device may send the target data to the second electronic device when the target data is acquired, or may send the target data to the second electronic device at a preset time.

In one possible scenario, the first information sent by the second electronic device to the first electronic device also indicates a time at which the target data is returned to the second electronic device, such that the first electronic device sends the target data to the second electronic device at the specified time.

Optionally, the first information further includes return information, where the return information is used to indicate a time when the target data is sent to the second electronic device.

The return information may indicate that the target data is sent to the second electronic device immediately after the target data is acquired, or may indicate that the target data is sent to the second electronic device at a preset time, which is not limited in the embodiment of the present application.

The first information may include information as shown in table 1.

TABLE 1

Type0x01 is register information, when the value of Type0x01 is 0, a breakpoint is issued, and the indicated register Type is FPB register; when the value of Type0x01 is 1, the monitoring point is issued, which corresponds to the indicated register Type being a DWT register.

Type0x02 is address information corresponding to the fault to be processed.

Type0x03 is return information, including immediate backhaul and later backhaul. If the later return is selected, the snapshot information is stored in a log file, and target data is sent to the testing machine in a log uploading mode. This situation applies to bluetooth headsets that have already been used by users, and that cannot return target data to the tester in real time.

Type0x04 is log information for indicating the data amount of target data returned to the tester. In one possible case, the value of Type0x04 is 0, which indicates that the latest system log does not need to be sent.

Optionally, the Type0x05 is address information, which may be used to indicate an address range corresponding to the collected snapshot information when the first electronic device runs to an address corresponding to the fault to be debugged. By way of example, the address range may be: [ addr1 to addr2, addr3, addr4 to addr5, … … ].

In the case where the first information includes information as shown in table 1, the first electronic device may store the first information according to the following data structure:

in the case where the first information may include information as shown in table 1, the corresponding target data transmitted to the second electronic device may include information as shown in table 2. The method comprises the following steps:

TABLE 2

Type0x01 indicates that the target data is obtained through breakpoint triggering, or that the target information is obtained through monitoring point triggering. For example, when the value of Type0x01 is 0, the target data is indicated to be obtained through breakpoint triggering, and when the value of Type0x01 is 1, the target data is indicated to be obtained through monitoring point triggering.

Type0x02 is used to indicate the time of the acquired target data.

Type0x03 refers to target data.

Alternatively, type0x04 refers to system log information having the smallest time difference from the target data.

S105, the second electronic device debugs the fault of the first electronic device based on the target data.

According to the fault debugging method provided by the embodiment of the application, the second electronic equipment sends first information to the first electronic equipment, the first electronic equipment stores address information into the register, when the address indicated by the address information is operated, target data are acquired, then the second electronic equipment sends the target data to the second electronic equipment, the second electronic equipment debugs the fault of the first electronic equipment based on the target data, wherein the first information comprises address information corresponding to the fault to be debugged, the target data comprise a system log of the first electronic equipment in a preset period, the preset period is a period taking the moment when the first electronic equipment is operated to the address indicated by the address information as an end point, and because the address information is the address information corresponding to the fault to be debugged, when the first electronic equipment is operated to the address indicated by the address information, the occurrence probability of the fault to be debugged is higher, the system log (target data) of the first electronic equipment in the period can reflect the fault condition of the fault to be debugged, and therefore the second electronic equipment can process the fault of the first electronic equipment according to the target data. By the fault debugging method provided by the embodiment of the application, the fault of the first electronic equipment can be processed without sending a new system version to the first electronic equipment, and further, the situation that the fault cannot be reproduced and cannot be processed due to the fact that the running environment is damaged caused by restarting after the new system version is installed on the first electronic equipment is avoided.

In one possible scenario, the first electronic device cannot connect directly to the second electronic device. In this case, the connection of the first electronic device and the second electronic device may also be achieved by the third electronic device, so that the second electronic device processes the failure of the first electronic device based on the target data.

As shown in fig. 3, the first electronic device is a bluetooth headset, the second electronic device is a server, and the third electronic device is a mobile phone. The Bluetooth headset cannot be directly connected with the server, and needs to be connected with the mobile phone first and then connected with the server through the mobile phone. Described in detail below by way of the embodiment shown in fig. 6.

Fig. 6 is a flow chart of a fault debugging method provided by the embodiment of the application, as shown in fig. 6, the method is applied to an application environment shown in fig. 3, wherein a mobile phone is respectively connected with a bluetooth headset and a server. The method comprises the following steps:

s201, the server sends first information to the mobile phone.

The first information comprises address information corresponding to the fault to be debugged. The first information may further include information as shown in table 1.

Illustratively, the register information included in the first information indicates that address information is stored in the FPB register, the log information indicates that the data amount of the acquired system log is 100kB, the corresponding time period is 10s, and the return information indicates that the target data is returned immediately.

Illustratively, the register information included in the first information indicates that address information is stored in the DWT register, the log information indicates that the data amount of the acquired system log is 10kB, the corresponding time period is 1s, and the return information indicates that the target data is returned later.

S202, the mobile phone sends first information to the Bluetooth headset.

S203, the Bluetooth headset stores address information into a register.

When the Bluetooth headset stores the first information, the Bluetooth headset can store the first information according to the following data structure:

s204, when the Bluetooth headset runs to the address indicated by the address information, acquiring target data.

The target data comprises a system log of the Bluetooth headset in a preset period, and the preset period is a period taking the moment when the Bluetooth headset runs to an address indicated by the address information as an end point.

S205, the Bluetooth headset sends target data to the mobile phone.

S206, the mobile phone sends the target data to the server.

S207, the server debugs the fault of the Bluetooth headset based on the target data.

The fault debugging method provided in one embodiment is applied to the first electronic device, and the first electronic device may be, for example, a bluetooth headset or an intelligent bracelet. The first electronic device is connected with the second electronic device. The second electronic device may be a testing machine or a server, which is not limited in this embodiment of the present application. As shown in fig. 7, the method includes:

s301, receiving first information sent by the second electronic equipment.

The first information comprises address information corresponding to the fault to be processed.

S302, storing address information into a register in the first electronic device.

S303, when the first electronic equipment runs to the address indicated by the address information, acquiring target data.

The target data comprise a system log of the first electronic equipment in a preset period, wherein the preset period is a period taking the moment when the first electronic equipment operates to address information as an end point;

and S304, sending target data to the second electronic equipment so that the second electronic equipment processes the fault of the first electronic equipment based on the target data.

The implementation principle and the beneficial effects of the above embodiment are similar to those of the embodiment shown in fig. 4 to 6, and are not repeated here.

The fault debugging method provided in one embodiment is applied to the second electronic device, and the second electronic device may be a testing machine or a server, which is not limited by the embodiment of the application. The first electronic device is connected with the second electronic device. The first electronic device may be a bluetooth headset or an intelligent bracelet, which is not limited in the embodiment of the present application. As shown in fig. 8, the method includes:

s401, first information is sent to the first electronic device.

S402, receiving target data.

The target data comprises a system log of the first electronic equipment in a preset period, wherein the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by the address information as an end point;

s403, processing the fault of the first electronic device based on the target data.

It should be understood that, although the steps in the flowcharts in the above embodiments are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least a portion of the steps in the flowcharts may include a plurality of sub-steps or stages that are not necessarily performed at the same time, but may be performed at different times, the order in which the sub-steps or stages are performed is not necessarily sequential, and may be performed in turn or alternately with at least a portion of the sub-steps or stages of other steps or other steps.

It will be appreciated that in order to achieve the above-described functionality, the electronic device comprises corresponding hardware and/or software modules that perform the respective functionality. The present application can be implemented in hardware or a combination of hardware and computer software, in conjunction with the example algorithm steps described in connection with the embodiments disclosed herein. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The embodiment of the application can divide the functional modules of the electronic device according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated in one module. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation. It should be noted that, in the embodiment of the present application, the names of the modules are schematic, and the names of the modules are not limited in practical implementation.

Fig. 9 is a schematic structural diagram of a fault-debugging device according to an embodiment of the present application.

It should be understood that the fault commissioning device 500 may perform the fault commissioning method shown in fig. 7; the fault debugging device 500 includes: an acquisition unit 510 and a processing unit 520.

The obtaining unit 510 is configured to receive first information sent by the second electronic device, where the first information includes address information corresponding to a fault to be processed;

the processing unit 520 is configured to store address information to a register in the first electronic device;

the obtaining unit 510 is configured to obtain target data when the first electronic device is running to an address indicated by the address information, where the target data includes a system log of the first electronic device in a preset period, and the preset period is a period taking a time when the first electronic device is running to the address information as an endpoint;

the processing unit 520 is configured to send the target data to the second electronic device, so that the second electronic device processes the failure of the first electronic device based on the target data.

And when the first electronic equipment runs to the address indicated by the address information, acquiring the target data according to the type of the register.

In one embodiment, the target register includes a flash patch and an FPB register corresponding to the interrupt FPB module, and the obtaining unit 510 is specifically configured to, when the address indicated by the address information of the first electronic device is indicated by the address information of the first electronic device, and the register is the FPB register, stop the running program of the first electronic device, and obtain the target data.

In one embodiment, the target register includes a DWT register corresponding to the data monitoring point and the trace DWT module, and the obtaining unit 510 is specifically configured to, when the address indicated by the address information operated by the first electronic device is the DWT register, operate a program that is being operated by the first electronic device, and obtain the target data.

In one embodiment, the first information further includes register information, where the register information is used to indicate a register corresponding to the first information.

In one embodiment, the first information further includes return information indicating a time at which the target data is transmitted to the second electronic device.

In one embodiment, the first information further includes log information for indicating a data amount of the target data.

In one embodiment, the first electronic device includes a Bluetooth headset and a smart band.

The fault debugging device provided in this embodiment is configured to execute the fault debugging method in the foregoing embodiment, and the technical principle and the technical effect are similar and are not repeated herein.

The fault-debugging device 500 is embodied as a functional unit. The term "unit" herein may be implemented in software and/or hardware, without specific limitation.

Fig. 10 is a schematic structural diagram of a fault-debugging device according to an embodiment of the present application.

It should be appreciated that the fault commissioning device 600 may perform the fault commissioning method shown in fig. 8; the fault debugging device 600 includes: an acquisition unit 610 and a processing unit 620.

The processing unit 620 is configured to send first information to the first electronic device, where the first information includes address information corresponding to a fault to be processed;

the obtaining unit 610 is configured to receive target data, where the target data includes a system log of the first electronic device in a preset period, and the preset period is a period that takes a time when the first electronic device runs to an address indicated by the address information as an endpoint;

the processing unit 620 is configured to process a failure of the first electronic device based on the target data.

In one embodiment the second electronic device comprises a cloud server.

The fault-debugging device 600 is embodied as a functional unit. The term "unit" herein may be implemented in software and/or hardware, without specific limitation.

For example, a "unit" may be a software program, a hardware circuit or a combination of both that implements the functions described above. The hardware circuitry may include application specific integrated circuits (application specific integrated circuit, ASICs), electronic circuits, processors (e.g., shared, proprietary, or group processors, etc.) and memory for executing one or more software or firmware programs, merged logic circuits, and/or other suitable components that support the described functions.

Thus, the elements of the examples described in the embodiments of the present application can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Fig. 11 shows a schematic structural diagram of an electronic device provided by the present application. The dashed line in fig. 11 indicates that the unit or the module is optional. The electronic device 700 may be used to implement the fault-commissioning method described in the method embodiments described above.

The electronic device 700 includes one or more processors 701, which one or more processors 701 may support the electronic device 700 to implement the fault debugging method in the method embodiments. The processor 701 may be a general-purpose processor or a special-purpose processor. For example, the processor 701 may be a central processing unit (central processing unit, CPU), digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA), or other programmable logic device such as discrete gates, transistor logic, or discrete hardware components.

The processor 701 may be used to control the electronic device 700, execute a software program, and process data of the software program. The electronic device 700 may further comprise a communication unit 705 for enabling input (reception) and output (transmission) of signals.

For example, the electronic device 700 may be a chip, the communication unit 705 may be an input and/or output circuit of the chip, or the communication unit 705 may be a communication interface of the chip, which may be an integral part of a terminal device or other electronic device.

For another example, the electronic device 700 may be a terminal device, the communication unit 705 may be a transceiver of the terminal device, or the communication unit 705 may be a transceiver circuit of the terminal device.

The electronic device 700 may include one or more memories 702 having a program 704 stored thereon, the program 704 being executable by the processor 701 to generate instructions 703 such that the processor 701 performs the impedance matching method described in the above method embodiments according to the instructions 703.

Optionally, the memory 702 may also have data stored therein. Alternatively, processor 701 may also read data stored in memory 702, which may be stored at the same memory address as program 704, or which may be stored at a different memory address than program 704.

The processor 701 and the memory 702 may be provided separately or may be integrated together; for example, integrated on a System On Chip (SOC) of the terminal device.

Illustratively, the memory 702 may be used to store a relevant program 704 of the fault debugging method provided in the embodiment of the present application, and the processor 701 may be used to call the relevant program 704 of the fault debugging method stored in the memory 702 when performing fault debugging, to execute the fault debugging method of the embodiment of the present application; comprising the following steps: receiving first information sent by the second electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed; storing the address information to a register in the first electronic device; when the first electronic equipment runs to an address indicated by the address information, acquiring target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment of the first electronic equipment running to the address information as an end point; and sending the target data to the second electronic equipment so that the second electronic equipment processes the fault of the first electronic equipment based on the target data.

Illustratively, the memory 702 may be used to store a relevant program 704 of the fault debugging method provided in the embodiment of the present application, and the processor 701 may be used to call the relevant program 704 of the fault debugging method stored in the memory 702 when performing fault debugging, to execute the fault debugging method of the embodiment of the present application; comprising the following steps: sending first information to the first electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed; receiving target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by the address information as an end point; and processing the fault of the first electronic equipment based on the target data.

The present application also provides a computer program product which, when executed by the processor 701, implements the fault-debugging method according to any one of the method embodiments of the present application.

The computer program product may be stored in the memory 702, for example, the program 704, and the program 704 is finally converted into an executable object file capable of being executed by the processor 701 through preprocessing, compiling, assembling, and linking.

The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a computer implements the fault commissioning method of any one of the method embodiments of the application. The computer program may be a high-level language program or an executable object program.

Such as memory 702. The memory 702 may be volatile memory or nonvolatile memory, or the memory 702 may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only one logic function division, and other division modes can be adopted in actual implementation; for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A fault-commissioning method, the method being applied to a first electronic device, the first electronic device being connected to a second electronic device, the method comprising:

receiving first information sent by the second electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed;

storing the address information to a register in the first electronic device;

when the first electronic equipment runs to an address indicated by the address information, acquiring target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment of the first electronic equipment running to the address information as an end point;

And sending the target data to the second electronic equipment so that the second electronic equipment processes the fault of the first electronic equipment based on the target data.

2. The method of claim 1, wherein the obtaining the target data when the first electronic device is running to the address indicated by the address information comprises:

3. The method according to claim 2, wherein the target register includes a flash patch and an FPB register corresponding to an interrupt FPB module, and the obtaining the target data according to the type of the register when the first electronic device runs to the address indicated by the address information includes:

and stopping the running program of the first electronic equipment and acquiring the target data under the condition that the address indicated by the address information operated by the first electronic equipment and the register is the FPB register.

4. The method according to claim 2, wherein the target register includes a DWT register corresponding to a data monitoring point and a trace DWT module, and the acquiring the target data according to the type of the register when the first electronic device runs to the address indicated by the address information includes:

And running a program running by the first electronic equipment and acquiring the target data under the condition that the address information of the first electronic equipment runs and the target register is the DWT register.

5. The method of any one of claims 1 to 4, wherein the first information further includes register information, the register information indicating a register to which the first information corresponds.

6. The method of any of claims 1-5, wherein the first information further comprises return information indicating a time of transmission of the target data to the second electronic device.

7. The method according to any one of claims 1 to 6, wherein the first information further includes log information for indicating a data amount of the target data.

8. The method of any of claims 1 to 7, wherein the first electronic device comprises a bluetooth headset and a smart band.

9. A fault-commissioning method, the method being applied to a second electronic device, the second electronic device being connected to a first electronic device, the method comprising:

Sending first information to the first electronic equipment, wherein the first information comprises address information corresponding to a fault to be processed;

receiving target data, wherein the target data comprises a system log of the first electronic equipment in a preset period, and the preset period is a period taking the moment when the first electronic equipment runs to an address indicated by the address information as an end point;

and processing the fault of the first electronic equipment based on the target data.

10. The method of claim 9, wherein the first information further comprises register information indicating a register to which the first information corresponds.

11. The method according to claim 9 or 10, wherein the first information further comprises return information indicating a time of sending the target data to the second electronic device.

12. The method according to any one of claims 9 to 11, wherein the first information further includes log information for indicating a data amount of the target data.

13. The method of any of claims 9 to 12, wherein the second electronic device comprises a cloud server.

14. A debug system, wherein the system comprises a first electronic device and a second electronic device, the first electronic device and the second electronic device being connected;

the first electronic device stores the address information into a register;

the first electronic device sends the target data to the second electronic device;

15. The system of claim 14, further comprising a third electronic device, wherein the first electronic device is coupled to the second electronic device via the third electronic device,

The second electronic device sending first information to the first electronic device, including:

the third electronic device sends the first information to the first electronic device;

the first electronic device sending the target data to the second electronic device, including:

the first electronic device sends the target data to the third electronic device;

and the third electronic device sends the target data to the second electronic device.

16. The system of claim 15, wherein the third electronic device comprises a terminal device.

17. A debugging device, characterized in that the device comprises a processor and a memory for storing a computer program, the processor being adapted to call and run the computer program from the memory, to cause the device to perform the method of any one of claims 1 to 8 or to cause the device to perform the method of any one of claims 9 to 13.

18. A chip comprising a processor that, when executing instructions, performs the method of any one of claims 1 to 8 or performs the method of any one of claims 9 to 13.

19. An electronic device comprising a processor for coupling with a memory and reading instructions in the memory and, in accordance with the instructions, causing the electronic device to perform the method of any one of claims 1 to 8 or, in accordance with the instructions, causing the electronic device to perform the method of any one of claims 9 to 13.

20. A computer readable storage medium, characterized in that the computer readable storage medium stores a computer program, which when executed by a processor causes the processor to perform the method of any one of claims 1 to 8 or causes the processor to perform the method of any one of claims 9 to 13.