drivers/at86rf2xx: support frame retry reporting on AT86RFR2#14596
drivers/at86rf2xx: support frame retry reporting on AT86RFR2#14596aabadie merged 1 commit intoRIOT-OS:masterfrom
Conversation
|
@aabadie has the hardware and could test! |
|
Testing this PR with No idea if this is expected or not. |
|
If it gets no ACK is will re-try as often as you have configured it to do. |
Thanks but sorry, I don't know about it that much. Do you have something more precise ? |
|
I don't have the hardware with me, but conceptually makes sense to me |
The radio will send the the frame a number of times until it receives an ACK from the destination if the ACK requested flag is set. If you send a packet to a node that doesn't exist, the radio will try that many times to deliver the packet. |
At86rfr2 doesn't report retries directly, but it can generate a TX start interrupt for each (re)try, so we can count manually.
ea615e4 to
0871b69
Compare
|
So I guess the output was correct. |
Contribution description
AT86RFR2 doesn't report retries directly, but it can generate a TX start interrupt for each (re)try, so we can count manually.
Testing procedure
Currently retry count is not used anywhere in RIOT.
So you will either need #14448 or you manually add
to check that retries are reported correctly.
Issues/PRs references
Missing feature from #9172