Start FPGA getting started guide in target.md #1083
Conversation
Start getting started guide for the FPGA test shield.
Add more details about connecting the FPGA test shield.
|
ping @mprse |
mprse
left a comment
mprse
left a comment
There was a problem hiding this comment.
Only 2 minor comments, otherwise ok.
| ``` | ||
| mbed test -t <toolchain> -m <target> -n mbed-os-tests-mbed_hal* | ||
| ``` | ||
|
|
There was a problem hiding this comment.
if PR ARMmbed/mbed-os#10820 will come in in current form, then:
mbed-os-tests-mbed_hal* -> tests-mbed_hal_fpga_ci_test_shield*.
There was a problem hiding this comment.
I just realized that this line is for general HAL testing, so please ignore this comment.
docs/porting/target/target.md
Outdated
| 1. Add the `FPGA_CI_TEST_SHIELD` component to the Device Under Test in the `targets.json` configuration file. | ||
| 1. Run the test: | ||
|
|
||
| `mbed test -t GCC_ARM -m K66F -n tests-mbed_hal_fpga_ci_test_shield-spi_slave -v` |
There was a problem hiding this comment.
At the moment spi_slave will be available only on spi feature branch. I suggest selecting different test which will be available on master (e.g. tests-mbed_hal_fpga_ci_test_shield-spi).
|
@jamesbeyond ping |
Update test code to code that points to master instead of a feature branch, as requested in comments.
|
As this has been approved by an engineer, I'm going to merge it. If there are any other updates, please raise them in a new PR. |
Apply changes from PR #1083 to v5.13.
Start getting started guide for the FPGA test shield.