EDA tool running parameter configuration management method, electronic device and storage medium

Abstract

The present application relates to the field of electronic design automation, in particular to an EDA tool running parameter configuration management method, electronic equipment and storage medium, which acquires the version of the EDA tool and the optional parameter list thereof; receives the current version and N target input parameters input by a user, identifies and extracts the target running parameter, the parameter identifier and the first check parameter in each target input parameter; checks the N target input parameters respectively, and starts the EDA tool based on the retained target input parameters after the N target input parameters all pass the check; if the check is different, the EDA tool is not started and an error is reported to exit. It can not only exit in time when the user inputs an error target input parameter, but also can ignore the supported parameters in the abandoned version or the new version, and normally start the EDA tool, which greatly accelerates the development efficiency of parameter iteration.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of electronic design automation, and in particular to an EDA operation parameter configuration management method, an electronic device and a storage medium. BACKGROUND

[0002] Unlike ordinary software tools, the development process of EDA tools is highly bound to customer use needs. A new function or a problem repair may need to go through multiple iterations of "function development / problem repair - trial feedback - re-development / re-repair" before it is stable. In order to avoid the impact of new functions or problem repairs on existing functions, the industry will use the method of adding parameter control for new functions / problem repairs. Only when a certain specific parameter is carried in the EDA tool operation parameter configuration, the corresponding new function / problem repair is introduced.

[0003] However, in the actual process of iterative development / problem repair with customers, it is found that this method has a natural contradiction between error parameter interception and stable parameter exit. In actual use, the customer requires that when the input parameter has an error, for example, when a certain parameter is input, a certain letter is omitted, etc., the EDA tool should clearly report an error when starting. When inputting the parameter of a stable function, since the function has been stable and does not need to input the parameter, it will be started by default, and the parameter has been deleted from the optional parameter list. The customer requires that the EDA tool can ignore the obsolete parameter and start the EDA tool with the remaining parameters. In fact, the EDA tool cannot simply distinguish between the two cases, so in actual use, it can only simply choose to report an error and exit when encountering an unrecognized parameter or to ignore and continue execution when encountering an unrecognized parameter. This contradiction is often encountered in the following two scenarios:

[0004] First, when using an old version of the EDA tool, if the customer uses the existing configuration, since the old version of the EDA tool does not contain some new parameters in the configuration, if it is set to report an error and exit immediately when encountering an unrecognized parameter, the customer cannot start the EDA tool with the existing configuration. If it is set to ignore when encountering an unrecognized parameter, the input error parameter may be ignored.

[0005] Second, when using a new version of the EDA tool, if the customer uses the existing configuration to test the new version, since some function parameters in the new version of the EDA tool may have been stable, and the existing configuration contains these parameters. If it is set to report an error and exit immediately when encountering an unrecognized parameter, the customer cannot start the EDA tool with the existing configuration. If it is set to ignore when encountering an unrecognized parameter, the input error parameter may be ignored; for example, when the user inputs an error parameter, it may directly start the EDA tool and cannot test the new version.

[0006] Such contradiction seriously hinders the agile iterative development of EDA, so there is an urgent need for a running parameter configuration management method which can exit with an error when an incorrect parameter is input, and can identify and ignore the supported parameters in the abandoned version or the new version and continue running. SUMMARY

[0007] In order to solve the above technical problems, the technical scheme adopted by the present application is as follows: An EDA tool running parameter configuration management method, the method comprising the following steps:

[0008] S100, obtaining the version of the EDA tool and its optional parameter list, each of the optional parameter list including R running parameters of new functions and T running parameters of problem repair functions, R and T are both greater than or equal to 0; wherein each version has an independent optional parameter list.

[0009] S300, receiving the current version and its N target input parameters input by the user, wherein N is greater than 0.

[0010] S500, identifying and extracting the target running parameter, the parameter identifier and the first check parameter in each of the target input parameters; wherein the first check parameter is the unique identifier data of the target running parameter.

