An interface fault detection system, method, and electronic device

Abstract

This application discloses an interface fault detection system, method, and electronic device, relating to the field of computer technology. The system obtains an interface fault detection command sent by a user when the device is powered on but has no display, through a control module. When the interface controller under test is functioning normally, the system responds to the command, obtains the disable information of the interface controller under test, and sends a fault signal to the control module. The control module responds to the fault signal, modifies the disable information, and reports the interface fault information. Since the control module has already reported the interface fault information, the detection module has ruled out firmware failure as the cause and determined that the fault is a physical failure of the interface under test. This application performs the disable modification of the VGA interface within the control module, rather than on the interface controller under test, to avoid affecting the normal use of other related functions in the system and improves the system's compatibility with VGA interface fault detection.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an interface fault detection system, method and electronic device. Background Technology

[0002] The Video Graphics Array (VGA) interface is a widely used video transmission interface between computers and display devices. However, it is prone to failure due to various reasons such as interface aging, loose connections, cable damage, and signal interference, which can lead to the phenomenon of no display when the computer is turned on.

[0003] In related technologies, when a system experiences a no-display issue upon power-on, specific debug firmware is typically loaded into the VGA controller to perform fault detection on the VGA interface. However, the VGA interface disabling operation implemented by the debug firmware during troubleshooting may cause other related functions in the system to malfunction, reducing the system's compatibility with VGA interface fault detection. Summary of the Invention

[0004] This application provides an interface fault detection system, method, and electronic device to at least solve the problem in the related art where the use of VGA interface disabling operation in debugging firmware affects system compatibility during fault diagnosis.

[0005] This application provides an interface fault detection system, including: a control module, an intermediate module, and a detection module;

[0006] The control module is used to obtain the interface fault detection command sent by the user when the device is powered on but there is no display. When it is determined that the interface controller under test is in normal working condition, it responds to the interface fault detection command and obtains the information to be disabled of the interface controller under test. The information to be disabled includes the status information of multiple interfaces under test.

[0007] The intermediate module is used to send fault signals to the control module, so that the control module responds to the fault signals, disables or modifies the information to be disabled in the control module, and reports the interface fault information.

[0008] The detection module is used to determine, when the control module has reported interface fault information, that the reason why the device has no display when powered on is that the interface under test has a physical fault.

[0009] This application also provides an interface fault detection method, the method comprising:

[0010] The control module obtains the interface fault detection command sent by the user when the device is powered on but there is no display. If it is determined that the interface controller under test is in normal working condition, it responds to the interface fault detection command and obtains the information to be disabled of the interface controller under test. The information to be disabled includes the status information of multiple interfaces under test.

[0011] The intermediate module sends a fault signal to the control module, so that the control module responds to the fault signal, disables or modifies the information to be disabled in the control module, and reports the interface fault information.

[0012] If the control module has reported interface fault information, it is determined that the reason why the device does not display anything when powered on is that the interface under test has a physical fault.

[0013] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for implementing the steps of any of the above-described interface fault detection methods when executing the computer program.

[0014] This application also provides a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of any of the above-described interface fault detection methods.

[0015] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described interface fault detection methods.

[0016] This application achieves this by acquiring an interface fault detection command sent by the user when the device is powered on but has no display via the control module. When the interface controller under test is functioning normally, the control module responds to the command, acquires the information to be disabled from the interface controller, sends a fault signal to the control module, and the control module responds to the fault signal, modifies the information to be disabled, and reports the interface fault information. Since the control module has already reported the interface fault information, the detection module has ruled out firmware failure as the cause and determined that the fault is a physical failure of the interface under test. This application performs the disabling modification of the VGA interface within the control module, rather than on the interface controller under test, to avoid affecting the normal use of other related functions in the system and improves the system's compatibility with VGA interface fault detection. Attached Figure Description

[0017] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1This is a schematic diagram of the interaction process of the interface fault detection system provided in the embodiments of this application;

[0019] Figure 2 A schematic diagram of the business process of an exemplary interface fault detection system provided in this application embodiment;

