drivers/at86rf2xx: setting rx timestamp based on symbol counter for ATmega*RFR2 #19605
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 PR adds setting the 802.15.4 packet reception timestamp based on the symbol counter available in ATmega64/128/256RFR2 MCU. The counter restarts every ~19 hours.
To enable the feature the
USEMODULE += gnrc_netif_timestamp
needs to be added to a Makefile.Testing procedure
The
tests/net/gnrc_netif_iee802154
was updated to check the behavior on real boards.The test was performed on
derfmega256
andnrf52840dongle
boards:Two commands
txtsnd 4 bcast test
issued on nrf52840dongle 10 seconds apart, lead to the following result on thederfmega256
:The received packets have
TIMESTAMP
flag and the timestamps differ by 10 seconds.The same command issued on derfmega256 board leads to similar printout on
nrf52840dongle
board, but as its driver doesn't have timestamp handling, the packet has noTIMESTAMP
flag and the value in the timestamp field is random.