Alarm configuration method and device for test engineering and electronic equipment

Abstract

This disclosure provides an alarm configuration method, apparatus, and electronic device for a test project. In response to an alarm configuration command, it determines the alarm type and alarm behavior parameters, whereby the alarm behavior parameters indicate the handling method when the configured alarm type is triggered. Based on a preset parameter mapping relationship and preset parameter writing rules, it verifies the alarm type and alarm behavior parameters to determine target alarm types and target alarm behavior parameters that meet the verification conditions. The preset parameter mapping relationship indicates the mapping rules that must be followed between the alarm type and the alarm behavior parameters. The target alarm type and target alarm behavior parameters are configured onto the test board. Therefore, the configuration parameters can be verified promptly upon receipt, ensuring the validity of the alarm configuration parameters sent to the test board.

Description

Technical Field

[0001] This disclosure relates to alarm processing technology, and in particular to an alarm configuration method, apparatus and electronic equipment for a test project. Background Technology

[0002] To ensure the stability of the testing process and the accuracy of the test results, the testing system alerts the user through alarms for various errors or other unexpected states during the testing of the chip under test.

[0003] In related technologies, alarm information is typically set and then directly sent to the test board to handle alarms and anomalies that occur during testing. However, if the alarm information is set incorrectly, it will be difficult to execute the correct alarm handling behavior, resulting in reduced debugging and operation efficiency of the test project. Summary of the Invention

[0004] This disclosure provides an alarm configuration method, apparatus, and electronic device for a test project, which can solve the above-mentioned technical problems to a certain extent.

[0005] One aspect of this disclosure provides an alarm configuration method for a test project, comprising: In response to an alarm configuration command, the alarm type and alarm behavior parameters are determined, wherein the alarm behavior parameters are used to indicate the processing method when the alarm type is triggered; Based on the preset parameter mapping relationship and preset parameter writing rules, the configured alarm type and the configured alarm behavior parameter are verified to determine the target alarm type and target alarm behavior parameter that meet the verification conditions. The preset parameter mapping relationship is used to indicate the mapping rules that need to be followed between the alarm type and the alarm behavior parameter. Configure the target alarm type and the target alarm behavior parameters onto the test board.

[0006] Another aspect of this disclosure provides an alarm configuration device for a test project, comprising: The parameter determination module is used to determine the configuration alarm type and configuration alarm behavior parameters in response to the alarm configuration command. The configuration alarm behavior parameters are used to indicate the processing method when the configuration alarm type is triggered. The parameter verification module is used to verify the configured alarm type and the configured alarm behavior parameter based on the preset parameter mapping relationship and the preset parameter writing rule, and to determine the target alarm type and target alarm behavior parameter that meet the verification conditions. The preset parameter mapping relationship is used to indicate the mapping rule that must be followed between the alarm type and the alarm behavior parameter. The parameter distribution module is used to configure the target alarm type and the target alarm behavior parameters to the test board.

[0007] Another aspect of this disclosure provides an electronic device, including: Memory, used to store computer programs; A processor is configured to execute a computer program stored in the memory, and when the computer program is executed, to implement the alarm configuration method for the test project described in any of the above embodiments of this disclosure.

[0008] In this embodiment of the present disclosure, after receiving the alarm configuration command, the alarm type and the corresponding alarm behavior parameters are obtained. The alarm type and the corresponding alarm behavior parameters are then verified based on the preset parameter mapping relationship and the preset parameter writing rules to obtain the target alarm type and target alarm behavior parameters that meet the verification conditions. These are then sent to the test board. Thus, the configuration parameters can be verified in a timely manner after receiving the alarm configuration parameters, so that users can handle incorrect configurations in a timely manner, ensuring the validity of the alarm configuration parameters and helping to improve the debugging and operation efficiency of the test project.

[0009] In addition, by verifying the configuration alarm type and the corresponding configuration alarm behavior parameter based on the preset parameter mapping relationship and preset parameter writing rules, it can be ensured that the mapping relationship between the determined target alarm type and the target alarm behavior parameter is valid, and that the parameters themselves are also valid, which can improve the reliability of alarm configuration.

[0010] The technical solutions of this disclosure will be further described in detail below with reference to the accompanying drawings and embodiments. Attached Figure Description

[0011] The accompanying drawings, which form part of this specification, illustrate embodiments of this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0012] This disclosure will become clearer with reference to the accompanying drawings and the following detailed description, wherein: Figure 1 A flowchart illustrating an alarm configuration method for a test project provided as an exemplary embodiment of this disclosure; Figure 2 A flowchart of a parameter verification process provided as an exemplary embodiment of this disclosure; Figure 3 A flowchart of a mapping relationship verification process provided as an exemplary embodiment of this disclosure; Figure 4 A flowchart of a parameter validity verification process provided as an exemplary embodiment of this disclosure; Figure 5 A flowchart of the process for determining a target bin value is provided as an exemplary embodiment of this disclosure; Figure 6 A flowchart illustrating the process of determining target annotation information provided in an exemplary embodiment of this disclosure; Figure 7 An interactive diagram illustrating the parameter configuration and verification process provided in an exemplary embodiment of this disclosure; Figure 8 This is a flowchart illustrating an exemplary embodiment of the alarm configuration parameter verification process disclosed herein; Figure 9 A flowchart of a process for determining updated target parameters provided as an exemplary embodiment of this disclosure; Figure 10 A flowchart of an update parameter verification process provided as an exemplary embodiment of this disclosure; Figure 11 This is a schematic diagram of the structure of an alarm configuration device for a test project provided in an exemplary embodiment of this disclosure; Figure 12 This is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this disclosure. Detailed Implementation

[0013] Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present disclosure.

[0014] Those skilled in the art will understand that the terms "first," "second," etc., in the embodiments of this disclosure are only used to distinguish different steps, devices, or modules, and do not represent any specific technical meaning, nor do they indicate a necessary logical order between them.

[0015] It should also be understood that in the embodiments disclosed herein, "a plurality of" may refer to two or more, and "at least one" may refer to one, two or more.

[0016] It should also be understood that any component, data or structure mentioned in the embodiments of this disclosure can generally be understood as one or more unless expressly defined or given to the contrary in the context.

[0017] Furthermore, the term "and / or" in this disclosure is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this disclosure generally indicates that the preceding and following related objects have an "or" relationship.

