A method and device for terminal equipment self-test in aging test

Abstract

The present application provides a method and apparatus for terminal device self-testing during a burn-in test. The method comprises: performing a burn-in test by having the terminal device respond to a set target test program; performing a power-on test during the burn-in test and generating a corresponding identification code; verifying the identification code to obtain a test result, and using the test result as the self-test result. The method implements a power-on test of the terminal device's status during the burn-in test, generates an identification code based on the test result, and verifies the identification code to determine whether the terminal device has any abnormalities during the burn-in test, as well as the specific problem causing the abnormality.

Description

Technical Field

[0001] The present application relates to the technical field of terminal detection management, and in particular to a method and apparatus for terminal device self-test in an aging test. Background Art

[0002] Burn-in testing simulates the various factors involved in real-world use and conducts intensive testing under corresponding conditions to simulate the aging of the device. To ensure the stability of terminal equipment, terminal equipment generally undergoes high-temperature burn-in testing before leaving the factory.

[0003] Traditional burn-in testing methods require connecting each terminal device to a computer after the test to view the results. This requires extensive manual work and is inefficient. With the widespread adoption of broadband networks and the annual increase in terminal device shipments, traditional burn-in testing methods are no longer able to meet current production efficiency requirements.

[0004] Furthermore, because the terminals cannot be connected to a computer during burn-in testing in the burn-in room, it is impossible to monitor the terminal device's status in real time during the burn-in process. Testers cannot determine whether the terminal device has experienced an abnormal restart during the burn-in test, which may result in the flow of problematic devices to the next production stage.

[0005] Therefore, how to monitor the status of terminal equipment during the aging test is a technical problem that needs to be solved. Summary of the Invention

[0006] The main purpose of this application is to provide a method and device for terminal device self-test in aging test, aiming to solve the technical problem that the status of the terminal device cannot be monitored in traditional aging test.

[0007] In a first aspect, the present application provides a method for self-testing a terminal device during a burn-in test, the method comprising the following steps:

[0008] The terminal equipment responds to the set target test program and performs the aging test;

[0009] When the terminal device is undergoing an aging test, it performs a power-on test and generates a corresponding identification code;

[0010] The terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result.

[0011] In some embodiments, when the terminal device is undergoing an aging test, performing a power-on test and generating a corresponding identification code specifically includes the following steps:

[0012] When the terminal device is performing the aging test, a power-on test is performed after each startup, and an identification is generated according to the result of the power-on test, and the identification is stored to form the identification code;

[0013] After the terminal device is started, if it is not restarted within a set time interval, a new identifier is additionally generated, and the new identifier is stored to update the identification code.

[0014] In some embodiments, the identifier includes a hardware fault identifier, and performing a power-on test after each startup, generating an identifier based on the result of the power-on test, and storing the identifier to form the identification code specifically includes the following steps:

[0015] Generate a hardware fault identifier at the beginning of power-on detection, and detect the hardware after generating the hardware fault identifier;

[0016] If the hardware has no fault, rewriting the hardware fault flag into a power-on detection success flag, and storing the power-on detection success flag to form the identification code;

[0017] If the hardware fails, the power-on detection is stopped, and the hardware failure identification is stored to form the identification code.

[0018] In some embodiments, the method further comprises the following steps:

[0019] After each identification is generated, the corresponding identification code is checked. If the check result of the corresponding identification code is that the aging test is not completed, the terminal device continues to perform power-on detection. Otherwise, the check result of the corresponding identification code is used as the self-test result of the terminal device and the aging test is stopped.

[0020] In some embodiments, after each startup of the terminal device and before performing a power-on test, the following steps are further included:

[0021] The identification code is checked. If the check result of the identification code includes that the aging test is not completed or the identification code does not exist, a power-on test is performed on the terminal device. Otherwise, the check result of the identification code is used as the self-test result of the terminal device and the aging test is stopped.

[0022] In some embodiments, the terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result, specifically comprising the following steps:

[0023] The terminal device determines whether there is a hardware fault identifier in the identification code. If so, the terminal device uses the hardware fault as the self-test result and stops the burn-in test. Otherwise, the terminal device compares the identification code with the target code corresponding to the target test program bit by bit and uses the comparison result as the self-test result of the terminal device.

[0024] The target code is stored in the memory of the terminal device.

[0025] In some embodiments, comparing the identification code bit by bit with the target code corresponding to the target test program and using the comparison result as the self-test result of the terminal device specifically includes the following steps:

[0026] Comparing the identification code and the target code bit by bit from front to back;

[0027] If the identification code in a corresponding position is a power-on detection success identifier and the target code is a device normal operation setting time identifier, an abnormal restart during the aging test is regarded as a self-test result and the aging test is stopped;

[0028] If the identification code in a corresponding position is a device normal operation setting time identifier and the target code is a power-on detection success identifier, failure to perform the aging test as required is regarded as a self-test result, and the aging test is stopped;

[0029] If the number of digits identified in the identification code is less than that of the target code, and the identification code and the target code in the corresponding positions are identical, then the aging test is deemed incomplete as a self-test result, and the aging test is continued;

