InfiniTimeOrg / InfiniTimeOrg/InfiniTime
Restrict DFU updates to a specific SoftDevice version for safety
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
- I searched for similar bug reports and found none was relevant.
What happened?
some users brick their devices by installing the DFU ZIP files of InfiniTime
What should happen instead?
FW metadata in ZIP should disallow
Reproduction steps
Currently DFU zip is produced without --sd-req option: https://github.com/InfiniTimeOrg/InfiniTime/blob/develop/src/CMakeLists.txt#L903
This makes dfu.zip harmful for some bootloaders used on nRF52 devices.
A simple solution here is to add --sd-req with pseudo SD code.
More details?
No response
Version
HEAD
Companion app
No response
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 at src/CMakeLists.txt around line 903 and inspect how the DFU ZIP is generated and how SoftDevice metadata is currently handled. Confirm the appropriate pseudo SoftDevice requirement from the surrounding build configuration or project history, then verify that generated ZIP metadata restricts installation to compatible nRF52 bootloaders.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake
- Domain
- build-system, embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100