SPI Driver Synchronous - Spi multi slave

This example application demonstrates the multi client feature of the synchronous mode of the SPI driver by reading and writing to two EEPROMs connected to the same SPI bus.

Description

The application uses the synchronous mode of the SPI driver and demonstrates the multi client feature by reading and writing to two EEPROMs connected to the same SPI bus. The example also demonstrates how to setup two different client transfers at two different baud rates.

The example has three RTOS threads for the purpose:

APP_EEPROM1_Tasks: This thread performs write-read operation on the first EEPROM APP_EEPROM2_Tasks: This thread performs write-read operation on the second EEPROM APP_MONITOR_Tasks: This thread checks the status of the EEPROM transfers and turns on the LED if the transfers are successful

The application communicates with two EEPROM 4 click boards that has AT24CM02 EEPROM on it.

Downloading and building the application

To clone or download this application from Github, go to the main page of this repository and then click Clone button to clone this repository or download as zip file. This content can also be downloaded using content manager by following these instructions.

Path of the application within the repository is apps/driver/spi/sync/spi_multi_slave/firmware .

To build the application, refer to the following table and open the project using its IDE.

Setting up the hardware

The following table shows the target hardware for the application projects.

• To run the demo, the following additional hardware are required:
  • Two EEPROM 4 click boards
  • Two mikroBUS Xplained Pro boards

Setting up SAM G55 Xplained Pro Evaluation Kit

• Install EEPROM 4 click boards on the mikroBUS Xplained Pro boards

• Connect the mikroBUS Xplained Pro boards on EXT1 and EXT3 headers of the SAM G55 Xplained Pro Evaluation Kit

• Connect the Debug USB port on the board to the computer using a micro USB cable

Running the Application

1. Build and Program the application using its IDE.
2. The LED indicates success or failure.
   • The LED turns ON when the data read from the EEPROMs matches with the data written to the EEPROMs.

Refer to the following table for LED name:

---