This warning message comes up when annotation is attempted on a design after creating Layout/PCB Editor netlist. Q - “Allegro/Layout PCB Netlist has been already generated for this design this operation may cause physical design to go out of sync, and result in problem(s) during Back-Annotation. Specify an End Value for the range, which is more than the total number of parts on the page. This error message comes up when total number of parts (components) on your schematic page exceeds the part reference range specified in the grid. This error arises when the tool is creating a report of unused parts and finds more than 4096 parts in a package.ĮRROR - “Part reference %s is out of range (%d to %d) %s(x=%d, y=%d)” This warning can be ignored if the connections are done intentionally.ĮRROR - “Part Count Overflow: %s.” When a common pin of two instantiated sections of a part has different net connections, Capture packages the two instances separately to eliminate design errors. WARNING - “Component %s%s has different common pin connection for two instances and hence packaged separately.” You can avoid this error by annotating all heterogeneous parts before running the tool. Group the parts into two different packages. This error arises when the tool encounters a second heterogeneous part with an identical part reference to the first part. One situation while this message comes up is if the user has specified some properties as part of combined property string, and they are not available in any of the parts in the design.ĮRROR - “Cannot perform annotation of heterogeneous part ‘%s(Value %s) at location (%s) on page %s’, part has not been uniquely grouped (using a common User Property with differing Values) or the device designation has not been chosen” User needs to check the messages and rectify. This warning message comes up when there are too many warning messages, and the number exceeds the limit. Please check combined property string for invalid specification. User should check the combined property string that was put while annotating. Capture assumes default combined property string in such case. This warning message comes up when the properties specified in the combined property string are not found in a part while performing annotation. Using default combine property string for this part.” WARNING - “Properties specified in combined property string not found on part, ‘%s’. Currently this is only encountered while organizing the parts on the page for the annotation order. This problem may exist because of an improperly configured combined property string in the Update Properties dialog box.ĮRROR - “Memory limit, unable to complete updating references”Ī memory limit was encountered while processing. This error arises when Update Part References tried to change the Part Reference’s package value to use the part’s package as the suffix, but the part’s package does not exist as a valid suffix to change to. Make sure that the part reference range does not conflict with the parts already annotated in the design.ĮRROR - “An attempt was made to change %s to part %d, however it is a %d part per package device” This error message comes up when during incremental annotation Capture encounters parts (components) in your design, which are already annotated with part references that are outside the range specified in the grid. You cannot remove Design Cache from your project.ĮRROR - “Part Occurrence for %s Not Found Please check if there is any recursive reference.” This error message appears when you click the Remove Library button on the Place Part dialog box with a library selected in the Libraries list box. To successfully generate parts from APD BGA/Die-Text files, the pin-Name and pin-number headers need to be defined.ĮRROR - “Unable to create VHDL file ‘%s’, file error (%d)” Generate Part Failed.”ĭuring part generation, if the Pin-Name / Pin-Number headers are missing for APD BGA/Die-Text files then this warning appears. Check the session log for details.ĮRROR - “No Pin-Name/Pin-Number headers found. This message occurs when Express encounters errors while attempting to export properties. See the Session Log for more information.” 在本地帮助文件中找到了, capture的所有错误消息说明文件如下: file:///D:/Cadence/SPB_17.4/doc/orcadmsgref/ORCAP_Messages.htmlĮRROR - “Error(s) encountered while attempting to export properties.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |