Experiment 11 IIC transmitting Experiment

11.1 Experiment Objective

1. Learning the basic principles of asynchronous IIC bus, and the IIC communication protocol
2. Master the method of reading and writing EEPROM
3. Joint debugging using logic analyzer

11.2 Experiment Implement

1. Correctly write a number to any address in the EEPROM (this experiment writes to the register of 8’h03 address) through the FPGA (here changes the written 8-bit data value by (SW7~SW0)). After writing in successfully, read the data as well. The read data is displayed directly on the segment display.
2. Program the FPGA and press the LEFT push button to execute the data write into EEPROM operation. Press the RIGHT push button to read the data that was just written.
3. Determine whether it is correct or not by reading the displayed number on the segment display. If the segment display has the same value as written value, the experiment is successful.
4. Analyze the correctness of the internal data with SignalTap II and verify it with the illustration of the segment display.

11.3 Experiment

11.3.1 Introduction to EEPROM and IIC Protocol

1. Introduction of EEPROM

EEPROM (Electrically Erasable Programmable Read Only Memory) refers to a charged erasable programmable read only register. It is a memory chip that does not lose data after turning off power.

On the experiment board, there is an IIC interface EEPROM chip 24LC02 with a capacity of 256 bytes. Users can store some hardware configuration data or user information due to the characteristics that the data is not lost after power-off.

1. The overall timing protocol of IIC is as follows
2. Bus idle state: SDA, SCL are high
3. Start of IIC protocol: SCL stays high, SDA jumps from high level to low level, generating a start signal
4. IIC read and write data stage: including serial input and output of data and response signal issued by data receiver
5. IIC transmission end bit: SCL is in high level, SDA jumps from low level to high level, and generates an end flag. See Figure 11.1.
6. SDA must remain unchanged when SCL is high. It changes only when SCL is low

Figure 11.1 Timing protocol of IIC

11.3.2 Hardware Introduction

Each IIC device has a device address. When some device addresses are shipped from the factory, they are fixed by the manufacturer (the specific data can be found in the manufacturer’s data sheet). Some of their higher bits are determined, and the lower bits can be configured by the user according to the requirement. The higher four-bit address of the EEPROM chip 24LC02 used by the develop board has been fixed to 1010 by the component manufacturer. The lower three bits are linked in the develop board as shown below, so the device address is 1010000. See Figure 11.2.

Figure 11.2 EEPROM schematics of IIC device

EEPROM reads and writes data from the FPGA through the I2C_SCL clock line and the I2C_SDA data line.

11.3.3 Introduction to the Program

This experiment has two main modules, IIC reading and writing module and LED display module; The first module is mainly introduced here.

The first step: establishment of the main program framework

The input 8-bit data is needed to be written into the EEPROM, provided by an 8-bit DIP switch.

The second step : Create clock I2C_CLK

First, use the system 50 MHz clock to get a 100 kHz clock with a period of 10us by frequency division as the transmission clock of the IIC protocol. Then, the rising edge, the high state, the falling edge and the low state of the clock are defined by the counter, prepared for the subsequent data reading and writing and the beginning of the IIC protocol. The last line of code means to define a data valid signal. Only when the signal is high, that is, when the data is valid, the IIC clock is valid again, otherwise it is in high impedance. This is also set according to the IIC transport protocol.

The third step: specific implementation of I2C transmission

The entire process is implemented using a state machine. When reset, it is idle state, while data line sda_r is pulled high, clock and data are both valid, i.e. scl_link, sda_link are high; counter num is cleared and read_data is 0. 5ms delay counter is cleared, IIC transmission end signal Iic_done is low thus invalid.

1. IDLE state: When receiving the read enable or write enable signal sw1_r || sw2_r, assign the write control word to the intermediate variable db_r <= `DEVICE_WRITE, and jump to the start state START1;
2. START1 state: pull the data line low when the clock signal is high, generating the start signal of IIC transmission, and jump to the device address state ADD1;
3. Device address status ADD1: After the write control word (device address plus one ‘0’ bit) is transmitted according to MSB (high order priority), the sda_link is pulled low causing data bus in a high impedance state, and jump to the first response state ACK1, waiting for the response signal from the slave (EEPROM).
4. The first response status ACK1: If the data line is pulled low, it proves that the slave receives the data normally, otherwise the data is not written into EEPROM, and then the rewriting or stopping is decided by the user. There is no temporary judgment and processing here, jump directly to the write register address state ADD2, and assign the address BYTE_ADDR written to the intermediate variable (this experiment writes the data into the third register, i.e. BYTE_ADDR = 0000_0011 )
5. Register address status ADD2: Same as (3), it transfers register address to slave and jump to second response status ACK2
6. The second response state ACK2: At this time, it is urgent to judge. If it is the write state sw1, it jumps to the data transfer state DATA, and at the same time assigns the written data to the intermediate variable. If it is the read state sw2, it jumps to the second start state START2 and assign the read control word to the intermediate variable.
7. The second start state START2: it produces a start signal identical to (2) and jumps to the read register address state ADD3
8. Read register address status ADD3: it jumps to the third response status ACK3S after the transfer of the register address that needs to be read out
9. The third response state ACK3: it jumps directly to the data transfer state DATA. In the read state, the data to be read is directly read out immediately following the register address.
10. ACK4 Data transfer status DATA: it needs to be judged here. If it is the read status, the data will be directly output. If it is the write status, the data to be written will be transferred to the data line SDA. Both states need to jump to the fourth response state. ACK4
11. The fourth response status ACK4: it direct jumps to stop transmission STOP1
12. Stop transmission STOP1: it pulls up data line when the clock line is high, generating a stop signal, and jumps to the transfer completion status STOP2
13. Transfer completion status STOP2: it releases all clock lines and data lines, and after a 5ms delay, returns to the IDLE state to wait for the next transfer instruction. This is because EEPROM stipulates that the interval between two consecutives read and write operations must not be less than 5ms.

11.4 Experiment Verification

The first step: pin assignements

See Table 11.1 for the pin assignment.

Table 11.1 IIC protocol transmission experiment pin mapping

The second step: board verification

After the pin assignment is completed, the compilation is performed, and the board is verified after passing.

After the board is programmed, press the LEFT key to write the 8-bit value represented by SW7~SW0 to EEPROM. Then press the RIGHT key to read the value from the write position. Observe the consistency between the value displayed on the segment display on the experiment board and the value written in the 8’h03 register of the EEPROM address (SW7~SW0) (this experiment writes 8’h34). The read value is displayed on the segment display. The experimental phenomenon is shown in Figure 11.3.

Figure 11.3 EEPROM experiment phenomenon