[riot-notifications] [RIOT-OS/RIOT] drivers/kw2xrf: Improved event callback policy (#12083)

Ilmu011 notifications at github.com
Mon Sep 16 13:39:32 CEST 2019


And another thing; I didn't even realize it, until you pointed it out, but why is TMR4 used to detect an ACK timeout? There is a dedicated timer for detecting timeouts in RX-operations and that is TMR3. I am working on #10364 right now and the kw41z driver uses TMR3 for this purpose, which makes much more sense to me. This is also smoother since a TMR3 timeout also means that the sequence is aborted, asserting the SEQIRQ flag.

This is described on [page 130](https://www.nxp.com/docs/en/reference-manual/MKW2xDxxxRM.pdf#page=130) of the reference manual.

> When Sequence R is initiated, the sequence manager warms up the receiver (analog and
> digital elements). This process takes 144 us. From this point forward, timer TMR3 can be
> enabled as a “bracketing” timer (software option). If a TMR3 timer match occurs, and
> software has asserted the TC3TMOUT bit, the sequence manager will warm down the
> receiver and return to SEQ_IDLE state.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/12083#issuecomment-531741231
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190916/2034ec8a/attachment.htm>


More information about the notifications mailing list