[0018] It should also be understood that the description of the various embodiments in this disclosure emphasizes the differences between the various embodiments, and the similarities or similarities can be referred to each other. For the sake of brevity, they will not be described in detail.

[0019] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0020] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use.

[0021] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0022] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0023] This disclosure provides an alarm configuration method for a test process, which can promptly verify the configured parameters after receiving a configuration command for an alarm, ensuring the validity of the configuration parameters. The method provided in this disclosure can be applied to the configuration of a test process for testing semiconductor devices, where the semiconductor devices can be chips, wafers, etc.

[0024] like Figure 1 As shown, a flowchart of an alarm configuration method for a test project provided by an exemplary embodiment of this disclosure is illustrated. The process may include steps 110-130: Step 110: In response to the alarm configuration command, determine the alarm type and configure the alarm behavior parameters.

[0025] In this embodiment of the disclosure, the alarm configuration command is used to instruct the configuration of alarm processing parameters. Optionally, the alarm processing parameters may include an alarm type and a corresponding alarm behavior parameter. The alarm behavior parameter is used to indicate the processing method when an alarm corresponding to the alarm type is triggered, such as ignoring it or stopping the test. Configuring the alarm type and configuring the alarm behavior parameter are for the currently edited alarm information to be verified.

[0026] In one possible implementation, an alarm configuration interface can be set in the user interface, allowing users to configure alarms based on this interface. Optionally, the alarm configuration interface can include configuration items for configuring alarm processing parameters, such as alarm type configuration items and alarm behavior parameter configuration items. Upon detecting a configuration operation on an alarm configuration item in the alarm configuration interface, it is determined that an alarm configuration command has been received.

[0027] In another possible implementation, users can configure alarm handling parameters by calling a user interface (such as an API). When the user interface receives an alarm configuration request, it determines that an alarm configuration instruction has been received.

[0028] Upon receiving an alarm configuration command, the system can obtain the configured alarm type and configured alarm behavior parameters included in the command. The configured alarm behavior parameters indicate the handling method when the configured alarm type is triggered. Optionally, the configured alarm type may include one configured alarm type, and the configured alarm behavior parameters may include the alarm behavior parameters corresponding to the configured alarm type. Alternatively, the configured alarm type may include multiple configured alarm types, and the configured alarm behavior parameters may include the alarm behavior parameters corresponding to each of the multiple alarm types.

[0029] Step 120: Based on the preset parameter mapping relationship and preset parameter writing rules, verify the configured alarm type and configured alarm behavior parameters to determine the target alarm type and target alarm behavior parameters that meet the verification conditions.

[0030] The preset parameter mapping relationship indicates the mapping rules that must be followed between alarm types and alarm behavior parameters. Optionally, the preset parameter mapping relationship may include mapping relationships between multiple alarm types and multiple alarm behavior parameters. In one possible implementation, verifying the configured alarm types and configured alarm behavior parameters based on the preset parameter mapping relationship can verify the mapping relationship between the configured alarm types and configured alarm behavior parameters, and determine whether the mapping relationship formed between the configured alarm types and configured alarm behavior parameters conforms to the preset parameter mapping relationship. It is understood that, based on the preset parameter mapping relationship, an alarm type may correspond to one or more alarm behavior parameters, indicating one or more alarm handling actions that need to be taken when the alarm type is triggered. Of course, an alarm type may also not correspond to any alarm behavior parameters, indicating that no alarm handling action needs to be taken when the alarm type is triggered.

[0031] Preset parameter writing rules are used to indicate the parameter configuration rules that alarm configuration parameters themselves must follow. Optionally, the preset parameter writing rules may include alarm type writing rules and alarm behavior parameter writing rules. Alarm type writing rules indicate the parameter configuration rules that the configured alarm type itself must satisfy. The configured alarm type can be validated based on the alarm type writing rules to determine whether it meets the rules. Alarm behavior parameter writing rules indicate the parameter configuration rules that the configured alarm behavior parameters themselves must satisfy. The configured alarm behavior parameters can be validated based on the alarm behavior parameter writing rules to determine whether it meets the rules.

[0032] Optionally, the verification conditions refer to the configuration conditions indicated by the preset parameter mapping relationship and the preset parameter writing rules. In one possible implementation, after verifying the configured alarm type and configured alarm behavior parameters based on the preset parameter mapping relationship and the preset parameter writing rules, if they conform to the preset parameter mapping relationship and the preset parameter writing rules, it is determined that the configured alarm type and configured alarm behavior parameters meet the verification conditions. The configured alarm type can then be determined as the target alarm type, and the configured alarm behavior parameters can be determined as the target alarm behavior parameters. The target alarm behavior parameters are used to indicate the processing method when the alarm corresponding to the target alarm type is triggered.

[0033] Optionally, if multiple sets of configuration alarm types and configuration alarm behavior parameters are included, each set of configuration alarm types and configuration alarm behavior parameters is verified based on preset parameter mapping rules and preset parameter writing rules. If a set of configuration alarm types and configuration alarm behavior parameters passes the verification, then that set of configuration alarm types and configuration alarm behavior parameters is determined as the target alarm type and target alarm behavior parameter, respectively.

[0034] Step 130: Configure the target alarm type and target alarm behavior parameters to the test board.

[0035] In one possible implementation, after determining the target alarm type and target alarm behavior parameters, the target alarm type and target alarm behavior parameters can be configured on the test board, so that when the test board detects an alarm corresponding to the target alarm type, it performs alarm processing based on the target alarm behavior processing parameters.

[0036] Optionally, the target alarm type and target alarm behavior parameters can be sent to the driver layer and configured on the test board through the driver layer.

[0037] In this embodiment of the disclosure, after receiving the alarm configuration command, the alarm type and corresponding alarm behavior parameters are obtained. Based on the preset parameter mapping relationship and preset parameter writing rules, the alarm type and corresponding alarm behavior parameters are verified to obtain the target alarm type and target alarm behavior parameters that meet the verification conditions. These are then sent to the test board. Thus, the configuration parameters can be verified in a timely manner after receiving the alarm configuration parameters, so that users can handle incorrect configurations in a timely manner. This ensures that the alarm configuration parameters are verified before being sent to the driver module, thus ensuring the validity of the alarm configuration parameters sent to the test board and helping to improve the debugging and operation efficiency of the test project.

