I2C Loopback (FAILED)
Overview
See tests/drivers/i2c for the original scope of tests, its structure and description.
Requirements
You will need an ST-LINK/V2 debug tool adapter already connected to the TiaC Magpie board, which has an already configured UART console connection.
On the TiaC MAGPIE pin headers the following I2C pins must be connected.
Building and Running
Build and run the tests on target as follows:
$ west twister \
--verbose --jobs 4 --inline-logs \
--enable-size-report --platform-reports \
--device-testing --hardware-map map.yaml \
--extra-args SHIELD="loopback_test_tmph" \
--alt-config-root bridle/zephyr/alt-config/tests \
--testsuite-root zephyr/tests --tag i2c
You should see the following messages on host console:
Device testing on: | Platform | ID | Serial device | |---------------------------|----------|-----------------| | magpie_f777ni/stm32f777xx | DT04BNT1 | /dev/ttyUSB0 | INFO - JOBS: 4 INFO - Adding tasks to the queue... INFO - Added initial list of jobs to queue INFO - 1/3 magpie_f777ni/stm32f777xx tests/drivers/i2c/i2c_bme688/drivers.i2c.bme688 FILTERED (runtime filter) INFO - 2/3 magpie_f777ni/stm32f777xx tests/drivers/i2c/i2c_api/drivers.i2c.api FILTERED (runtime filter) INFO - 3/3 magpie_f777ni/stm32f777xx tests/drivers/i2c/i2c_target_api/drivers.i2c.target_api.dual_role ERROR Build failure (device) INFO - .../twister-out/magpie_f777ni_stm32f777xx/tests/drivers/i2c/i2c_target_api/drivers.i2c.target_api.dual_role/build.log INFO - 2294 test scenarios (2077 test instances) selected, 2076 configurations filtered (2074 by static filter, 2 at runtime). INFO - 0 of 1 executed test configurations passed (0.00%), 0 built (not run), 0 failed, 1 errored, with no warnings in 22.66 seconds. INFO - 0 of 1 executed test cases passed (0.00%), 1 blocked on 1 out of total 876 platforms (0.11%). INFO - 16091 selected test cases not executed: 6 skipped, 16085 filtered. INFO - 0 test configurations executed on platforms, 1 test configurations were only built. Hardware distribution summary: | Board | ID | Counter | Failures | |---------------------------|----------|-----------|------------| | magpie_f777ni/stm32f777xx | DT04BNT1 | 0 | 0 | INFO - Saving reports... INFO - Writing JSON report .../twister-out/twister.json INFO - Writing xunit report .../twister-out/twister.xml... INFO - Writing xunit report .../twister-out/twister_report.xml... INFO - Writing target report for magpie_f777ni/stm32f777xx... INFO - Writing JSON report .../twister-out/magpie_f777ni_stm32f777xx.json INFO - -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ INFO - The following issues were found (showing the top 10 items): INFO - 1) tests/drivers/i2c/i2c_target_api/drivers.i2c.target_api.dual_role on magpie_f777ni/stm32f777xx error (Build failure) INFO - INFO - To rerun the tests, call twister using the following commandline: INFO - west twister -p <PLATFORM> -s <TEST ID>, for example: INFO - INFO - west twister -p magpie_f777ni/stm32f777xx -s tests/drivers/i2c/i2c_target_api/drivers.i2c.target_api.dual_role INFO - or with west: INFO - west build -p -b magpie_f777ni/stm32f777xx zephyr/tests/drivers/i2c/i2c_target_api -T drivers.i2c.target_api.dual_role INFO - -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ INFO - Run completed
Open Issues
Dual role with one I2C controller and one I2C device
... ... ... .../zephyr/drivers/i2c/target/eeprom_target.c:234:12: error: 'i2c_eeprom_target_init' defined but not used .../zephyr/drivers/i2c/target/eeprom_target.c:217:43: error: 'api_funcs' defined but not used ... ... ... ... ... ... ... ... ...