[0030] If the number of digits identified in the identification code is the same as the number of digits in the target code, and the identification code and the target code in the corresponding positions are the same, the aging test is considered successful as a self-test result and the aging test is terminated.

[0031] In some embodiments, after the terminal device performs the aging test in response to the set target test program and before performing the power-on test and generating the corresponding identification code, the following steps are further included:

[0032] determining a current location of an aging log storing the identification code;

[0033] If the aging log is in the first position, it is determined that the terminal device is undergoing an aging test;

[0034] If the aging log is in the second location, the terminal device has not undergone aging testing;

[0035] The terminal device generates the aging log at the first location when the aging test starts, and transfers the aging log from the first location to the second location after the aging test is completed.

[0036] In some embodiments, the terminal device indicates a self-test result of the terminal device by turning on or off at least one indicator light.

[0037] In a second aspect, the present application further provides a device for self-testing a terminal device during a burn-in test, the device comprising:

[0038] an aging test module, configured to perform an aging test in response to a set target test program;

[0039] An identification code generation module, which is used for performing power-on detection on the terminal device during the aging test and generating a corresponding identification code;

[0040] A detection module is used for the terminal device to detect the identification code to obtain a detection result, and use the detection result as a self-detection result.

[0041] The present application provides a method and apparatus for terminal device self-testing during a burn-in test. The method comprises: performing a burn-in test by having the terminal device respond to a set target test program; performing a power-on test during the burn-in test and generating a corresponding identification code; verifying the identification code to obtain a test result, and using the test result as the self-test result. The method implements a power-on test of the terminal device's status during the burn-in test, generates an identification code based on the test result, and verifies the identification code to determine whether the terminal device has any abnormalities during the burn-in test, as well as the specific problem causing the abnormality. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0043] Figure 1 A flowchart of a method for terminal device self-test in an aging test provided in an embodiment of the present application;

[0044] Figure 2 This is a schematic diagram of the terminal device hardware system;

[0045] Figure 3 Schematic diagram of the specific process of generating identification codes for power-on detection;

[0046] Figure 4 This is a schematic diagram of the specific process of identification code verification;

[0047] Figure 5 A schematic diagram of a specific process for terminal equipment self-testing in aging testing;

[0048] Figure 6 A schematic block diagram of an apparatus for terminal device self-test in an aging test provided in an embodiment of the present application.

[0049] The realization of the objectives, functional features and advantages of this application will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0050] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0051] The flowcharts shown in the accompanying drawings are for illustrative purposes only and do not necessarily include all contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps may be decomposed, combined, or partially merged, so the actual execution order may vary depending on the actual situation.

[0052] The present invention provides a method and apparatus for terminal device self-testing during a burn-in test. The method can be applied to terminal devices, such as PON (Passive Optical Network) terminals, wireless routers, and converged terminals. The present invention uses a PON terminal device as an example for illustration.

[0053] The following describes some embodiments of the present application in detail with reference to the accompanying drawings. In the absence of conflict, the following embodiments and features therein may be combined with each other.

[0054] Please refer to Figure 1 , Figure 1 A flowchart of a method for terminal device self-test in an aging test provided in an embodiment of the present application.

[0055] like Figure 1 As shown, the method includes steps S1 to S3.

[0056] Step S1: The terminal device performs an aging test in response to a set target test program.

[0057] Step S2: When the terminal device is undergoing an aging test, it performs a power-on test and generates a corresponding identification code.

[0058] Step S3: The terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result.

[0059] In the embodiment of the present application, a PON terminal device is taken as an example to illustrate a method for terminal device self-test in an aging test.

[0060] like Figure 2 As shown, the hardware of a PON terminal device consists of a SOC chip, memory, buttons, indicator lights, an optical module, a voice module, and a Wi-Fi module. The SOC chip is the core unit of the device and can be replaced by a CPU in other terminal devices. In this embodiment, when performing a burn-in test on a PON terminal device, the optical module, voice module, and Wi-Fi module responsible for specific services in the terminal device need to be tested. When performing a burn-in test on other terminal devices, the modules to be tested can be selected.

[0061] It's worth noting that different terminal devices have different burn-in test requirements at different stages of production. For example, during the small-batch production phase, burn-in testing requires the device to run for eight hours, with a power cycle every two hours to observe whether the device can boot normally. During mass production, the device must run for four hours without power cycles.

[0062] In an embodiment of the present application, different target test programs are set according to the different burn-in test requirements of the terminal device to control the terminal device to operate according to the burn-in test requirements. A corresponding target code is then set according to the target test program. The target code consists of identifiers. Specifically, in this embodiment, a first identifier is set to indicate that the terminal device needs to be powered on once during the burn-in test. This identifier can indicate a successful power-on test, i.e., a power-on test success identifier. A second identifier is set to indicate normal operation of the device, i.e., a normal operation time setting identifier, after startup. Finally, a complete target code can be set according to the test requirements. For example, if the burn-in test requirement for the target test program is that the terminal device should be powered on and run for four hours, with a power-off and restart every two hours, the target code can be set to consist of a first identifier, a second identifier, a second identifier, a first identifier, a second identifier, and a second identifier. If 0 represents the first identifier and 1 represents the second identifier, the target code can be 011011. If the terminal device is required to run for four hours without powering off and restarting, the target code can be set to 01111.

