SLVUAW9C September 2016 – February 2020 UCD90320
These bytes configure which pin is used for each GPI and its polarity. A mode other than “Unused” or “Input” causes this command to be rejected (receive Please see
| GPI Index M + 1 | GPI Index M | |||||||
|---|---|---|---|---|---|---|---|---|
| BYTE N + 1 | BYTE N + 2 | BYTE N | ||||||
| Bit[7] | Bit[6] | Bit[5:4] | Bit[3:0] | Bit[7:4] | Bit[3] | Bit[2] | Bit[1:0] | Bit[7:0] |
| Fault Pin | Polarity | Mode | Pin ID[7:4] | Pin ID[3:0] | Fault Pin | Polarity | Mode | Pin ID[7:0] |
N = (GPI _M/ 2) * 3
NOTE
The input pin configurations, if used, must start in the Input Pin Configuration byte and continue in consecutive order with no gaps. That is, no Unused-Mode Pin Configurations can be between any Input-Mode Pin Configurations.
NOTE
Fault Pin bit. When this bit is set with GPI_CONFIG command, the corresponding pin is behaved as FAULT pin instead of GPI pin. MAX 4 pin could be configured as Fault pin. Device shall NACK if there are more than 4 pins are configured as Fault pin. The first fault pin is the first pin who has the fault pin bit set. Fault Enable Flags
When the bit corresponding to a given GPI is set, the de-assertion of the GPI is treated as a fault. This fault will be noted in the MFR_STATUS command (see Section 10.33) and will be logged if configured to do so (see Section 10.29). When a GPI fault occurs, the PMBALERT# pin is asserted.
| 31 | 30 | 29 | 28 | 27 | 26 | 25 | 24 | 23 | 22 | 21 | 20 | 19 | 18 | 17 | 16 |
| GPI31 | GPI30 | GPI29 | GPI28 | GPI27 | GPI26 | GPI25 | GPI24 | GPI23 | GPI22 | GPI21 | GPI20 | GPI19 | GPI18 | GPI17 | GPI16 |
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| GPI15 | GPI14 | GPI13 | GPI12 | GPI11 | GPI10 | GPI9 | GPI8 | GPI7 | GPI6 | GPI5 | GPI4 | GPI3 | GPI2 | GPI1 | GPI0 |