Feat/uart sbc#378
Draft
towynlin wants to merge 6 commits into
Draft
Conversation
Contributor
|
Note that Borealis will require this functionality on usart3 rather than pluart. |
towynlin
force-pushed
the
feat/uart-sbc
branch
3 times, most recently
from
44bf447 to
9f146b8
Compare
older gtest does not handle -Wcharacter-conversion warning from newer clang
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What changed?
Added
native_serial_bridgedev kit app, which treats the PLUART as a 3rd Bristlemouth port. If you run a Raspberry Pi on the other end of that UART with an app built from thebm_sbcrepo, then this new dev kit app bridges the Bristlemouth traffice between the hardware motes with ADINs and processes running on the pi.How does it make Bristlemouth better?
Where should reviewers focus?
Checklist