[0038] In addition, by verifying the configured alarm type and the corresponding configured alarm behavior parameters based on the preset parameter mapping relationship and preset parameter writing rules, it can be ensured that the mapping relationship between the determined target alarm type and the target alarm behavior parameters is valid, and that the parameters themselves are also valid, thus ensuring the validity of the alarm configuration.

[0039] In one possible implementation, such as Figure 2 As shown, the execution process of step 120 above may include the following steps 1201-1203: Step 1201: Based on the preset parameter mapping relationship, verify the mapping relationship between the configured alarm type and the configured alarm behavior parameters.

[0040] The mapping relationship verification is used to check whether the mapping relationship between the configured alarm type and the configured alarm behavior parameters meets the preset parameter mapping relationship. Optionally, the preset parameter mapping relationship includes parameter mapping relationships corresponding to multiple alarm types, and the parameter mapping relationship corresponding to the alarm type is used to indicate the alarm behavior parameters that are allowed to be configured for that alarm type.

[0041] In one possible implementation, the parameter mapping relationship corresponding to the configured alarm type can be obtained from the preset parameter mapping relationship, and the mapping relationship between the configured alarm type and the configured alarm behavior parameter can be verified based on the parameter mapping relationship corresponding to the configured alarm type.

[0042] Step 1202: Based on the preset parameter writing rules, perform parameter validity verification on the configured alarm type and configured alarm behavior parameters.

[0043] Parameter validity validation is used to verify the validity of the configured alarm type and the configured alarm behavior parameters themselves. Optionally, the preset parameter writing rules may include one or more parameter configuration rules that the alarm configuration parameters must follow during configuration. For example, parameter configuration rules may include at least one of data configuration rules, duplicate configuration rules, and type configuration rules. Data configuration rules are used to verify whether the alarm configuration parameters fall within the scope of preset parameter validity; duplicate configuration rules are used to verify whether the alarm configuration parameters are configured repeatedly; and type configuration rules are used to verify whether the parameter type of the alarm configuration parameters is valid.

[0044] In one possible implementation, different alarm configuration parameters can be configured with corresponding parameter writing rules, and the parameter writing rules for different alarm configuration parameters include different parameter configuration rules. For example, alarm type writing rules may include data configuration rules and repeat configuration rules. Alarm behavior parameter writing rules may include data configuration rules.

[0045] For configuring alarm types, validity checks can be performed on the alarm types based on one or more parameter configuration rules included in the alarm type writing rules, using one or more dimensions of validation. For configuring alarm behavior parameters, validity checks can be performed on the alarm behavior parameters based on one or more parameter configuration rules included in the alarm behavior parameter writing rules, using one or more dimensions of validation.

[0046] Step 1203: If the verification conditions for mapping relationship verification and parameter validity verification are met, determine the configured alarm type as the target alarm type and determine the configured alarm behavior parameter as the target alarm behavior parameter.

[0047] In one possible implementation, during the mapping relationship verification process, if it is determined that the mapping relationship between the configured alarm type and the configured alarm behavior parameter conforms to the preset parameter mapping rules, the verification condition for the mapping relationship verification is determined to be met. During the parameter validity verification process, if it is determined that both the configured alarm type and the configured alarm behavior parameter conform to the preset parameter writing rules, the verification condition for the parameter validity verification is determined to be met.

[0048] If the verification conditions of mapping relationship verification and parameter validity verification are met, and it is determined that both the configuration alarm type and the configuration alarm behavior parameter are valid, and the mapping relationship between them is also valid, then the configuration alarm type can be determined as the target alarm type and the configuration alarm behavior parameter can be determined as the target alarm behavior parameter, and the mapping relationship between the target alarm type and the target alarm behavior parameter can be constructed.

[0049] In this embodiment, for configuring alarm types and configuring alarm behavior parameters, mapping relationship verification and parameter validity verification can be performed respectively to verify both the parameters themselves and the mapping relationship between them, ensuring the validity of the parameters themselves and the resulting mapping relationship, thereby helping to ensure the effectiveness of alarm processing.

[0050] In one possible implementation, the preset parameter mapping relationship includes a mapping relationship between each alarm type and multiple preset alarm behavior parameters. For example, for alarm type A, it may include a mapping relationship between alarm type A and behavior parameters A and B. For alarm type B, it may include a mapping relationship between alarm type B and behavior parameters B and C.

[0051] like Figure 3 As shown, the execution process of step 1201 above may include the following steps 1210-1211: Step 1210: Verify whether there are any configured alarm behavior parameters among the multiple preset alarm behavior parameters corresponding to the configured alarm type.

[0052] Based on the preset parameter mapping relationship, when validating the configuration alarm type and configuration alarm behavior parameters, multiple preset alarm behavior parameters corresponding to the configuration alarm type can be obtained from the preset parameter mapping relationship, and it can be determined whether the multiple preset alarm behavior parameters exist as configuration alarm behavior parameters.

[0053] For example, if the alarm type is configured as alarm type A, the corresponding preset alarm behavior parameters include behavior parameter A and behavior parameter B. It is possible to verify whether the configured alarm behavior parameter is either behavior parameter A or behavior parameter B.

[0054] Step 1211: If it exists, determine whether the configured alarm type and configured alarm behavior parameters meet the verification conditions of the mapping relationship verification.

[0055] If a configuration alarm behavior parameter exists among the multiple preset alarm behavior parameters corresponding to the configuration alarm type, it is determined that the configuration alarm type and the configuration alarm behavior parameter satisfy the preset parameter mapping relationship, that is, the verification condition is met.

[0056] In one possible implementation, if no alarm behavior parameter is configured among the multiple preset alarm behavior parameters, it is determined that the configured alarm type and the configured alarm behavior parameter do not meet the verification conditions of the mapping relationship verification. A prompt message indicating that the mapping relationship configuration is invalid can be generated so that the user can modify the configured alarm behavior parameter in a timely manner.

[0057] In this embodiment, a mapping relationship between each alarm type and multiple preset alarm behavior parameters can be preset, and the mapping relationship between the configured alarm type and the configured alarm behavior parameters can be verified based on the preset mapping relationship to ensure that the alarm behavior parameters configured for the alarm type are valid and can be executed normally during the alarm processing, which helps to ensure the effectiveness and accuracy of alarm processing.

