-
Notifications
You must be signed in to change notification settings - Fork 3k
Add GreenTea SPI communication test - wip. #8216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GreenTea SPI communication test - wip. #8216
Conversation
This test cannot be run on CI. It is designed for manual testing. Detailed description is provided in the test.
How about put a readme.md in the folder, rather than writing all the test descriptions in the code comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to the inline comments, this file actually contains 2 "firmware".
To keep things clear & tidy, what do you think about having them splitted in distinct files and use a shared header for the defines & the structures ?
} else if (config.symbol_size <= 16) { | ||
slave_transfer<uint16_t>(&spi_slave, &config); | ||
} else { | ||
slave_transfer<uint16_t>(&spi_slave, &config); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean uint32_t
in the last branch ?
#define BUILD_NONE 0 | ||
|
||
/* Select build type (BUILD_MASTER, BUILD_SLAVE, BUILD_NONE). */ | ||
#define BUILD_TYPE BUILD_MASTER |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This forces the BUILD_TYPE
to BUILD_MASTER
. Is that intended ?
What about giviong the BUILD_TYPE as command line argument and only build/run this test if BUILD_TYPE
is defined to make it transparent in CI ?
@mprse Any more work being done on this? @ARMmbed/mbed-os-maintainers This PR's unittests also needs to be restarted. |
Closing this PR appears to have idled for too long. Feel free to reopen once updates are available. |
* f) When both sides can handle the specified configuration, then slave and master | ||
* loads the configuration and perform communication test. | ||
* | ||
* 3. Steps to run the test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- comes before 3. :D
Description
Provide SPI communication test and test header file based on the new HAL API description.
This PR can not be merged until PR which defines the new HAL API and adds at least one example implementation is merged. Probably then the test will have to be adapted to the final API version.
Detailed description is provided in the test.
Please assign @ithinuel as a reviewer.
Pull request type