[0063] The memory in the terminal device includes volatile memory and non-volatile memory. The volatile memory is generally DDR, and the non-volatile memory is generally Flash. The target code and the corresponding target test program are stored in the non-volatile memory in the form of files. In order to meet the needs of different production stages, a terminal device can store multiple target test programs, that is, multiple target codes, each target code corresponding to a target test program. When a burn-in test is required, different target codes are selected through the target code input module. In the embodiment of the present application, when a burn-in test is required, the tester selects the target code by pressing a button. For example, pressing the button once indicates the selection of the first target code, and at the same time, the indicator LED1 flashes three times to indicate that the setting is successful. Similarly, pressing the button twice indicates the selection of the second target code, and at the same time, the indicator LED2 flashes three times to indicate that the setting is successful. The selected target code will be stored in the set location of the memory, so that the terminal device can be tested according to the target test program corresponding to the target code. The tester can also exit the burn-in test mode of the terminal device by pressing a button.

[0064] Exemplarily, the terminal device responds to the set target test program, and the specific steps of performing the aging test include: the terminal device is powered on after being connected to the power supply, receives the target code selection signal sent by the tester through the key after being powered on, and then responds to the target test program corresponding to the selected target code to run to perform the aging test.

[0065] Furthermore, when the terminal device is undergoing the aging test, the power-on detection and generation of the corresponding identification code specifically include the following steps:

[0066] When the terminal device is performing the aging test, a power-on test is performed after each startup, and an identification is generated according to the result of the power-on test, and the identification is stored to form the identification code;

[0067] After the terminal device is started, if it is not restarted within a set time interval, a new identifier is additionally generated, and the new identifier is stored to update the identification code.

[0068] For example, the aging test requires that the terminal device run for 4 hours and restart every 2 hours, and set a new identifier to be generated every one hour after the terminal device is started. After the terminal device is started for the first time, a power-on test is performed, and an identifier is generated based on the power-on test result, and the identifier is stored to form an identification code. The current identification code only includes one identifier. The terminal device restarts every two hours, and generates an identifier every hour. Then, two identifiers will be generated two hours before the first restart. The current target code includes three identifiers. After the terminal device restarts according to the aging test requirements, the terminal device will perform another power-on test and generate another identifier based on the power-on test result. The aging test of the terminal device ends after two hours, so two more identifiers will be generated before the end of the aging test. The above example is a case where no abnormalities or failures occur during the aging test. After the aging test is completed, the terminal equipment runs for 4 hours according to the aging test requirements and restarts once every 2 hours. The identification code includes a total of 6 digits. The number of digits representing the aging test completion identification code is the same as that of the target code, and the generated identification code is completely consistent with the identification of the target code.

[0069] It is worth noting that after each identifier is generated, it will be stored in the aging log in the storage. Multiple identifiers constitute an identification code, and there is no separator between identifiers.

[0070] Specifically, the identification includes a hardware fault identification. The steps of performing a power-on test after each startup, generating an identification based on the result of the power-on test, and storing the identification to form the identification code specifically include the following steps:

[0071] Generate a hardware fault identifier at the beginning of power-on detection, and detect the hardware after generating the hardware fault identifier;

[0072] If the hardware has no fault, rewriting the hardware fault flag into a power-on detection success flag, and storing the power-on detection success flag to form the identification code;

[0073] If the hardware fails, the power-on detection is stopped, and the hardware failure identification is stored to form the identification code.

[0074] Exemplarily, the identifier constitutes an identification code. The generation of the identifier in this application includes:

[0075] After the power-on test is successful, the first flag is generated, which can be recorded as 0;

[0076] The second identifier is generated after the terminal device operates normally for one hour and can be recorded as 1;

[0077] A hardware fault identifier X is generated when a hardware module of a terminal device undergoes power-on detection abnormality. In the embodiment of the present application, a power-on detection includes sequentially detecting three hardware modules of the terminal device, namely, an optical module, a voice module, and a WiFi module. The hardware fault identifier includes an optical module fault identifier, a voice module fault identifier, and a WiFi module fault identifier. The optical module fault identifier can be recorded as a third identifier, X1; the voice module fault identifier can be recorded as a fourth identifier, X2; and the WiFi module fault identifier can be recorded as a fifth identifier, X3.

[0078] The first identifier in the identification code and the first identifier in the target code correspond to the power-on detection success identifier, and the second identifier in the identification code and the second identifier in the target code correspond to the normal operation setting time identifier of the device.

[0079] like Figure 3 As shown, performing a power-on detection to generate an identifier specifically includes the following steps:

[0080] Step S201: Write a third identifier into the aging log.

[0081] Step S202: Detect whether the optical module is faulty. If the optical module is faulty, stop the current power-on detection and store the third identifier to form an identification code.