[0058] In one possible implementation, such as Figure 4 As shown, the execution process of step 1202 above may include the following steps 1220-1221: Step 1220: Verify whether the configured alarm type and configured alarm behavior parameters exist in the preset parameter list.

[0059] In one possible implementation, the preset parameter writing rule includes a preset parameter list, which includes preset valid parameters. The validity of alarm configuration parameters can be verified based on the preset parameter list.

[0060] Optionally, the preset parameter list includes multiple preset configuration alarm types and multiple preset configuration alarm behavior parameters. The preset configuration alarm types are the valid alarm types that are allowed to be configured, and the preset configuration alarm behavior parameters are the valid alarm behavior parameters that are allowed to be configured.

[0061] After determining the configured alarm type and configured alarm behavior parameters, it is possible to verify whether multiple preset configured alarm types contain the configured alarm type, and whether multiple preset configured alarm behavior parameters contain the configured alarm behavior parameters. For example, if multiple preset configured alarm types include alarm type A, alarm type B, and alarm type C, it is possible to verify whether the configured alarm type is any one of alarm type A, alarm type B, and alarm type C.

[0062] Step 1221: If it exists, then determine whether the configured alarm type and configured alarm behavior parameters meet the verification conditions for parameter validity verification.

[0063] If a configured alarm type exists among multiple preset alarm types, the configured alarm type is determined to be valid, satisfying the parameter validity verification conditions. If a configured alarm behavior parameter exists among multiple preset alarm behavior parameters, the configured alarm behavior parameter is determined to be valid, satisfying the parameter validity verification conditions.

[0064] If no alarm type is configured among multiple preset alarm types, it is determined that the alarm type is invalid and does not meet the validation conditions for parameter validity. A prompt message indicating that the alarm type is invalid can be generated so that the user can modify the configured alarm type in time.

[0065] If no alarm behavior parameter is found among the multiple preset alarm behavior parameters, it is determined that the alarm behavior parameter is invalid and does not meet the validation conditions for parameter validity. A prompt message indicating that the alarm behavior parameter is invalid can be generated so that the user can modify the configured alarm behavior parameter in a timely manner.

[0066] In this embodiment, the configuration alarm type and configuration alarm behavior parameters can be verified based on a preset parameter list to determine whether the configuration alarm type and configuration alarm behavior parameters belong to the preset valid parameters, so as to ensure the validity of the configuration parameters themselves.

[0067] In one possible implementation, the preset parameter writing rules include a duplicate configuration rule, which is used to indicate that the configuration alarm type duplicate configuration is invalid.

[0068] Optionally, in response to multiple alarm configuration commands, multiple alarm types can be determined. Optionally, each alarm configuration command may include a corresponding alarm type. When multiple alarm configuration commands are received, multiple alarm types can be determined. For example, when a user configures alarms based on the alarm configuration interface, multiple alarm types can be configured in batches. Each of the batch-configured alarm types generates its own corresponding alarm configuration command, and the corresponding alarm type can be determined based on these multiple commands.

[0069] When multiple configuration alarm types are determined, the duplicate configuration rules indicated by the preset parameter writing rules can be used to determine whether any two configuration alarm types are duplicates. If they are not duplicates, the configuration alarm types meet the validity verification conditions.

[0070] If two alarm types are configured to be duplicated, and it is determined that the duplicate alarm type does not meet the verification conditions, a message indicating that the alarm type is duplicated can be generated, instructing the user to modify the duplicate alarm type.

[0071] In this embodiment, the alarm type configuration can be repeatedly verified to avoid the same alarm type being configured repeatedly. This can prevent different processing methods from being configured for the same alarm type, ensuring the uniqueness of the alarm processing behavior for the same alarm type and thus avoiding alarm processing errors.

[0072] In one possible implementation, the determined target alarm type and target alarm behavior parameters can be distributed to the test board via incremental loading.

[0073] After determining the configuration alarm type and configuration alarm behavior parameters, you can first verify the loading status of the configuration alarm type and configuration alarm behavior parameters. The loading status is used to indicate whether the configuration alarm type and configuration alarm behavior parameters have been loaded. The loading status includes a loaded status and an unloaded status. The loaded status indicates that the parameter has been successfully loaded during the historical loading process, and the unloaded status indicates that the parameter has not been loaded during the historical loading process.

[0074] If the loading status is "Loaded", it means that the configured alarm type and configured alarm behavior parameters meet the verification conditions. Specifically, if the status is "Loaded", it means that the configured alarm type and configured alarm behavior parameters have been successfully loaded, that is, they have been verified and the verification conditions are met.

[0075] If the loading status is not loaded, the configuration alarm type and configuration alarm behavior parameters need to be verified based on the preset parameter mapping relationship and preset parameter writing rules.

[0076] In this embodiment, the loaded alarm types and alarm behavior parameters can be directly determined to meet the verification conditions, avoiding repeated verification processes and helping to improve verification efficiency.

[0077] In one possible implementation, the alarm configuration parameters also include bin values, where the bin values ​​indicate the group to which the chip under test should be assigned when executing alarm behavior parameters. For example... Figure 5 As shown, the alarm configuration method for the test project also includes the following steps 210-220: Step 210: In response to the alarm configuration command, determine the configuration bin value.

[0078] Upon receiving the alarm configuration command, the configuration bin value included in the alarm configuration command can be determined. The configuration bin value is used to indicate the group that the chip under test needs to be assigned when the alarm behavior parameters configured in the alarm configuration command are executed.

[0079] Step 220: Based on the preset parameter writing rules, verify the configuration bin value to determine the target bin value corresponding to the target alarm behavior parameter.

[0080] Optionally, the preset parameter writing rules include the valid range of bin values. Based on this range, the rules can be used to verify whether the configured bin value is a valid integer within that range. For example, the valid range of bin values ​​can be 1-32767. When verifying the configured bin value, it can be determined whether it is a valid integer within 1-32767. If it is a valid integer within this range, the configured bin value is deemed valid and meets the verification condition.

