boards: update driver at86rf213 to at86rf233 #228
Merged
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
luisan00
approved these changes
Apr 8, 2022
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Contribution description
The driver in m4a-24g it's not reading by auto_init_gnrc_netif and netdec_default, because the referred driver it's wrong, the at86rf213 doesn't exist in samr21. see also in samr21 datasheet about more info.
Testing procedure
Use the RIOT submodule to testing with gnrc_networkin example:
cd RIOT/examples/gnrc_networkingIn the m4a-firmware shell execute the command line:
Then of previous steps, you should see the integrated radio as a network interface
Issues/PRs references