[0020] Figure 3 A flowchart illustrating the interface fault detection method provided in this application embodiment;

[0021] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the protection scope of this application.

[0023] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0024] VGA is an analog signal transmission interface standard primarily used for video signal transmission between a host computer and a display device. In daily use, it is prone to malfunction due to various reasons such as interface aging, loose connections, cable damage, and signal interference. Traditional VGA troubleshooting methods mainly rely on manual inspection. Repair personnel need to use their experience to check the VGA cable connections for security, interface damage, and monitor settings for accuracy. This method requires a high level of technical skill from the repair personnel, and it is easy to miss some potential faults during the troubleshooting process, resulting in the inability to repair the fault promptly and accurately.

[0025] A device powering on with no display is a typical symptom of VGA failure, which may involve hardware link interruption, firmware configuration errors, or controller malfunction. This situation is often accompanied by abnormalities in the VGA signal transmission link, such as a loose interface causing signal interruption, a controller not being initialized causing signal generation failure, or the firmware not loading the driver, preventing the system from recognizing the display device. Disabling the device is a key method for troubleshooting a power-on failure. By sending a disable command to the VGA controller, the interface is disabled. If the VGA controller can issue a fault alarm normally after disabling, it indicates a physical fault in the original VGA interface; if the VGA controller cannot issue a fault alarm normally, the problem points to a problem with the motherboard (VGA controller) or the device firmware.

[0026] To address the aforementioned technical problems, this application provides an interface fault detection system, method, and electronic device. In this system, a control module receives an interface fault detection command sent by a user when the device is powered on but has no display. If the interface controller under test is functioning normally, the control module responds to the command, obtains the disable information for the interface controller, and sends a fault signal to the control module. The control module responds to the fault signal, modifies the disable information, and reports the interface fault information. Since the control module has reported the interface fault information, the detection module, having ruled out firmware failure, determines the fault as a physical failure of the interface under test. This application disables the VGA interface within the control module, rather than at the interface controller under test, to avoid affecting the normal operation of other related functions in the system and improves the system's compatibility with VGA interface fault detection. To enable those skilled in the art to better understand this application, the following detailed description, in conjunction with the accompanying drawings and specific embodiments, further illustrates this application.

[0027] This application provides an interface fault detection system for troubleshooting VGA interface faults when there is no display after power-on, without affecting system compatibility.

[0028] like Figure 1 The diagram shown is an interactive flow diagram of the interface fault detection system provided in this application embodiment. The system includes: a control module, an intermediate module, and a detection module.

[0029] The control module is used to receive interface fault detection commands sent by users when the device is powered on but has no display. If the controller of the interface under test is determined to be functioning normally, the control module responds to the interface fault detection command and obtains the information to be disabled for the controller. This information includes the status information of multiple interfaces under test. The intermediate module sends a fault signal to the control module, causing the control module to respond to the fault signal, modify the information to be disabled, and report the interface fault information. The detection module, if the control module has already reported the interface fault information, determines that the reason for the device's lack of display upon power-on is a physical fault in the interface under test.

[0030] Specifically, a Baseboard Management Controller (BMC) is typically used as the control module. The interface under test (DUT) controller includes a VGA controller. A normal operating condition of the DUT controller means that all functions within it are functioning correctly, such as status management, signal switching control, command response, and fault status feedback. When the DUT controller is operating normally, it responds to user-sent interface fault detection commands and obtains information to be disabled through the BIOS. This information includes the status information of multiple interfaces under test, such as whether the interface is currently enabled, whether it is receiving data normally, and whether the received data is complete. The BIOS is responsible for initializing the VGA controller and outputting display signals.