[0081] Optionally, for different bin values, different grouping types can be preset. The grouping type of a bin value can include failure type and pass type. Since triggering an alarm indicates an anomaly in the test of the chip under test, its configured bin value should belong to the failure type bin value. In one possible implementation, the preset parameter writing rule indicates the bin value corresponding to the failure type. For the configured bin value, it can be verified whether the configured bin value belongs to the bin value corresponding to the failure type. If it does, the configured bin value is determined to be valid and meets the verification condition.

[0082] In one possible implementation, the configuration bin value can be first verified based on the valid range of the bin value. If it is determined that the configuration bin value belongs to the valid range of the bin value, it is verified whether there is a configuration bin value among the preset failure type bin values. If there is a configuration bin value, it is determined that the configuration bin value meets the verification condition.

[0083] In one possible implementation, if the configuration bin value is not within the valid range of bin values, or if the configuration bin value is not the bin value corresponding to the failure type, it is determined that the configuration bin value does not meet the verification conditions, and an invalid configuration bin value prompt message can be generated to prompt the user.

[0084] If the configuration bin value meets the verification conditions, the configuration bin value can be determined as the target bin value. The target bin value is used to indicate the group that the chip under test needs to be assigned when executing the target alarm behavior parameters.

[0085] In this embodiment, the configured bin value can be verified based on the preset parameter writing rules to ensure the validity of the configured bin value. The verified target bin value can indicate the group that the chip under test should be assigned when executing the target alarm behavior parameter, so that the chip under test can be accurately binned and the binning accuracy can be improved.

[0086] In one possible implementation, the alarm configuration parameters also include comments. For example... Figure 6 As shown, the alarm configuration method for the test project also includes the following steps 310-320: Step 310: In response to the alarm configuration command, determine the configuration remarks information.

[0087] Upon receiving the alarm configuration command, the configuration remarks information in the alarm configuration command can be determined. The configuration remarks information is used to indicate the alarm remarks generated when the alarm is triggered. For example, it may include the cause of the alarm and the time of the alarm.

[0088] Step 320: Based on the preset parameter writing rules, verify the configuration remarks information to determine the target remarks information corresponding to the target alarm type.

[0089] Optionally, the preset parameter writing rules include the remark information writing rules. The configuration remark information can be verified based on the remark information writing rules. If the configuration remark information meets the remark information writing rules, it is determined that the configuration remark information meets the verification conditions, and it can be determined that the configuration remark information is the target remark information corresponding to the target alarm type.

[0090] For example, the rules for writing notes can include pre-set notes. If the configured notes belong to the pre-set notes, then the configured notes are determined to meet the verification conditions.

[0091] In this embodiment, corresponding remarks can be set for alarm types, and the configuration remarks are verified based on preset parameter writing rules to ensure the validity of the configuration remarks.

[0092] In one possible implementation, the user can configure alarms based on the alarm configuration interface, which can be a newly added user interaction interface, or it can be a sub-interface set in an existing user interaction interface. This embodiment does not limit this.

[0093] Optionally, the alarm configuration interface may include alarm type configuration items, behavior parameter configuration items, bin value configuration items, and remarks information configuration items. Optionally, configuration items may include preset options, which users can use to configure the system. Alternatively, configuration items may be content edit boxes, allowing users to customize and edit the configuration content.

[0094] In one example, the alarm type configuration item includes preset alarm type options, from which the user can select. The selected alarm type can then be designated as the configured alarm type. The behavior parameter configuration item includes preset behavior parameter options, from which the user can select. The selected alarm behavior parameter can then be designated as the configured alarm behavior parameter.

[0095] In one possible implementation, default alarm behavior parameters can be preset for different alarm types. Upon receiving a configuration operation for an alarm type, the corresponding default alarm behavior parameters can be obtained based on the configured alarm type and displayed in the behavior parameter configuration item to improve configuration efficiency. Users can modify the displayed default alarm behavior parameters based on the behavior parameter configuration item to configure the desired alarm behavior parameters.

[0096] In one example, the bin value configuration item and the remarks information configuration item can be content editing boxes. Users can configure the bin value in the bin value content editing box and the remarks information in the remarks information editing box. The bin value edited in the bin value content editing box can be determined as the configured bin value, and the remarks information edited in the remarks information editing box can be determined as the configured remarks information.

[0097] In one possible implementation, after determining the configuration alarm type, configuration alarm behavior parameters, configuration bin values, and configuration remarks, the configuration parameters can be verified in real time. If the verification passes, the configuration parameters can be used for alarm processing. If any configuration parameter fails verification, an anomaly mark can be made in the corresponding configuration item on the alarm configuration interface, allowing the user to modify the corresponding configuration parameter promptly. For example, when it is determined that the configuration alarm type is invalid, the configuration alarm type displayed in the alarm type configuration item can be marked as invalid, allowing the user to intuitively understand that the configuration parameter is invalid. When it is determined that the mapping relationship between the configuration alarm type and the configuration alarm behavior parameters is invalid, the configuration alarm type displayed in the alarm type configuration item and the configuration alarm behavior parameters displayed in the behavior parameter configuration item can be marked as invalid, allowing the user to intuitively understand that the mapping relationship configuration is invalid. Optionally, the anomaly mark can be a colored mark, text mark, pattern mark, etc., which is not limited in this embodiment.

[0098] like Figure 7As shown, during parameter configuration, alarm configuration operations can be performed in the alarm configuration interface. Based on the received alarm configuration operations, the alarm configuration interface determines the alarm configuration parameters (including alarm type, alarm behavior parameters, bin values, and remarks). Then, the alarm configuration parameters are sent to the middle layer. The middle layer can forward the alarm configuration parameters to the data layer, which stores the alarm configuration parameters in memory and then sends a successful configuration notification to the middle layer. Upon receiving the successful configuration notification, the middle layer can send a parameter verification command to the data layer. The data layer verifies the stored alarm configuration parameters and returns the verification result to the middle layer. If the verification result indicates that there are alarm configuration parameters that failed verification, it can return corresponding error information to the alarm configuration interface. The alarm configuration interface parses the error information, obtains the abnormal configuration parameters, and renders the alarm configuration interface based on the abnormal configuration parameters, marking the abnormal configuration parameters to remind the user to modify them promptly.

[0099] In one possible implementation, such as Figure 8 As shown, the verification process for alarm configuration parameters in the test project may include the following steps: Step 410: In response to the alarm configuration command, determine the alarm configuration parameters.

