Test Case: Linux I2C driver testing - Slave Mode. 1. Test Case ID: TC_I2C_Lin_004

Transcription

1 Contents Test Case: Linux I2C driver testing - Slave Mode Test Case ID: TC_I2C_Lin_ Description: Hardware Setup Details: Software Setup Details: Test Execution Procedure: Expected Result: Table of Figure Figure 1 : Test Setup... 2 Figure 2 : Connect Aardvark Adapter... 3 Figure 3 : Configure I2C-SPI mode... 3 Figure 4 : Aardvark GUI Settings... 4 Figure 5 : Slave register output... 4 Figure 6 : 100 bytes Master Write... 5 Figure 7 : 100 bytes Received at slave... 5 Figure 8 : Master Write... 5 Figure 9 : 100 bytes Master Read... 6 Figure 10 : 200 bytes Master Write... 6 Figure 11 : 200 bytes received at slave... 7 Figure 12 : Master Write... 7 Figure 13 : 200 bytes Master Read... 8 Figure 14 : 255 bytes Master Write... 8 Figure 15 : 255 bytes Received at slave... 9 Figure 16 : Master Write... 9 Figure 17 : 255 bytes Master Read Figure 18 : 300 bytes Master Write Figure 19 : 300 bytes Received at slave Figure 20 : Master Write Figure 21 : 300 bytes Master Read

2 Test Case: Linux I2C driver testing - Slave Mode 1. Test Case ID: TC_I2C_Lin_ Description: To test I2C driver slave mode, configure ZCU102 I2C controller as a slave device and Aardvark adapter as a master. Test Communication between them by sending/receiving data. 3. Hardware Setup Details: 1. Board: ZynqMP ZCU102 (I2C Slave) 2. Aardvark Adapter (I2C Master) 3. Host Machine Windows/Linux PC 4. Software Setup Details: Figure 1: Test Setup Download and install USB driver for Aardvark adapter in Linux/Windows PC Refer user manual to know how to install USB driver, go through section ppy7my_sahugvo8khdndbigqfgggmae&url=http%3a%2f%2fwww.totalphase.com% 2Fsupport%2Farticle_attachments%2F %2Faardvarkv5.15.pdf&usg=AFQjCNFtI5Qk_RUg2ZjRCJ8OGcGCgE6y2g Download control center application for Aardvark GUI in Linux/Windows PC from below link Go to installation directory and unzip the software package. Run >./controlctr or Run Control Center serial Aardvark GUI Settings: o To configure Aardvark Adapter, Go to menu: Adapter>Connect. You will get list of available Aardvark Adapters. Select proper Adapter. 2

3 Figure 2: Connect Aardvark Adapter Figure 3: Configure I2C-SPI mode o Set Following Parameters in Aardvark I2C Master window: Clock Rate: 400 khz Slave Address: It can be anything within 7 bit range. Let s take 0x64 as an example. (Please make sure this address must be configured in Linux too) 3

4 Figure 4: Aardvark GUI Settings 5. Test Execution Procedure: Step 1: Register Slave Run 'echo slave-24c02 0x10xx > /sys/bus/i2c/devices/i2c-y/new_device' on the board after bootup. Here xx is the 7 bit slave address configured in aardvark adapter (we have set it 0x64 for a test) and y is the I2C device ID, where ZCU102 will be configured as I2C slave. In Petalinux, ZCU102 I2C controller is on I2C-1. We have selected slave address as 0x64 and hence, command is, 'echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device' Figure 5: Slave register output Free the I2C bus by clicking "Free Bus" on Aardvark GUI. Step 2: Read/Write Data Transfer 100 bytes: 1. Load 100 bytes in message window and add 00 as a first byte. Here 00 is an offset where slave will store data. Initiate Write command by clicking button "Master Write". 4

5 Figure 6: 100 bytes Master Write 2. Run command, 'hexdump C /sys/devices/platform/amba/ff i2c/i2c-1/1-1064/slave-eeprom' on board, to compare the data received. Figure 7: 100 bytes Received at slave 3. To check in Aardvark GUI, first write the address from where you want to read. Write 00 in the message window and click on "Master Write". Figure 8: Master Write 5

6 4. To read the data in GUI, write 100 in the Number of Data Bytes text-box. Now click on "Master Read" button. Figure 9: 100 bytes Master Read 5. You will see the data in Transaction Log. 6. Compare Write and Read data, both should be matching. Transfer 200 bytes: 1. Load 200 bytes in message window and add 00 a first byte. Here 00 is an offset where slave will store data. Initiate Write command by clicking button "Master Write". Figure 10: 200 bytes Master Write 2. Run command, 'hexdump C /sys/devices/platform/amba/ff i2c/i2c-1/1-1064/slave-eeprom' on board, to compare the data received. 6

7 Figure 11: 200 bytes received at slave 3. To check in Aardvark GUI, first write the address from where you want to read. Write 00 in the message window and click on "Master Write". Figure 12: Master Write 4. To read the data in GUI, write 200 in the Number of Data Bytes text-box. Now click on "Master Read" button. 7

8 Figure 13: 200 bytes Master Read 5. You will see the data in Transaction Log. 6. Compare Write and Read data, both should be matching. Transfer 255 bytes: 1. Load 255 bytes in message window and add 00 a first byte. Here 00 is an offset where slave will store data. Initiate Write command by clicking button "Master Write". Figure 14: 255 bytes Master Write 2. Run command, 'hexdump C /sys/devices/platform/amba/ff i2c/i2c-1/1-1064/slave-eeprom' on board, to compare the data received. 8

9 Figure 15: 255 bytes Received at slave 3. To check in Aardvark GUI, first write the address from where you want to read. Write 00 in the message window and click on "Master Write". Figure 16: Master Write 4. To read the data in GUI, write 255 in the Number of Data Bytes text-box. Now click on "Master Read" button. 9

10 Figure 17: 255 bytes Master Read 5. You will see the data in Transaction Log. 6. Compare Write and Read data, both should be matching. Transfer 300 bytes: 1. Load 300 bytes in message window and add 00 a first byte. Here 00 is an offset where slave will store data. Initiate Write command by clicking button "Master Write". Figure 18: 300 bytes Master Write 2. Run command, 'hexdump C /sys/devices/platform/amba/ff i2c/i2c-1/1-1064/slave-eeprom' on board, to compare the data received. 10

11 Figure 19: 300 bytes Received at slave 3. To check in Aardvark GUI, first write the address from where you want to read. Write 00 in the message window and click on "Master Write". Figure 20: Master Write 4. To read the data in GUI, write 300 in the Number of Data Bytes text-box. Now click on "Master Read" button. 11

12 Figure 21: 300 bytes Master Read 5. You will see the data in Transaction Log. 6. Compare Write and Read data, both should be matching. 6. Expected Result: After executing 'echo slave-24c02 0x1064 > /sys/bus/i2c/devices/i2c-1/new_device', slave should be registered. I2c controller in slave mode should be able to read 100, 200, 255 and 300 bytes of data from the Aardvark Adapter without any problem. For 100, 200 and 255 bytes transfer, write respective bytes from Aardvark Adapter (I2C Master) and Read back from ZCU102 (I2C slave). Write and Read data, both should be same. For 300 bytes, write respective bytes from Aardvark Adapter (I2C Master) and Read back from ZCU102 (I2C slave). Write and Read data, both should be mismatched. NOTE: As the size of buffer at back-end is 255, only 255 bytes can be stored. So, if we send more than 255 bytes then, data will be overwritten and we will get data mismatch. 12