[0031] Specifically, a Complex Programmable Logic Device (CPLD) is typically used as an intermediate module. This intermediate module sends a fault signal to the control module, which responds to the signal and triggers the control module to disable or modify the information to be disabled, simulating a VGA controller failure. If the detection module detects that the control module has reported an interface fault, it proves that the communication between the VGA controller, control module, and intermediate module is normal (device firmware is normal), thus ruling out both VGA controller malfunction (controller) and device firmware failure. If no actual interface fault information is received from the control module before the device powers on without display, the cause of the lack of display is determined to be a physical fault in the tested interface (VGA interface). Physical faults include interface aging, loose connections, cable damage, and monitor settings issues.

[0032] Accordingly, by simulating the disabling modification in the control module, the problem of directly disabling the VGA interface on the VGA controller, which would otherwise cause other related functions in the system to malfunction, is avoided, thus improving the system's compatibility with VGA interface fault detection.

[0033] Based on the above embodiments, as an implementable approach, in one embodiment, the control module is further configured to:

[0034] Send a first command to the interface controller under test to obtain the first command response value returned by the interface controller under test in response to the first command;

[0035] Based on the response value of the first command, determine whether the controller of the interface under test can be accessed normally;

[0036] If the controller of the interface under test cannot be accessed normally, it is determined that the controller of the interface under test has failed.

[0037] Specifically, before sending the first command to the controller of the interface under test (DUT), the BMC account must be logged in. If the returned status is invalid, login to the BMC account is unsuccessful, indicating a controller failure at the DUT. If the returned status is successful, login to the BMC account is successful. Then, the first command is sent to the DUT controller. This first command is used to access the controller. The response value returned by the DUT controller indicates whether access to the controller is possible. If the response value is abnormal, access to the controller is unsuccessful; if it is normal, access is successful. If the DUT controller cannot be accessed normally, the fault is confirmed to be a controller failure at the DUT.

[0038] Accordingly, the first command was used to determine whether the interface controller under test could be accessed normally, and the source of the fault was further investigated to see if it was in the interface controller.

[0039] Specifically, in one embodiment, the control module is further configured to:

[0040] If the interface controller under test can be accessed normally, a second command is sent to the interface controller under test to obtain the second command response value returned by the interface controller under test in response to the second command.

[0041] Based on the response value of the second command, determine whether the information to be disabled of the interface controller under test can be read normally;

[0042] If the information to be disabled from the controller of the interface under test cannot be read normally, it is determined that the controller of the interface under test has failed.

[0043] Specifically, assuming the interface controller under test is accessible, the server is shut down, and a second command is sent to the interface controller. This second command reads the disable information from the interface controller. The response value returned by the interface controller indicates the status of the disable information reading. If an abnormal return value is found in the response, the disable information cannot be read correctly; otherwise, it can be read correctly. If the disable information cannot be read, the fault is identified as a controller failure in the interface under test. The disable information includes the VGA record VGA1.

[0044] Accordingly, the second command was used to determine whether the interface controller under test could read the information to be disabled normally, and further investigation was conducted to determine whether the source of the fault was in the interface controller.

[0045] Specifically, in one embodiment, the control module is further configured to:

[0046] If the information to be disabled of the interface controller under test can be read normally, a third command is sent to the interface controller under test to obtain the response value of the third command returned by the interface controller under test.

[0047] Based on the response value of the third command, determine whether the information to be disabled by the controller of the interface under test can be disabled and modified.

[0048] If the information to be disabled on the controller of the interface under test cannot be modified, it is determined that the interface under test has a controller failure.

[0049] Specifically, if the controller under test (DUT) can read the information to be disabled normally, a third command is sent to the DUT. This third command is used to disable the information to be disabled on the DUT. The response value of the third command returned by the DUT indicates whether the information to be disabled can be modified. If the response value reports an error, the DUT cannot be modified normally; if the response value does not report an error, the DUT can be modified normally. A functional module's status value of 1 indicates normal use, and 0 indicates disabling. During modification, the status value of the disabled functional module is changed from 1 to 0 to disable the function. If the information to be disabled on the DUT cannot be modified (i.e., the original status value is 0), then the fault is determined to be a controller failure in the DUT.

[0050] Accordingly, the third command was used to determine whether the information to be disabled in the interface controller under test could be modified to disable it, further investigating whether the source of the fault was in the interface controller.

