I had to make some tweaks to mbed_app.json to add pin defines that the SD driver requires. However, the SPI tests continue to use the pin definitions for SPI_MOSI, etc in mbed_app.json. Normally, these resolve to D11, which usually targets have defined. If D11-D13 are not defined, or the SPI pins need to be connected through somewhere else, then the target overrides section needs to be updated for the device under test.
Test Results
I tested this on a few targets, including those with SD component and SPI_MOSI already available (e.g. K64F), and those that have none of this (e.g DRAGONFLY_L471QG, and other new platforms).
More platforms should be tested. But, this should work on any target with D10, D11, D12, D13 defined, and having SPI functionality on those pins.
Background
Mbed OS 5.10 added support for SD Card driver in Mbed OS components. The CI Test Shield repo needs to be updated accordingly. This PR bumps it up to the latest available Mbed OS release 5.11.3.
It should fully fix https://github.com/ARMmbed/ci-test-shield/issues/87 & https://github.com/ARMmbed/ci-test-shield/issues/82
Details
I had to make some tweaks to mbed_app.json to add pin defines that the SD driver requires. However, the SPI tests continue to use the pin definitions for SPI_MOSI, etc in mbed_app.json. Normally, these resolve to D11, which usually targets have defined. If D11-D13 are not defined, or the SPI pins need to be connected through somewhere else, then the target overrides section needs to be updated for the device under test.
Test Results
I tested this on a few targets, including those with SD component and SPI_MOSI already available (e.g. K64F), and those that have none of this (e.g DRAGONFLY_L471QG, and other new platforms).
More platforms should be tested. But, this should work on any target with D10, D11, D12, D13 defined, and having SPI functionality on those pins.