UG:309
Page 8
The sequence for sending the data in Figure 6 applies to a generic I
2
C interface, not the Buck GUI
software. There are many devices available on the market (including microcontrollers) that may be
configured for this function. In the end, the final result is the same. The sequence was:
START WRITE 98h 2 Bytes 1Ah,00h followed by STOP
START READ 99h 1 Byte followed by STOP
The returned value in the data field is the actual fault register value sent by the PI33xx‑xx.
Figure 7 shows the bus capture of the instructions sent after clicking on the “Clear” button using Buck
GUI. Here there are four I
2
C messages sent. The address field shows the address of the PI33xx‑xx and
then there are two bytes of data. The first byte is the address of the FREG_CLR register. The second byte
is the data. The next message is a read of the address. This read is performed by the LinkM and is not
needed to make the transaction complete. This command could be sent by a generic I
2
C interface as:
START WRITE 98h 2 Bytes 1Bh,00h followed by STOP
START WRITE 98h 2 bytes 1Ah,00 followed by STOP
START READ 99h 1 Byte followed by STOP
The data returned should be the same as seen previously. In the event an actual fault occurs, the
Buck GUI will indicate the fault graphically as a result of decoding the fault register. Figure 8 shows
the I
2
C bus capture of the event, while the Buck GUI decodes the fault and gives a visual indication as
shown in Figure 9.
Figure 6
Bus capture read fault register
with generic I
2
C™ interface
Figure 7
I
2
C bus capture clear fault
register using the Buck GUI
and LinkM™
Summary of Contents for PI33 EVAL1 Series
Page 13: ...UG 309 Page 13 Figure 14 PI33xx xx SYNC 1000 timing Figure 15 PI33xx xx SYNC 1111 1 4MP ...
Page 14: ...UG 309 Page 14 Figure 16 PI33xx xx SYNC 1110 1 3MP Figure 17 PI33xx xx SYNC 1101 1 2MP ...
Page 15: ...UG 309 Page 15 Figure 18 PI33xx xx SYNC 1100 2 3MP Figure 19 PI33xx xx SYNC 1001 3 4MP ...