[0011] S700, checking the N target input parameters respectively, and starting the EDA tool based on the reserved target input parameters after the N target input parameters all pass the check; wherein the check step of each target input parameter comprises:

[0012] S710, verifying the legality according to the first check parameter of the current target input parameter, if the verification fails, the EDA tool is not started and an error is exited; if the verification passes, S720 is executed.

[0013] S720, obtaining the target optional parameter list of the current version, matching the target running parameter corresponding to the current target input parameter with the running parameter in the target optional parameter list; if the matching is successful, the current target input parameter is reserved; if the matching is unsuccessful, the current target input parameter is discarded.

[0014] In addition, the present application also provides a non-transitory computer readable storage medium, the storage medium stores at least one instruction or at least one program, the at least one instruction or the at least one program is loaded and executed by the processor to realize the above method.

[0015] In addition, the present application also provides an electronic device comprising a processor and the above non-transitory computer readable storage medium.

[0016] The present application has at least the following beneficial effects:

[0017] The application provides an EDA tool running parameter configuration management method, electronic equipment and storage medium, which receives a current version and N target input parameters input by a user, each target input parameter comprising a first check parameter; checks the N target input parameters respectively, and starts the EDA tool based on the retained target input parameters after the N target input parameters all pass the check; if the checks are different, the EDA tool is not started and an error is reported to exit. It can not only report an error and exit in time when the user inputs an incorrect target input parameter, but also ignore the supported parameters in the abandoned version or the new version and normally start the EDA tool, greatly improving the development efficiency of parameter iteration. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed in the embodiment description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0019] Figure 1 An EDA tool running parameter configuration management method flowchart is provided for the embodiments of the present application.

[0020] Figure 2 A check step flowchart of each target input parameter is provided for the embodiments of the present application. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present application will be described clearly and completely in combination with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0022] Unless otherwise defined, all technical and scientific terms used in the embodiments of the present application have the same meanings as commonly understood by those skilled in the art.

[0023] Please refer to Figure 1 which shows an EDA tool running parameter configuration management method, the method comprising the following steps:

[0024] S100, obtain a version of an EDA tool and a list of optional parameters thereof, each list of optional parameters comprising R running parameters of new functions and T running parameters of problem repair functions, R and T are both greater than or equal to 0; wherein each version has an independent list of optional parameters.

[0025] The EDA tool has different versions with different functions, and the version of the EDA tool is provided with a unique version parameter by the software supplier. When the EDA tool is started, the version parameter is input to specify the version of the EDA tool to be started.

[0026] In an embodiment, the running parameters of the new function and the running parameters of the problem fixing function are the names of the corresponding functions.

[0027] The running parameters in the optional parameter list are the names of a new function or a problem fixing function. In the code, each running parameter is taken as an entry parameter of a conditional statement, and the code block of the conditional statement includes the logic code of the new function or the problem fixing function of the current running parameter. When the running parameter is successfully started, the logic code in the corresponding conditional statement is executed. Other types of running parameters included in the optional parameter list also fall within the protection scope of the present application.

[0028] As an example, the running parameter of the first new function is feature1, and the running parameter of the second new function is feature2. In the code, the code block including the conditional statement if (feature1) and the code block including the conditional statement if (feature2) are included.

[0029] In an embodiment, S100 further includes an updating step of the optional parameter list: S110, when the running parameter is the running parameter of the stable new function or the problem fixing function, the running parameter is deleted from the optional parameter list.

[0030] It should be noted that the running parameters saved in the optional parameter list are parameters of the corresponding function which are not yet stable. When the corresponding function is stable, it will be deleted from the optional parameter list, but the corresponding logic code is retained.

[0031] As an example, when feature1 is stable, it is deleted from the optional parameter list, and the logic code in the code block of if (feature1) is retained, and only the if conditional judgment logic is deleted.

