SLVSJC6 December 2025 TPS544B27W
PRODUCTION DATA
MFR_REVISION is shown in Figure 7-65 and described in Table 7-85.
Return to the Summary Table.
Write Transaction: Block Write
Read Transaction: Block Read
Data Format: unsigned binary (2 bytes)
NVM Back-up: EEPROM
Updates: On-the-fly The MFR_REVISION command provides a location to program the device with data identifying the device's revision. This typically occurs during manufacturing. Data Validity: Attempts to send a MFR_REVISION command for a Block Write with a byte count not equal to 2 bytes are considered as invalid data or unsupported data (ivd) and the device responds as described in the IVD bit in STATUS_CML.
| 15 | 14 | 13 | 12 | 11 | 10 | 9 | 8 |
| MFR_REVISION[15:0] | |||||||
| R/W-XXXXh | |||||||
| 7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 |
| MFR_REVISION[15:0] | |||||||
| R/W-XXXXh | |||||||
| Bit | Field | Type | Reset | Description |
|---|---|---|---|---|
| 15:0 | MFR_REVISION[15:0] | R/W | X | 2-bytes of arbitrarily writable user-storable NVM for manufacturer revision information. This field's NVM is also used to set the value for the PMBus configuration file version located a Security byte addresses 04h and 05h. Additionally, the NVM for MFR_REVISION<7:0> is used to set the value for SVID register 1Eh CFG_FILE_ID. |