<h1>iicps v2_2</h1><p>This is an implementation of IIC driver in the PS block. The device can be either a master or a slave on the IIC bus. This implementation supports both interrupt mode transfer and polled mode transfer. Only 7-bit address is used in the driver, although the hardware also supports 10-bit address.</p>
<p>IIC is a 2-wire serial interface. The master controls the clock, so it can regulate when it wants to send or receive data. The slave is under control of the master, it must respond quickly since it has no control of the clock and must send/receive data as fast or as slow as the master does.</p>
<p>The higher level software must implement a higher layer protocol to inform the slave what to send to the master.</p>
<p><b>Initialization & Configuration</b></p>
<p>The <aclass="el"href="struct_x_iic_ps___config.html">XIicPs_Config</a> structure is used by the driver to configure itself. This configuration structure is typically created by the tool-chain based on HW build properties.</p>
<p>To support multiple runtime loading and initialization strategies employed by various operating systems, the driver instance can be initialized in the following way:</p>
<li>XIicPs_LookupConfig(DeviceId) - Use the device identifier to find the static configuration structure defined in <aclass="el"href="xiicps__g_8c.html">xiicps_g.c</a>. This is setup by the tools. For some operating systems the config structure will be initialized by the software and this call is not needed.</li>
<li>XIicPs_CfgInitialize(InstancePtr, CfgPtr, EffectiveAddr) - Uses a configuration structure provided by the caller. If running in a system with address translation, the provided virtual memory base address replaces the physical address in the configuration structure.</li>
</ul>
<p><b>Multiple Masters</b></p>
<p>More than one master can exist, bus arbitration is defined in the IIC standard. Lost of arbitration causes arbitration loss interrupt on the device.</p>
<p><b>Multiple Slaves</b></p>
<p>Multiple slaves are supported by selecting them with unique addresses. It is up to the system designer to be sure all devices on the IIC bus have unique addresses.</p>
<p><b>Addressing</b></p>
<p>The IIC hardware can use 7 or 10 bit addresses. The driver provides the ability to control which address size is sent in messages as a master to a slave device.</p>
<p><b>FIFO Size </b> The hardware FIFO is 32 bytes deep. The user must know the limitations of other IIC devices on the bus. Some are only able to receive a limited number of bytes in a single transfer.</p>
<p><b>Data Rates</b></p>
<p>The data rate is set by values in the control register. The formula for determining the correct register values is: Fscl = Fpclk/(22 x (divisor_a+1) x (divisor_b+1))</p>
<p>When the device is configured as a slave, the slck setting controls the sample rate and so must be set to be at least as fast as the fastest scl expected to be seen in the system.</p>
<p>The user must connect the interrupt handler of the driver, XIicPs_InterruptHandler to an interrupt system such that it will be called when an interrupt occurs. This function does not save and restore the processor context such that the user must provide this processing.</p>
<p>The driver handles the following interrupts:</p>
<ul>
<li>Transfer complete</li>
<li>More Data</li>
<li>Transfer not Acknowledged</li>
<li>Transfer Time out</li>
<li>Monitored slave ready - master mode only</li>
<li>Receive Overflow</li>
<li>Transmit FIFO overflow</li>
<li>Receive FIFO underflow</li>
<li>Arbitration lost</li>
</ul>
<p><b>Bus Busy</b></p>
<p>Bus busy is checked before the setup of a master mode device, to avoid unnecessary arbitration loss interrupt.</p>
<p><b>RTOS Independence</b></p>
<p>This driver is intended to be RTOS and processor independent. It works with physical addresses only. Any needs for dynamic memory management, threads or thread mutual exclusion, virtual memory, or cache control must be satisfied by the layer above this driver.</p>
<dlclass="note"><dt><b>Note:</b></dt><dd>. Less than FIFO size transfers work for both 100 KHz and 400 KHz. . Larger than FIFO size interrupt-driven transfers are not reliable on busy systems where interrupt latency is high. . Larger than FIFO size interrupt-driven transfers are not reliable for data rate of 400 KHz. . Larger than FIFO size polled mode transfers work reliably.</dd></dl>
<pre> MODIFICATION HISTORY:</pre><pre> Ver Who Date Changes