[0032] S300, receiving the current version and N target input parameters input by the user, where N is greater than 0.

[0033] It should be noted that the current version input by the user and the target input parameter are both from a software provider, which is a party developing the EDA tool and can also be referred to as an input parameter provider. The current version parameter and the target input parameter provided by the software provider are both standard parameters. However, when the user inputs the standard parameters into the EDA tool to start the EDA tool, the user may input incorrectly due to various reasons, or the version and the target input parameter do not match.

[0034] In the target input parameter input by the user, the target input parameter can carry a check parameter identifier and a check parameter, or can not carry the check parameter identifier and the check parameter. Whether to carry the check parameter identifier and the check parameter is provided by the input parameter provider. When the function corresponding to one running parameter is not stable, it is generally recommended that the input parameter carries the check parameter identifier and the check parameter; when one running parameter is always unstable, it is generally recommended that the input parameter does not carry the check parameter identifier and the check parameter. When the target input parameter carries the check parameter identifier and the check parameter, the check logic is executed. When the target input parameter does not carry the check parameter identifier and the check parameter, the matching logic is executed.

[0035] In an embodiment, the method further comprises: S400, judging whether the check parameter identifier is carried in each of the target input parameters, and if not, performing the following matching step:

[0036] S410, obtaining a target optional parameter list of the current version, matching the current target input parameter with the running parameter in the target optional parameter list; if the matching is successful, the current target input parameter is reserved; and if the matching is unsuccessful, the EDA tool is not started.

[0037] It should be noted that if the current target input parameter is matched successfully, the EDA tool cannot be started directly, and the EDA tool can be started only after all the target input parameters are matched successfully. If one of the target input parameters is not matched successfully, it indicates that the target input parameter can be input incorrectly, or the function corresponding to the target input parameter is stable and has been deleted from the target optional parameter list, and thus the EDA tool is not started directly and is exited.

[0038] S420, after the N target input parameters are all matched, the EDA tool is started based on the reserved target input parameters.

[0039] It should be noted that this mode can quickly identify whether the target input parameter input by the user is correct, and if not, the EDA tool is directly exited. This method can be compatible with the target input parameter without the check parameter input by the user.

[0040] S500, identifying and extracting a target running parameter, a parameter identifier and a first check parameter in each of the target input parameters; wherein the first check parameter is unique identification data of the target running parameter.

[0041] The target running parameter is a parameter that can actually start a corresponding function, and the parameter identifier is used to identify the first check parameter.

[0042] In an embodiment, in S500, the first check parameter is a check parameter calculated by an input parameter provider according to an original running parameter, and the check parameter is obtained by a preset check algorithm. The first check parameter is used to check whether the target running parameter input by a user is changed relative to the original running parameter.

[0043] In an embodiment, in S500, the parameter identifier is a special character that is not occupied by a related parameter of the EDA tool.

[0044] In an embodiment, the parameter identifier is “*”, “^” or “#”, and other types of special characters also fall within the protection scope of the present application.

[0045] In an embodiment, the target running parameter and the first check parameter in each of the target input parameters are extracted according to the parameter identifier.

[0046] It should be noted that in the target input parameter, the parameter identifier is configured between the target running parameter and the first check parameter, so that the two parameters can be directly extracted through the parameter identifier. As an example, the target input parameter is “-new_feat*2”, wherein “*” is the parameter identifier, “-new_feat” is the target running parameter, and “2” is the first check parameter.

[0047] S700, respectively checking N target input parameters, and starting the EDA tool based on the reserved target input parameters after the N target input parameters are all checked.

[0048] It should be noted that a user may test multiple new functions or problem repair functions at a time when starting the EDA tool, and therefore, the target input parameters of these functions need to be checked respectively.

[0049] Further, referring to Figure 2 , the checking step of each target input parameter includes:

