-
Notifications
You must be signed in to change notification settings - Fork 3k
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
NCS36510: SPISLAVE enabled #3724
Conversation
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.
What about testing for this enablement?
/morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
Just to be certain, we would like to know how was this tested, if any test reports can be provided. |
@0xc0170 One of the NCS36510 mbed board used as master and one more as slave and tried to exchange data between them. No report maintained, tried basic data exchange. |
please resolve conflicts (sorry for the delay) |
1ef5122
to
a8a31da
Compare
Description
SPISLAVE enabled.
Status
READY
Migrations
SPI slave features can be used.
Related PRs
This PR is one of the feature(SPISLAVE) from #3611. So PR #3611 will be invalid and can be closed.
Todos
Deploy notes
No changes required
Steps to test or reproduce
Can be tested with SPISLAVE ci-test-shield tests