[0082] Step S203: If the optical module is not faulty, rewrite the third identifier written in S201 to the fourth identifier.

[0083] Step S204: Continue to detect whether the voice module is faulty. If the voice module is faulty, stop the current power-on detection and store the fourth identifier to form an identification code.

[0084] Step S205: If there is no fault in the voice module, rewrite the fourth identifier written in S203 to the fifth identifier.

[0085] Step S206: Check whether the WiFi module is faulty. If the WiFi module is faulty, stop the power-on test and store the fifth identifier to form an identification code.

[0086] Step S207: If the WiFi module is not faulty, the fifth flag written in S205 is rewritten to the first flag, indicating that the power-on detection is successful.

[0087] If the terminal device is not restarted within the set time interval after startup, a new second identifier is added. Since the target test program controls the terminal device to restart, the timing for adding the second identifier is before the terminal device restarts, that is, after the terminal device restarts after the second identifier is generated.

[0088] The reason for writing the third identifier in advance is that the system may restart abnormally when the optical module is powered on, resulting in insufficient time to write the third identifier. Therefore, writing the third identifier in advance avoids the situation where no identifier is generated after the power-on test.

[0089] The power-on detection of three hardware in this application is only used as an example. The power-on detection of this application is not limited to the number or type of hardware mentioned above. The specific detection process and steps of the power-on detection of the hardware can be carried out according to the relevant aging test method, which will not be repeated here.

[0090] In some embodiments, after the terminal device performs a burn-in test in response to a set target test program and before performing a power-on test and generating a corresponding identification code, the step of determining whether the terminal device is performing a burn-in test is further included. Specifically, the steps include:

[0091] determining a current location of an aging log storing the identification code;

[0092] If the aging log is in the first position, it is determined that the terminal device is undergoing an aging test;

[0093] If the aging log is in the second location, the terminal device has not undergone aging testing;

[0094] When the aging log does not exist, the terminal device generates the aging log at the first location when performing the aging test, and transfers the aging log from the first location to the second location after the aging test is completed.

[0095] It is worth noting that when the terminal device performs an aging test in response to the target test program, an aging log will be generated in the non-volatile memory to store the identification code. When the aging test starts, the aging log does not exist, and the aging test will be generated at the first position of the non-volatile memory. The aging log will be stored in the first position while the aging test is ongoing. Only when the terminal device exits the aging test will the aging log be moved from the first position to the second position for storage. Therefore, it is possible to determine whether the terminal device is performing an aging test based on the position of the aging log during the aging test. If the aging log is in the first position, it is determined that the terminal device is performing an aging test. If the aging log is in the second position, the terminal device is not performing an aging test. It is worth noting that the identification code is stored in the aging log, and the aging log can be used by the tester to analyze after the aging test is completed to determine the specific status of the terminal device during the aging test.

[0096] The first position and the second position represent storage positions in the storage device and can be set according to actual conditions.

[0097] Furthermore, the terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result, specifically including the following steps:

[0098] The terminal device determines whether there is a hardware fault identifier in the identification code. If so, the terminal device uses the hardware fault as the self-test result and stops the burn-in test. Otherwise, the terminal device compares the identification code with the target code corresponding to the target test program bit by bit and uses the comparison result as the self-test result of the terminal device.

[0099] The target code is stored in the memory of the terminal device.

[0100] Furthermore, the step of comparing the identification code with the target code corresponding to the target test program bit by bit and using the comparison result as the self-test result of the terminal device specifically includes the following steps:

[0101] Comparing the identification code and the target code bit by bit from front to back;

[0102] If the identification code in a corresponding position is a power-on detection success identifier and the target code is a device normal operation setting time identifier, an abnormal restart during the aging test is regarded as a self-test result and the aging test is stopped;

[0103] If the identification code in a corresponding position is a device normal operation setting time identifier and the target code is a power-on detection success identifier, failure to perform the aging test as required is regarded as a self-test result, and the aging test is stopped;

[0104] If the number of digits identified in the identification code is less than that of the target code, and the identification code and the target code in the corresponding positions are identical, then the aging test is deemed incomplete as a self-test result, and the aging test is continued;

[0105] If the number of digits identified in the identification code is the same as the number of digits in the target code, and the identification code and the target code in the corresponding positions are the same, the aging test is considered successful as a self-test result and the aging test is terminated.

[0106] It is worth noting that in the embodiment of the present application, the verification of the generated identification code can be set to output a total of 7 types of verification results, specifically:

[0107] Result 1 indicates that the aging test is not completed.

[0108] Result 2: Indicates that the aging test is successful.

[0109] Result three: The optical module power-on detection is abnormal.

[0110] Result 4: The voice module power-on detection is abnormal.

[0111] Result 5: Indicates that the WiFi module power-on detection is abnormal.

[0112] Result 6: Indicates that an abnormal restart occurred during the aging test.

[0113] Result 7: Indicates that the aging test was not performed as required. For example, Figure 4 As shown, checking the identification code includes:

[0114] Step S301: Determine whether the identification code includes a third identification; if so, execute step S302; if not, execute step S303.