[0050] S710, verifying legality according to the first check parameter of the current target input parameter, if the verification fails, the EDA tool is not started and an error is reported and exited; if the verification passes, S720 is executed.

[0051] The first check parameter can be used to exit with an error message in time when the user inputs an incorrect target input parameter.

[0052] In an embodiment, S710 further includes:

[0053] S711, obtaining a preset check algorithm for generating the first check parameter; the first check parameter is generated by a preset check algorithm based on the original running parameter by an input parameter provider.

[0054] S712, calculating the target running parameter according to the preset check algorithm to obtain a second check parameter.

[0055] It should be noted that using the preset check algorithm for generating the first check parameter to generate the second check parameter can ensure the uniqueness of the variable, if the target running parameter is completely the same as the original running parameter, the first check parameter and the second check parameter will also be completely the same. If the target running parameter has changed relative to the original running parameter, even if the change is small, the first check parameter and the second check parameter will not be the same.

[0056] In an embodiment, in S712, the preset check algorithm includes the following steps:

[0057] S7121, inputting the target running parameter into a hash function to obtain a hash value.

[0058] S7122, extracting a specified K-bit in the hash value as the second check parameter according to a preset extraction strategy, K is greater than or equal to 1.

[0059] In an embodiment, in S7122, the specified K-bit is the lowest K-bit, the highest K-bit or a specified continuous K-bit in the hash value. Other types of preset extraction strategies also fall within the protection scope of the present application.

[0060] In an embodiment, K=1, 2, 3 or 4. Other values of K also fall within the protection scope of the present application.

[0061] As an example, for the target running parameter "-new_feat", inputting it into a hash function, the output hash value is "F7F6DD50C42DE21FC787E22BD0C73CD2", if the lowest 1-bit is extracted as the second check parameter, the second check parameter is 2.

[0062] It should be noted that the preset checking algorithm for obtaining the first checking parameter and the second checking parameter is the same, and will not be repeated.

[0063] S713, whether the first checking parameter of the current target input parameter is the same as the second checking parameter, if not, the verification is not passed; if the same, the verification is passed.

[0064] S720, obtaining the target optional parameter list of the current version, matching the target running parameter corresponding to the current target input parameter with the running parameter in the target optional parameter list; if the matching is successful, the current target input parameter is retained; if the matching is not successful, the current target input parameter is discarded.

[0065] It should be noted that if the matching is successful, it means that the target input parameter input by the user is correct and matches the current version. If the matching is not successful, it means that the target input parameter input by the user is correct, is an abandoned version or a supported parameter in a new version, and does not affect the normal start of the current version, so the target input parameter can be discarded. The method provided by the application not only satisfies the contradictory requirement that the user originally intercepts the use of the input error target input parameter to run the EDA and ignores the abandoned or new version parameter, and greatly accelerates the development efficiency of parameter iteration.

[0066] In summary, the application provides an EDA tool running parameter configuration management method, which receives a current version and N target input parameters input by a user, each target input parameter including a first checking parameter; checks the N target input parameters respectively, and starts the EDA tool based on the retained target input parameters after the N target input parameters are all checked. If the checking is different, the EDA tool is not started and an error is reported to exit. It not only can report an error and exit in time when the user inputs an error target input parameter, but also can ignore the abandoned version or the supported parameter in the new version and start the EDA tool normally, greatly accelerating the development efficiency of parameter iteration.

[0067] The embodiment of the application also provides a non-transitory computer readable storage medium, which can be arranged in an electronic device to save at least one instruction or at least one program related to a method in the method embodiment, and the at least one instruction or the at least one program is loaded and executed by the processor to realize the method provided by the above-mentioned embodiment.

[0068] The embodiment of the application also provides an electronic device, which includes a processor and the aforementioned non-transitory computer readable storage medium.

[0069] Embodiments of the present application also provide a computer program product comprising program code for causing an electronic device to perform the steps of the methods according to various exemplary embodiments of the present application described above in the specification when said program product is run on the electronic device.

