ARMmbed / ARMmbed/mbed-os-example-lorawan
DevNonce is random and not incremented
Open
Nobody has claimed this yet.
type: bug
- Dominant language
- C++
- Stars
- 83
- Forks
- 94
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Lorawan 1.1 says that the DevNonce should be incremented with each join. Looking at the Mbed stack I don't see that the nonce is stored on something non-volatile. Also the API does not allow me to set the nonce.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where DevNonce is generated and where join state is stored in the Mbed LoRaWAN stack. Check the LoRaWAN 1.1 requirement against the current API and storage behavior; done means the nonce is incremented for each join, survives restart through non-volatile storage, and can be configured through the API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100