prvLoRaMACTask() is handling the LoRaWAN Stack via LoRaMacProcess()
When calling LoRaWAN_Send(...) internal state of the LoRaWAN stack is modified, e.g. LoRaMacMcpsRequest() modifies the non volatile MacCtx which is also accessed in LoRaMacProcess()
It's not that I have any actual bug with this, but I want to understand the architecture. Is this is by purpose, or should we actually sync the "sending" of the telegram inside the prvLoRaMACTask() via a queue?
prvLoRaMACTask()
is handling the LoRaWAN Stack viaLoRaMacProcess()
When calling
LoRaWAN_Send(...)
internal state of the LoRaWAN stack is modified, e.g.LoRaMacMcpsRequest()
modifies the non volatileMacCtx
which is also accessed inLoRaMacProcess()
It's not that I have any actual bug with this, but I want to understand the architecture. Is this is by purpose, or should we actually sync the "sending" of the telegram inside the
prvLoRaMACTask()
via a queue?