[riot-devel] Netdev2 State changes
peter.kietzmann at haw-hamburg.de
Tue Sep 13 09:23:18 CEST 2016
there might be code snippets that actively wait for a state transition,
but AFAIK not in the netdev part any more. Then there is interrupt
handling which signals tx/rx start/end points to the upper layer. Of
course you can't implement anything once it's not available on the
device. The great thing about netdev is that it's pretty generic and you
don't *need* to implement every function/message/interrupt/state
change/whatsoever to get the device running.
But looking at the data sheet I stumbled upon the RFSTATE register which
signals the following (useful) sates:
111 = RTSEL2
110 = RTSEL1
101 = RX
100 = TX
011 = CALVCO
010 = SLEEP
001 = CALFIL
000 = RESET
In addition there is the INTSTAT register which seems somehow similar to
the Atmel radio. Where exactly did you stuck? Could you be a more precise?
Am 11.09.2016 um 17:38 schrieb Neo:
> Dear radio module driver developers,
> as far as I have seen, the netdev2 architecture reads several time the
> state of the radio chip to synchronize with the hardware dependent part
> of the driver (state changes). This is wonderful if the radio chip has a
> register which shows the actual state of the radio-modul - like the
> TRX_STATUS register inside of the Atmel chips.
> What could be done, if the radio chip doesn't have such a register or
> shows only rudiment state informations to synchronize/trigger the
> netdev2 part of the driver.
> The MRF24J40 from Microchip for example shows only the following useful
> state information:
> Transmission is done in the RX state without any changes, just trigger
> the transission (TXNCON-Reg./TXNTRIG-Bit).
> Thanks a lot!
> devel mailing list
> devel at riot-os.org
Hamburg University of Applied Sciences
Dept. Informatik, Internet Technologies Group
Berliner Tor 7, 20099 Hamburg, Germany
More information about the devel