[0100] Step 420: Initiate the verification of alarm configuration parameters.

[0101] Step 430: Determine whether the configured alarm type is valid. If yes, proceed to step 440; otherwise, proceed to step 450.

[0102] Step 440: Determine if the configured alarm type is duplicated. If yes, proceed to step 450; otherwise, proceed to step 460.

[0103] Step 450: Mark the alarm types as abnormal.

[0104] Step 460: Determine whether the configured alarm behavior parameters are in a loaded state. If yes, proceed to step 4100; otherwise, proceed to step 470.

[0105] Step 470: Determine whether the configured alarm behavior parameters are valid. If yes, proceed to step 480; otherwise, proceed to step 490.

[0106] Step 480: Determine whether the mapping relationship between the configured alarm type and the configured alarm behavior parameters is valid. If yes, proceed to step 4100; otherwise, proceed to step 490.

[0107] Step 490: Mark the configuration alarm behavior parameters as abnormal.

[0108] Step 4100: Determine if the configuration bin value is empty. If yes, end the process; otherwise, proceed to step 4110.

[0109] Step 4110: Determine whether the configured bin value is a valid integer within the preset valid range. If yes, proceed to step 4120; otherwise, proceed to step 4130.

[0110] Step 4120: Determine whether the configured bin value is a bin value of the failure type. If yes, end; otherwise, proceed to step 4130.

[0111] Step 4130: Mark the configuration bin value as abnormal.

[0112] The execution process of steps 410-4130 can be referred to the above embodiments, and will not be repeated here.

[0113] In one possible implementation, after configuring the target alarm type and target alarm behavior parameters to the test board, the user can also call the user interface to update the configured alarm configuration parameters, such as... Figure 9 As shown, the process may include the following steps: Step 510: In response to the user interface receiving a parameter update request, determine the updated parameters.

[0114] When the user interface receives a parameter update request, it can parse the request to obtain the updated parameters. These updated parameters include updated alarm behavior parameters and / or updated bin values. The updated parameters can be specific to a target alarm type, used to update the target alarm behavior parameters and / or target bin values ​​corresponding to that type.

[0115] Step 520: Based on the preset parameter mapping relationship and preset parameter writing rules, the updated parameters are verified to determine the updated target parameters that meet the verification conditions.

[0116] In cases where the updated parameters include updated alarm behavior parameters, the validity of the updated alarm behavior parameters can be verified based on preset parameter writing rules, and the mapping relationship between the target alarm type and the updated alarm behavior parameters can be verified based on preset parameter mapping relationships. If the updated alarm behavior parameters meet the verification conditions, the updated alarm behavior parameters are determined as the updated target alarm behavior parameters, and the target alarm behavior parameters corresponding to the target alarm type in the test board are updated based on the updated target alarm behavior parameters.

[0117] When updating parameters include updating bin values, the updated bin values ​​can be verified based on preset parameter writing rules. If the updated bin values ​​meet the verification conditions, the updated bin values ​​are determined as the updated target bin values, and the target bin values ​​corresponding to the target alarm type are updated based on the updated target bin values.

[0118] The specific method for verifying the updated parameters based on the preset parameter mapping relationship and preset parameter writing rules can be referred to the implementation method for verifying alarm configuration parameters based on the preset parameter mapping relationship and preset parameter writing rules in the above embodiments, and will not be repeated here.

[0119] In this embodiment, the update parameters included in the parameter update request based on the user interface can be validated to ensure the validity of the update parameters.

[0120] In one possible implementation, the updated target parameter includes the updated bin value. Figure 9 Based on the example, after determining the updated target parameters, the following steps can also be performed: Step 530: Verify whether the bin value anomaly classification rules have been set in the interface parameters of the user interface.

[0121] In current testing technologies, alarms are typically only reported as errors without further detailed classification. Therefore, further confirmation of the error type is required, resulting in low efficiency in error handling. This application uses bin value anomaly classification rules, including alarm anomaly classification and non-alarm anomaly classification. Different bin values ​​can be pre-defined with corresponding grouping types. Bin values ​​belonging to the failure type can be further divided into bin values ​​corresponding to alarm anomaly classifications (failbin) and bin values ​​corresponding to non-alarm anomaly classifications (Errorbin). The bin values ​​corresponding to alarm anomaly classifications indicate the group the chip under test (DUT) should be assigned to when an alarm is triggered, while the bin values ​​corresponding to non-alarm anomaly classifications indicate the group the DUT should be assigned to when other anomalies besides alarms are triggered during testing.

[0122] Step 540: If so, the updated bin value will be determined as the alarm anomaly category.

[0123] In one possible scenario, if a bin value anomaly classification rule has been set, and it can be determined that the updated bin value will be used to indicate the alarm anomaly classification.

[0124] In this embodiment, by setting alarm anomalies as a separate anomaly category, timely responses and processing actions can be performed when alarms are triggered in the test process, which effectively improves the efficiency of alarm anomaly handling and thus improves test efficiency.

[0125] In one possible implementation, such as Figure 10 As shown, the verification process for the updated parameters may include the following steps: Step 610: In response to the parameter update request, determine the update alarm behavior parameters and update the bin value.

[0126] Step 620: Verify whether the updated alarm behavior parameters meet the verification conditions. If yes, proceed to step 630; otherwise, proceed to step 640.

[0127] Step 630: Update the alarm behavior parameters and store them in the alarm behavior parameter cache.

[0128] Step 640: Record abnormal behavior parameters and output error logs.

[0129] Step 650: Verify whether the updated bin value meets the verification conditions. If yes, proceed to step 660; otherwise, proceed to step 670.

[0130] Step 660: Store the updated bin value into the alarm bin value cache.

[0131] Step 670: Record the abnormal information of the bin value and output the error log.

[0132] Step 680: Check if the interface parameters are set incorrectly. If yes, proceed to step 61300; otherwise, proceed to step 690.

[0133] In cases where the interface parameter settings are incorrect, a sub-bin value corresponding to Errorbin can be set for the chip under test to indicate the non-alarm anomaly classification.

[0134] Step 690: Determine if the cached data is not empty. If yes, proceed to step 6100; otherwise, proceed to step 6110.

[0135] Step 6100: Update the parameters in the cache and clear the parameter cache.

[0136] Step 6110: Output alarm log.