[0115] Step S302: Output the third test result (abnormality in the optical module power-on detection), use the result as the terminal device self-test result, and stop the aging test.

[0116] Step S303, determining whether the identification code includes the fourth identification; if so, executing step S304; if not, executing step S305.

[0117] Step S304: Output the test result 4 (the voice module is abnormal when it is powered on), and use the result as the terminal device self-test result, and stop the aging test.

[0118] Step S305 , determining whether the identification code includes the fifth identification; if so, executing step S306 ; if not, executing step S307 .

[0119] Step S306: Output the test result five (WiFi module power-on detection abnormality), and use the result as the terminal device self-test result, and stop the aging test.

[0120] Step S307, determine whether there is an abnormal first identifier in the identification code, specifically, determine whether there is a corresponding position in which the identification code is a power-on detection success identifier, and the target code is a time identifier for setting the normal operation of the device; if so, execute step S308; if not, execute step S309.

[0121] Step S308: Output the test result 6 (abnormal restart occurs during the aging test), use the result as the terminal device self-test result, and stop the aging test.

[0122] Step S309, determine whether there is an abnormal second identifier in the identification code. Specifically, determine whether there is a corresponding position in which the identification code is a time identifier for setting the normal operation of the equipment, and the target code is a power-on detection success identifier; if so, execute step S310; if not, execute step S311.

[0123] Step S310: Output the inspection result seven (aging test is not performed as required), use the result as the terminal device self-test result, and stop the aging test.

[0124] Step S311, determine whether the number of digits identified in the identification code is less than the target code; if so, execute step S312; if not, execute step S313.

[0125] Step S312: Output test result 1 (indicating that the aging test is not completed) and use the result as the terminal device self-test result. If the target code and the identification code in the corresponding position are the same after the previous test, and the identification code is less than the target code, it means that the aging test is not completed.

[0126] Step S313, determine whether the identification code is exactly the same as the target code. Specifically, determine whether the number of digits in the identification code is the same as the number of digits in the target code, and whether the identification code and the target code in the corresponding positions are the same. If so, execute step S314; otherwise, execute step S315.

[0127] Step S314: Output the second test result (aging test success), and use the result as the terminal device self-test result.

[0128] Step S315: Output test result seven (aging test not performed as required) and use the result as the terminal device self-test result. If the identification code and the target code are still different after eliminating the above situations, it means that the terminal device has not performed the aging test as required.

[0129] It is worth noting that, for corresponding positions, the first identifier in the identification code and the first identifier in the target code are corresponding positions, and so on.

[0130] After each power-on test completes, an identifier is generated, or an identifier is generated at a set interval. After the identification code is updated, the corresponding identification code must be verified according to the above steps. If the verification result of the corresponding identification code indicates that the aging test is not completed, the terminal device continues to perform the aging test. If other results are obtained, the verification result of the corresponding identification code is used as the self-test result of the terminal device, and the aging test is stopped, waiting for the tester to perform subsequent operations. The verification of the identification code in this embodiment is the same as the above-mentioned verification process. The identification code is verified after each identifier is generated. This ensures that when a hardware fault is detected during power-on, the test result can be reflected in a timely manner for the tester to respond, thereby improving the self-test efficiency of the terminal device.

[0131] In a specific embodiment, the terminal device performs an aging test according to a target test program that runs for 4 hours after power-on and is powered off and restarted every two hours, with a target code of 011011. After the device is started for the first time, a power-on test is performed, and the first identifier is written according to the power-on test result to form an identification code. The current identification code contains only this identifier. The identification code is checked. If the identifier in the identification code is found to be a hardware fault identifier X, a hardware fault is output as the self-test result of the terminal device, and the aging test stops, waiting for the tester to process. If the identifier is found to be the same as the identification code, both are the power-on test success identifier 0, and the identification code at this time represents less than the target code, the aging test continues.

[0132] After the terminal device continues the aging test for one hour, the second identifier will be written to update the identification code. At this time, the identification code includes two identifiers, and the identification code is checked again. It can be understood that since the aging test can only continue when the first identifier of the identification code is the same as the first identifier of the target code, the first identifier in the identification code detected at this time is the same as the first identifier of the target code. If the second digit of the identification code is detected to be the power-on detection success identifier 0, and the corresponding second digit of the target code is the power-on operation one hour identifier 1, indicating that the terminal device has an abnormal restart, the self-test result of the abnormal restart in the aging test of the terminal device is output; if the second digit of the identification code is 1, which is the same as the first two digits of the target code, and the number of digits in the identification code is less than the target code at this time, the aging test continues.

[0133] After the device continues the aging test for one hour, the third identifier is written to update the identification code, the identification code is checked again, and the aging test continues when the identification code at the corresponding position is the same as the target code.

[0134] After the third identifier is generated, the terminal device will be restarted according to the target test program. After the relevant setting program is executed, the fourth identifier will be generated. At this time, the identification code includes four identifiers. The identification code is checked. According to the above steps, it can be understood that the first three identifiers of the identification code are the same as the first three identifiers of the target code. The fourth identifier of the identification code is checked. If the fourth identifier code is 1, which indicates one hour of power-on operation, and the corresponding second identifier of the target code is 0, which indicates a successful power-on test, it indicates that the terminal device did not restart as required and perform the power-on test. Then, the self-test result of the terminal device failing to perform the aging test as required is output, and the aging test is stopped.