[0051] Specifically, in one embodiment, the control module is further configured to: determine that the interface controller under test is operating normally if the information to be disabled of the interface controller under test can be disabled and modified.

[0052] Specifically, when the interface controller under test meets the requirements of being able to access normally, being able to read the information to be disabled normally, and being able to disable or modify the information to be disabled, it indicates that the BMC can process the information to be disabled through the interface controller under test.

[0053] Accordingly, commands were used to sequentially determine whether the interface controller under test could be accessed normally, whether the information to be disabled could be read normally, and whether the disabling modification could be performed, thus troubleshooting the faults of the interface controller under test and confirming that the interface controller under test was operating normally.

[0054] Based on the above embodiments, as an implementable approach, in one embodiment, the intermediate module is further configured to:

[0055] Obtain the trigger logic status signal of the intermediate module;

[0056] Based on the trigger logic status signal, determine whether the intermediate module has the conditions to send a fault signal;

[0057] If it is determined that the intermediate module has the conditions to send a fault signal, the transmission status signal of the signal transmission link between the intermediate module and the control module is obtained.

[0058] Based on the transmission status signal, determine whether the intermediate module and the control module have the conditions for communication;

[0059] When communication is possible between the intermediate module and the control module, a fault signal is sent to the control module.

[0060] If the intermediate module does not have the conditions to send fault signals or there is no communication between the intermediate module and the control module, then the reason why the device has no display when powered on is determined to be a device firmware failure.

[0061] Specifically, based on the trigger logic status signal of the intermediate module, it indicates whether the intermediate module has the conditions for generating a fault signal, i.e., whether the intermediate module can generate a fault signal normally. If the trigger logic status signal is 1, the intermediate module does not have the conditions for sending a fault signal, meaning there is a logic problem with the CPLD, causing the fault signal to fail to be transmitted to the control module normally. If the trigger logic status signal is 0, the intermediate module has the conditions for sending a fault signal, and the fault signal can be transmitted to the control module normally. Given that the intermediate module has the conditions for sending a fault signal, i.e., the control module can receive the fault signal normally, the transmission status signal of the signal transmission link between the intermediate module and the control module is obtained. This transmission status signal indicates whether the intermediate module and the control module have the conditions for communication, i.e., whether they can communicate normally. If the transmission status signal is 1, the intermediate module and the control module cannot communicate normally, meaning there is another logic problem with the CPLD, which also causes the fault signal to fail to be transmitted to the control module normally. If the transmission status signal is 0, the intermediate module and the control module can communicate normally, and the fault signal can be transmitted to the control module normally.

[0062] Accordingly, by triggering logic status signals and transmission status signals, potential device firmware faults in the communication between the intermediate module and the control module were investigated.

[0063] Based on the above embodiments, as an implementable approach, in one embodiment, the intermediate module is further configured to:

[0064] After sending a fault signal to the control module, access the signal status register of the control module to read the first signal status value and the second signal status value;

[0065] Based on the first signal status value, determine whether the control module has identified the source of the fault signal; the source of the fault includes the interface controller under test.

[0066] Based on the second signal status value, determine the validity verification result of the fault signal by the control module;

[0067] If the control module is unsure of the source of the fault signal or the validity verification result of the fault signal is invalid, then the cause of the device not displaying anything upon power-on is determined to be a device firmware fault.

[0068] Specifically, when the intermediate module can normally send fault signals to the control module, the control module receives the fault signals. For example, the Advanced Platform Management Link (APML) module of the BMC processes the fault signals and then accesses the signal status register of the control module to obtain the first signal status value and the second signal status value. The first signal status value indicates that the control module has determined the source of the fault signal. If the first signal status value is 1, it indicates that the source of the fault is the interface controller under test. If the first signal status value is 0, it indicates that the control module does not know the source of the fault signal. The second signal status value indicates the validity verification result of the control module on the fault signal. If the second signal status value is 1, the validity verification result of the fault signal is valid, indicating that the fault signal is real and valid after verification by the control module. If the second signal status value is 0, the validity verification result of the fault signal is invalid, indicating that the fault signal has not passed the verification of the control module. For example, the identity identification (ID) of the fault signal is partially missing. If the control module is unsure of the source of the fault signal or the validity verification result of the fault signal is invalid, then the cause of the device not displaying anything upon power-on is determined to be a device firmware fault.

