SLUA888 May 2018 TPS53622 , TPS53659 , TPS53679 , TPS53681
-
NVM Programming for VR13 Power Controllers
- Trademarks
- 1 Introduction
- 2 Technical Overview
- 3
Use of TI Programming Tools
- 3.1
Fusion Digital Power Designer
- 3.1.1 Build and Export a System (.tifsp) File
- 3.1.2 View a Project File or System File Offline
- 3.1.3 Import a Project File to a Single Online Device
- 3.1.4 Import a System File to an Online System
- 3.1.5 Export CSV Script for Third Party Tools
- 3.1.6 Compare Two Project Files
- 3.1.7 Build a System File from Existing Project Files
- 3.2 Fusion Manufacturing Tool
- 3.3 TI Programming Board
- 3.1
Fusion Digital Power Designer
2.2 Communication Protocol and Interfacing
These devices comply with the PMBus version 1.3 specification. Use this link to find timing and electrical characteristics of the PMBus specification in the PMB Power Management Protocol Specification, Part 1, revision 1.3 available at http://pmbus.org.. The PMBus specification inherits its transport and network layer behavior from the SMBus specification. These devices comply with the SMBus 3.0 specification, which is available at this URL: http://smbus.org/specs/. Use the transaction prototypes to program the device NVM correctly. Refer to the Section 2.3 section for more information about prototype use in NVM programming.
The use of Packet Error Correction (PEC) is optional. If clock pulses are supplied for a PEC byte, these devices use PEC, otherwise they do not. For simplicity, Table 3 lists required transaction types without PEC bytes.
Table 3. SMBus Transaction Types
| Transaction Type | Purpose |
|---|---|
| Send Byte | Used to issue NVM Store operations (STORE_DEFAULT_ALL). |
| Write Byte | Used to change the current PAGE |
| Write Word | Used to Write the value of VOUT_MAX. |
| Read Word | Used to Read the current value of VOUT_MAX. |
| Write Block | Used to Write the USER_DATA commands, which contain most of the NVM storable parameters these devcies support. |
| Read Block | Used to read the USER_DATA commands and checksum (MFR_SERIAL). |
Figure 2. Send Byte Protocol
Figure 3. Write Byte Protocol
Figure 4. Write Word Protocol
Figure 5. Read Word Protocol
Figure 6. Block Write Protocol
Figure 7. Block Read Protocol