|
Description
|
Defined in
|
Composed of/Definition
|
|
Program_Output
|
Figure 1
|
Cmd_Status | I2C_Activity | Rcvd_Data
|
|
User_Input
|
Figure 1
|
Valid input
|
|
Listener_Clk
|
Figure 1
|
I2C clock, which is driven by the target system
|
|
Master_Clk
|
Figure 1
|
I2C clock, which is driven by the I2C Monitor Program
|
|
I2C_Data
|
Figure 1
|
Data obtained from the I2C data line during the high-clock period
|
|
Params_Cmds
|
Figure 2
|
Master_Cmds | Set_Trigger | Monitor_Cmd
|
|
I2C_Activity
|
Figure 2
|
Received I2C data that is obtained while "listening" to the target's I2C bus
|
|
Rcvd_Data
|
Figure 2
|
I2C data that is returned to us while we're operating in master mode
|
|
Data_Avail
|
Figure 2
|
Boolean value (TRUE/FALSE) indicating that data has been supplied by the user; usually for the purpose of aborting operations in progress
|
|
Status_Output
|
Figure 2
|
|
|
Set_Time
|
Figure 2
|
Desired time in ms (unsigned long)
|
|
Cmd_Status
|
Figure 2
|
Returned-error status of a dispatched command
|
|
Input_Buffer
|
Figure 2
|
The buffer of data that the user supplied the I2C program as a command
|
|
Monitor_Cmd
|
Figure 3
|
Command to begin monitoring the I2C bus (GO)
|
|
Mon_Buf_Size
|
Figure 3
|
A buffer address and size for where the monitor should place obtained data
|
|
Mon_Buf_Status
|
Figure 3
|
This is the caller-supplied buffer (containing data), plus the read status
|
|
Set_Trigger
|
Figure 3
|
This is the slave address of I2C device that we want to monitor exclusively (see Slave_Addr below)
|
|
Master_Cmds
|
Figure 4
|
Slave_Buf_Cnt | Slave_Addr | Addr_Data_Cnt
|
|
Slave_Buf_Cnt
|
N/A
|
In master mode, this is the buffer-and its size-where received data from the slave device should be stored
|
|
Addr_Data_Cnt
|
N/A
|
Multi-byte write operations specify both the slave address to write to, the address of the data and the count of bytes to write
|
|
Slave_Addr
|
N/A
|
The 7-bit address assigned to the slave we wish to communicate with (or watch)
|