[0070] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of each functional unit and module is exemplified, and in actual application, the above-mentioned functions can be completed by different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the above-described functions.

[0071] Although some specific embodiments of the present application have been described in detail by way of example, it should be understood that the above examples are only for illustration and are not intended to limit the scope of the present application. Those skilled in the art should understand that various modifications can be made to the embodiments without departing from the scope and spirit of the present application. The scope of the present application is defined by the appended claims.

Claims

1. A method for configuring and managing runtime parameters of an EDA tool, characterized in that, The method includes the following steps: S100, Obtain the version of the EDA tool and its list of optional parameters. Each list of optional parameters includes R running parameters for new functions and T running parameters for problem-solving functions, where R and T are both greater than or equal to 0; wherein, each version has an independent list of optional parameters. S300 receives the current version and N target input parameters input by the user, where N is greater than 0; S500, identify and extract the target operating parameter, verification parameter identifier and first verification parameter from each of the target input parameters; wherein, the first verification parameter is the unique identification data of the target operating parameter; S700, verify each of the N target input parameters. After all N target input parameters pass verification, start the EDA tool based on the retained target input parameters; wherein the verification step for each target input parameter includes: S710: Verify the validity of the first verification parameter of the current target input parameter. If the verification fails, the EDA tool will not be started and will exit with an error message. If the verification passes, proceed to S720. S720, obtain the target optional parameter list of the current version, and match the target running parameter corresponding to the current target input parameter with the running parameter in the target optional parameter list; if the match is successful, retain the current target input parameter; if the match is unsuccessful, discard the current target input parameter.

2. The method according to claim 1, characterized in that, The S710 also includes: S711, Obtain the preset verification algorithm for generating the first verification parameter; the first verification parameter is generated by the input parameter provider based on the original running parameters through the preset verification algorithm; S712, calculate the target operating parameters according to the preset verification algorithm to obtain the second verification parameter; S713, compare whether the first verification parameter and the second verification parameter of the current target input parameter are the same. If they are different, the verification fails; if they are the same, the verification passes.

3. The method according to claim 2, characterized in that, In S712, the preset verification algorithm includes the following steps: S7121, Input the target operating parameters into a hash function to obtain a hash value; S7122, According to the preset extraction strategy, extract the specified K bits from the hash value as the second verification parameter, where K is greater than or equal to 1.

4. The method according to claim 3, characterized in that, In S7122, the specified K bits are the lowest K bits, the highest K bits, or a series of K bits in the middle of the specified hash value.

5. The method according to claim 1, characterized in that, The method further includes: S400, determine whether each of the target input parameters carries a verification parameter identifier. If not, perform the following matching steps: S410, obtain the target optional parameter list of the current version, and match the current target input parameter with the running parameters in the target optional parameter list; if the match is successful, retain the current target input parameter; if the match is unsuccessful, do not start the EDA tool; S420, after all N target input parameters have been matched, the EDA tool is started based on the retained target input parameters.

6. The method according to claim 1, characterized in that, S100 also includes an update step for the optional parameter list: S110, when the running parameter is a running parameter for a stable new function or a problem-fixing function, then the running parameter is deleted from the list of optional parameters.

7. The method according to claim 1, characterized in that, In S500, the first verification parameter is a verification parameter calculated by the input parameter provider based on the original running parameters. This verification parameter is obtained by calculating through a preset verification algorithm.

8. The method according to claim 1, characterized in that, In S500, the verification parameter identifier is a special character that is not used by the relevant parameters of the EDA tool.

9. A non-transitory computer-readable storage medium, wherein the storage medium stores at least one instruction or at least one program segment, characterized in that, The at least one instruction or the at least one program segment is loaded and executed by the processor to implement the method as described in any one of claims 1-8.

10. An electronic device, characterized in that, Includes a processor and the non-transitory computer-readable storage medium as described in claim 9.

Images