Nitropy nk3 test #239
Merged
Nitropy nk3 test #239
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexgithublab
force-pushed
the
nitropy-nk3-test
branch
3 times, most recently
from
bc89950 to
220fdfe
Compare
alexgithublab
force-pushed
the
nitropy-nk3-test
branch
from
431ef0b to
dae1ea6
Compare
|
nice, will be next in the merge-queue ~friday |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems like nitropy nk3 test is very useful to know if the nk is damaged or not.
But in the documentation this test is only visible in the firmware update section.
readme changed to add a command to make the build working
plus some dead link and wrong code