| Table of Contents |
|---|
READ_PIN_REPORT
The READ_PIN_REPORT goes through several steps:
Read and Verify Pin Report File
The First step is to read the Selected PIN_REPORT_FILE. The PIN_REPORT_TYPE setting tells PartBuilder what kind of file to expect
PartBuilder builds an internal database of all the pins it finds in the PIN_REPORT and stores:
- Pin name,
- Pin Number,
- Pin Type
- IO_STD if present
- Pin Delay if present
Rename Pins
If a RENAME_RULE is provided or if RENAME_RULES points to a file containing multiple RENAME_RULES, PartBuilder will go through the current pin database and rename any pins that match the RENAME_RULES. PartBuilder stores off the orginal name and then uses the new Name going forward
Override Pin Types
if a PinTypeOverride file exists, PartBuilder will go through the current pin database and change the PIN_TYPE for any pinnames that match the override rule
Override rules can be created in a text file by hand, or the PinExplorer pop-up can be used to add pin-mapping types to the file
Find Diff Pairs
After the Pins have been Renamed and PIN_TYPES assigned, PartBuilder goes through the internal Pin database and hunts for DIFF_PAIRS using the DIFF_PAIR_MATCH_POL rules.
Report Warnings
PartBuilder will report the following warnings
- Unrecognized lines in the specified PIN_REPORT_FILE
- The specified NUM_PINS entry does not match the number of pins found in the PIN_REPORT_FILE
- If the user sets up the configuration setting for PIN_ROW_CHK and PIN_COL_CHK in the PINOUT_CONTROL TAB of CONFIGURATION SETTINGS, PartBuilder will report the pins it didn't find
- Any Pins that do not have a PIN_TYPE mapped
Pin Report and Pin Difference Reports
Pin Report
PartBuilder always creates 2 spreadsheets reporting what the result of the pin data extraction operations. They detail all the extracted pinData.
pin_num_pin_summary_{timestamp}.csv is sorted by Pin Number, and pin_name_pin_summary_{timestamp}.csv is sorted by pin_name. They both get created in the OUTPUT_FILES directory in the selected part directory. The time_stamp is appended to the filenames so that it never overwrites the last set of data.
Pin Difference Report
If the LAST_PIN_SUMMARY_FILE CSET points to a valid file (which would typically be made from a copy of one of the 2 time-stamped report files in the OUTPUT_FILES directory) PartBuilder will compare the latest pinData to the data stored in the corresponding LAST_PIN_SUMMARY_FILE. It will report any differences to the status window and also create 2 spreadsheets (one sorted by PinName and one by PinNumber) detailing only the differences. This can be very helpful when working on parts whose pinout is expected to change.