SLVSC86A January 2014 – March 2014 UCD9244-EP
PRODUCTION DATA.
In 8-bit VID mode, the four VID input signals are not used. Instead, an 8-bit VID code is transmitted to the UCD9244 through the PMBus / I2C port using one of the VID_CODE_RAILn commands, where n is the rail number from 1 to 4.
NAME | DESCRIPTION(1) | CODE |
---|---|---|
VID_CONFIG | Selects the VID mode, sets the upper and lower voltage limits, and the starting voltage code at power-up. | 0xBB |
VID_CODE_RAIL1 | Selects the VID code used to set the output voltage for Rail 1. | 0xBC |
VID_CODE_RAIL2 | Selects the VID code used to set the output voltage for Rail 2. | 0xBD |
VID_CODE_RAIL3 | Selects the VID code used to set the output voltage for Rail 3. | 0xBE |
VID_CODE_RAIL4 | Selects the VID code used to set the output voltage for Rail 4. | 0xBF |
SYMBOL | PARAMETER | CONDITIONS | TYP | UNITS |
---|---|---|---|---|
TmsgPEC | Message Transmit Time, with PEC | 400 kHz clock, PEC enabled | 162 – 256 | µs |
Message Transmit Time, without PEC | 400 kHz clock, PEC enabled | 126 – 221 | ||
Tvo | End of message until Vout starts changing | 28 – 140 | µs | |
Tmsgvo | Start of message until Vout start changing | 400 kHz clock, PEC disabled | 169 – 314 | µs |
The total time to transmit the serial VID command will vary depending on the other tasks that the UCD92xx processor is performing. Typical packet times varied from 162 to 256µs when the PMBus is configured for a 400 kb/s transfer rate running and the optional PEC byte is enabled. Disabling the PEC byte saves about 35µs and the transfer times are from 126 to 221µs. Note that these are not specified best-case/worst-case timings, but indicate a range given the typical acknowledge overhead in the host and controller.
After the VID packet has been received by the controller there is a delay before the set-point reference DAC is updated. This delay time varies from ~28µs to 140µs (typical ) depending on the existing priority of updating set-point reference DAC when the command is received.
With a 221µs packet transfer time, it would seem possible to send 4500 VID messages per second to the device. Very short bursts at this rate might be acceptable, but doing so for sustained periods could overwhelm the available processing resources in the UCD92xx, causing it to be delayed in performing its other monitoring and fault response tasks. In addition, if multiple hosts are trying to talk on the PMBus at such high rates then bus contention will occur with great regularity.
To prevent these issues, it is prudent to limit the total VID messaging rate to less than 4 messages per millisecond. In a system with four independent hosts, each host might need to be limited to less than 1 message per millisecond. Therefore, to minimize PMBus traffic, it is best to only issue the VID command when a voltage change is required. There is no benefit to sending the same VID code continuously and repeatedly.