[0069] Accordingly, the source of the fault was located by the first signal status value and the second signal status value, and the validity of the fault signal was verified. By characterizing the first signal status value and the second signal status value, when the control module is uncertain about the source of the fault signal or the validity verification result of the fault signal is invalid, the source of the fault can be determined to be a device firmware fault.

[0070] Based on the above embodiments, as an implementable approach, in one embodiment, the detection module is further configured to: determine that the reason for the device's lack of display upon power-on is a device firmware failure when the control module fails to report interface fault information.

[0071] Specifically, upon server startup, check the Integrated Diagnostic Log (IDL) in the web interface to determine if the management module reports interface fault information. If fault information is successfully reported, it indicates that the Basic Input / Output System (BIOS) has successfully sent interface fault information, and the fault can be determined based on this information. If no fault information is reported, it means that the BIOS has not successfully sent interface fault information, thus confirming that the cause of the device's lack of display upon startup is a firmware fault.

[0072] Accordingly, depending on whether the control module reports interface fault information, it can be determined whether the reason for the device's lack of display upon startup is a firmware fault or a physical fault.

[0073] For example, such as Figure 2 The diagram shows a business process of an exemplary interface fault detection system provided in this application embodiment. First, the user account of the Baseboard Management Controller (BMC) is logged in. After logging in, the server is shut down, and a first command is sent to the interface controller under test. The first command response value is obtained. If the first command response value indicates that the interface controller under test is accessing normally, a second command is sent to the interface controller under test. The second command response value is obtained. If the second command response value indicates that the information to be disabled of the interface controller under test is read normally, a third command is sent to the interface controller under test. The third command response value is obtained. If the third command response value indicates that the information to be disabled of the interface controller under test can be disabled and modified, it indicates that the interface controller under test is not faulty. Then, the system responds to the fault signal of the intermediate module and starts the server. The intermediate module obtains its trigger logic status signal. If the trigger logic fault signal indicates that the intermediate module has the conditions to send a fault signal, the intermediate module obtains the transmission status signal of the signal transmission link between the intermediate module and the control module. After sending the fault signal to the control module, the intermediate module accesses the signal status register to read the first and second signal status values. If the control module is unsure of the fault source or the validity verification result of the fault signal is invalid, the cause of the device's lack of display upon startup is determined to be a device firmware fault. Then, the server powers on, and the control module reports interface fault information. If the reporting is successful, it is determined to be a physical fault; otherwise, it is determined to be a device firmware fault.

[0074] Specifically, in one embodiment, the control module sends a test command to the intermediate module. Based on the response of the intermediate module to the test command, the specific type of firmware fault is determined, and an attempt is made to repair it. For example, if the specific type of fault is a configuration parameter error, the pre-saved standard parameters are retrieved from the backup storage area, the abnormal values ​​are overwritten, and the parameters are restored to the normal working state, so that normal data communication between the control module and the intermediate module can be quickly restored.