[0137] Step 6120: Returns the parameter update success value.

[0138] Step 6130: Output the error log and the corresponding bin value for Errorbin.

[0139] Step 6140: Clear parameter cache.

[0140] Step 6150 returns an error code.

[0141] Error codes are used to indicate the type of error in the interface parameters.

[0142] like Figure 11 The diagram illustrates a structural schematic of an alarm configuration device for a test project provided in an exemplary embodiment of this disclosure. In one possible implementation, the device may include: The parameter determination module 1110 is used to determine the configuration alarm type and configuration alarm behavior parameters in response to the alarm configuration command. The configuration alarm behavior parameters are used to indicate the processing method when the configuration alarm type is triggered. The parameter verification module 1120 is used to verify the configured alarm type and the configured alarm behavior parameter based on the preset parameter mapping relationship and the preset parameter writing rule, and to determine the target alarm type and target alarm behavior parameter that meet the verification conditions. The preset parameter mapping relationship is used to indicate the mapping rule that must be followed between the alarm type and the alarm behavior parameter. The parameter distribution module 1130 is used to configure the target alarm type and the target alarm behavior parameters to the test board.

[0143] In some optional implementations, the parameter verification module 1120 is specifically used for: Based on the preset parameter mapping relationship, the mapping relationship between the configured alarm type and the configured alarm behavior parameter is verified; Based on the preset parameter writing rules, the validity of the configured alarm type and the configured alarm behavior parameters is verified. If the verification conditions of the mapping relationship verification and the parameter validity verification are met, the configured alarm type is determined to be the target alarm type and the configured alarm behavior parameter is determined to be the target alarm behavior parameter.

[0144] In some optional implementations, the parameter verification module 1120 is specifically used for: Verify whether the configured alarm type and the configured alarm behavior parameter exist in the preset parameter list, which includes multiple preset configured alarm types and multiple preset configured alarm behavior parameters; If they exist, then it is determined that the configured alarm type and the configured alarm behavior parameters meet the verification conditions for the parameter validity check.

[0145] In some optional implementations, the parameter determination module 1110 is specifically used for: In response to multiple alarm configuration commands, determine multiple configured alarm types; In some optional implementations, the parameter verification module 1120 is specifically used for: Determine whether any two configured alarm types are duplicates; if they are not duplicates, then determine that the configured alarm type meets the validity check conditions.

[0146] In some optional implementations, the preset parameter mapping relationship includes a mapping relationship between each alarm type and multiple preset alarm behavior parameters; The parameter verification module 1120 is specifically used for: Verify whether the configured alarm behavior parameter exists among the multiple preset alarm behavior parameters corresponding to the configured alarm type; If it exists, then it is determined that the configured alarm type and the configured alarm behavior parameters satisfy the verification conditions of the mapping relationship verification.

[0147] In some optional implementations, the parameter determination module 1110 is further configured to: In response to the alarm configuration command, a configuration bin value is determined, wherein the bin value is used to indicate the group that the chip under test needs to be assigned when executing the alarm behavior parameters; The parameter verification module 1120 is also used to verify the configuration bin value based on the preset parameter writing rules, and determine the target bin value corresponding to the target alarm behavior parameter.

[0148] In some optional implementations, the alarm configuration device for the test project further includes: The update determination module is used to determine the update parameters in response to the user interface receiving a parameter update request. The update parameters include update alarm behavior parameters and / or update bin values. The update verification module is used to verify the update parameters based on the preset parameter mapping relationship and the preset parameter writing rules, and determine the updated target parameters that meet the verification conditions.

[0149] In some optional implementations, the updated target parameter includes the updated bin value; The alarm configuration device for the test project also includes: The rule verification module is used to verify whether the interface parameters of the user interface have been set with bin value anomaly classification rules, which include alarm anomaly classification and non-alarm anomaly classification. The classification determination module is used to determine the updated bin value as the alarm anomaly category when the rule verification module determines that an anomaly classification rule for bin value has been set.

[0150] In some optional implementations, the parameter determination module 1110 is further configured to: determine configuration remarks information in response to the alarm configuration command; The parameter verification module 1120 is also used to verify the configuration remarks information based on the preset parameter writing rules, and determine the target remarks information corresponding to the target alarm type.

[0151] In some optional implementations, the alarm configuration device for the test project further includes: A loading verification module is used to verify the loading status of the configured alarm type and the configured alarm behavior parameters; The parameter verification module 1120 is further configured to determine that the configuration alarm type and the configuration alarm behavior parameter meet the verification conditions if the loading verification module determines that the loading status is loaded.

[0152] The alarm configuration device for the test project in this disclosure corresponds to the alarm configuration method for the test project described above, and the relevant content can be referred to each other, which will not be repeated here. The beneficial technical effects of the alarm configuration device for the test project in this disclosure can be found in the corresponding beneficial technical effects of the exemplary method section described above, which will not be repeated here.

[0153] In addition, embodiments of this disclosure also provide an electronic device, including: Memory, used to store computer programs; A processor is configured to execute a computer program stored in the memory, and when the computer program is executed, to implement the alarm configuration method for the test project described in any of the above embodiments of this disclosure.

[0154] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this disclosure, such as... Figure 12 As shown, the electronic device includes one or more processors and memory.

[0155] A processor can be a central processing unit (CPU) or other form of processing unit with data processing and / or instruction execution capabilities, and can control other components in an electronic device to perform desired functions.

[0156] The memory can store one or more computer program products, and the memory can include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program products can be stored on the computer-readable storage medium, and the processor can run the computer program products to implement the alarm configuration methods of the test engineering of the various embodiments of this disclosure described above, and / or other desired functions.

[0157] In one example, the electronic device may also include input devices and output devices, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).

[0158] In addition, the input device may also include, for example, a keyboard, a mouse, etc.

[0159] This output device can output various information to the outside, including determined distance information, direction information, etc. The output device may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.

[0160] Of course, for the sake of simplicity, Figure 12 Only some of the components of the electronic device relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the electronic device may include any other suitable components depending on the specific application.

[0161] In addition to the methods and apparatus described above, embodiments of this disclosure may also be computer program products comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps in the alarm configuration method for a test project according to various embodiments of this disclosure as described in the foregoing portion of this specification.

