Reference System: OPB IIC Using the
ML403 Evaluation Platform
XAPP979 (v1.0) February 26, 2007
SummaryThis application note describes how to build a reference system forthe On-Chip PeripheralBus
Inter IC (OPB IIC) core using the IBM PowerPC™405 Processor (PPC405) based embedded
system in the ML403 Embedded DevelopmentPlatform. The reference system is Base System
Builder (BSB) based.
An IIC primer is given and an OPB IIC register referenceis provided. The Xilinx Microprocessor
Debugger (XMD) commands are used for verifying that the OPB IIC core operates correctly.
Severalsoftware projects illustrate how to configure the OPB IIC core, set up interrupts, and do
read and write operations. Some of the software projects interface the OPB IIC to the
MicroChip 24LC04B serial EEPROM with an IIC interface, while others interface to the
TotalPhaseAardvark Adapter,which providesIIC masterandslavefunctionality.The procedure
for using ChipScope™ to analyze OPB IIC functionality is provided. The steps used to build a
Linux kernel using MontaVista are listed. Simulation output files for analyzing basic IIC
transactions are provided.
Included
Systems
This application note includes one reference system:
www.xilinx.com/bvdocs/appnotes/xapp979.zip
Author: Paul Glover, Ed Meinelt, Lester Sanders
Required
Hardware/Tools
The project name used in xapp979.zip is ml403_ppc_opb_iic.
Users must have the following tools, cables, peripherals, and licenses available and installed:
•Xilinx EDK 8.2.02i
•Xilinx ISE 8.2.03
•Xilinx Download Cable (Platform Cable USB or Parallel Cable IV)
NOTICEOF DISCLAIMER: Xilinx is providing this design, code, or information "as is." By providing the design, code, or information as one possible implementation of this feature,
application, or standard, Xilinx makes no representation that this implementation is free from any claims of infringement. You are responsible for obtaining any rights you may
require for your implementation. Xilinx expressly disclaims anywarranty whatsoeverwith respect to the adequacy of the implementation, including but not limited to any warranties
or representations that this implementation is free from claims of infringement and any implied warranties of merchantability or fitness for a particular purpose.
XAPP979 (v1.0) February 26, 2007www.xilinx.com 1
Introduction
IntroductionThis application note accompanies a referencesystem built on the ML403 development board.
Figure 1 is a block diagram of the reference system.
R
OPB
INTC
PowerPC™
405 Processor
PLB
DDR
OPB UART
16550
PLB
BRAM
OPB
IIC
OPB
PLB
X979_01_022307
Figure 1: OPB IIC Reference System Block Diagram
The system uses the embedded PowerPC(PPC) as the microprocessor and the OPB IIC core.
IIC Primer
Figure 2 shows components on an IIC bus.Two IIC masters and three IIC slaves are shown.
The master is responsible for setting up transactions. This includes generating the clock on
SCL and defining which slave is involved in the communication, with an address field, and
which component is transmitting and which component is receiving. Some components are
slave only, while others can transition between master and slave operation.
M1M2
SCL
SDA
S1S2
S3
X979_02_022307
Figure 2: IIC Bus
Figure 3 shows the START and STOP conditions. A START condition is a falling edge on SDA
when SCL is high. A STOP condition is a rising edge on SDA when SCL is high. During data
transfer, the data line is stable on SDA when SCL is high. Data transitions on SDA when SCL
is low. Note that the START and STOP conditions are special conditions, violating the rule that
data cannot transition while SCL is high.
SDA
SCL
StartStop
X979_03_022307
Figure 3: Start and Stop Conditions
XAPP979 (v1.0) February 26, 2007www.xilinx.com 2
Introduction
R
Figure 4 shows the format of the data transfer of two bytes on the IIC bus, beginning with the
START (S) condition and ending with the STOP (P) condition, bounded by an idle IIC (F) bus.
After a START condition, an eight bit field is transmitted containing a 7 bit address and a single
Read/Write (R/W) bit. This 8 bit address/direction field is followedby an Acknowledge bit. After
the address/data field, an eight bit data field is followed by an acknowledge bit (A). The last 8bit data field is followed by a not acknowledge bit (A). This is followed by the STOP condition
(P).
A single message can contain multiple startconditions, or a repeated start, without intervening
STOP conditions.
In this data transfer, there are two acknowledge bits and one Not Acknowledge on the IIC bus.
The distinction between a Not Acknowledge and a No Acknowledge is that Not Acknowledge
occursafter a master has read a byte from a slave and a No Acknowledgeoccurs aftera master
has written a byte to a slave.
A synchronized SCL is generated with its LOW period determined by the device with the
longest low period and its HIGH period determined by the device with the shortest HIGH
period.
FAAR/WSPF
Slave
Address
DataData
A
SDA
SCL
X979_04_012907
Figure 4: Data Transfer on the IIC Bus
Figure 5 shows the data transfer on the IIC bus, beginning with the START condition and
ending with the STOP condition.
P
SDA
Sr
Sr
or
P
STOP or
repeated START
condition
X979_05_022307
SCL
S
or
SR
START or
repeated START
condition
MSB
12127893 - 89
Acknowledgment
signal from slave
Byte complete;
interrupt within slave
Clock lines held low while
interruptsare serviced
Acknowledgment
signal from receiver
ACKACK
Figure 5: Generic Data Transer on the IIC Bus
XAPP979 (v1.0) February 26, 2007www.xilinx.com 3
Reference System Specifics
R
Figure 6 shows the acknowledge bit on the IIC bus.
Data output
by transmitter
Data output
by receiver
SCL from
master
S
START
condition
1289
Not acknowledge
Acknowledge
Clock pulse for
acknowledgment
X979_06_012907
Figure 6: Acknowledge on the IIC Bus
Figure 7 shows bus arbitration of two masters. The IIC bus is a multi-master bus. Masters
monitor the IIC bus to determine if the bus is active. The busis inactive when SCL and SDAare
high for a bus free period tBUF of 1.3 us (FAST) or 4.7 us (STD). If two or more masters
monitoring the IIC bus determine that the bus is free and begin a bus transaction
simultaneously, the IIC bus is arbitrated to determine which master owns the bus. The IIC is a
wired AND bus. This means that the bus is HIGH unless any component is driving it LOW.
Masters monitor the bus evenafter they have starteda transaction as the master.If a master is
not driving the IIC bus low and the bus is low, the master knows that another master is driving
the IIC bus. If a master cannot get the SDA or SCL to go high it loses arbitration. When a master
loses arbitration, it stops transmission. The master driving the bus with the last low when the
other master(s) drives high becomes the master of the bus.
Master 1
Reference
System
Specifics
Master 2
SDA
SCL
S
X979_07_012907
Figure 7: Arbitration of two Masters
In addition to the PowerPC405 processor and OPB IIC, this system includes DDR and BRAM
memory on the PLB, and a UART and interrupt controller on the OPB. Figure 1 provides the
block diagram. Table 1 provides the address map of the ML403 XC4VFX12. This is in the
system.mhs.
Table 3 provides a description of the OPB IIC control register.
Table 3: OPB IIC Control Register
Bit(s)NameDescription
0- 24ReservedReserved.
25GC_EN
26RSTA
XAPP979 (v1.0) February 26, 2007www.xilinx.com 5
General Call Enable. Setting this bit High allows the OPB IIC to respond to a
general call address.
Repeated Start. Writing a “1” to this bit generates a repeated START condition
on the bus if the OPB IIC Bus Interface is the current bus Master. Attempting a
repeatedSTARTat the wrong time, if the busis owned by another Master,results
in a loss of arbitration. This bit is reset when the repeated start occurs. This bit
must be set prior to writing the new address to the Tx FIFO or DTR.
Reference System Specifics
Table 3: OPB IIC Control Register (Contd)
Bit(s)NameDescription
TransmitAcknowledge Enable. This bit specifies thevalue drivenonto the SDA
line during acknowledge cycles for both Master and Slave receivers.
27TXAK
28TX
29MSMS
30
Tx FIFO
Reset
Because Master receivers indicate the end of data reception by not
acknowledging the last byte of the transfer, this bit is used to end a Master
receiver transfer.As a slave, this bit must be set prior to receiving the byte to no
acknowledge.
Transmit/Receive Mode Select. This bit selects the direction of Master/Slave
transfers.This bit does not control the Read/Write bit that is sent on the bus with
the address. The Read/Write bit that is sent with an address must be the LSB of
the address written into the transmit FIFO.
Master/Slave Mode Select. When this bit is changed from 0 to 1, the OPB IIC
Bus Interface generates a START condition in Master mode. When this bit is
cleared, a STOP condition is generated and the OPB IIC Bus Interface switches
to Slave mode. When this bit is cleared by the hardware, because arbitration for
the bus has been lost, a STOP condition is not generated.
Transmit FIFO Reset
occurs to flush the FIFO.
. This bit must be set if arbitration is lost or if a transmit error
R
31ENOPB IIC Enable. This bit must be set before any other CR bits have any effect.
Status Register (SR)
This register contains the status of the OPB IIC Bus Interface. All bits are cleared upon reset.
Table 4 provides a definition of the status register.
Table 4: Status Register Bit Definitions
Bit(s)NameDescription
0 - 23N/AReserved.
24Tx_FIFO_
Empty
25Rc_FIFO_
Transmit FIFO empty. This bit is set High when the transmit FIFO is
empty.
Receive FIFO empty.This is set Highwhen the receive FIFO is empty.
Empty
26Rc_FIFO_
Full
Receive FIFO full. This bit is set High when the receive FIFO is full.
This bit is set only when all sixteen locations in the FIFO are full,
regardless of the value written into Rc_FIFO_PIRQ.
27Tx_FIFO_F
Transmit FIFO full. This bit is set High when the transmit FIFO is full.
ull
28SRWSlaveRead/Write. WhentheIIC Bus Interfacehas been addressed as
a Slave (AAS is set), this bit indicates the value of the read/write bit
sent by the Master. This bit is only valid when a complete transfer has
occurred and no other transfers have been initiated. A “1” indicates
Master reading from Slave. A “0” indicates Master writing to Slave.
29BBBus Busy. This bit indicates the status of the IIC bus. This bit is set
when a START condition is detected and cleared when a STOP
condition is detected.
XAPP979 (v1.0) February 26, 2007www.xilinx.com 6
Reference System Specifics
R
Table 4: Status Register Bit Definitions (Contd)
Bit(s)NameDescription
30AASAddressed as Slave. When the address on the IIC bus matches the
Slave address in the Address Register (ADR), the IIC Bus Interface is
being addressed as a Slave and switches to Slave mode. If 10-bit
addressing is selected this devicewill only respond to a 10-bit address
or general call if enabled. This bit is cleared when a stop condition is
detected or a repeated start occurs.
31ABGCAddressed By a General Call. This bit is set high when another
master has issued a general call and the general call enable bit is set
high, CR(1) = ’1’.
Table 5 provides a register description of the Interrupt Status register.
Table 5: Interrupt Status Register
BitNameDescription
24TFHETransmit FIFO Half Empty
25NAASNot Addressed as Slave
26AASAddressed as Slave
27BNBBus is not Busy
28RFFReceive FiFO Full
29TFETransmit FIFO Empty
30TE/STCTransmit Error/Slave Transmit Complete
31ALArbitration Lost
XAPP979 (v1.0) February 26, 2007www.xilinx.com 7
Reference System Specifics
R
Configuring the OPB IIC Core
Figure 8 shows how to specify the values of IIC generics in EDK. To access the dialog box in
the figure, double click on the OPB IIC core in the EDK System Assembly View..
X979_08_012907
Figure 8: Specifying the Values of OPB IIC Generics in EDK
Microchip 24LC04
The Microchip Technology 24LC04B-I/ST with 4-KB EEPROM is provided on the ML403 board
to store non-volatile data. The EEPROM write protect is tied off on the board to disable its
hardware write protect. The IIC bus is extended to the expansion connector to allow additional
devices to be added to the IIC bus.
Figure 9 shows IIC Bus Devices on the ML403.
XC4VSX12
FPGA
SCL
SDA
Microchip
24LC04B
Expansion
Figure 9: ML403 IIC Bus
I/O
Header
X979_09_022307
The 24LC04 is organized as two blocks of 256 bytes. It has a page write buffer of up to 16
bytes. The 24LC04 operates as an IIC slave. The 24LC04 accepts a control byte which
contains control code, block select, and Read/Writefields shown inFigure 10. The control code
XAPP979 (v1.0) February 26, 2007www.xilinx.com 8
ML403 Board Information
R
is ‘1010 for read and write operations. The A2, A1 bits are dont cares. The A0 bit is used by the
master device to select which of the two 256-word blocks of memory are accessed. The
24LC04 write transactions are either a byte write or a page write. The page write begins the
same as the byte write but instead of generating a stop condition the master transmits up to 16
data bytes to the 24LC04B. The 24LC04 supports current address, random, and sequential
read operations.
Slave
Address
ML403 Board
Information
S
010A2A1
A01
AR/W
X979_10_012907
Figure 10: 24LC04 Control Byte Allocation
According to the MicroChip 24L024B data sheet, the ML403 board has a low-level output
current (IOL) of 3.0 mA at a VCC of 2.5v. The ML403 boards are shipped in the configuration
shown in Figure 11. The board must be modified for this design to work correctly. Replace the
10K Ohm R70 and R71resistors with 833 or 1K Ohm resistors. See Answer Record 24049 for
additional information.
24LC04B - I / ST
1
A0
2
A1
3
A2
4
A3
C280
0.1 µF
TSSOPSU9
VCC
WP
SCL
SDA
VCC2V5
R70
8
10k
7
6
5
2
2
R71
10k
1
1
IIC_SCL
IIC_SDA
X979_11_022307
Figure 11: ML40x Schematic for IIC Connections
XAPP979 (v1.0) February 26, 2007www.xilinx.com 9
ML403 Board Information
R
The resistors are located on the board as shown in Figure 12.
Figure 12: ML40x Resistors
X979_12_022307
XAPP979 (v1.0) February 26, 2007www.xilinx.com 10
Loading...
+ 23 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.