Hi Baptiste,
you could try reading out the frame buffer after that
although I am not sure the current mode of operation actually
updates the frame buffer with the ACK frame.
(The data sheet is also kind of unspecific on this.)
Other than that I don't see an easy solution, only porting
the driver to basic operation mode.
Best, Thomas
On 14 Jun 2017, at 23:17 PDT(-0700), Baptiste Clenet wrote:
Which mean that automated ACK by the transceiver is fine.
1 - RIOT sends a frame
2 - Transceiver receives an ACK and transmit a
AT86RF2XX_TRX_STATE__TRAC_SUCCESS
3 - Here I want to get the ACK frame content
4 - Use it with openthread (Have a look here [1] to understand why we
need it)
[1]
https://github.com/openthread/openthread/blob/master/include/openthread/platform/radio.h#L404
Cheers,
2017-06-13 15:46 GMT+02:00 Baptiste Clenet <bapcle...@gmail.com>:
2017-06-13 14:45 GMT+02:00 Oleg <o...@riot-os.org>:
Hi Baptiste!
On 2017-06-13 12:30, Baptiste Clenet wrote:
On netdev event: NETDEV_EVENT_TX_COMPLETE (after
AT86RF2XX_TRX_STATE__TRAC_SUCCESS state), how may I get the ACK
frame
received by at86rf2xx?
The ACK frame is processed automatically by the transceiver. There
is no way
to access it using the extended mode. If you use the base mode, you
will
have to send and process the ACK yourself.
Ok I don't want to process the ACK myself, I only want to get the
frame on AT86RF2XX_TRX_STATE__TRAC_SUCCESS state. Is the ACK frame
store in a register/frame buffer? Or do we must use base mode to get
the ACK frame.
Cheers,
Oleg
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
--
Baptiste
--
Baptiste
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