[0075] The interface fault detection system provided in this application includes a control module, an intermediate module, and a detection module. The control module is used to acquire an interface fault detection command sent by a user when the device is powered on but has no display. If the controller of the interface under test is determined to be functioning normally, the control module responds to the interface fault detection command and acquires the information to be disabled for the controller of the interface under test. The information to be disabled includes the status information of multiple interfaces under test. The intermediate module sends a fault signal to the control module, causing the control module to respond to the fault signal, modify the information to be disabled in the control module, and report the interface fault information. The detection module, if the control module has reported the interface fault information, determines that the reason for the device's lack of display upon power-on is a physical fault in the interface under test. The method provided by the above solution obtains the interface fault detection command sent by the user when the device is powered on but has no display through the control module. When the interface controller under test is functioning normally, the module responds to the command, obtains the disable information of the interface controller under test, sends a fault signal to the control module, and the control module responds to the fault signal, modifies the disable information, and reports the interface fault information. Since the control module has reported the interface fault information, the detection module has ruled out device firmware failure as the cause and determined that the fault is a physical fault in the interface under test. This application performs the disable modification of the VGA interface within the control module, rather than on the interface controller under test, to avoid affecting the normal use of other related functions in the system, thus improving the system's compatibility with VGA interface fault detection. Furthermore, by simulating the disable modification in the control module, the problem of directly disabling the VGA interface on the VGA controller, which could lead to the inability of other related functions in the system to function properly, is avoided, further improving the system's compatibility with VGA interface fault detection. The first command determines whether the interface controller under test can be accessed normally, further investigating whether the source of the fault lies with the interface controller. The second command was used to determine whether the interface controller under test could read the information to be disabled normally, further investigating whether the fault source was in the interface controller. The third command was used to determine whether the information to be disabled in the interface controller could be modified, further investigating whether the fault source was in the interface controller. Commands were used sequentially to determine whether the interface controller under test could be accessed normally, whether the information to be disabled could be read normally, and whether it could be modified to disable, thus identifying faults in the interface controller under test and confirming that its operating condition was normal. By triggering logic status signals and transmission status signals, potential firmware faults in the communication between the intermediate module and the control module were investigated. The fault source was located using the first and second signal status values, and the validity of the fault signal was verified. Based on the first and second signal status values, when the control module is uncertain about the fault source of the fault signal or the validity verification result of the fault signal is invalid, the fault source can be determined to be a firmware fault.Whether the control module reports interface fault information can indicate whether the device's lack of display upon startup is due to a firmware or physical fault.

[0076] Through the above description of the embodiments, those skilled in the art can clearly understand that the system according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platform, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method.

[0077] This application provides an interface fault detection method, applied to the host side of the interface fault detection system (provided in the above embodiments). The executing entity of this application is an electronic device, such as a server, desktop computer, laptop computer, tablet computer, and other electronic devices capable of heterogeneous computing.

[0078] like Figure 3 The diagram shown is a flowchart of an interface fault detection method provided in an embodiment of this application. The method includes:

[0079] Step 301: Based on the interface fault detection command sent by the user when the device is powered on but there is no display, the control module obtains the interface fault detection command and obtains the disabling information of the interface controller under test in response to the interface fault detection command. The disabling information includes the status information of multiple interfaces under test.

[0080] Step 302: Based on the intermediate module, a fault signal is sent to the control module so that the control module responds to the fault signal, disables or modifies the information to be disabled in the control module, and reports the interface fault information.

[0081] Step 303: If the control module has reported interface fault information, determine that the reason why the device has no display when powered on is that the interface under test has a physical fault.

[0082] For a description of the features in the embodiment corresponding to the interface fault detection method, please refer to the relevant description of the embodiment corresponding to the interface fault detection system, which will not be repeated here.

[0083] Embodiments of this application also provide an electronic device, such as... Figure 4 The diagram shown is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, including a processor 10 and a memory 20. The memory 20 stores a computer program, and the processor 10 is configured to run the computer program to execute the steps in any of the above-described interface fault detection method embodiments.

[0084] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described interface fault detection method embodiments at runtime.

[0085] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0086] The embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described interfaces fault detection method embodiments.

[0087] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described interface fault detection method embodiments.