[0135] Only when the terminal equipment is powered on and runs for 4 hours and is powered off and restarted every two hours after the aging test, and the identification code 011011 that is the same as the target code is generated, the aging test is ended and the self-test result of the aging test success is output.

[0136] As a preferred embodiment, after each startup (restart) of the terminal device, before performing a power-on test, the identification code is also checked. If the verification result of the identification code indicates that the aging test is incomplete or the identification code does not exist, the terminal device is subjected to a power-on test. Otherwise, the verification result of the identification code is used as the self-test result of the terminal device. This step is to determine the progress of the aging test before the restart based on the identification code after the restart, thereby determining whether to continue the power-on test after the restart.

[0137] Furthermore, after the terminal device stops the aging test or the aging test is successfully completed, the self-test result of the terminal device is represented by the lighting of at least one indicator light, so that the tester can know the self-test result of the terminal device in the re-aging test only by observing the indicator light of the terminal device.

[0138] Exemplarily, as shown in Table 1, the PON terminal device of the present application includes four indicator lights, and the self-test results of the terminal device are indicated by the on and off of the four indicator lights.

[0139] Table 1 Comparison table of terminal equipment self-test results

[0140] Self-test results LED1 LED2 LED3 LED4 Result 1 Extinguished Extinguished Extinguished Extinguished Result 2 Constantly on Constantly on Constantly on Constantly on Result 3 Constantly on Extinguished Extinguished Extinguished Result 4 Extinguished Constantly on Extinguished Extinguished Result 5 Extinguished Extinguished Constantly on Extinguished Results 6 Constantly on Constantly on Extinguished Extinguished Results 7 Extinguished Extinguished Constantly on Constantly on

[0141] After the aging test is complete, the indicator lights begin to flash at set intervals based on the self-test results until the device is powered off. For example, if the self-test result is Result 1, indicating that the aging test is not completed, all four indicators on the terminal device will be off. If the self-test result is Result 2, indicating that the aging test is successful, all four indicators on the terminal device will light up.

[0142] When one or more indicator lights are constantly on, it means that the aging test has been completed and the results have been output. Pressing the button can exit the aging mode. In this embodiment, pressing the button when all the indicator lights are off indicates selecting the target code, and pressing the button when one or more indicator lights are constantly on indicates exiting the aging test mode.

[0143] If the terminal device has no indicator light or a limited number of indicator lights, if the terminal has a sound-emitting device, it can also be used to emit different sounds, issue voice broadcasts, or other methods to indicate the self-test result of the terminal device.

[0144] In one embodiment, if Figure 5 As shown, the terminal device self-test method in the aging test of the present application takes the terminal device running for one hour after power-on as an example, and includes the following steps.

[0145] Step S401: Determine whether the terminal device is in burn-in mode. In this embodiment, the determination of whether the device is in burn-in mode is based on the storage location of the burn-in log. If the burn-in log is in designated location 1, indicating that the device is in burn-in mode, the burn-in detection process continues with step S402. If the burn-in log is in location 2, the terminal device does not perform a power-on self-test.

[0146] Step S402: perform identification code verification.

[0147] Step S403, determining whether the identification code verification result is result 1; if so, executing step S404; if not, taking result 1 as the self-test result of the terminal device.

[0148] Step S404: perform power-on detection and write a new identifier to update the identifier code.

[0149] Step S405: perform identification code verification.

[0150] Step S406, determining whether the identification code verification result is result 1; if so, executing step S407; if not, taking result 1 as the self-test result of the terminal device.

[0151] Step S407, delay for one hour.

[0152] Step S408: Add a second identifier to the aging log.

[0153] Step S409: perform identification code verification.

[0154] Step S410, determining whether the identification code verification result is result 1; if so, executing step S411; if not, executing step S412;

[0155] Step S411: Determine whether the terminal device needs to be restarted. If so, wait for restart and execute step S401 after restart. If not, execute step S407. Whether restart is required is determined according to the target test program.

[0156] Step S412: Use result 1 as the self-test result of the terminal device, end the aging test, and display the self-test result.

[0157] It can be seen from the aging detection process that the identification code check and power-on detection are two sub-processes of the aging detection. The identification code check and power-on detection in this embodiment can be performed according to the above steps of the identification code check step and the power-on detection step.

[0158] The present application provides a method and apparatus for terminal device self-test during an aging test, wherein the terminal device responds to a set target test program to perform an aging test; the terminal device performs a power-on test during the aging test and generates a corresponding identification code; the terminal device verifies the identification code to obtain a test result, and uses the test result as a self-test result. The method implements a power-on test of the terminal device's status during the aging test, generates an identification code based on the test result, and verifies the identification code to determine whether the terminal device has any abnormalities during the aging test, as well as the specific problems that caused the abnormalities. For devices with normal aging tests, there is no need to connect to an external computer, and the indicator light can be used to determine whether the aging test is successful and whether the hardware module has faults, greatly improving production efficiency. For devices with abnormal aging tests, the aging log file can be viewed to determine the problems with the device and whether there is an abnormal restart, thereby enabling monitoring of abnormal restarts of terminal devices during aging tests.

