-
Notifications
You must be signed in to change notification settings - Fork 139
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
test the nrf52840 HAL using defmt-test #291
Conversation
this commit adds tests that exercise the GPIO API 3 connections are required: - P0.03 <-> GND - P0.04 <-> VDD - P0.28 <-> P0.29 the first two are used to test the Input API against reference voltages the short-circuit connection is used to test the Input and Output API using the input API that was previously tested
@@ -1,8 +1,2 @@ | |||
[alias] | |||
xtask = "run -p xtask --" | |||
|
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.
moved these into examples/.cargo/config
because rustflags in .cargo/config
compose and w/o the move I ran into knurling-rs/probe-run#143
also check the input state of the pin configured in pull up/down mode
Would it be possible to use the internal pull-up/down resistors to create reference voltages instead? That way it keeps the external wiring to a minimum. |
that's a different test in my opinion (and it's already there in the if we do that and remove |
bors r+ |
Build succeeded: |
this PR adds tests that exercise the GPIO API
3 connections are required:
the first two are used to test the Input API against reference voltages
the short-circuit connection is used to test the Input and Output API using the input API that was
previously tested
I tried testing the Uarte API but ran into #289. It seems to me that we can't test TX/RX loopback or overrun errors with the existing
read
API