Here's how we enable #LoRaWAN for our #NuttX Build in GitHub Actions ... Let's do Automated NuttX Testing with LoRaWAN! 👍

https://github.com/lupyuen/incubator-nuttx/blob/master/.github/workflows/bl602-commit.yml#L91-L200

We update #BL602 Auto Flash & Test to send the "lorawan_test" command ... Which will start the LoRaWAN Test on #NuttX OS

https://github.com/lupyuen/remote-bl602/blob/main/scripts/test.sh#L108-L111

#BL602 Auto Flash & Test ... Now auto-tests the #LoRaWAN Stack on Apache #NuttX OS! 🎉

https://youtu.be/JtnOyl5cYjo

#LoRaWAN is a great Auto-Test for Apache #NuttX OS ... It tests GPIO Input / Output / Interrupt, SPI, Timers, Message Queues, PThreads AND Strong Random Number Generator!

https://github.com/lupyuen/remote-bl602/

If #BL602 Auto-Test successfully joins a #LoRaWAN Network ... Means that everything is super hunky dory on Apache #NuttX OS ... GPIO Input / Output / Interrupt, SPI, Timers, Message Queues, PThreads AND Strong Random Number Generator! 👍

https://github.com/lupyuen/remote-bl602/#output-log-for-release-build

PineCone #BL602 connected to SBC for Auto Flash & Test ... Plus Semtech SX1262 for #LoRaWAN Auto-Testing

https://github.com/lupyuen/remote-bl602/#run-the-script

What are these addresses in the #NuttX Stack Trace? Let's do Auto Crash Analysis for #BL602 ... And see the Source Code for the Stack Trace

https://github.com/lupyuen/remote-bl602/#output-log-for-upstream-build

Our Crash Analysis Script finds #BL602 Code Addresses in the Output Log ... And shows the matching Source Code from the #NuttX RISC-V Disassembly ... Which was auto-generated by GitHub Actions

https://github.com/lupyuen/remote-bl602/blob/main/scripts/test.sh#L129-L152

Now our Crash Analysis Script shows the matching Source Code whenever #NuttX crashes 👍

https://github.com/lupyuen/remote-bl602/#output-log-for-upstream-build

We also match up the Data Addresses in the #NuttX Stack Trace with the RISC-V Disassembly ... Not very interesting now, might be useful later

https://github.com/lupyuen/remote-bl602/#output-log-for-upstream-build

Here's a demo of #BL602 Auto Flash & Test ... With #NuttX Crash Analysis

https://github.com/lupyuen/remote-bl602/

Now we can Flash & Test Apache #NuttX OS on #BL602 ... Remotely from a Phone! 🎉

https://github.com/lupyuen/remote-bl602/

Merged a huge bunch of #NuttX Upstream Updates ... LoRaWAN still works great! 🎉 Testing upstream updates is so much easier with #BL602 Auto Flash & Test 👍

https://github.com/lupyuen/incubator-nuttx/pull/21

https://github.com/lupyuen/remote-bl602/

#BL602 Auto Flash & Test creates Duplicate #LoRaWAN Nonces ... Because the Boot Timing is always identical! Let's fix this by adding Internal Temperature Sensor Data to the Entropy Pool

https://lupyuen.github.io/articles/lorawan3#lorawan-nonce

Here's how we read #BL602's Internal Temperature Sensor ... And add the data to the Entropy Pool in #NuttX OS ... To create truly random LoRaWAN Nonces

https://github.com/lupyuen/lorawan_test/blob/main/lorawan_test_main.c#L772-L797

#NuttX now generates different #LoRaWAN Nonces for every #BL602 Flash & Test ... And the Join Network Request always succeeds! 🎉

https://github.com/lupyuen/incubator-nuttx/releases/tag/release-2022-01-19

Automagically Flash and Test Apache #NuttX OS on #BL602 ... All shall be explained in this article

https://lupyuen.github.io/articles/auto?1

Here's why we Auto Flash and Test #BL602 ... Inspired by Remote #PineTime

https://lupyuen.github.io/articles/auto?2