[0159] like Figure 6 As shown, the present application also provides a device for self-testing a terminal device in an aging test, the device comprising:

[0160] an aging test module, configured to perform an aging test in response to a set target test program;

[0161] An identification code generation module, which is used for performing power-on detection on the terminal device during the aging test and generating a corresponding identification code;

[0162] A detection module is used for the terminal device to detect the identification code to obtain a detection result, and use the detection result as a self-detection result.

[0163] The terminal device performs power-on detection during the aging test, and generates a corresponding identification code, specifically including the following steps:

[0164] When the terminal device is performing the aging test, a power-on test is performed after each startup, and an identification is generated according to the result of the power-on test, and the identification is stored to form the identification code;

[0165] After the terminal device is started, if it is not restarted within a set time interval, a new identifier is additionally generated, and the new identifier is stored to update the identification code.

[0166] The identification includes a hardware fault identification. The steps of performing a power-on test after each startup, generating an identification based on the result of the power-on test, and storing the identification to form the identification code specifically include the following steps:

[0167] Generate a hardware fault identifier at the beginning of power-on detection, and detect the hardware after generating the hardware fault identifier;

[0168] If the hardware has no fault, rewriting the hardware fault flag into a power-on detection success flag, and storing the power-on detection success flag to form the identification code;

[0169] If the hardware fails, the power-on detection is stopped, and the hardware failure identification is stored to form the identification code.

[0170] Among them, the terminal equipment self-test device in the aging test is also used for:

[0171] After each identification is generated, the corresponding identification code is checked. If the check result of the corresponding identification code is that the aging test is not completed, the terminal device continues to perform power-on detection. Otherwise, the check result of the corresponding identification code is used as the self-test result of the terminal device and the aging test is stopped.

[0172] Wherein, after each startup of the terminal device, before performing a power-on detection, the following steps are also included:

[0173] The identification code is checked. If the check result of the identification code includes that the aging test is not completed or the identification code does not exist, a power-on test is performed on the terminal device. Otherwise, the check result of the identification code is used as the self-test result of the terminal device and the aging test is stopped.

[0174] The terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result, specifically including the following steps:

[0175] The terminal device determines whether there is a hardware fault identifier in the identification code. If so, the terminal device uses the hardware fault as the self-test result and stops the burn-in test. Otherwise, the terminal device compares the identification code with the target code corresponding to the target test program bit by bit and uses the comparison result as the self-test result of the terminal device.

[0176] The target code is stored in the memory of the terminal device.

[0177] The step of comparing the identification code with the target code corresponding to the target test program bit by bit and using the comparison result as the self-test result of the terminal device specifically includes the following steps:

[0178] Comparing the identification code and the target code bit by bit from front to back;

[0179] If the identification code in a corresponding position is a power-on detection success identifier and the target code is a device normal operation setting time identifier, an abnormal restart during the aging test is regarded as a self-test result and the aging test is stopped;

[0180] If the identification code in a corresponding position is a device normal operation setting time identifier and the target code is a power-on detection success identifier, failure to perform the aging test as required is regarded as a self-test result, and the aging test is stopped;

[0181] If the number of digits identified in the identification code is less than that of the target code, and the identification code and the target code in the corresponding positions are identical, then the aging test is deemed incomplete as a self-test result, and the aging test is continued;

[0182] If the number of digits identified in the identification code is the same as the number of digits in the target code, and the identification code and the target code in the corresponding positions are the same, the aging test is considered successful as a self-test result and the aging test is terminated.

[0183] Wherein, after the terminal device performs the aging test in response to the set target test program and before performing the power-on test and generating the corresponding identification code, the following steps are further included:

[0184] determining a current location of an aging log storing the identification code;

[0185] If the aging log is in the first position, it is determined that the terminal device is undergoing an aging test;

[0186] If the aging log is in the second location, the terminal device has not undergone aging testing;

[0187] When the aging log does not exist, the terminal device generates the aging log at the first location when performing the aging test, and transfers the aging log from the first location to the second location after the aging test is completed.

[0188] Among them, the terminal equipment self-test device in the aging test is also used for:

[0189] The self-test result of the terminal device is represented by the on and off of at least one indicator light.

[0190] It should be noted that those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules and units can refer to the corresponding processes in the aforementioned embodiments and will not be repeated here.

[0191] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or system comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or system. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or system comprising the element.

