Page Comparison

1. Select the More PIN_REPORT Settings... 

We press this button to open up a new GUI where we can enter more configuration settings (CSETS)

2. Setup the PCHK_DEVICE_PIN_NUMBERS Entry

In this step we tell partBuilder what Pins to expect from the device Pin Report

Note that this step is optional, but it improves partBuilders ability to verify pin_data.

If we don't enter them, then partBuilder will only check to see that there are the proper number of pins and that no pins have been duplicated.

If we do enter it partBuilder makes sure that every pin read from the PIN_REPORT_FILE is a valid pin number.

We use the simpler of the 2 approaches we talked about on the datasheet step

We want to tell partBuilder here what pins to expect and sometimes we need to tell it 

what pins not to expect.

PCHK_DEVICE_PIN_NUMBERS

In the PCHK_DEVICE_PIN_NUMBERS Entry We enter:

BGA_PIN_NUMS[A1..T3],BGA_PIN_NUMS[A7..T9] 

The comma is used to split multiple commands or pin numbers here

(we could also have typed out every expected pin_number by hand

! But that would be long boring and error-prone)

The BGA_PIN_NUMS[startRowCol:EndRowCol] is a command that partBuilder recognizes 

and uses to build the full 

array of Row/Col pins that normally appear in the Range. 

It knows that

standard BGAs skip row Letters I,O,Q,S,X and Z (It also provide a way to specify what rows should be skipped if your BGA is not standard)

More Complicated Use of PCHK_DEVICE_PIN_NUMBERS and PCHK_VALID_MISSING_PINS

As discussed before we could have used BGA_PIN_NUMS[A1..T9] in the PCHK_DEVICE_PIN_NUMBERS

Entry  to describe the FULL BGA ARRAY

and then

used

[A..T][4..6] in the PCHK_VALID_MISSING_PINS entry,

The combination of the 2 Entries would have created the same checks

, Here its not necessary, but there are many cases where the PCHK_VALID_MISSING_PINS entry makes it very easy to modify what to expect from a full array

For instance it makes it easy to handle a BGA that has a few un-populated corner pins.  

If you are interested, See the PinData Verification Checks section for a more complicated example

3. Here is the finished entry

4.