[0088] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0089] The foregoing has provided a detailed description of an interface fault detection system, method, and electronic device provided in this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to aid in understanding the method and core ideas of this application. It should be noted that those skilled in the art can make various improvements and modifications to this application without departing from its principles, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. An interface fault detection system, characterized in that, include: Control module, intermediate module, and detection module; The control module is used to acquire the interface fault detection command sent by the user when the device is powered on but there is no display, and when it is determined that the interface controller under test is in normal working condition, it responds to the interface fault detection command and acquires the disabling information of the interface controller under test; wherein, the disabling information includes the status information of multiple interfaces under test. The intermediate module is used to send a fault signal to the control module, so that the control module responds to the fault signal, disables or modifies the information to be disabled in the control module, and reports the interface fault information. The detection module is used to determine, when the control module has reported interface fault information, that the reason why the device has no display when powered on is that the interface under test has a physical fault.

2. The interface fault detection system according to claim 1, characterized in that, The control module is also used for: Send a first command to the interface under test controller to obtain a first command response value returned by the interface under test controller in response to the first command; Based on the first command response value, determine whether the interface controller under test can be accessed normally; If the controller of the interface under test cannot be accessed normally, it is determined that the controller of the interface under test has failed.

3. The interface fault detection system according to claim 2, characterized in that, The control module is also used for: If the interface controller under test can be accessed normally, a second command is sent to the interface controller under test to obtain the second command response value returned by the interface controller under test in response to the second command. Based on the second command response value, determine whether the information to be disabled of the interface controller under test can be read normally; If the information to be disabled by the controller of the interface under test cannot be read normally, it is determined that the controller of the interface under test has failed.

4. The interface fault detection system according to claim 3, characterized in that, The control module is also used for: If the information to be disabled of the interface controller under test can be read normally, a third command is sent to the interface controller under test to obtain the third command response value returned by the interface controller under test in response to the third command. Based on the third command response value, determine whether the information to be disabled by the interface controller under test can be disabled or modified. If the information to be disabled on the controller of the interface under test cannot be modified, it is determined that the interface under test has a controller failure.

5. The interface fault detection system according to claim 4, characterized in that, The control module is also used for: If the information to be disabled in the interface controller under test can be disabled and modified, it is determined that the interface controller under test is operating normally.

6. The interface fault detection system according to claim 1, characterized in that, The intermediate module is also used for: Obtain the trigger logic status signal of the intermediate module; Based on the trigger logic status signal, determine whether the intermediate module has the conditions to send the fault signal; If it is determined that the intermediate module has the conditions to send the fault signal, the transmission status signal of the signal transmission link between the intermediate module and the control module is obtained; Based on the transmission status signal, it is determined whether the intermediate module and the control module have the conditions for communication; When communication is possible between the intermediate module and the control module, a fault signal is sent to the control module. If the intermediate module does not have the conditions to send the fault signal or there is no communication between the intermediate module and the control module, then the reason why the device has no display when powered on is determined to be a device firmware fault.

7. The interface fault detection system according to claim 1, characterized in that, The intermediate module is also used for: After sending a fault signal to the control module, access the signal status register of the control module to read the first signal status value and the second signal status value; Based on the first signal status value, the control module determines whether it has identified the source of the fault signal; wherein the source of the fault includes the interface controller under test. Based on the second signal status value, the validity verification result of the fault signal by the control module is determined; If the control module is unsure of the source of the fault signal or the validity verification result of the fault signal is invalid, then it determines that the reason for the device not displaying anything upon power-on is a device firmware fault.

8. The interface fault detection system according to claim 1, characterized in that, The detection module is also used for: If the control module does not report interface fault information, it is determined that the reason why the device has no display when powered on is a device firmware fault.

9. A method for detecting interface faults, characterized in that, The method includes: The control module acquires the interface fault detection command sent by the user when the device is powered on but there is no display. If the controller of the interface under test is determined to be in normal working condition, the module responds to the interface fault detection command and acquires the information to be disabled of the controller of the interface under test. The information to be disabled includes the status information of multiple interfaces under test. The intermediate module sends a fault signal to the control module, so that the control module responds to the fault signal, disables or modifies the information to be disabled, and reports the interface fault information. If the control module has reported interface fault information, it is determined that the reason why the device has no display when powered on is that the interface under test has a physical fault.

10. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the interface fault detection method as described in claim 9 when executing the computer program.

Images