zephyr/tests/drivers/i2c/i2c_slave_api
Rajavardhan Gundi ff4e84ba45 tests: i2c_slave_api: Add test for mec1501modular_assy6885 board
This commit adds a DTS overlay file for mec1501modular_assy6885.

Signed-off-by: Rajavardhan Gundi <rajavardhan.gundi@intel.com>
2021-01-20 14:16:27 -05:00
..
boards tests: i2c_slave_api: Add test for mec1501modular_assy6885 board 2021-01-20 14:16:27 -05:00
common tests: convert DEVICE_AND_API_INIT to DEVICE_DEFINE 2020-12-19 20:05:40 -05:00
src Revert "drivers: move eeprom_slave driver to tests directory" 2020-12-16 16:39:49 -05:00
CMakeLists.txt
Kconfig
README.txt tests: i2c_slave_api: document test requirements and design 2020-08-13 11:49:12 +02:00
prj.conf Revert "drivers: move eeprom_slave driver to tests directory" 2020-12-16 16:39:49 -05:00
testcase.yaml tests: i2c: i2c_slave_api add nucleo_g071 2020-12-14 13:17:46 -05:00

README.txt

I2C Slave API test
##################

This test verifies I2C slave driver implementations using two I2C
controllers on a common bus.  The test is supported by a test-specific
driver that simulates an EEPROM with an I2C bus follower ("slave")
interface.  Data is pre-loaded into the simulated devices outside the
I2C API, and the Zephyr application issues commands to one controller
that are responded to by the simulated EEPROM connected through the
other controller.

In slightly more detail the test has these phases:

* Use API specific to the simulated EEPROM to pre-populate the simulated
  devices with device-specific content.
* Register each simulated EEPROM as a I2C follower device on a bus.
* Issue commands on one bus controller (operating as the bus leader
  (master)) and verify that the data supplied by the other controller
  (as bus follower) match the expected values given the content known to
  be present on the simulated device.

Transfer of commands from one bus controller to the other is
accomplished by hardware through having the SCL (and SDA) signals
shorted to join the two buses.

Presence of this required hardware configuration is identified by the
`i2c_bus_short` fixture.  If the buses are not connected as required,
or the controller driver has bugs, the test will fail one or more I2C
transactions.