Our #NuttX App was waiting for the #LoRaWAN Join Request to be transmitted before receiving the Join Response ... But because we're polling SX1262, we missed the Join Response ... Let's fix this with the multithreading functions from NimBLE Porting Layer
Here's how we check the SX1262 Busy Pin on #NuttX OS ... By reading the GPIO Input
We handle GPIO Interrupts (SX1262 DIO1) in a #NuttX Background Thread ... Awaiting the Signal for GPIO Interrupt
NimBLE Porting Layer doesn't work for multiple Callout Timers on #NuttX OS, unless we loop the thread ... Will submit a Pull Request to Apache NimBLE 👍
Switching a #NuttX GPIO Interrupt Pin to Trigger On Rising Edge ... Crashes with an Assertion Failure ... I'll submit a NuttX Issue, meanwhile I have disabled the assertion
We handle SX1262 GPIO Interrupts in #NuttX with a Background Thread ... That inserts into an Event Queue
How we handle SX1262 GPIO Interrupts in #NuttX OS ... With NimBLE Porting Layer
On #NuttX OS, NimBLE Porting Library needs POSIX Timers and Message Queues
#LoRaWAN Max Message Size depends on 1️⃣ Data Rate 2️⃣ LoRaWAN Region
How often can we send a #LoRaWAN Message? Check the LoRaWAN Airtime Calculator
#LoRaWAN is Time Sensitive! Here's why
QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.