<?xml version="1.0" encoding="UTF-8"?>
<MsgFile>
  <Msg>
    <Id>0</Id>
    <Category>E</Category>
    <Desc>
      "Internal database error occurred in %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>1</Id>
    <Category>E</Category>
    <Desc>
      "Property list not specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>2</Id>
    <Category>W</Category>
    <Desc>
      "Only maximum of %d properties used in sort.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>3</Id>
    <Category>W</Category>
    <Desc>
      "Invalid value of %s specified for property %s. Using default value of %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>4</Id>
    <Category>E</Category>
    <Desc>
      "Objects of type '%s' currently cannot be sorted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>5</Id>
    <Category>E</Category>
    <Desc>
      "Pin '%s' on the following primitive instance cannot be packaged in package of type '%s'.
      Primitive Instance: %s
      No description of the logical pin being used by a primitive instance could be found in the chips.prt file.
      Ensure that the chips.prt file for the part contains a description of the pin. This error can also occur if the selected symbol does not match the selected primitive. Make sure that the symbol you select matches the primitive specified by the PACK_TYPE property.
      "
    </Desc>
    <ExtDesc>
      "Packager-XL generates the above error if it does not find a description of a logical pin, which is being used by a primitive instance, in the chips.prt file. Ensure that the chips.prt file for the physical part that generated the error contains a description for the logical pin mentioned in the error message."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>6</Id>
    <Category>E</Category>
    <Desc>
      "Cannot package primitive instance '%s' in package of type '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>7</Id>
    <Category>E</Category>
    <Desc>
      "The following primitive instance of size requires %d sections for packaging. Only %d sections are available in the package of type '%s'. Check the size of all the pins on this primitive.
      Primitive Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>8</Id>
    <Category>E</Category>
    <Desc>
      "Specified section is not a package instance section.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>9</Id>
    <Category>I</Category>
    <Desc>
      "Unpacking following primitive instance from section.
      Primitive Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>10</Id>
    <Category>E</Category>
    <Desc>
      "Primitive instance '%s' already packaged in section.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>11</Id>
    <Category>E</Category>
    <Desc>
      "Pin %s is not a primitive instance pin.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>12</Id>
    <Category>E</Category>
    <Desc>
      "Object of type '%s' not supported in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>13</Id>
    <Category>E</Category>
    <Desc>
      "Unable to find section %d assigned to the instance in physical part %s. Check and update the section assignment for the instance.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>14</Id>
    <Category>W</Category>
    <Desc>
      "PPT '%s' has no key properties.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>15</Id>
    <Category>E</Category>
    <Desc>
      "Property '%s' is not a key property for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>16</Id>
    <Category>E</Category>
    <Desc>
      "Expected '%c' while parsing added properties on line %d.
      Check the property assignment statement to ensure that you use the equal to ( = ) operator  while assigning a value to the added or injected property and enclose the property name in quotation marks.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when an equal to operator is missing while assigning a value to an added/injected property in the ptf file or when you assign an added property without enclosing it within quotes in the ptf file. Ensure that you use an equal to operator while assigning values to added properties. Also make sure that added properties are enclosed within quotation marks."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>17</Id>
    <Category>E</Category>
    <Desc>
      "Added property not enclosed in quotes on line %d.
      Ensure that all the added properties are enclosed in quotation marks in the part table file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>18</Id>
    <Category>E</Category>
    <Desc>
      "End of file encountered while parsing added properties.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>19</Id>
    <Category>E</Category>
    <Desc>
      "Duplicate injected property %s found on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>20</Id>
    <Category>E</Category>
    <Desc>
      "Keyword '%s' not found on line %d in the part table file, or the character ':' is missing from the beginning of the key property header. Correct the entry in the part table file.
      "
    </Desc>
    <ExtDesc>
      "This error can occur for multiple reasons. A keyword FILE_TYPE, PART or END_PART may be missing on the line mentioned in the error in the ptf file. The LIBRARY_PARTS or some other keyword may not be there in the chips.prt file. Words that do not seem a property definition (name=value pair) exist after the keyword PART. Characters such as period or comma may have been placed after the keyword in the same PPT row. As a result of ERROR 20, Packager-XL is unable to load the ptf file properly. It may also generate ERROR 47. Ensure that you place keywords at the right place and that no extra words exist in the part definition. The END_PART keyword should be the only word in its line. The FILE_TYPE definition should be the first definition in the ptf file or the chips.prt file and should appear before any other part definition. Note: You should not hand edit the ptf or chips.prt files. Use Part Table Editor to create ptf files. For more information about defining a ptf file, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>21</Id>
    <Category>E</Category>
    <Desc>
      "Expected '=' character while parsing global props on line %d.
      "
    </Desc>
    <ExtDesc>
      "If you do not begin the property header for a part (which lists key and injected properties) with a colon ( : ) in a ptf file, the ptf file will not be loaded properly. As a result of ERROR 21, Packager-XL will also display ERROR 47. If a colon is placed in the key/injected property list but is placed after a property, ERROR 24 is generated. Ensure that you place a colon as the first character in the line that lists all global properties. Do not hand edit ptf or chips.prt files. Use Part Table Editor to work with ptf files."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>22</Id>
    <Category>E</Category>
    <Desc>
      "The %s property for PPT %s is defined twice as a global property. Ensure that the part table file does not have duplicate property values.
      "
    </Desc>
    <ExtDesc>
      "You have defined the same property twice as a global property. Packager-XL is unable to pick the right version and load the ptf file. As a result of this error, Packager-XL may also generate ERROR 47. Ensure that you do not have duplicate property values in any PPT row."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>23</Id>
    <Category>E</Category>
    <Desc>
      "End of file encountered while reading global properties.
      "
    </Desc>
    <ExtDesc>
      "This error is caused when you have an incomplete global properties section for a PPT part definition. You have used the PART keyword but have not defined it completely. Ensure that the ptf file ends with the END. keyword, where period ( . ) is part of the keyword."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>24</Id>
    <Category>E</Category>
    <Desc>
      "Extra property value found on line %d."
    </Desc>
    <ExtDesc>
      "There may be an extra property in the line displayed in the error message. The = character or the property separator could be incorrectly placed. The name of the property may be missing in the header definition. As a result of this error, Packager-XL may also generate ERROR 47. Ensure that you do not have any extra property values in PPT rows."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>25</Id>
    <Category>E</Category>
    <Desc>
      "Multiple subtypes found on line %d.
      Ensure that you have specified only one subtype name for a particular PPT row.
      "
    </Desc>
    <ExtDesc>
      "This error is caused when you assign two or more subtypes in the same PPT row. You cannot use more than one subtype for the same PPT row. As a result of this error, Packager-XL might also generate ERROR 47. Ensure that you have specified only one subtype name definition for a particular PPT row.

      You can define the subtype name for a part using one of three formats:
      !: Packager-XL uses the instance property value as the suffix. This is the default behavior.
      subtype_name_suffix: Packager-XL appends the suffix to the parent part name.
      ~complete_user_subtype_name: Packager-XL uses the entire subtype name that appears after the tilde ( ~ ) character.

      For more information about defining the part subtype names, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>26</Id>
    <Category>E</Category>
    <Desc>
      "The closing round bracket is missing from the subtype name on line %d.
      Ensure that you have specified the closing round bracket for the subtype name definition.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you do not use the closing round bracket ')' character in the subtype name. As a result of this error, Packager-XL also generates ERROR 47. Ensure that you specify the subtype name definition within both, opening, and closing round brackets.

      You can define the subtype name for a part using one of three formats:
      !: Packager-XL uses the instance property value as the suffix. This is the default behavior.
      subtype_name_suffix: Packager-XL appends the suffix to the parent part name.
      ~complete_user_subtype_name: Packager-XL uses the entire subtype name that appears after the tilde ( ~ ) character. Each of these subtype name definitions requires that you place the value between brackets."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>27</Id>
    <Category>E</Category>
    <Desc>
      "The row separator on line %d does not match the header definition.
      The row separator should exactly match, in number and position, the header definition.
      You cannot use a pipe ( | ) symbol in the header row and a comma ( , ) in a PPT row as row separators.
      Ensure that the row separators match the separators defined in the header for the concerned PPT part.
      "
    </Desc>
    <ExtDesc>
      "The row separator should exactly match in number and in its position with the header definition. The row separator should also be the same character. You cannot use a pipe ( | ) in the header row and a comma ( , ) in a PPT row as the row separator. You could have used a different number of row separators as listed in the header row of the PPT part which generated the problem or you could have forgotten to add the quote ( ' ) for the first property value. As a result, Packager-XL is unable to load the ptf file properly. Ensure that the row separators match the separators defined in the header for the concerned PPT part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>28</Id>
    <Category>E</Category>
    <Desc>
      "Extra '%c' character found on line %d.
      Ensure that there is only one such character in each PPT row and you have not used it as a property separator.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have added an extra '=' character on any PPT line. You may have defined '=' as the property separator, which is not allowed. As a result, Packager-XL is unable to load the ptf file properly. Ensure that there is only one '=' character in a PPT line. Do not use the '=' character as the property separator."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>29</Id>
    <Category>E</Category>
    <Desc>
      "Values not found for all %s properties on line %d.
      Ensure that all properties are properly defined and the property header row lists the correct set of properties.
      In addition, do not use the '=' character as the property separator.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when injected properties are not properly defined for a line per the injected property definition in the header row. The problem could be in the PPT line listed in the error or in the injected property definition itself. Ensure that all injected properties are properly defined and the injected property header row lists the right set of injected properties. Also ensure that the = character is not used as the property separator."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>30</Id>
    <Category>E</Category>
    <Desc>
      "PPT file terminated early while parsing part table rows.
      PPT file terminated early while parsing part table rows.
      The part table file was closed because the keyword END_PART was not found before the last keyword END. in the part table file.
      Check if some other character, such as a period ( . ) or a comma ( , ) is placed after END_PART.
      Ensure that the header property is defined only once for the PTF file and END_PART is placed before END. in the PTF file.
      "
    </Desc>
    <ExtDesc>
      "This error is caused if the END_PART keyword is missing before the last keyword in a ptf file, that is END. The error can occur if the END_PART keyword is missing or if some other character such as period ( . ) or comma ( , ) is placed after the END_PART keyword. As a result of this error, Packager-XL may also generate ERROR 20 and ERROR 47. Ensure that the header property is defined only once for the PPT and the END_PART keyword is placed before the END keyword in a ptf file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>31</Id>
    <Category>E</Category>
    <Desc>
      "Duplicate header property %s found for PPT %s. The property might be defined both in the Global property declaration and as a key or injected property. Ensure that the property is defined only once for the part table file.
      "
    </Desc>
    <ExtDesc>
      "A header property should be defined only once for each PPT. You could have added a property both, in the Global property declaration, and as a key or injected property. This error is also followed by ERROR 47, which states that the concerned ptf file was not loaded. Ensure that the header property is defined only once for the PPT."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>32</Id>
    <Category>E</Category>
    <Desc>
      "Extra character(s) were found after %s on line %d.
      Ensure that no extra text is present after the END keyword or after the semicolon in the header property row definition.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you place one or more extra characters after a keyword such as END or semicolon ( ; ). For example, the END keyword is used to terminate a ptf file. Packager-XL expects the end of file delimiter after that keyword and no extra text. Similarly, the semicolon ( ; ) is used to terminate the header property row definition, and any extra text after it causes Packager-XL to generate this error. Ensure that there is no text after the END keyword or after the semicolon in the header property row definition."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>33</Id>
    <Category>E</Category>
    <Desc>
      "The OPT keyword is expected after the opening round bracket character '(' on line %d. This keyword defines whether a property is optional on an instance of a part. Place this keyword after the property name in the property header row for a PPT part. Ensure that you have defined all the properties and values in the property header row using the correct syntax.
      "
    </Desc>
    <ExtDesc>
      "This error occurs if you add the opening round bracket '(' character in the property header row but do not follow it with the OPT keyword. The OPT keyword in a PTF file defines whether a property is optional for a part instance. The keyword is used after the property name in the property header row for a PPT part. Ensure that you have defined all properties and values in the property header row as defined in the following syntax:

      property_name [(OPT='value')] [separator property_name ...] = property_name [separator property_name ...] ;

      For more information about defining a ptf file, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>34</Id>
    <Category>W</Category>
    <Desc>
      "Expected '%c' character on line %d. Check the name and value syntax for invalid characters in the primitive definition before the line number.
      "
    </Desc>
    <ExtDesc>
      "Packager-XL expects ptf files and chips.prt file to conform to a standard syntax. If you use PPT Editor to define part definitions, you will not get such errors. However, if you manually edit the ptf file and forget to place a standard character or change a standard character, Packager-XL will not be able to parse the file or load it. Therefore, Packager-XL will exit with error status 2. You may also get this error if you edit the pxl.state file manually and remove an expected character from it. Ensure that you have added the specified characters as required to create a ptf file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>35</Id>
    <Category>E</Category>
    <Desc>
      "The OPT property value on line %d is not enclosed within quotes. Ensure that you have defined all the properties and values in the property header row according to the required syntax.
      "
    </Desc>
    <ExtDesc>
      "The syntax for defining the OPT keyword in the property header row is as follows: : property_name [(OPT='value')] [separator property_name ...] = property_name [separator property_name ...] ; If you add the OPT keyword, which is optional, and do not add quotes to define the OPT value, Ensure that you have defined all properties and values in the property header row as defined in the syntax described above. The OPT value must be enclosed within quotes. Packager-XL displays the above error."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>36</Id>
    <Category>E</Category>
    <Desc>
      "The OPT keyword has been specified without a value on line %d.
      Ensure that you specify a value when you set the OPT keyword.
      "
    </Desc>
    <ExtDesc>
      "The syntax for defining the OPT keyword in the property header row is as follows: If you define the OPT keyword, you must specify a value for it. If you do not add the OPT value, Packager-XL displays this error. As a result of this error, Packager-XL also generates ERROR 47. Ensure that you have defined all properties and values in the property header row as defined in the syntax. The OPT value must be enclosed within quotes."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>37</Id>
    <Category>E</Category>
    <Desc>
      "Injected properties not found on header line %d. Check the part table file and ensure that each part definition has a header row consisting of key and injected properties separated by the '=' character.
      "
    </Desc>
    <ExtDesc>
      "Packager-XL expects each part definition to have a header row consisting of key and injected properties separated by the "=" character. If you do not add any injected property, this error is displayed. As a result of this error, Packager-XL also generates ERROR 47. Ensure that you have added injected properties to the required header line."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>38</Id>
    <Category>W</Category>
    <Desc>
      "Terminating character '%c' not found on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error is displayed while running Design Differences. The error occurs due to the equal to ("=") operator being used in the reference designator (LOCATION property) value on a component. For example, LOCATION = U1=1. Rename the reference designator (REF DES) and remove the "=" operator."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>39</Id>
    <Category>E</Category>
    <Desc>
      "Closing ptf file early.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>40</Id>
    <Category>E</Category>
    <Desc>
      "File is not of type %s.
      A part table file must be of the type MULTI_PHYS_TABLE. Ensure that you have added FILE_TYPE=MULTI_PHYS_TABLE as the first keyword in the PTF file. If this keyword is not the first keyword in a PTF file, further errors will be generated.
      "
    </Desc>
    <ExtDesc>
      "Packager-XL expects a ptf file to be of the type MULTI_PHYS_TABLE. If you have defined any other file type, this error is generated and the ptf file is closed. As a result of this error, Packager-XL also generates ERROR 47. If you add the MULTI_PHYS_TABLE keyword later in the file after other keywords, Packager-XL generates ERROR 40 and ERROR 20. Ensure that you have added the FILE_TYPE=MULTI_PHYS_TABLE keyword as the first keyword in the ptf file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>41</Id>
    <Category>W</Category>
    <Desc>
      "Opening quotation mark is missing for the part name on line %d.
      Ensure that all part names are enclosed in quotation marks.
      "
    </Desc>
    <ExtDesc>
      "This warning is generated when you have defined a part name without using the leading quote ( ' ). This warning is generally followed by WARNING 42. Ensure that all part names are enclosed within quotes."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>42</Id>
    <Category>W</Category>
    <Desc>
      "The closing quotation mark not found for part name on line %d.
      Ensure that all part names are enclosed within quotation marks.
      "
    </Desc>
    <ExtDesc>
      "This warning is generated when you have defined a part name without using the closing quote ( ' ). Ensure that all part names are enclosed within leading and closing quotes."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>43</Id>
    <Category>E</Category>
    <Desc>
      "End of file encountered while reading PPT tables. The END keyword might be missing from the part table file. Ensure that all the part table files contain all keywords including END. Ensure that the END keyword is followed by a period.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when you have a ptf file that ends without the END keyword. This error also generates ERROR 47, which lists the file where the END keyword was not properly defined. Ensure that all ptf files contain all keywords including END. Ensure that the END keyword is followed by a period."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>44</Id>
    <Category>W</Category>
    <Desc>
      "File %s not found. Cannot load PPT file(s). System Error(%d): %s. Check the physical path of the part table files defined under the PPT directive.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>45</Id>
    <Category>E</Category>
    <Desc>
      "Could not open directory '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>46</Id>
    <Category>E</Category>
    <Desc>
      "I/O error occurred for file %s. PPT file(s) not loaded. System Error(%d): %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>47</Id>
    <Category>E</Category>
    <Desc>
      "Packaging cannot be completed because the file %s could not be loaded. There might be syntax errors in this file. Ensure that the syntax is correct before proceeding.
      "
    </Desc>
    <ExtDesc>
      "This error is generated along with another packaging error, which prevents Packager-XL from completing its operation. Fix the other errors that are generated in the pxl.log file and package the design again."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>48</Id>
    <Category>E</Category>
    <Desc>
      "PANIC! Could not close directory '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>49</Id>
    <Category>E</Category>
    <Desc>
      "Could not find file '%s'. PPT file(s) not loaded.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>50</Id>
    <Category>E</Category>
    <Desc>
      "%s do not match for multiple occurrences of the same hierarchy.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>51</Id>
    <Category>E</Category>
    <Desc>
      "Part table file '%s' could not be opened because there is no read permission on the part table file.
      Assign the read permission to the file and package.
      "
    </Desc>
    <ExtDesc>
      "This error can occur if read permissions have not been set for the ptf file. As a result, Packager-XL is not able to load the ptf file. Assign read permissions for the file and re-run Packager-XL."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>52</Id>
    <Category>E</Category>
    <Desc>
      "Object of type '%s' specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>53</Id>
    <Category>E</Category>
    <Desc>
      "Packaging cannot be completed because packaging has encountered a null object ID. The design may not have been saved correctly. Save the design before packaging.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>54</Id>
    <Category>E</Category>
    <Desc>
      "Object must be a %s in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>55</Id>
    <Category>W</Category>
    <Desc>
      "%s view associated with design view. Delete not performed.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>56</Id>
    <Category>E</Category>
    <Desc>
      "%s object cannot be deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>57</Id>
    <Category>E</Category>
    <Desc>
      "%s property cannot exist for a %s object.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>58</Id>
    <Category>E</Category>
    <Desc>
      "Illegal property scope specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>59</Id>
    <Category>E</Category>
    <Desc>
      "Pin instance cannot be created for a %s type object.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>60</Id>
    <Category>W</Category>
    <Desc>
      "Pin specified in call to %s is not a %s pin.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>61</Id>
    <Category>W</Category>
    <Desc>
      "Pin specified in call to %s is a %s pin.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>62</Id>
    <Category>E</Category>
    <Desc>
      "Internal error in %s while extracting %s from %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>63</Id>
    <Category>E</Category>
    <Desc>
      "Internal error in %s. No page number in path %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>64</Id>
    <Category>E</Category>
    <Desc>
      "Could not find module instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>65</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create a %s object for a %s object.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>66</Id>
    <Category>W</Category>
    <Desc>
      "Could not find property %s for %s %s.
      "
    </Desc>
    <ExtDesc>
      "This error typically occurs because certain properties are missing in the property file. To resolve this error, run File > Save Hierarchy in Design Entry HDL then package the design. If the problem persists, contact Cadence Customer Support."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>67</Id>
    <Category>E</Category>
    <Desc>
      "Old path name '%s' not relative for primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error occurs because a BODY_NAME property is present with different values in a body file and chips.prt file. If a BODY_NAME property appears in a body file and the chips.prt file for any part, it should have the same property value. Ensure that if a BODY_NAME property appears in a body file and the chips file for any part, it should have the same property value."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>68</Id>
    <Category>E</Category>
    <Desc>
      "Illegal expansion type specified in %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>69</Id>
    <Category>E</Category>
    <Desc>
      "Could not load this design because of compilation errors.
      Refer to the cmplog.dat file to determine what errors occurred. Fix the errors and package again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>70</Id>
    <Category>E</Category>
    <Desc>
      "Illegal directive type specified in %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>71</Id>
    <Category>W</Category>
    <Desc>
      "Closing quote was missing on line %d. Ensure that a closing quote is present at the end of the state/chips.prt file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>72</Id>
    <Category>E</Category>
    <Desc>
      "A mismatch in the number of sections occurred on line %d while parsing logical pins.
      To avoid such errors, use Part Developer instead of manually editing the library part definition.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>73</Id>
    <Category>E</Category>
    <Desc>
      "Illegal class type specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>74</Id>
    <Category>E</Category>
    <Desc>
      "End of file encountered while parsing %s.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when the packager state file or a chips.prt file ended while a particular section was being parsed. You might have forgotten to terminate the chips.prt file with the END. keyword. Ensure that you have defined the chips.prt file properly and terminated it with the END.keyword. Note that a period ( . ) follows the END keyword. For more information about creating the chips.prt file, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>75</Id>
    <Category>E</Category>
    <Desc>
      "Expected %s on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when Packager-XL expects a particular type of data while parsing the packager state file or a chips.prt file. The name of that data type is mentioned in the error. Ensure that you have used proper keywords such as end_primitive at the right places."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>76</Id>
    <Category>E</Category>
    <Desc>
      "Null argument specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>77</Id>
    <Category>E</Category>
    <Desc>
      "Could not open file %s.
      You might be trying to reuse a design with an inaccessible state file. To reuse a design, ensure that the design being reused is treated as a subdesign and the subdesign state file is accessible and readable. To create the subdesign state file, use the GEN_SUBDESIGN directive.
      "
    </Desc>
    <ExtDesc>
      "This is a generic error message generated when the output file is missing. Ensure that the file mentioned in the error is available with the right access permissions. If you are trying to reuse a design, ensure that the design being reused is treated as a subdesign. The subdesign state file should be accessible and readable. To create the subdesign state file, use the GEN_SUBDESIGN directive. For instance, in the above example, run Packager-XL with the following directive: GEN_SUBDESIGN = DESIGN1 (where DESIGN1 represents the root design). This will create the pxl_DESIGN1.state file, which is required for effective design reuse."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>78</Id>
    <Category>E</Category>
    <Desc>
      "Expected 'BODY_NAME = %s' on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>79</Id>
    <Category>E</Category>
    <Desc>
      "Power net name expected before '%c' character in 'POWER_PINS' = '%s'. The ':' might be missing or there is an extra ';' character. To prevent such syntax problems, avoid manual editing of the property and use the Assign Power Pins dialog box.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when the POWER_PINS definition in the chips.prt file does not conform to the syntax. Ensure that the POWER_PINS property is properly defined. Check that you have used a colon to separate the supply name from the pin list and used a semicolon to separate each supply specification."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>80</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create power pin for body part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>81</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create power sec pin %s for body part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>82</Id>
    <Category>E</Category>
    <Desc>
      "Invalid separator character '%c' found on line %d.
      In case chips.prt is being loaded, check the logical pin section in chips.prt for this part. To avoid such errors, use Part Developer instead of manually editing the library part.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>83</Id>
    <Category>E</Category>
    <Desc>
      "Could not create property %s for body part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>84</Id>
    <Category>E</Category>
    <Desc>
      "Extraneous text found on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have added some extra unrecognizable characters on a line in the chips.prt file where Packager-XL is expecting a standard delimiter such as quote, semicolon, or colon. Ensure that you have removed all extra characters from the line reporting the error. If a standard delimiter is expected, add it."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>85</Id>
    <Category>E</Category>
    <Desc>
      "The '(' character for PIN_NUMBER is missing from line %d. Ensure the PIN_NUMBER range is enclosed within the '(' and ')' characters.To avoid such errors, use Part Developer instead of manually editing the library part definition.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you do not add the quotes to separate the PIN_NUMBER range in the chips.prt file. As a result, Packager-XL is unable to load the chips.prt file. Ensure that you have separated the PIN_NUMBER range with the ( and ) characters."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>86</Id>
    <Category>E</Category>
    <Desc>
      "Null pin name found for PIN_NUMBER on line %d. To avoid such problems, use Part Developer to edit library parts instead of manually editing them.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when you have not defined any pin number in the PIN_NUMBER range in the chips.prt file. As a result, Packager-XL is unable to load the chips.prt file. Ensure that you specify at least one valid PIN_NUMBER or specify a valid PIN_NUMBER range in the chips.prt file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>87</Id>
    <Category>E</Category>
    <Desc>
      "Wrong number of PIN_NUMBER vector pins on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>88</Id>
    <Category>E</Category>
    <Desc>
      "Invalid %s pin in PIN_NUMBER range on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you use an invalid pin width in the PIN_NUMBER range. Ensure that you have defined a valid PIN_NUMBER range for the physical pin corresponding to the logical pin name."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>89</Id>
    <Category>E</Category>
    <Desc>
      "Expected '..' PIN_NUMBER range specifier on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>90</Id>
    <Category>E</Category>
    <Desc>
      "Invalid PIN_NUMBER repeat factor on line %d. Expecting an integer value after '*' character.
      "
    </Desc>
    <ExtDesc>
      "This error is caused when you use an invalid character for defining the PIN_NUMBER range for vector pins. For instance, in the following example, an asterisk ( * ) is used as part of the PIN_NUMBER range. For vector pins, specify the PIN_NUMBER range explicitly, as shown below:
      PIN_NUMBER='(&lt;13,14,15,1&gt;,&lt;13,14,15,1&gt;,&lt;13,14,15,1&gt;,&lt;13,14,15,1&gt;)'
      However, you can use an asterisk character for defining the PIN_NUMBER range for scalar pins, as follows:
      'ad'&lt;0&gt;: pin_number='(13*4)'; 'ad'&lt;1&gt;: pin_number='(14*4)'; 'ad'&lt;2&gt;: pin_number='(15*4)'; 'ad'&lt;3&gt;: pin_number='(1*4)'"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>91</Id>
    <Category>E</Category>
    <Desc>
      "Misplaced PIN_NUMBER range specifier on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>92</Id>
    <Category>E</Category>
    <Desc>
      "Invalid PIN_NUMBER separator on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>93</Id>
    <Category>E</Category>
    <Desc>
      "Common path names do not match for '%s' and '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>94</Id>
    <Category>E</Category>
    <Desc>
      "Could not find %d sections for packaging the following primitive instance in physical part '%s'. Different common pins defined across desired sections.
      Primitive Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>95</Id>
    <Category>I</Category>
    <Desc>
      "State file primitive %s has been deleted from the design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>96</Id>
    <Category>E</Category>
    <Desc>
      "State file(s) already loaded for design %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>97</Id>
    <Category>E</Category>
    <Desc>
      "State file package pin %s not found for physical part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>98</Id>
    <Category>E</Category>
    <Desc>
      "Properties not propagated for %s %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>99</Id>
    <Category>E</Category>
    <Desc>
      "State file previously written for design %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>100</Id>
    <Category>E</Category>
    <Desc>
      "State file not written for design %s.
      "
    </Desc>
    <ExtDesc>
      "This error message appears with other error messages, which indicate why the state file was not written. To fix this error, you need to fix the other errors in the Packager-XL run."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>101</Id>
    <Category>E</Category>
    <Desc>
      "Primitive %s is not packaged.
      "
    </Desc>
    <ExtDesc>
      "This error message appears with other error messages, which indicate why the primitive instance was not packaged. To fix this error, you need to fix the other errors (ERROR 1131 and ERROR 1137 ) in the Packager-XL run. This error occurs because two pin numbers were swapped across two different pin groups, and one pin was not found in the physical part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>102</Id>
    <Category>E</Category>
    <Desc>
      "Could not find module %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>103</Id>
    <Category>E</Category>
    <Desc>
      "Could not find %s '%s' for %s '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>104</Id>
    <Category>E</Category>
    <Desc>
      "Physical net name '%s' loaded from state file for net '%s' is NOT unique. A new net name will be synthesized.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>105</Id>
    <Category>W</Category>
    <Desc>
      "Physical net names will be replaced by names from the state file or re-synthesized.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>106</Id>
    <Category>E</Category>
    <Desc>
      "Same pin name '%s' specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>107</Id>
    <Category>E</Category>
    <Desc>
      "Pin '%s' not found for package instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>108</Id>
    <Category>E</Category>
    <Desc>
      "Cannot swap because pins '%s' and '%s' are not in the same section for package instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>109</Id>
    <Category>E</Category>
    <Desc>
      "Cannot swap common pin '%s' on package instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>110</Id>
    <Category>E</Category>
    <Desc>
      "Physical part id not associated with specified design view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>111</Id>
    <Category>E</Category>
    <Desc>
      "Phys part name information corrupt for:
      Schematic instance: %s
      This error can be corrected by performing the following steps:
      1. Delete the schematic instance listed above
      2. Package the design
      3. Re-add the schematic instance
      4. Package the design again
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have accidentally deleted information from packaging files. Do not manually edit packaging files. You can correct this error by deleting the schematic instance listed in the error message, packaging the design, re-adding the schematic instance, and packaging the design again."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>112</Id>
    <Category>E</Category>
    <Desc>
      "Illegal subtype '%s' specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>113</Id>
    <Category>E</Category>
    <Desc>
      "Physical part %s already exists. Alternate part not created.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>114</Id>
    <Category>E</Category>
    <Desc>
      "Duplicate physical part name %s found on line %d in %s. Edit the chips.prt file to remove the duplicate entry from the primitive name.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>115</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Cannot copy section pins for phys part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>116</Id>
    <Category>E</Category>
    <Desc>
      "PPT part id not associated with specified design view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>117</Id>
    <Category>E</Category>
    <Desc>
      "Parent object not specified. '%s' object not deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>118</Id>
    <Category>E</Category>
    <Desc>
      "Cannot delete a '%s' type object for a '%s' type object.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>119</Id>
    <Category>E</Category>
    <Desc>
      "'%s' object not owned by specified parent. Object not deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>120</Id>
    <Category>E</Category>
    <Desc>
      "Package instance previously deleted from design view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>121</Id>
    <Category>E</Category>
    <Desc>
      "Package instance %s is used. Object not deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>122</Id>
    <Category>E</Category>
    <Desc>
      "Package instance not in specified view. Object not deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>123</Id>
    <Category>W</Category>
    <Desc>
      "Package instance deleted after state file written.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>124</Id>
    <Category>W</Category>
    <Desc>
      "Pin '%s' not found in design for primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error might also occur when incorrect logical pin names are assigned in the PACK_SHORT property. Update the property value with the correct logical pin names.

      Example:

      Pin 'A0' not found in design for the primitive instance '@TEST_LIB.D1(SCH_~1):PAGE1_I3@LSTTL.LS00(CHIPS)'.

      Explanation: In the design, the correct logical pin names are A&lt;0&gt;, B&lt;0&gt;. However, the PACK_SHORT property is assigned as follows:

      PACK_SHORT = (A0, B0)

      Solution: Update the property value with the correct logical pin names. In the given example, the correct logical pin names should be assigned as:

      PACK_SHORT = (A&lt;0&gt;, B&lt;0&gt;)"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>125</Id>
    <Category>E</Category>
    <Desc>
      "State file properties for %s '%s' not used.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>126</Id>
    <Category>W</Category>
    <Desc>
      "State file pin swap info for pin '%s' not used.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>128</Id>
    <Category>E</Category>
    <Desc>
      "Load state file error. Part name conflict found for '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you change the logical part name in a subdesign after packaging it in the root design. This prevents Packager-XL from loading the subdesign state file. You can correct this error by deleting all instances of this subdesign from the root design, packaging the root design, then adding the subdesign instances to the root design and packaging again. Or, change the instance back to its original name and generate the subdesign. Then package the root design again."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>129</Id>
    <Category>E</Category>
    <Desc>
      "Load state file error. Cannot find section %d for physical part %s associated with state file primitive instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>131</Id>
    <Category>E</Category>
    <Desc>
      "Cannot set pin number for pin %s owned by object of type '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>132</Id>
    <Category>E</Category>
    <Desc>
      "State file view previously created for design %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>133</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Physical part %s already associated with PPT part %s. Cannot create new PPT physical part.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>134</Id>
    <Category>E</Category>
    <Desc>
      "Alternate phys part %s previously created using physical part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>135</Id>
    <Category>E</Category>
    <Desc>
      "Physical part name not specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>136</Id>
    <Category>E</Category>
    <Desc>
      "Illegal section count specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>137</Id>
    <Category>E</Category>
    <Desc>
      "Duplicate section numbers specified in list to swap.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>138</Id>
    <Category>E</Category>
    <Desc>
      "Illegal section number specified in swap list for primitive instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>139</Id>
    <Category>E</Category>
    <Desc>
      "Internal database error. Cannot swap sections. Sections don't contain same number of pins.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>140</Id>
    <Category>E</Category>
    <Desc>
      "Internal database error. Cannot swap pins %s and %s. Pins don't share same basename.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>141</Id>
    <Category>E</Category>
    <Desc>
      "Illegal pin swap count specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>142</Id>
    <Category>E</Category>
    <Desc>
      "Pin %s for primitive instance %s is not packaged in the list of pins to swap to. Possible pin is in different section. Cannot swap pins.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>143</Id>
    <Category>E</Category>
    <Desc>
      "Physical part name %s conflicts with logical part name %s for instance %s. %s not performed.
      "
    </Desc>
    <ExtDesc>
      "This error is displayed when the design is packaged. This error occurs if the PART_NAME property is defined on the schematic part, but the value of this property is not the same as the logical name of the part. If PART_NAME is defined in the chips.prt file, this property need not be defined in the schematic. If the property is defined on the schematic part, update the value of this property so it is the same as the logical name of the part, as it appears in the chips.prt file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>144</Id>
    <Category>E</Category>
    <Desc>
      "Instance %s currently packaged in package of type %s. Cannot change phys part.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>145</Id>
    <Category>E</Category>
    <Desc>
      "File %s is a directory. Cannot load.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>146</Id>
    <Category>E</Category>
    <Desc>
      "Unable to perform %s operation. Contact Cadence Customer Support.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>147</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Sized primitive instance %s has no vectored pins.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>148</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Could not create top module %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>149</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Could not create module %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>150</Id>
    <Category>W</Category>
    <Desc>
      "Name '%s' found in '%s'. Name not added to '%s'.
      "
    </Desc>
    <ExtDesc>
      "You can add a subdesign name in either the FORCE SUBDESIGN list or the USE SUBDESIGN list but not in both lists. If you add a subdesign name in both, the FORCE SUBDESIGN, and USE SUBDESIGN lists, Packager-XL uses the FORCE SUBDESIGN directive to package the subdesign."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>151</Id>
    <Category>E</Category>
    <Desc>
      "Net count mismatch in sort table for design %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>152</Id>
    <Category>I</Category>
    <Desc>
      "Physical net name '%s' for net '%s' is not unique. A new net name will be synthesized.
      "
    </Desc>
    <ExtDesc>
      "This message is generated when the physical net name of a net is not unique in the design. In such cases, Packager-XL generates a new unique net name. For example, you get this information message when the same subdesign is reused more than once in the top level design."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>153</Id>
    <Category>E</Category>
    <Desc>
      "Part name %s has multiple parent phys part names associated with it in the %s.
      The possible cause could be that a COMP_DEF_PROPERTY has been added in the reuse block which results in change of the part name in the root design. Increase the part name length to a larger value in the Part Type Length field on the Packager Setup dialog box and package again in preserve mode.
      "
    </Desc>
    <ExtDesc>
      "This error will not occur if a state file generated by Packager-XL is used. But if you have modified the state file and changed the base physical part name for an alternate physical part, this error can occur. A possible cause for the error could be that a COMP_DEF_PROPERTY has been added in the reuse block which results in a change of the part name in the root design. Increase the part name length to a larger value in the Part Type Length field on the Packager Setup dialog box and package again in preserve mode."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>154</Id>
    <Category>W</Category>
    <Desc>
      "Package %s is not used.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>155</Id>
    <Category>E</Category>
    <Desc>
      "Existing state file was generated for another design. State file not loaded for %s '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>156</Id>
    <Category>E</Category>
    <Desc>
      "Page %s not found in design for module %s of type %s.
      Information for the page is available in the pxl subdesign state file of the module but not present in the schematic.
      To update the subdesign state file, set the module as root and package. Once the subdesign state file is corrected, set the top as root and package again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>157</Id>
    <Category>E</Category>
    <Desc>
      "The hierarchy in the state file for subdesign %s does not match the hierarchy in the design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>158</Id>
    <Category>E</Category>
    <Desc>
      "Conflicting pkg names for multi-sectioned part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>159</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find PPT %s when loading state file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>160</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find PPT phys part %s when loading state file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>161</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find or create phys part %s when loading state file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>162</Id>
    <Category>E</Category>
    <Desc>
      "PPT part name '%s' for PPT '%s' is not unique in the part_table view.
      "
    </Desc>
    <ExtDesc>
      "This error message appears when multiple rows are defined in the part table with the same name. This can result from duplicate names or suffixes assigned to the row or duplicate key properties. As a result of this error, Packager-XL also generates Error 47.You can fix the problem by assigning a unique name or suffix to the PPT row. If you use different PPT definition formats such as ~ or !, the part name created after merging the PPT rows is unique."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>163</Id>
    <Category>W</Category>
    <Desc>
      "Case-sensitivity is not supported for the name of property '%s'. Ignoring your request to make this case-sensitive.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>164</Id>
    <Category>E</Category>
    <Desc>
      "Could not open file %s in write mode.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>165</Id>
    <Category>E</Category>
    <Desc>
      "Maximum %s name length allowed is %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>166</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create a unique physical name for net '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>167</Id>
    <Category>E</Category>
    <Desc>
      "Syntax error in pack short value for property '%s' on primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>168</Id>
    <Category>E</Category>
    <Desc>
      "Nets not shorted for primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>169</Id>
    <Category>E</Category>
    <Desc>
      "Physical part name '%s' exceeds the maximum set length of %d characters.
      If you have reduced the value for the PART_TYPE_LENGTH directive since the last time the design was packaged, the pxl.state file might contain part names that are longer than the new PART_TYPE_LENGTH. Increase the maximum permissible part name length in the Packager Setup dialog box.
      "
    </Desc>
    <ExtDesc>
      "This error is generated if a physical part name exceeds the maximum specified length for net names, which is controlled by the PART_TYPE_LENGTH directive. The default PART_TYPE_LENGTH is 31. This error is typically generated when you have packaged the design once and then reduced the value in the PART_TYPE_LENGTH directive. This may cause data in the pxl.state file to contain part names whose length exceeds the PART_TYPE_LENGTH value. If you now package the design, Packager-XL will generate this error. Increase the maximum permissible part name length by entering a new value in the Part Type Length field in the Packager Setup - Layout tab."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>170</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create a unique %s name from '%s'. Increase the maximum permissible part name length in the Packager Setup dialog box.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when a unique name cannot be found within the maximum length allowed for defining a part name. Increase the maximum permissible part name length by entering a new value in the Part Type Length field in the Packager Setup - Layout tab."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>171</Id>
    <Category>E</Category>
    <Desc>
      "Error deleting old version of archives - %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>172</Id>
    <Category>E</Category>
    <Desc>
      "Error renaming %s to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>173</Id>
    <Category>E</Category>
    <Desc>
      "Error found while parsing POWER_PINS for %s.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when Packager-XL parses a POWER_PINS property value that has a syntax error. Ensure that the POWER_PINS property is defined using the following syntax: POWER_PINS=(supply:pin list; supply:pin list; ...)"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>174</Id>
    <Category>E</Category>
    <Desc>
      "Error found while parsing POWER_GROUP for %s.
      Property value - %s."
    </Desc>
    <ExtDesc>
      "This error occurs when Packager-XL parses a POWER_GROUP property value that has a syntax error. Ensure that the POWER_GROUP property is defined using the following syntax: POWER_GROUP = supply=newsupply [;supply=newsupply...][(subtype_name)]"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>175</Id>
    <Category>E</Category>
    <Desc>
      "                    Property value - %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>176</Id>
    <Category>E</Category>
    <Desc>
      "Power pin '%s' not found for physical part '%s'. Refer to property 'POWER_GROUP' = '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>177</Id>
    <Category>E</Category>
    <Desc>
      "Power pin '%s' is not unique for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>178</Id>
    <Category>E</Category>
    <Desc>
      "Physical net name '%s' loaded from the state file exceeds the maximum set length of %d characters.
      You might have changed the maximum physical net name length since the state file was last generated. To correct this, change the net name length in the Packager Setup dialog box or select the option of regenerating physical net names while packaging.
      "
    </Desc>
    <ExtDesc>
      "This error occurs if you change the net length option after successfully running Export Physical once. The error is reported in the pxl.log file. The Packager tries to preserve physical net names from the previous run (assuming the 'Preserve' option is selected). Ensure that the Regenerate Physical Net Names check box is selected in the Export Physical dialog box and re-run Export Physical. This will regenerate all the physical net names to comply with the new character length constraint."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>179</Id>
    <Category>E</Category>
    <Desc>
      "The TIMES property was found on the primitive instance '%s' when loading the design. TIMES expansion is not supported.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>180</Id>
    <Category>W</Category>
    <Desc>
      "The TIMES property was found on primitive instance '%s' when loading an old state file. TIMES expansion is not supported.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>181</Id>
    <Category>I</Category>
    <Desc>
      "Loading %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>182</Id>
    <Category>E</Category>
    <Desc>
      "Check 'PART_NAME' property in chips_prt file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>183</Id>
    <Category>E</Category>
    <Desc>
      "Null property value must be specified using leading/closing quotes on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error is generated if a null value is specified as the key property for a part in a ptf file. You could have accidentally added two property separators back-to-back. You could also have accidentally added a carriage return (End of Line) in place of the tilde ( ~ ) character. This error generally prevents Packager-XL from loading the PTF file properly. As a result of this error, Packager-XL may also generate ERROR 47. If you need to assign a null value to a property, use leading/closing quotes to specify that value."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>184</Id>
    <Category>E</Category>
    <Desc>
      "Flag body pin '%s' for '%s' has neither a 'INPUT_LOAD' or 'OUTPUT_LOAD' property.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>185</Id>
    <Category>W</Category>
    <Desc>
      "The bit size of pin '%s'&lt;%d..%d> is not equal to the section size of %d derived from the 'PIN_NUMBER' property on line %d in file '%s'. The derived section size will be used.
      "
    </Desc>
    <ExtDesc>
      "This warning is generated when you have defined a pin that does not have the same section size as used in the PIN_NUMBER property for that part. If you need to change any properties, edit the chips.prt file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>186</Id>
    <Category>E</Category>
    <Desc>
      "POWER_GROUP = '%s' was found on line %d in '%s'. This property will be ignored.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>187</Id>
    <Category>E</Category>
    <Desc>
      "Power pin '%s' also appears as a non-power pin in section %d for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when the same pin is defined as a power and non-power pin in a section of a physical part in the chips.prt file. As a result of this error, Packager-XL may also generate ERROR 1084. Ensure that for each section of a physical part, a pin is defined as either a power pin or a non-power pin but not as both."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>188</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find pins specified in swap list for primitive instance %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>189</Id>
    <Category>E</Category>
    <Desc>
      "Vectored pin name '%s' terminated early on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have used a vector pin but have not terminated it with the closing angle bracket '>' character in the chips.prt file. Ensure that all vectored pin names conform to the following syntax: pin_name&lt;higher_pin_number..lower_pin_number&gt;"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>190</Id>
    <Category>E</Category>
    <Desc>
      "Illegal pin range notation in pin name '%s' on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have used a vector pin but have not specified the lower and upper bus range or forgot to use two periods (..) as the separator for the pin range. Ensure that all vectored pin names conform to the following syntax: pin_name&lt;higher_pin_number..lower_pin_number&gt;"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>191</Id>
    <Category>E</Category>
    <Desc>
      "Illegal '%c' character found in pin name '%s' on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>192</Id>
    <Category>I</Category>
    <Desc>
      "Swapped section %d with section %d for the primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      "This message is generated for information purposes. It notifies you that a section swap for a primitive instance has occurred."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>193</Id>
    <Category>I</Category>
    <Desc>
      "
      The following pins were swapped in %s for primitive instance '%s':
      "
    </Desc>
    <ExtDesc>
      "This message is generated for information purposes. It notifies you that a pin swap for a primitive instance has occurred."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>194</Id>
    <Category>I</Category>
    <Desc>
      "  Pin %s was swapped from %s to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>195</Id>
    <Category>I</Category>
    <Desc>
      "By default logical pin '%s' would be assigned to section %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>196</Id>
    <Category>I</Category>
    <Desc>
      "Logical pin '%s' swapped to section %s in state file.

      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>197</Id>
    <Category>I</Category>
    <Desc>
      "Propagating section swaps from state file for primitive instance '%s' of type '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>198</Id>
    <Category>W</Category>
    <Desc>
      "Phys part '%s' not found for primitive instance '%s' with property 'PACK_TYPE' = '%s'.
      "
    </Desc>
    <ExtDesc>
      "This warning occurs when you have assigned the value NULL to the PACK_TYPE property and have also defined the SIZE property. If you have a sizeable part, ensure that the PACK_TYPE property has a valid value."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>199</Id>
    <Category>E</Category>
    <Desc>
      "Cannot create alternate phys part '%s' with grandparent PPT phys part.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>200</Id>
    <Category>E</Category>
    <Desc>
      "Did not find a %s%s for part name '%s' in the %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>201</Id>
    <Category>E</Category>
    <Desc>
      "PPT '%s' and PPT part '%s' found in the %s are not associated in the PPT view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>202</Id>
    <Category>E</Category>
    <Desc>
      "Unexpected token '%s' found on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs if the pxl.state file contains a wrong keyword. This error will not occur if you use a pxl.state file generated by the Packager-XL. Do not edit the pxl.state file. Use Packager-XL to generate the pxl.state and *.pst feedback files."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>203</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find PPT part %s when loading state file.
      "
    </Desc>
    <ExtDesc>
      "This warning appears for all single node nets. The message is for information purposes. If you do not want Packager-XL to display the warning, assign the following property: NO_SINGLE_CHECK=TRUE"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>204</Id>
    <Category>E</Category>
    <Desc>
      "Part name '%s' maps to '%s' and '%s' in the %s.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when LONG_PART_NAME is different for the part in the top level and in the subdesign files. To resolve this, package the subdesign blocks again then package the top-level block. If the problem persists, contact Cadence Customer Support."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>205</Id>
    <Category>W</Category>
    <Desc>
      "The state file is empty.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>206</Id>
    <Category>E</Category>
    <Desc>
      "Expected '%c' character in 'POWER_PINS' = '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error appears when the starting delimiter, the ( character, is missing from the POWER_PINS property definition in a chips.prt file. As a result of this error, Packager-XL can also generate more errors such as ERROR 206 and ERROR 1084. Ensure that you have defined the POWER_PINS property properly using the following syntax: POWER_PINS=(supply:pin list; supply:pin list; ...) For details about the POWER_PINS property, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>207</Id>
    <Category>E</Category>
    <Desc>
      "'POWER_PINS' property value '%s' terminated early.
      "
    </Desc>
    <ExtDesc>
      "This error appears when the ending delimiter, the ) character, is missing from the POWER_PINS property definition in a chips.prt file. Ensure that you have defined the POWER_PINS property properly using the following syntax: POWER_PINS=(supply:pin list; supply:pin list; ...)"
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>208</Id>
    <Category>E</Category>
    <Desc>
      "Extra text after '%c' character in 'POWER_PINS' = '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error appears when you have placed extra text after the ')' character in the POWER_PINS property in a chips.prt file. The ')' character is the ending delimiter. As a result of this error, Packager-XL can also generate more errors such as ERROR 210 and ERROR 1084. Ensure that you have no extra text after the ) character in the POWER_PINS property definition."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>209</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load power pins in property on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>210</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load power pins for alternate phys part '%s'.
      There might be syntax errors in the power pins value assignment. To prevent such problems, use the Assign Power Pins dialog box to edit properties.
      "
    </Desc>
    <ExtDesc>
      "This error message appears with other error messages, which indicate why Packager-XL is unable to read power signals. Fix the cause of the other error that prevents Packager-XL from reading properties correctly."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>211</Id>
    <Category>E</Category>
    <Desc>
      "Token '%s' was terminated by a carriage return on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you forget to place a semicolon ( ; ) as the last character in the property header row in a ptf file. As a result of this error, Packager-XL also generates Error 47. Ensure that the property header row for a part is terminated with a semicolon ( ; ) and fix the error in the ptf file listed in ERROR 47."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>212</Id>
    <Category>E</Category>
    <Desc>
      "Could not merge PPT parts for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>213</Id>
    <Category>E</Category>
    <Desc>
      "%s property name:value '%s:%s' clashes with '%s' for PPT '%s'. Multiple property name:value pairs might exist for a particular PPT property in the part table files that are being merged. Ensure that each PPT has a unique property name:value pair. Fix one of the property name:value pairs listed in this message.
      "
    </Desc>
    <ExtDesc>
      "This error occurs in situations where multiple property name:value pairs exist for a particular property of a PPT in a ptf file. Often, this error causes another error such as ERROR 47. For example, an injected property for a PPT has two values, such as 1K and 1000, or the same PPT is loaded from two different files and both files have different values for the CLASS property. In such a scenario, injected property values of 1K and 1000 were specified in two or more part rows, which should be merged because the key properties on the corresponding rows can be merged. Ensure that each PPT has a unique property name:value pair. Fix one of the property name:value pairs listed in the error."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>214</Id>
    <Category>E</Category>
    <Desc>
      "Multiple PPT part '%s' found when merging PPT '%s'. If multiple rows exist by the same name, multiple values of a key property must match and multiple values of an injected property must match.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when multiple PPT parts with the same name exist and this prevents Packager-XL from merging PPT parts. If multiple rows exist by the same name, multiple values of a key property must match and multiple values of the injected property must also match. Check the key property values for VALUE. Check the injected property values for PART_NUMBER."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>215</Id>
    <Category>I</Category>
    <Desc>
      "Merging part rows for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>216</Id>
    <Category>I</Category>
    <Desc>
      "Created merged part '%s' for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>217</Id>
    <Category>E</Category>
    <Desc>
      "Following part row for PPT '%s' was not merged:
      "
    </Desc>
    <ExtDesc>
      "This error occurs when two or more PPT rows cannot be merged together for the same PPT part. This error can occur if there are multiple tables in one file preventing the merging of a PPT part row. Using a dump of what the part row looks like and the file from which it is loaded, you can determine where the table is located and fix the error. It is a good practice to have PPT rows for a part in one table to reduce the chance of PPT merging errors. Ensure that if PPT rows are defined for the same part in multiple files, they have a consistent definition, and each PPT row has a unique PPT value."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>218</Id>
    <Category>E</Category>
    <Desc>
      "Property '%s' appears as both '%s' and '%s' for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      "The above error occurs when a property is defined as global in one PPT row for a part and as injected in another row for the PPT part in the ptf files. This error may occur if you have two sets of PPT row definitions for the same part in one ptf file or across two ptf files. If the error occurs because of different definitions for the same part in two files, Packager-XL also generates ERROR 221. Define the PPT definition for a part in only one file and in one part definition. This will ensure that you have only one set of global properties."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>219</Id>
    <Category>E</Category>
    <Desc>
      "Default values of '%s' and '%s' found for key property '%s' for PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>220</Id>
    <Category>E</Category>
    <Desc>
      "Different property scopes found for key property '%s' for PPT '%s'.
      Check the part table files that are being loaded for this part and ensure that the PTF headers in these files are consistent.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>221</Id>
    <Category>E</Category>
    <Desc>
      "PPT '%s' was loaded from the following files:
      "
    </Desc>
    <ExtDesc>
      "This error occurs when a PPT is defined in multiple files. Packager-XL is unable to resolve the PPT to one set of values. As a result of this error, Packager-XL can also generate ERROR 213 and ERROR 47. Define the PPT definition for a part in only one file by listing all required properties and remove the PPT definitions for the part from other files."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>222</Id>
    <Category>I</Category>
    <Desc>
      "PPT part row loaded from file:
      "
    </Desc>
    <ExtDesc>
      "The above error occurs along with ERROR 217 in cases where a PPT part row is not merged. Fix the issue with ERROR 217 to fix this error."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>223</Id>
    <Category>I</Category>
    <Desc>
      "	%s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>224</Id>
    <Category>E</Category>
    <Desc>
      "Check %s property values for '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>225</Id>
    <Category>W</Category>
    <Desc>
      "Quoted value of property '%s' is not closed on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>226</Id>
    <Category>E</Category>
    <Desc>
      "Illegal %s scope specified in call to %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>227</Id>
    <Category>E</Category>
    <Desc>
      "Design '%s' is empty.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>228</Id>
    <Category>E</Category>
    <Desc>
      "Cannot package the following primitive instance in any section of the physical part '%s'.
      Primitive Instance: %s
      The primitive instance has pins which does not match the section definition in chips.prt. Check the pin definitions for each section in the chips.prt file. Regenerate the netlist and rerun packager.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when the entity/verilog.v file is not in sync with the physical part used in the design and Packager-XL fails to package the primitive instance in any of the sections of the physical part. Rewrite the part symbols with the new name. This will create a new entity/verilog.v file and then package the design."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>229</Id>
    <Category>E</Category>
    <Desc>
      "Part selection not performed. Refer to previous error(s) regarding attempt to merge PPT '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error is followed by error 217, when the Packager fails to merge two or more PPT rows together for the same PPT part. There could be multiple tables in one file preventing the merging of a PPT part row. As a result, part selection cannot be performed. You should have all the PPT rows for a part in one table. This reduces the chances of any PPT merging problems. If PPT rows are defined for the same part in multiple files, ensure that they have a consistent definition and each PPT row results in a unique PPT value."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>230</Id>
    <Category>W</Category>
    <Desc>
      "Can't determine installation path for file '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>231</Id>
    <Category>W</Category>
    <Desc>
      "Allegro properties '%s' and '%s' both truncated to '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>232</Id>
    <Category>W</Category>
    <Desc>
      "Can't open Allegro property file '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>233</Id>
    <Category>E</Category>
    <Desc>
      "Out of Memory!
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>234</Id>
    <Category>W</Category>
    <Desc>
      "Truncated Allegro property names will not be expanded.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>235</Id>
    <Category>E</Category>
    <Desc>
      "Cannot shorten name '%s' specified using %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>236</Id>
    <Category>E</Category>
    <Desc>
      "Reserved name '%s' specified illegally multiple times.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>237</Id>
    <Category>E</Category>
    <Desc>
      "A %s was not specified in call to routine %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>238</Id>
    <Category>W</Category>
    <Desc>
      "The subdesign state file for %s is out-of-sync with the design.
      The schematic for this module might have been updated with a different root design. Update the subdesign state file by packaging this module as the root design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>239</Id>
    <Category>E</Category>
    <Desc>
      "Conflicting directives '%s' and '%s' were specified. Directive '%s' will be ignored.
      "
    </Desc>
    <ExtDesc>
      "You have defined the same file in both, the INCLUDE_PPT, and EXCLUDE_PPT directives. This causes Packager-XL to ignore the EXCLUDE_PPT directive for that file. You cannot include and exclude the same ptf file while packaging a design. If a file is listed in the INCLUDE_PPT and EXCLUDE_PPT directives, the file is considered to be included for packaging. The EXCLUDE_PPT directive is ignored. If you want the file to be excluded while packaging, remove its name from the INCLUDE_PPT list."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>240</Id>
    <Category>E</Category>
    <Desc>
      "Illegal pin name '%s' specified to contain range notation.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>241</Id>
    <Category>E</Category>
    <Desc>
      "Power nets %s and %s have same power pin %s on physical part %s.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when multiple power nets have a common power pin for a physical part. To correct the error, remove the common pin from one of the power nets in the chips.prt file for the given part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>242</Id>
    <Category>E</Category>
    <Desc>
      "Cannot determine legal range for pins '%s' and '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error is caused when you use an invalid PIN_NUMBER range. For instance, when a negative number is used as part of the PIN_NUMBER range. As a result of this error, Packager-XL can also generate ERROR 88. Ensure that you have defined a valid PIN_NUMBER range for the physical pin corresponding to the logical pin name."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>243</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load pin section for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>244</Id>
    <Category>E</Category>
    <Desc>
      "Pin name '%s' is not unique.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>245</Id>
    <Category>E</Category>
    <Desc>
      "Sizable pins must have unique base name. Bit range found for pin with non-unique base name of '%s' for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>246</Id>
    <Category>E</Category>
    <Desc>
      "No physical pins found for logical pin '%s' on physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error message occurs when you have specified a logical pin name but have not specified a corresponding physical pin. To specify a physical pin, use the following syntax:
      pin
      'logical_pin_name' &lt;bit_number&gt; :
      PIN_NUMBER='(&lt;physical_pin_number&gt;, &lt;physical_pin_number2&gt;, ...)';
      property1='(value1, value2, ...)';
      property2='(value1, value2, ...)';
      end_pin;

      To fix the problem, ensure that a physical pin is specified for the logical pin. For more information about the chips.prt file, see the documentation."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>247</Id>
    <Category>E</Category>
    <Desc>
      "No logical pins found for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>248</Id>
    <Category>E</Category>
    <Desc>
      "Part '%s' cannot be used because there are no unique physical pins in section '%d'. Open and edit the part to ensure that there is at least one unique pin in each section of the physical part."
    </Desc>
    <ExtDesc>
      "This error occurs when all pins for a section are common. Ensure that you have at least one non-common pin for each section of a physical part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>249</Id>
    <Category>E</Category>
    <Desc>
      "The width of pin '%s' does not equal the size of %d for primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>250</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Expanded instance '%s' not found.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>251</Id>
    <Category>E</Category>
    <Desc>
      "Design not loaded.
      "
    </Desc>
    <ExtDesc>
      "This error message is always generated with another error message that is more informative. To fix the problem, fix the issue listed in the other error message."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>252</Id>
    <Category>E</Category>
    <Desc>
      "Instance does not match physical part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>253</Id>
    <Category>I</Category>
    <Desc>
      "Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>254</Id>
    <Category>E</Category>
    <Desc>
      "Invalid common pins swap, PN: %s, Pkg: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>255</Id>
    <Category>E</Category>
    <Desc>
      "Cannot swap common pins %s and %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>256</Id>
    <Category>E</Category>
    <Desc>
      "Pins must be defined for same set of sections in phys part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>257</Id>
    <Category>E</Category>
    <Desc>
      "Property %s found on more than one module instance of %s (%s and %s).
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>258</Id>
    <Category>E</Category>
    <Desc>
      "Power pins are not associated with a section. Pin '%s' is a power pin.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>259</Id>
    <Category>E</Category>
    <Desc>
      "Internal error. Cannot determine parent of %s '%s' in call to routine '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>260</Id>
    <Category>E</Category>
    <Desc>
      "Pin '%s' for primitive instance '%s' does not map to a logical pin in the chips_prt. Sizable pins must map to a pin with a unique base name.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>261</Id>
    <Category>E</Category>
    <Desc>
      "'%s' object not owned by specified parent. Cannot rename it.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>262</Id>
    <Category>E</Category>
    <Desc>
      "Expected %s while parsing 'NC_PINS' = '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have defined the NC_PINS property but have not assigned the leading or closing quote. Depending on whether the leading or closing quote is missing, the error message will show the appropriate missing character. While checking for the cause of this error, check the assignment for the NC_PINS or MERGE_NC_PINS property. To avoid this error, ensure that all NC_PINS or MERGE_NC_PINS property value definitions are enclosed within leading and closing quotes."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>263</Id>
    <Category>E</Category>
    <Desc>
      "NC_PINS properties were not merged for %s '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have defined an incorrect MERGE_NC_PINS property. You may not have assigned the leading or closing quote. This error may often appear with ERROR 262. Ensure that all NC_PINS or MERGE_NC_PINS property value definitions are enclosed within leading and closing quotes."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>264</Id>
    <Category>E</Category>
    <Desc>
      "Physical pin '%s' is specified for logical pins '%s' and '%s'.The same physical pin number cannot be specified for two or more logical pins.
      "
    </Desc>
    <ExtDesc>
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>265</Id>
    <Category>I</Category>
    <Desc>
      "Cannot create section pin '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>266</Id>
    <Category>E</Category>
    <Desc>
      "System error. Cannot determine current working directory.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>267</Id>
    <Category>E</Category>
    <Desc>
      "Suffix '%s' is assigned to '%s(MODULE: %s)'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>268</Id>
    <Category>W</Category>
    <Desc>
      "Ignoring 'SUBDESIGN_SUFFIX' = '%s' specified for '%s(MODULE: %s)'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>269</Id>
    <Category>E</Category>
    <Desc>
      "The following block instances have same value '%s' specified for the property 'SUBDESIGN_SUFFIX':
      '%s(MODULE: %s)' and
      '%s(MODULE: %s)'.
      The 'SUBDESIGN_SUFFIX' property value needs to be unique across the design.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have specified the same value for the SUBDESIGN_SUFFIX property for two different modules. Packager-XL will use the value of the module it reads first and ignore the value assigned to the second module. To avoid this error, ensure that you have defined different values for the SUBDESIGN_SUFFIX property across different modules."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>270</Id>
    <Category>E</Category>
    <Desc>
      "An internal error occurred. %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>271</Id>
    <Category>E</Category>
    <Desc>
      "Cannot swap suffix from '%s' to '%s' for '%s(MODULE: %s)'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>272</Id>
    <Category>E</Category>
    <Desc>
      "Physical net name '%s' already assigned to net '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>273</Id>
    <Category>W</Category>
    <Desc>
      "Illegal value of %d specified for %s. Using default value of %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>274</Id>
    <Category>E</Category>
    <Desc>
      "Illegal value of %d specified for %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>275</Id>
    <Category>E</Category>
    <Desc>
      "%s '%s' not created.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>276</Id>
    <Category>W</Category>
    <Desc>
      "The state file generated for the root drawing differs from the current root name of '%s'. The names found in the state file will be modified accordingly.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>277</Id>
    <Category>E</Category>
    <Desc>
      "Following Primitive instance of size %d requires %d sections for packaging. Verify the size of the primitive instance is correct. Otherwise, a non-sizable pin on the primitive instance is described as sizable in the chips_prt.
      Primitive Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>278</Id>
    <Category>E</Category>
    <Desc>
      "Design configuration %s not found.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>279</Id>
    <Category>E</Category>
    <Desc>
      "Design configuration %s is of type %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>280</Id>
    <Category>E</Category>
    <Desc>
      "Must be of type LOGIC.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>281</Id>
    <Category>E</Category>
    <Desc>
      "Refer to file 'cmplog.dat' to determine what errors occurred.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>282</Id>
    <Category>E</Category>
    <Desc>
      "Pin '%s' on the following HAS_FIXED_SIZE instance is not sizable. Check the pin definitions for this pin in the chips_prt file.
      Schematic Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>283</Id>
    <Category>W</Category>
    <Desc>
      "Deleting property '%s' = '%s' on this mechanical part:
      "
    </Desc>
    <ExtDesc>
      "Mechanical parts with no pins do not require section assignment. As a result, SEC/$SEC properties are deleted for this part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>284</Id>
    <Category>W</Category>
    <Desc>
      "NC pin '%s' not unique for physical part '%s'. Duplicate will be removed.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>285</Id>
    <Category>E</Category>
    <Desc>
      "NC pin '%s' also defined as a %s for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have defined a NC_PINS property to contain a pin that is already defined as a physical pin (as a PIN_NUMBER property in the chips.prt file). As a result of this error, Packager-XL also generates ERROR 286. Ensure that you have different values for NC pins and physical pins for a physical part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>286</Id>
    <Category>E</Category>
    <Desc>
      "NC pins not unique for %s '%s'.
      "
    </Desc>
    <ExtDesc>
      "The above error occurs when you have defined a NC pin and one or more of those pins are defined as physical pins. This error generally occurs with ERROR 285.
      Example:
      ERROR(285): NC pin '1' also defined as a physical pin for physical part '~
      74LS00-(1,2,3,4,5,6,7)'.
      ERROR(286): NC pins not unique for alternate physical part '74LS00-(1,2,3,4,5,6,7)'.
      ERROR(1084): The alternate physical part '74LS00-(1,2,3,4,5,6,7)' for schematic instance
      @PROJ_LIB.DESIGN(SCH_1):PAGE1_I1@MYTTL.LS00(CHIPS)(MODULE: DESIGN; PART: 74LS00) cannot be created. The physical part might be incorrectly defined. Check the component definition properties (COMP_DEF_PROP) defined on the instance in Design Entry HDL for any possible syntax error. For more information on COMP_DEF_PROP, refer to the Packager documentation.
      Description of Example: The above error was caused as both, the NC_PINS, and PIN_NUMBER property, had a common pin, 1, for part 74LS00.
      Ensure that you have different values for NC pins and physical pins for the same physical part."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>287</Id>
    <Category>E</Category>
    <Desc>
      "No pin of the following instance is connected to pin %s of package %s.
      Schematic Instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>288</Id>
    <Category>E</Category>
    <Desc>
      "Line %d for '%s' is too long.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when a property name definition is longer than the supported length. For example, this error may occur for NC_PINS and POWER_PINS if they have a long definition. If the description of a property is long and you need to retain the entire description, you can break the property definition into two or more lines.
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>289</Id>
    <Category>I</Category>
    <Desc>
      "Part name conflict found for '%s'. This may be updated during packaging.
      Sub Design Part Name   : %s
      Root Design Part Name  : %s
      "
    </Desc>
    <ExtDesc>
      "This error message is generated whenever part names are changed for components in either the subdesign or the root design after the subdesign has been packaged in the root design. The change in part names can occur due to one of the following reasons: change in component definition properties; selection of a different PPT row for the component (by using the Modify command in Design Entry HDL); use of COMP_NAME or COMP_NAME_SUFFIX properties.
      This message is not generated if the subdesign was packaged using USE_SUBDESIGN. Packager-XL picks up the part names from the previous run of the root design packaging and does not read the subdesign state file again, whereas, in the case of FORCE_SUBDESIGN, the part names are read from the subdesign state file for each packaging run."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>290</Id>
    <Category>E</Category>
    <Desc>
      "Could not create hierarchy for EDB occurrence '%s'
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>291</Id>
    <Category>W</Category>
    <Desc>
      "Illegal property '%s' = '%s' found for primitive instance '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>292</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load EDB for lib.cell:view %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>293</Id>
    <Category>E</Category>
    <Desc>
      "EDB is unable to load the design. The .sir file might be missing or incorrect.
      EDB reports:
      %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>294</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load EDB property '%s' of type '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>295</Id>
    <Category>W</Category>
    <Desc>
      "EDB %s '%s' not treated as vectored.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>296</Id>
    <Category>E</Category>
    <Desc>
      "Error occurred while traversing '%s'. Verify you have saved all changes to this cell.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>297</Id>
    <Category>E</Category>
    <Desc>
      "Internal database error. Net '%s' not found.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>298</Id>
    <Category>E</Category>
    <Desc>
      "Cannot extract page number from name '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>299</Id>
    <Category>E</Category>
    <Desc>
      "Error in format of hierarchical signal name '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>300</Id>
    <Category>W</Category>
    <Desc>
      "Extraneous EDB %s found when loading the design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>301</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find path for lib.cell:view '%s.%s:%s'
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>302</Id>
    <Category>E</Category>
    <Desc>
      "%s has not been implemented at this time.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>303</Id>
    <Category>E</Category>
    <Desc>
      "Loading ValidPACKAGER state files is currently not supported in an HDL-centric environment. If they exist, they will not be loaded.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>304</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find a .sir file for '%s'. The .sir file of cell '%s' is out of sync with the symbol.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>305</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find file '%s' in lib.cell:view '%s.%s:%s'.
      Expected a chips file for cell '%s' because this cell has no hierarchy. Verify you have saved all schematic changes for this cell and provide a chips file if appropriate.
      Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      "This error message is generated when there are either all upper case or mixed case values in the cds.lib file used by the design. Modify the cds.lib file to contain all lower case values.
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>306</Id>
    <Category>E</Category>
    <Desc>
      "Trying to load a Scald state file in an HDL-centric mode.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>307</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find map file '%s'. Run '%s' to generate this file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>308</Id>
    <Category>W</Category>
    <Desc>
      "Scald state file not in sync with design loaded in HDL mode.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>309</Id>
    <Category>W</Category>
    <Desc>
      "Ignoring state file info for %s: '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>310</Id>
    <Category>E</Category>
    <Desc>
      "Cannot load a %s state file in %s mode and vice-versa.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>311</Id>
    <Category>E</Category>
    <Desc>
      "Asymmetrical section group '%s' not found for physical part '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>312</Id>
    <Category>E</Category>
    <Desc>
      "Verify a correct value was assigned to the '%s' property for:
      Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>313</Id>
    <Category>E</Category>
    <Desc>
      "Occurred on line %d of file '%s': %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>314</Id>
    <Category>E</Category>
    <Desc>
      "Occurred while reading cds.lib:
      "
    </Desc>
    <ExtDesc>
      "This error occurs when the cds.lib file includes a reference to a file, which is not available or which cannot be accessed. Ensure that all INCLUDE file entries in the cds.lib file point to valid files. Also ensure that you have at least read-access to the files being included."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>315</Id>
    <Category>E</Category>
    <Desc>
      "The following asymmetrical part does not have a '%s' property:
      Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>316</Id>
    <Category>E</Category>
    <Desc>
      "EDB%s reports:
      "
    </Desc>
    <ExtDesc>
      "This error displays the messages generated by design expansion library functions. The errors can occur when global buses such as DATA&lt;7..0&gt;\G are used in a design and individual bits of the bus (say, DATA&lt;3&gt;\G) are connected to components. When the design is saved, these connections may be incorrectly written to the verilog.v netlist and/or the glbl module."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>317</Id>
    <Category>E</Category>
    <Desc>
      "A PACK_TYPE property may be required for the following inst:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>318</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find physical part '%s'.
      Check 'PART_NAME' property in chips_prt file.
      A PACK_TYPE property may be required for the following inst:
      Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>319</Id>
    <Category>E</Category>
    <Desc>
      "Pins found on this schematic instance do not match the pins defined in the chips.prt file for asymmetrical group '%s' of physical part '%s'.
      Verify a correct value was assigned to the '%s' property for:
      Schematic instance: %s
      These pins were found on the schematic inst:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>321</Id>
    <Category>E</Category>
    <Desc>
      "These pins %s:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>322</Id>
    <Category>E</Category>
    <Desc>
      "    %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>323</Id>
    <Category>E</Category>
    <Desc>
      "Otherwise, verify a correct pin description appears for this instantiation in the verilog.v file for cell '%s'. Also check the width of the missing pins in the verilog.v file for cell '%s' against the width of the pins in the chips.prt file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>324</Id>
    <Category>W</Category>
    <Desc>
      "File '%s' already loaded into PPT view. Will not load again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>325</Id>
    <Category>E</Category>
    <Desc>
      "This problem occurred for %s:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>326</Id>
    <Category>E</Category>
    <Desc>
      "One or more port mismatches were reported by EDB. Verify a correct pin description appears for the specified instantiation(s) in the appropriate verilog.v file(s). This design cannot be packaged until all port mismatches have been resolved.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>327</Id>
    <Category>W</Category>
    <Desc>
      "Multiple properties found. Ignoring the following for:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>328</Id>
    <Category>E</Category>
    <Desc>
      "Net name: '%s'
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>329</Id>
    <Category>E</Category>
    <Desc>
      "    Property: '%s' = '%s'
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>330</Id>
    <Category>W</Category>
    <Desc>
      "This property has been deleted.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>331</Id>
    <Category>E</Category>
    <Desc>
      "Unknown keyword '%s' found on line %d.
      "
    </Desc>
    <ExtDesc>
      "This error occurs if you use an unrecognized keyword in the cdsprop.paf file, which specifies the case sensitivity of properties. Valid keywords include permit, inherit, uppercasevalue, preservename, and parameter. Ensure that you have defined a valid keyword in the cdsprop.paf file."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>332</Id>
    <Category>E</Category>
    <Desc>
      "Unable to save the property file for the root design. Ensure that you have write permission for this file then package the design again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>333</Id>
    <Category>E</Category>
    <Desc>
      "The &lt;design_name&gt;.dcf could not be opened for lib.cell:view '%s.%s:%s' as the file might have been damaged or modified from its original format.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>334</Id>
    <Category>E</Category>
    <Desc>
      "%s Unable to write the property '%s' = '%s' on '%s'  in the root design property file. Contact Cadence Customer Support for details.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>335</Id>
    <Category>E</Category>
    <Desc>
      "Could not write opf property '%s' = '%s' for '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>336</Id>
    <Category>I</Category>
    <Desc>
      "Loading occurrence properties from %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>337</Id>
    <Category>E</Category>
    <Desc>
      "Expected a chips file for cell '%s' because this cell has no hierarchy. Verify you have saved all schematic changes for this cell and provide a chips file if appropriate.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>338</Id>
    <Category>E</Category>
    <Desc>
      "In addition, verify the correct library for cell '%s' has been specified in the liblist of all cfg_package/expand.cfg files used during expansion of this design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>339</Id>
    <Category>E</Category>
    <Desc>
      "The PIN section for part '%s' contains properties but no pin names. Add the appropriate pin name(s) to the chips.prt file for this part.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you have specified properties for the PIN section corresponding to a part in the chips.prt file but have not specified pin names corresponding to that part. Ensure that you use the following syntax while defining the PIN section for any part:
      pin
      'logical_pin_name' &lt;bit_number&gt;:
      PIN_NUMBER='(&lt;physical_pin_number&gt;, &lt;physical_pin_number2&gt;, ...)';
      property1='(value1, value2, ...)';
      property2='(value1, value2, ...)';
      end_pin;

      Ensure that you have defined a logical pin name in the PIN section for the part that is specified in the error."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>340</Id>
    <Category>E</Category>
    <Desc>
      "This error occurred for %s: '%s'
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>341</Id>
    <Category>E</Category>
    <Desc>
      "A short property name was found instead of the long name.
      %s property name: %s
      %s property name: %s
      Net name: '%s'
      "
    </Desc>
    <ExtDesc>
      "SCALD designs have a limitation (16) on the number of characters allowed in property names. When Packager-XL is run on a newly migrated SCALD design, errors are generated and the truncated property names are identified as the cause. After design migration, run the "s2l design" command in the Design Entry HDL console window. Do not substitute the word "design" with the actual design name. This command updates all short properties on HDL to long properties and the design should then package without problems."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>342</Id>
    <Category>E</Category>
    <Desc>
      "In HDL mode, short properties are no longer extended using the allegroprp.dat file. One or more short properties were found in this design. Use the Markers utility to assist you in updating your design with the desired long property names.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>344</Id>
    <Category>I</Category>
    <Desc>
      "Pin name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>345</Id>
    <Category>W</Category>
    <Desc>
      "Default BODY_NAME '%s' in chips.prt does not match cell name '%s'. Verify the correct chips.prt file is being used for this cell.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>346</Id>
    <Category>E</Category>
    <Desc>
      "Unable to expand this design for packaging. The chips view was not found for cell '%s' in library '%s'.
      "
    </Desc>
    <ExtDesc>
      "The above problem is caused when there is a cell in the design that does not have the chips view defined. You need to define a chips view containing the chips.prt file for all cells that require packaging. If a cell does not need packaging, then assign the PACK_IGNORE property to it."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>347</Id>
    <Category>E</Category>
    <Desc>
      "When binding to '%s', the port definition is determined using the '%s' view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>348</Id>
    <Category>W</Category>
    <Desc>
      "The value of property '%s' is case-sensitive. Ignoring your request to make this case-insensitive.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>349</Id>
    <Category>W</Category>
    <Desc>
      "The value of property '%s' is always treated as case-insensitive. You need to add this to your cdsprop.paf file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>350</Id>
    <Category>W</Category>
    <Desc>
      "Partially quoted text macro name found in property value:  %s = %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>351</Id>
    <Category>W</Category>
    <Desc>
      "The %s directive has become obsolete.
      "
    </Desc>
    <ExtDesc>
      "This warning occurs when you define a directive in the project file, which is not being used in the current version of Packager-XL. Remove the directive from the .cpm file to fix the warning."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>352</Id>
    <Category>E</Category>
    <Desc>
      "Sub Design Part Name   : %s
      Root Design Part Name  : %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>353</Id>
    <Category>E</Category>
    <Desc>
      "Non permitted character '%c' is found in net '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>354</Id>
    <Category>W</Category>
    <Desc>
      "Invalid module name in GEN_SUBDESIGN directive '%s'.
      GEN_SUBDESIGN can only be used for root design.
      "
    </Desc>
    <ExtDesc>
      "This warning occurs when you define a non-root design in the GEN_SUBDESIGN directive. To correct this problem, you must ensure that the root design name matches with the design name defined in the GEN_SUBDESIGN directive."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>355</Id>
    <Category>E</Category>
    <Desc>
      "The part '%s' found in library '%s' during design expansion has been instantiated from library '%s'. The part '%s' has been instantiated from more than one library.
      "
    </Desc>
    <ExtDesc>
      "If a part moves from one library to another, Packager-XL will not flag any error and use the part from the updated library. But if a part is instantiated from more than one library, Packager-XL generates this fatal error. Ensure that you instantiate a part from only one library."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>356</Id>
    <Category>E</Category>
    <Desc>
      "'REUSE_INSTANCE'='%s' present on design '%s' is found on more than one design. It should be unique across the instances of reused blocks.
      "
    </Desc>
    <ExtDesc>
      "This error occurs when you add the REUSE_INSTANCE property with the same value on multiple reuse modules. To correct this problem, you must ensure that the REUSE_INSTANCE property has unique values when assigned to each module."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>357</Id>
    <Category>W</Category>
    <Desc>
      "The %s signal in the property %s=%s of the instance %s is not global or is not present in the design.
      Add the signal name to the POWER_GROUP property for the instance or declare the signal as global.
      "
    </Desc>
    <ExtDesc>
      "In the POWER_GROUP property, you should have a global signal. If a global signal is not present, this warning is issued. Ensure that the signal defined in the POWER_GROUP property is a valid global signal."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>358</Id>
    <Category>I</Category>
    <Desc>
      "Physical net name '%s' for net '%s' is NOT unique or contains lower case char. A new net name will be synthesized.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>359</Id>
    <Category>I</Category>
    <Desc>
      "NO_BACKANNOTATE=ALL set for the block %s.
      "
    </Desc>
    <ExtDesc>
      "This information message is displayed for the block that has the NO_BACKANNOTATE=ALL property set. Packager-XL ignores such blocks during
      backannotation. If you want the block to be backannotated, remove the NO_BACKANNOTATE=ALL property from the block."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>360</Id>
    <Category>W</Category>
    <Desc>
      "PPT file "%s" not found in any of the directories specified by the PPT directive.
      "
    </Desc>
    <ExtDesc>
      "You have entered a ptf file name (my_parts.ppt), which is not available in any of the directories specified by the PPT directive. Ensure that the name of the ptf file is correct, and it is located in one of the directories specified by the PPT directive."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>361</Id>
    <Category>W</Category>
    <Desc>
      "Length of PartName "%s", existing in design, is more than the specified part_type_length.
      part_type_length specified in project file is %d.
      One possibility could be that the part_type_length was reduced after the previous run.
      Regenerating the PartName based on the specified part_type_length.
      "
    </Desc>
    <ExtDesc>
      "If the length of any part name is greater than the specified PART_TYPE_LENGTH, Packager-XL regenerates the part name based on the specified PART_TYPE_LENGTH and displays this warning message."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>362</Id>
    <Category>E</Category>
    <Desc>
      "Two global signals are shorted. If you want to short these global signals, add them in Allowed Global Shorts list in editor setup options.
      Net name: '%s'
      Net name: '%s'
      "
    </Desc>
    <ExtDesc>
      "This error occurs when Packager-XL finds an illegal global signal short. It displays the two net names that are being shorted, and exits with error status 2. You should ensure that there is no shorting of global signals. If you want a global signal to be shorted, add it in the ALLOWED_GLOBAL_SIGNALS list."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>363</Id>
    <Category>W</Category>
    <Desc>
      "POWER_GROUP property is not allowed in chips.prt file. Add the same in either PPT or on schematic. Ignoring the POWER_GROUP property specified on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>364</Id>
    <Category>W</Category>
    <Desc>
      "The value %s of the SWAP_INFO property in the part definition is not valid and is being ignored.
      Ensure that the part definition is correct.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>365</Id>
    <Category>W</Category>
    <Desc>
      "Multiple definitions found for SWAP_INFO property in the part definition.
      The value %s of SWAP_INFO is being ignored.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>366</Id>
    <Category>W</Category>
    <Desc>
      "Section Number %s is present in more than one Logical groups in the SWAP_INFO property in the chips.prt.
      Or is present in more than once in a Logical group.Such a value is not valid.This property is being ignored.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>367</Id>
    <Category>W</Category>
    <Desc>
      "Pin %s has multiple pin numbers for one logical group in the SWAP_INFO property in the part definition. This property is being ignored.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>368</Id>
    <Category>E</Category>
    <Desc>
      "Canonical Path %s could not be parsed in the 5x architecture. Look for illegal characters
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>369</Id>
    <Category>E</Category>
    <Desc>
      "Unable to load physical part '%s' with reference designator '%s' because changes made to the schematic are not synchronized with the physical netlist or variant database. Repackage the design and synchronize the package and design database.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>370</Id>
    <Category>W</Category>
    <Desc>
      "Property %s found on the schematic net '%s'. This property will be ignored. Constraint Manager has replaced the use of this property for setting constraints. Add this constraint in Constraint Manager and remove the property from the net.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>371</Id>
    <Category>E</Category>
    <Desc>
      "Instance does not match phys part %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>372</Id>
    <Category>I</Category>
    <Desc>
      "Schematic instance: %s"
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>373</Id>
    <Category>W</Category>
    <Desc>
      "Invalid module name '%s' in USE_SUBDESIGN directive.
      Ignoring USE_SUBDESIGN directive for this module.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>374</Id>
    <Category>W</Category>
    <Desc>
      "Ignoring the FORCE_SUBDESIGN directive for module '%s' because of an invalid module name. Specify a valid, existing module name in the Force Subdesign field on the Subdesign tab page of the Packager Setup dialog box.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>375</Id>
    <Category>E</Category>
    <Desc>
      "The Part Type length specified in the Packager setup options is less than the length of logical part name and pack type combined together for part name '%s'. Packager requires the part length to be at least as long as the length of the  logical part name and pack type combined. Therefore, Packager cannot truncate the part type length to the specified level. Increase the Part Type length in the Packager setup options and package again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>376</Id>
    <Category>E</Category>
    <Desc>
      "'REUSE_INSTANCE'='%s' present on design '%s' is found on more than one design. The REUSE_INSTANCE should be unique across all instances of blocks in the entire design. Rename the value for the block.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>377</Id>
    <Category>E</Category>
    <Desc>
      "Expected '%c' character in '%s' = '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>378</Id>
    <Category>E</Category>
    <Desc>
      "Invalid separator '%c' character in '%s' = '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>379</Id>
    <Category>E</Category>
    <Desc>
      "Incorrect zero value of pin name found for PIN_NUMBER on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>380</Id>
    <Category>E</Category>
    <Desc>
      "A short property name was found instead of the long name.
      %s property name: %s
      %s property name: %s
      Net name: '%s'
      Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>381</Id>
    <Category>E</Category>
    <Desc>
      "A short property name was found instead of the long name.
      %s property name: %s
      %s property name: %s
      Net name: '%s'
      Schematic instance: %s
      Pin name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>382</Id>
    <Category>E</Category>
    <Desc>
      "Error at line %d in file %s. Unable to load the parts list file. Run Packager-XL (Export - Physical) again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>383</Id>
    <Category>E</Category>
    <Desc>
      "Error at line %d in file %s. Unable to load the net list file. Run Packager-XL (Export - Physical) again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>384</Id>
    <Category>E</Category>
    <Desc>
      "Error at line %d in file %s. Could not package design view
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>385</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Not all parts specified for sized part.
      Schematic Instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>386</Id>
    <Category>E</Category>
    <Desc>
      "
      No reference designator specified for instance : %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>387</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Physical part not found for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>388</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Could not create new pkg for Schematic instance : %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>389</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Could not package Schematic instance : %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>390</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Cannot find section number %d for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>391</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Could not pack schematic instance %s in sections.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>392</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Section and Pin swaps - Section Number: %d inconsistent for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>393</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Illegal pin swap occurred for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>394</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Could not swap pins for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>395</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. PN number does not match SEC number in pst file for Pin: %s.
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>396</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Illegal Pin Swap. Pin: %s.
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>397</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Illegal section pin value. Pin: %s.
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>398</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Pins: %s and %s do not belong to the same pin group.
      Schematic Instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>399</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Section value: %d out of range for Pin: %s.
      Schematic Instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>400</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Section value: %d out of range for pin: %s.
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>401</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Inconsistent section swap for pin: %s.
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>402</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Error swapping sections for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>403</Id>
    <Category>E</Category>
    <Desc>
      "
      Pins %s and %s do not match.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>404</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot find the schematic page 1.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>405</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. NET_NAME value not specified.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>406</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Additional information found after 'END.' keyword
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>407</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Location value not specified.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>408</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Pin value value not specified.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>409</Id>
    <Category>E</Category>
    <Desc>
      "Error at line %d while loading the %s file. Unable to create the following new pin instance, %s, as the pin definition was not found.
      Reference Designator: %s.
      Schematic Instance: %s.
      Check the symbol and ensure that the pin definition is consistent.
      "
    </Desc>
    <ExtDesc>
      "Packager-XL generates this error when there is a mismatch between the pins in the pstxnet.dat file and those in the pstchip.dat file.
      To resolve this error, generate the pstxnet.dat and pstchip.dat files again by running Export > Physical. If the problem persists, contact Cadence Customer Support.
      "
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>410</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Error at line %d in file %s. Cannot have two instances of a non-common pin: %s.
      Schematic Instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>411</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Error at line %d in file %s. Cannot create duplicate pin instance: %s.
      Schematic Instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>412</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot find primitive part for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>413</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Reference designators are inconsistent in the xprt and xnet files. Reference designator in xprt file: %s. Reference designator in xnet file: %s. Schematic instance :%s.
      "
    </Desc>
    <ExtDesc>
      "To resolve this error, package the design again by running Export > Physical. If the problems persists, contact Cadence Customer Support."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>414</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot read C_SIGNAL property value.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>415</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error reading DIRECTIVES section.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>416</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Unable to load physical part: %s with reference designator: %s. Part not found in the design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>417</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Property string not specified in definition of primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>418</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error in Syntax in definition of primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>419</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Unable to load physical part: %s with reference designator: %s. Part not found in the design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>420</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot add property $location = %s to prop list.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>421</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot add property $sec = %s to prop list.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>422</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Property string not specified.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>423</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Cannot add property %s=%s to prop list.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>424</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error reading XY property for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>425</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error reading part size for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>426</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error in syntax for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>427</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error setting XY property string for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>428</Id>
    <Category>E</Category>
    <Desc>
      "
      Reference Designator: %s. Error at line %d in file %s. Section number: %s specified is not an integer value for :
      Schematic instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>429</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Illegal Section Number: %s for Part Name: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>430</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Mechanical Parts should not have pins. Part Name: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>431</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Object Id recovered is not legal.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>432</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error in syntax for primitive instance: %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>433</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Error in syntax.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>434</Id>
    <Category>E</Category>
    <Desc>
      "Error at line %d in file %s. Offset must be an integer number.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>435</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Incorrect format for DRAWING value string.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>436</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Unable to read page number value.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>437</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Unable to read version number value.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>438</Id>
    <Category>E</Category>
    <Desc>
      "
      Error at line %d in file %s. Invalid integer value.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>439</Id>
    <Category>E</Category>
    <Desc>
      "The connectivity server is unable to load the design. The .xcon file might be missing or may be incorrect. To fix this error, the design should be netlisted in 16.5 or a later version of Design Entry HDL.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>440</Id>
    <Category>E</Category>
    <Desc>
      "This error occurred because you may have edited some interface ports in the hierarchical blocks and the connectivity of the parent designs of these blocks was not updated with the port changes. Run File > Save Hierarchy in Design Entry HDL before running Export/Import Physical.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>500</Id>
    <Category>E</Category>
    <Desc>
      "Too many tokens in line %d
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>501</Id>
    <Category>E</Category>
    <Desc>
      "There must be %d tokens.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>502</Id>
    <Category>E</Category>
    <Desc>
      "! is not the last character on line %d
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>503</Id>
    <Category>E</Category>
    <Desc>
      "Too few tokens in line %d
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>504</Id>
    <Category>E</Category>
    <Desc>
      "Only %d are found. %d required.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>505</Id>
    <Category>E</Category>
    <Desc>
      "Unknown property type %s in file %s. Ignored
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>506</Id>
    <Category>E</Category>
    <Desc>
      "Cannot accept properties of type %s in %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>507</Id>
    <Category>E</Category>
    <Desc>
      "Physical net name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>508</Id>
    <Category>E</Category>
    <Desc>
      "Phys Part Name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>509</Id>
    <Category>E</Category>
    <Desc>
      "Times property is in view file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>510</Id>
    <Category>E</Category>
    <Desc>
      "Ignoring line %d from view file %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>511</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find physical part %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>512</Id>
    <Category>E</Category>
    <Desc>
      "Ignoring line: %d
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>513</Id>
    <Category>E</Category>
    <Desc>
      "Package %s in %s refers to multiple physical parts.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>514</Id>
    <Category>E</Category>
    <Desc>
      "Instance in pinView.dat refers to multiple packages.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>515</Id>
    <Category>E</Category>
    <Desc>
      "Packages: %s and %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>516</Id>
    <Category>E</Category>
    <Desc>
      "Line Number: %d
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>517</Id>
    <Category>E</Category>
    <Desc>
      "Pin %s is not valid for physical part %s. Ensure that the specified pin is present in the part definition.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>518</Id>
    <Category>E</Category>
    <Desc>
      "File Name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>519</Id>
    <Category>E</Category>
    <Desc>
      "%s is required in each data line of %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>520</Id>
    <Category>E</Category>
    <Desc>
      "%s must be specified in line %d of %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>521</Id>
    <Category>E</Category>
    <Desc>
      "Cannot process pin %s on pkg %s connected to net.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>522</Id>
    <Category>E</Category>
    <Desc>
      "Unexpected end of file for file %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>523</Id>
    <Category>E</Category>
    <Desc>
      "The first line of %s has bad format. Must be:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>524</Id>
    <Category>E</Category>
    <Desc>
      "The first line of %s has bad format.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>525</Id>
    <Category>E</Category>
    <Desc>
      "A!NET_NAME!REFDES!PIN_NUMBER!FUNC_LOGICAL_PATH!COMP_DEVICE_TYPE!FUNC_SCH_SIZE!FUNC_HAS_FIXED_SIZE!FUNC_DES!
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>526</Id>
    <Category>E</Category>
    <Desc>
      "And any other user specific %s properties.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>527</Id>
    <Category>E</Category>
    <Desc>
      "The second line of %s has bad format. Must begin with J
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>528</Id>
    <Category>E</Category>
    <Desc>
      "Must begin with %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>529</Id>
    <Category>E</Category>
    <Desc>
      "File not found %s. No %s properties to load.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>530</Id>
    <Category>E</Category>
    <Desc>
      "File not found %s. Cannot continue to load.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>531</Id>
    <Category>E</Category>
    <Desc>
      "Error generating physical net names for design.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>532</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find %s in design view.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>533</Id>
    <Category>E</Category>
    <Desc>
      "Name: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>534</Id>
    <Category>E</Category>
    <Desc>
      "Unable to create any physical parts while loading pinview.dat. This error occurred because chipsview.dat was not loaded correctly. To ensure that pinview.dat and chipsview.dat are in sync, run Genfeedformat again before running Packager-XL (Export - Physical).
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>535</Id>
    <Category>E</Category>
    <Desc>
      "Missing required properties in compView.dat
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>536</Id>
    <Category>E</Category>
    <Desc>
      "Missing required properties in pinView.dat
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>537</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find chips_prt file of "%s" from "%s"
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>538</Id>
    <Category>E</Category>
    <Desc>
      "Schematic instance: %s
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>539</Id>
    <Category>E</Category>
    <Desc>
      "Expected an HDL-centric %s file.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>540</Id>
    <Category>E</Category>
    <Desc>
      "The following non HDL-centric instance name was found on line %d:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>541</Id>
    <Category>E</Category>
    <Desc>
      "Missing required properties in funcView.dat
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>542</Id>
    <Category>E</Category>
    <Desc>
      "Missing required properties in netView.dat
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>543</Id>
    <Category>E</Category>
    <Desc>
      "A!FUNC_LOGICAL_PATH!COMP_DEVICE_TYPE!REFDES!FUNC_PRIM_FILE!COMP_PARENT_PPT!COMP_PARENT_PPT_PART!COMP_PARENT_PART_TYPE!FUNC_SCH_SIZE!FUNC_HAS_FIXED_SIZE!FUNC_DES!FUNC_GROUP!FUNC_ROOM!
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>544</Id>
    <Category>E</Category>
    <Desc>
      "A!NET_NAME!NET_LOGICAL_PATH!
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>545</Id>
    <Category>E</Category>
    <Desc>
      "Found unassigned pin %s.%s on a used function %s.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>546</Id>
    <Category>E</Category>
    <Desc>
      "%s must be specified in line %d of %s, re-run Netrev to update the board
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>547</Id>
    <Category>E</Category>
    <Desc>
      "Cannot find '%s' in lib.cell:view '%s.%s:%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>548</Id>
    <Category>E</Category>
    <Desc>
      "Cannot make a VHDL name for '%s'.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>549</Id>
    <Category>E</Category>
    <Desc>
      "No physical part found for COMP_DEVICE_TYPE=%s. Regenerate the netlist (Export - Physical) to sync with the PCB Editor board.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>550</Id>
    <Category>E</Category>
    <Desc>
      "The %s property found on line %d in file %s does not seem to be correct. Check if multiple %s files exist in the packaged directory (for example, funcview.dat and funcView.dat.) Try deleting all *view.dat files and regenerating them.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>551</Id>
    <Category>E</Category>
    <Desc>
      "Instance %s cannot be used in the schematic because it has different pin definitions from chips.prt.
      To correct this problem, remove the instance and modify the symbol of the instance in Part Developer.
      Add the instance with the corrected symbol and package again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>552</Id>
    <Category>E</Category>
    <Desc>
      "Property '%s' has invalid value '%s' for PPT '%s'. Remove initial blanks from the value.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>553</Id>
    <Category>E</Category>
    <Desc>
      "Instance %s cannot be used in the schematic because it has different pin definitions from chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>554</Id>
    <Category>E</Category>
    <Desc>
      "Logical Pin %s cannot have both positive and negative Differential property in pin definitions for Physical Part %s in chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>555</Id>
    <Category>E</Category>
    <Desc>
      "Physical Pin %s in Logical Pin %s and physical Pin %s in Logical Pin %s cannot have the same positive Differential property value of %s in pin definitions for Physical Part %s in chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>556</Id>
    <Category>E</Category>
    <Desc>
      "Physical Pin %s in Logical Pin %s and physical Pin %s in Logical Pin %s cannot have the same negative Differential property value of %s for Physical Part %s in pin definitions in chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>557</Id>
    <Category>E</Category>
    <Desc>
      "Differential Pair %s on logical pin %s is missing positive polarity pin for Physical Part %s in pin definitions in chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>558</Id>
    <Category>E</Category>
    <Desc>
      "Differential Pair %s on logical pin %s is missing negative polarity pin for Physical Part %s in pin definitions in chips.prt.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>559</Id>
    <Category>E</Category>
    <Desc>
      "Pin name %s specified in PACK_SHORT property in chips file is not present on the physical part %s. Nets not shorted for pin %s."

    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>560</Id>
    <Category>E</Category>
    <Desc>
      "System assigned net '%s' appears to be shorted on page '%d' of block '%s'. Modify signal names in Design Entry HDL to avoid any unintended shorts.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>561</Id>
    <Category>E</Category>
    <Desc>
      "System assigned net '%s' appears to be shorted across pages '%s' of block '%s'. Modify these signal names in Design Entry HDL to avoid any unintended shorts
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>562</Id>
    <Category>W</Category>
    <Desc>
      "Occurred while reading cds.lib:
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>563</Id>
    <Category>E</Category>
    <Desc>
      "The following blocks have netlisting errors: %s Fix them in Design Entry HDL before packaging.

      To view the netlisting errors, run File - Save Hierarchy in Design Entry HDL. When you save the hierarchy, error details are listed in hierwrite_netlister.mkr. To access the .mkr file, choose Tools - Markers, then navigate to &lt;TEMP_DIR&gt;/hierwrite.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>565</Id>
    <Category>W</Category>
    <Desc>
      "Reference designator value "%s" has leading blank or tab character(s). These will be skipped for reference designator generation.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>566</Id>
    <Category>W</Category>
    <Desc>
      "Reference designator value "%s" has trailing blank or tab character(s). These will be omitted for reference designator generation.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>567</Id>
    <Category>W</Category>
    <Desc>
      "Pin name '%s' specified in PIN_SHORT property '%s' does not exist on the instance. Ignoring the pin specification.
      Check and update the PIN_SHORT property.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>568</Id>
    <Category>W</Category>
    <Desc>
      "Fewer than 2 connected pins found in pins specified in PIN_SHORT property value '%s'. Ignoring the property.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>569</Id>
    <Category>W</Category>
    <Desc>
      "Fewer than 2 pins found using physical net names specified in NET_SHORT property value '%s'. Ignoring the property.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>570</Id>
    <Category>E</Category>
    <Desc>
      "SUBDESIGN_SUFFIX = '%s' is attached to module %s. Module %s is not specified in the FORCE_SUBDESIGN or USE_SUBDESIGN directive design name list.
      "
    </Desc>
    <ExtDesc>
      "This error is generated when design reuse has not been enabled for a design with an instance that has the  SUBDESIGN_SUFFIX property.

      The block name has not been specified in the FORCE_SUBDESIGN or USE_SUBDESIGN  directive.

      Specify the block name in the FORCE or USE_SUBDESIGN list by adding the name of the subdesign (base_level) in the USE_SUBDESIGN or FORCE_SUBDESIGN fields in the Packager Setup - Subdesign tab.
      "
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>571</Id>
    <Category>E</Category>
    <Desc>
      "Incorrect value for %s is found on line %d of the module's state file.
      To update the subdesign state file, set the module as root and package. Once the subdesign state file is corrected, set the top as root and package again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>572</Id>
    <Category>E</Category>
    <Desc>
      "Illegal '%c' character found in property value '%s' on line %d.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>573</Id>
    <Category>E</Category>
    <Desc>
      "Subtype string is empty on line %d. The tilde( ~ ) character must be followed by a string.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>574</Id>
    <Category>E</Category>
    <Desc>
      "Conflicts found in the property values specified for nets and their synonyms. Refer to the pstprop.dat file for details. To resolve these conflicts, run 'Audit > Alias property conflicts' in Constraint Manager.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>575</Id>
    <Category>E</Category>
    <Desc>
      "Reference designator value %s has an invalid character. The list of invalid characters in reference designators is as follows: space, tab, asterisk, comma, semicolon, colon, backslash, the equal sign, double quotes, single quotes and braces. Update the reference designator in Design Entry HDL and then run Packager.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>576</Id>
    <Category>E</Category>
    <Desc>
      "An incorrect physical net name has been generated for the NC signal. To resolve this, run Packager XL with the Regenerate Physical Net Name option selected.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>577</Id>
    <Category>E</Category>
    <Desc>
      "Reuse block(s) '%s' added in the design have been modified but packaging has not been updated. Run Packager XL for the mentioned block(s) to update reuse block packaging data.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>578</Id>
    <Category>E</Category>
    <Desc>
      "The '%s' net is connected to more than one component pin but it has the 'OK_NET_ONE_PIN' property. The 'OK_NET_ONE_PIN' property should be specified only for nets that are connected to one pin. Check the connections for the net and if required, delete the 'OK_NET_ONE_PIN' property from the net.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>579</Id>
    <Category>E</Category>
    <Desc>
      "Newline character found in property value for property '%s' while generating packaged data. Fix the property in the schematic design and package the design again.
      "
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>580</Id>
    <Category>E</Category>
    <Desc>
      "Unable to load physical part %s with reference designator %s of path %s. Part not found in the design."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <!-- These error codes (600 onwards) contain:
       1. Chips Editing Errors. 
       2. Error codes suppressing some errors when in PDV mode. -->
  <Msg>
    <Id>600</Id>
    <Category>W</Category>
    <Desc>
      "Pin number '%s' specified for logical pin %s already existing for logical pin %s. Renamed to default pin number %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>601</Id>
    <Category>W</Category>
    <Desc>
      "Logical pin '%s' renamed to %s due to duplicate primitive name."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>602</Id>
    <Category>E</Category>
    <Desc>
      "Invalid input parameter(s)"
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>603</Id>
    <Category>E</Category>
    <Desc>
      "Transaction object not initialized."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>604</Id>
    <Category>E</Category>
    <Desc>
      "Logical pin %s not found."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>605</Id>
    <Category>E</Category>
    <Desc>
      "Cannot edit pin number %s for logical pin %s for section %s as it is not existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>606</Id>
    <Category>E</Category>
    <Desc>
      "Property %s not found."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>607</Id>
    <Category>E</Category>
    <Desc>
      "Property %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>608</Id>
    <Category>E</Category>
    <Desc>
      "Pin number %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>609</Id>
    <Category>E</Category>
    <Desc>
      "Pin number %s not found."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>610</Id>
    <Category>W</Category>
    <Desc>
      "Pin number %s specified for logical pin %s in section %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>611</Id>
    <Category>W</Category>
    <Desc>
      "Logical pin %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>612</Id>
    <Category>E</Category>
    <Desc>
      "Failed to create logical pin %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>613</Id>
    <Category>E</Category>
    <Desc>
      "Cell %s already created."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>  
  <Msg>
    <Id>614</Id>
    <Category>E</Category>
    <Desc>
      "Cell %s creation failed."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>615</Id>
    <Category>E</Category>
    <Desc>
      "Cell %s not found."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>616</Id>
    <Category>E</Category>
    <Desc>
      "Primitive %s already exists."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>617</Id>
    <Category>E</Category>
    <Desc>
      "Primitive %s not found."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>618</Id>
    <Category>E</Category>
    <Desc>
      "Primitive %s creation failed."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>619</Id>
    <Category>W</Category>
    <Desc>
      "Primitive name '%s' renamed to %s due to duplicate pin names."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>620</Id>
    <Category>W</Category>
    <Desc>
      "Section number %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>621</Id>
    <Category>E</Category>
    <Desc>
      "Section creation failed for section %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>622</Id>
    <Category>E</Category>
    <Desc>
      "Global pin with ID %s not existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>  
  <Msg>
    <Id>623</Id>
    <Category>W</Category>
    <Desc>
      "Global pin %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>  
  <Msg>
    <Id>624</Id>
    <Category>E</Category>
    <Desc>
      "Failed to create global pin %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>  
  <Msg>
    <Id>625</Id>
    <Category>E</Category>
    <Desc>
      "Failed to delete global pin %s with ID %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>626</Id>
    <Category>E</Category>
    <Desc>
      "Failed to delete pin number for global pin %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>627</Id>
    <Category>E</Category>
    <Desc>
      "Failed to edit pin number for global pin %s."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg> 
  <Msg>
    <Id>628</Id>
    <Category>E</Category>
    <Desc>
      "Failed to change global pin %s type."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>629</Id>
    <Category>E</Category>
    <Desc>
      "Failed to change global pin %s name."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg> 
  <Msg>
    <Id>630</Id>
    <Category>E</Category>
    <Desc>
      "Pin number(s) %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>631</Id>
    <Category>E</Category>
    <Desc>
      "Pin number(s) %s not in correct format or have redundant pin numbers."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>632</Id>
    <Category>E</Category>
    <Desc>
      "Invalid Pin ID."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
    <Msg>
    <Id>633</Id>
    <Category>E</Category>
    <Desc>
      "%s is reserved global pin name."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>634</Id>
    <Category>W</Category>
    <Desc>
      "Pin %s already existing."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg>
  <Msg>
    <Id>635</Id>
    <Category>E</Category>
    <Desc>
      "Invalid pin name."
    </Desc>
    <ExtDesc>
      ""
    </ExtDesc>
    <Output>C</Output>
  </Msg> 
  <Msg>
    <Id>636</Id>
    <Category>E</Category>
    <Desc>
      "Part definition for the component %s could not be loaded from the library %s. There are syntax errors in the part definition. Ensure that the syntax is correct for the part definition.
      "
    </Desc>
    <ExtDesc>
      "This error is generated along with another packaging error, which prevents Packager-XL from completing its operation. Fix the other errors that are generated in the pxl.log file and package the design again."
    </ExtDesc>
    <Output>C</Output>
  </Msg>
</MsgFile>