[0162] The computer program product can be written in any combination of one or more programming languages ​​to perform the operations of the embodiments of this disclosure. The programming languages ​​include object-oriented programming languages ​​such as Java and C++, as well as conventional procedural programming languages ​​such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.

[0163] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions that, when executed by a processor, cause the processor to perform the steps in the alarm configuration method of a test project according to various embodiments of this disclosure as described in the foregoing portion of this specification.

[0164] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.

[0165] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.

[0166] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For system embodiments, since they largely correspond to method embodiments, the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0167] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.

[0168] The methods and apparatus of this disclosure may be implemented in many ways. For example, they may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order of steps for the methods is for illustrative purposes only, and the steps of the methods of this disclosure are not limited to the order specifically described above unless otherwise specifically stated. Furthermore, in some embodiments, this disclosure may also be implemented as a program recorded on a recording medium, the program including machine-readable instructions for implementing the methods according to this disclosure. Thus, this disclosure also covers recording media storing programs for performing the methods according to this disclosure.

[0169] It should also be noted that in the apparatus, devices, and methods of this disclosure, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions to this disclosure.

[0170] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.

[0171] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.

Claims

1. A method for configuring alarms in a test project, characterized in that, The method includes: In response to an alarm configuration command, the alarm type and alarm behavior parameters are determined, wherein the alarm behavior parameters are used to indicate the processing method when the alarm type is triggered; Based on the preset parameter mapping relationship and preset parameter writing rules, the configured alarm type and the configured alarm behavior parameter are verified to determine the target alarm type and target alarm behavior parameter that meet the verification conditions. The preset parameter mapping relationship is used to indicate the mapping rules that need to be followed between the alarm type and the alarm behavior parameter. Configure the target alarm type and the target alarm behavior parameters onto the test board.

2. The method according to claim 1, characterized in that, The step of verifying the configured alarm type and the configured alarm behavior parameters based on preset parameter mapping relationships and preset parameter writing rules, and determining the target alarm type and target alarm behavior parameters that meet the verification conditions, includes: Based on the preset parameter mapping relationship, the mapping relationship between the configured alarm type and the configured alarm behavior parameter is verified; Based on the preset parameter writing rules, the validity of the configured alarm type and the configured alarm behavior parameters is verified. If the verification conditions of the mapping relationship verification and the parameter validity verification are met, the configured alarm type is determined to be the target alarm type and the configured alarm behavior parameter is determined to be the target alarm behavior parameter.

3. The method according to claim 2, characterized in that, The step of validating the configuration alarm type and configuration alarm behavior parameters based on the preset parameter writing rules includes: Verify whether the configured alarm type and the configured alarm behavior parameter exist in the preset parameter list, which includes multiple preset configured alarm types and multiple preset configured alarm behavior parameters; If it exists, then determine that the configured alarm type and the configured alarm behavior parameters satisfy the parameters. Validation conditions for validity verification.

4. The method according to claim 2, characterized in that, The step of determining the alarm type in response to the alarm configuration command includes: In response to multiple alarm configuration commands, determine multiple configured alarm types; The step of validating the parameters of the configured alarm type based on preset parameter writing rules includes: Determine whether any two configured alarm types are duplicates; if they are not duplicates, then determine that the configured alarm type meets the validity check conditions.

5. The method according to claim 2, characterized in that, The preset parameter mapping relationship includes the mapping relationship between each alarm type and multiple preset alarm behavior parameters; The step of validating the mapping relationship between the configured alarm type and the configured alarm behavior parameter based on the preset parameter mapping relationship includes: Verify whether the configured alarm behavior parameter exists among the multiple preset alarm behavior parameters corresponding to the configured alarm type; If it exists, then it is determined that the configured alarm type and the configured alarm behavior parameters satisfy the verification conditions of the mapping relationship verification.

6. The method according to claim 1, characterized in that, The method further includes: In response to the alarm configuration command, a configuration bin value is determined. The bin value is used to indicate the group that the chip under test needs to be assigned when executing alarm behavior parameters. Based on the preset parameter writing rules, the configuration bin value is verified to determine the target bin value corresponding to the target alarm behavior parameter.

7. The method according to claim 6, characterized in that, After configuring the target alarm type and the target alarm behavior parameters to the test board, the method further includes: In response to a parameter update request received by the user interface, the update parameters are determined, including update alarm behavior parameters and / or update bin values; Based on the preset parameter mapping relationship and the preset parameter writing rules, the updated parameters are verified to determine the updated target parameters that meet the verification conditions.

8. The method according to claim 7, characterized in that, The updated target parameters include the updated bin values; after determining the updated target parameters that meet the verification conditions, the following are also included: Verify whether the interface parameters of the user interface have been set with bin value anomaly classification rules, which include alarm anomaly classification and non-alarm anomaly classification; If so, the updated bin value will be determined as the alarm anomaly category.

9. The method according to claim 1, characterized in that, The method further includes: In response to the alarm configuration command, determine the configuration remarks information; Based on the preset parameter writing rules, the configuration remarks information is verified to determine the target remarks information corresponding to the target alarm type.

10. The method according to claim 1, characterized in that, Before validating the configuration alarm type and the configuration alarm behavior parameters based on preset parameter mapping relationships and preset parameter writing rules, the method further includes: Verify the loading status of the configured alarm type and the configured alarm behavior parameters; If the loading status is "loaded", then it is determined that the configuration alarm type and the configuration alarm behavior parameters meet the verification conditions.

11. An alarm configuration device for a test project, characterized in that, The device includes: The parameter determination module is used to determine the configuration alarm type and configuration alarm behavior parameters in response to the alarm configuration command. The configuration alarm behavior parameters are used to indicate the processing method when the configuration alarm type is triggered. The parameter verification module is used to verify the configured alarm type and the configured alarm behavior parameter based on the preset parameter mapping relationship and the preset parameter writing rule, and to determine the target alarm type and target alarm behavior parameter that meet the verification conditions. The preset parameter mapping relationship is used to indicate the mapping rule that must be followed between the alarm type and the alarm behavior parameter. The parameter distribution module is used to configure the target alarm type and the target alarm behavior parameters to the test board.

12. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute a computer program stored in the memory, wherein when the computer program is executed, it implements the alarm configuration method of the test project as described in any one of claims 1 to 10.

Images