[0192] The serial numbers of the embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments. The above description is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in this application, and these modifications or replacements should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for self-testing a terminal device during an aging test, characterized in that: The following steps are involved: The terminal equipment responds to the set target test program and performs the aging test; When the terminal device is undergoing an aging test, it performs a power-on test and generates a corresponding identification code; The terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result; The terminal device performs power-on detection during the aging test, and generates a corresponding identification code, specifically including the following steps: When the terminal device is performing the aging test, a power-on test is performed after each startup, and an identification is generated according to the result of the power-on test, and the identification is stored to form the identification code; After the terminal device is started, if it is not restarted within the set time interval, a new identifier is additionally generated, and the new identifier is stored to update the identification code; The identification includes a hardware fault identification. The steps of performing a power-on test after each startup, generating an identification based on the result of the power-on test, and storing the identification to form the identification code specifically include the following steps: Generate a hardware fault identifier at the beginning of power-on detection, and detect the hardware after generating the hardware fault identifier; If the hardware has no fault, rewriting the hardware fault flag into a power-on detection success flag, and storing the power-on detection success flag to form the identification code; If the hardware fails, the power-on detection is stopped, and the hardware failure identification is stored to form the identification code; The method further comprises the following steps: After each identification is generated and stored to form the identification code, the corresponding identification code is checked. If the check result of the corresponding identification code is that the aging test is not completed, the terminal device continues to perform power-on detection. Otherwise, the check result of the corresponding identification code is used as the self-test result of the terminal device, and the aging test is stopped.

2. The terminal device self-test method in the aging test according to claim 1, characterized in that: After each startup of the terminal device, and before performing a power-on test, the following steps are also included: The identification code is checked. If the check result of the identification code includes that the aging test is not completed or the identification code does not exist, a power-on test is performed on the terminal device. Otherwise, the check result of the identification code is used as the self-test result of the terminal device and the aging test is stopped.

3. The terminal device self-test method in the aging test according to claim 1, characterized in that: The terminal device verifies the identification code to obtain a verification result, and uses the verification result as a self-test result, specifically comprising the following steps: The terminal device determines whether there is a hardware fault identifier in the identification code. If so, the terminal device uses the hardware fault as the self-test result and stops the burn-in test. Otherwise, the terminal device compares the identification code with the target code corresponding to the target test program bit by bit and uses the comparison result as the self-test result of the terminal device. The target code is stored in the memory of the terminal device.

4. The method for terminal device self-test in aging test according to claim 3, characterized in that: The step of comparing the identification code with the target code corresponding to the target test program bit by bit and using the comparison result as the self-test result of the terminal device specifically comprises the following steps: Comparing the identification code and the target code bit by bit from front to back; If the identification code in a corresponding position is a power-on detection success identifier and the target code is a device normal operation setting time identifier, an abnormal restart during the aging test is regarded as a self-test result and the aging test is stopped; If the identification code in a corresponding position is a device normal operation setting time identifier and the target code is a power-on detection success identifier, failure to perform the aging test as required is regarded as a self-test result, and the aging test is stopped; If the number of digits identified in the identification code is less than that of the target code, and the identification code and the target code in the corresponding positions are identical, then the aging test is deemed incomplete as a self-test result, and the aging test is continued; If the number of digits identified in the identification code is the same as the number of digits in the target code, and the identification code and the target code in the corresponding positions are the same, the aging test is considered successful as a self-test result and the aging test is terminated.

5. The method for terminal device self-test in aging test according to claim 1, characterized in that: After the terminal device performs the aging test in response to the set target test program, and before performing the power-on test and generating the corresponding identification code, the following steps are further included: determining a current location of an aging log for storing the identification code; If the aging log is in the first position, it is determined that the terminal device is undergoing an aging test; If the aging log is in the second location, the terminal device has not undergone aging testing; When the aging log does not exist, the terminal device generates the aging log at the first location when performing the aging test, and transfers the aging log from the first location to the second location after the aging test is completed.

6. The terminal device self-test method in the aging test according to claim 1, characterized in that: The terminal device indicates a self-test result of the terminal device by turning on or off at least one indicator light.

7. A terminal device self-test device in aging test, characterized in that: include: an aging test module, configured to perform an aging test in response to a set target test program; An identification code generation module, which is used for performing power-on detection on the terminal device during the aging test and generating a corresponding identification code; a detection module, configured for the terminal device to detect the identification code to obtain a detection result, and use the detection result as a self-test result; The identification code generation module is further configured to: When the terminal device is performing the aging test, a power-on test is performed after each startup, and an identification is generated according to the result of the power-on test, and the identification is stored to form the identification code; After the terminal device is started, if it is not restarted within the set time interval, a new identifier is additionally generated, and the new identifier is stored to update the identification code; The identification code generation module is further configured to: Generate a hardware fault identifier at the beginning of power-on detection, and detect the hardware after generating the hardware fault identifier; If the hardware has no fault, rewriting the hardware fault flag into a power-on detection success flag, and storing the power-on detection success flag to form the identification code; If the hardware fails, the power-on detection is stopped, and the hardware failure identification is stored to form the identification code; The device is also used for: After each identification is generated and stored to form the identification code, the corresponding identification code is checked. If the check result of the corresponding identification code is that the aging test is not completed, the terminal device continues to perform power-on detection. Otherwise, the check result of the corresponding identification code is used as the self-test result of the terminal device, and the aging test is stopped.

Images