...
...
1
Stepshot confluence view macro | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
We press this button to open up a new GUI where we can enter more configuration settings (CSETS)
2
Stepshot confluence view macro | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
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.
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 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 most BGAs skip row I,O,Q,S,X and Z
As discussed before we could have used BGA_PIN_NUMS[A1..T9] in the PCHK_DEVICE_PIN_NUMBERS Entry
and then put
[A..T][4..6] in the PCHK_VALID_MISSING_PINS entry, and the combination of the 2 would have created the same checks.
Note that this step is optional but 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.
3
Stepshot confluence view macro | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
4
Stepshot confluence view macro | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|