Radio dev updates with some changes to template that may need to be looked at #12
Conversation
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
This is an update to the drivers accounting for the new SX1280 datasheet revision.
This is just minor fixes to the comments in the driver code, as well as further testing of the hardware.
These are big updates to how we transmit, test code for main.c, and reformatting.
update
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.
Merging radio development updates with a focus on optimal long-range config at SF12, 400 kHz, and implementing a test for large packet transmission over a task in main.c.
Spreading Factor 12 and 400 kHz bandwidth was found for ideal testing inside the mezzanine.
In the main.c of the limestone-template, a 2-chunk transmission test is used to split a large 375-byte payload into two LoRa packets for sequential transmission and putting it back together.
Should be noted that the testing logic is currently integrated directly into limestone-template's main.c's default task, so it should be reviewed to decide if this is acceptable or if it should have its own dedicated template or radio_test_main.c file to keep the limestone-template clean and standardized