SLVUCU5 December 2025 UCD91160 , UCD91320
This Read/Write Block command configures the sequencing dependencies and enable pin for a given rail.
Features include:
All configurations done with the GPI_CONFIG command must be done before writing this command.
When this command is written, the enable pin for the rail is deasserted. Then the state of the rail is re-evaluated. If it is determined that the rail should be on, the enable pin is then asserted.
| Byte Number (Write) | Byte Number (Read) | Payload Index | Description |
|---|---|---|---|
| 0 | CMD = F6 | ||
| 1 | 0 | BYTE_COUNT = 29 | |
| 2 | 1 | 0 | Enable Pin Configuration (Pin ID) |
3 | 2 | 1 | Enable Pin Configuration (Other) |
4 | 3 | 2 | GPI Sequence On Dependency Mask (Byte 0 - LSB) |
5 | 4 | 3 | GPI Sequence On Dependency Mask (Byte 1) |
6 | 5 | 4 | GPI Sequence On Dependency Mask (Byte 2) |
7 | 6 | 5 | GPI Sequence On Dependency Mask (Byte 3 - MSB) |
8 | 7 | 6 | GPI Sequence Off Dependency Mask (Byte 0 - LSB) |
9 | 8 | 7 | GPI Sequence Off Dependency Mask (Byte 1) |
10 | 9 | 8 | GPI Sequence Off Dependency Mask (Byte 2) |
11 | 10 | 9 | GPI Sequence Off Dependency Mask (Byte 3- LSB) |
12 | 11 | 10 | Sequencing Timeout Configuration |
| 13 | 12 | 11 | Sequencing On Timeout |
| 14 | 13 | 12 | Sequencing Off Timeout |
| 15 | 1 4 | 1 3 | Page Sequence On Dependency Mask (Byte 0 - LSB) |
| 16 | 1 5 | 1 4 | Page Sequence On Dependency Mask (Byte 1) |
| 17 | 1 6 | 1 5 | Page Sequence On Dependency Mask (Byte 2) |
18 | 17 | 16 | Page Sequence On Dependency Mask (Byte 3- MSB) |
| 19 | 1 8 | 17 | Page Sequence Off Dependency Mask (Byte 0 - LSB) |
20 | 1 9 | 18 | Page Sequence Off Dependency Mask (Byte 1) |
21 | 20 | 19 | Page Sequence Off Dependency Mask (Byte 2) |
22 | 21 | 20 | Page Sequence Off Dependency Mask (Byte 3- MSB) |
23 | 22 | 21 | Fault Slaves Mask (Byte 0 - LSB) |
24 | 23 | 22 | Fault Slaves Mask (Byte 1) |
25 | 24 | 23 | Fault Slaves Mask (Byte 2) |
26 | 25 | 24 | Fault Slaves Mask (Byte 3- LSB) |
27 | 26 | 25 | GPO Sequence On Dependency Mask (Byte 0) |
28 | 27 | 26 | GPO Sequence On Dependency Mask (Byte 1) |
29 | 28 | 27 | GPO Sequence Off Dependency Mask (Byte 0) |
30 | 29 | 28 | GPO Sequence Off Dependency Mask (Byte 1) |
The turn on condition for each page can depend on the state of several other pages or input pins. The same pages and pins also may be used to control multiple pages. The GPI and Page dependencies (Sequence On Dependencies) define a set of conditions which allow a page to turn on when met. Note that the logical AND of all conditions must be met before a page can be turned on. Once the page is on, these dependencies have no further effect on the operating status of the page. Specifically, they do not cause a page to turn off.
Sequence On Dependencies work in parallel with the PMBus defined mechanisms used to enable an output. That is, both the Sequence On Dependencies and the PMBus mechanism must be satisfied. For example, if the page responds to an OPERATION command and the OPERATION command specifies OFF, the page remains off even if all of the sequencing Sequence On Dependencies are met. Further, the order in which they are met is irrelevant; if the OPERATION command is issued first, the page waits for the sequencing requirements to be met before it can be turned on; or if the sequencing requirements are met first, the page waits for the OPERATION command before it can be turned on.
In the ON_OFF_CONFIG command, a “None” setting is still subject to the specified Sequence On Dependencies.
Turn on delay (TON_DELAY) is applied after the page has been commanded on and all Sequence On Dependencies are met.
Unless the rail is instructed to turn off immediately, the previous descriptions also apply to the Sequence Off Dependencies – they must be met before the rail is turned off, the turn off delay (TOFF_DELAY) is applied after the dependencies are met, and so forth.
After a fault, the PMBus specification requires that an OFF/ON sequence occurs before the rail is allowed to restart. The toggle of sequencing pin (such as CONTROL pin and Pin-Selected State GPI) is interpreted to meet this requirement. For example, consider a page that responds to the CONTROL pin and was shut down due to a fault. A toggle low then high on the CONTROL pin is sufficient to restart the page.