False "nRF9160_xxAA APPROTECT enabled" causes settings lose by mass erase
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
pyocd: 0.36.0
ubuntu: 22.04.1
Board 1: nRF9161 feather (beta) with RP20240 as probe, circuitdojo.com
Board 2: nRF9151 Connect Kit with nRF52820 as probe, makerdiary.com
pyocd is flashing both boards, but randomly the message
W nRF9160_xxAA APPROTECT enabled: will try to unlock via mass erase [target_nRF91]
is shown and the nRF91 is erased. The very nasty downside is, it erases also the zephyr settings section.
APPROTECT is not activated by me.
Would it be possible, to check, if the 00 are caused by an error and are not read?
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 the target_nRF91 entry point that emits the APPROTECT warning and trace how the protection state is read before mass erase. Reproduce with the nRF9161 Feather and nRF9151 Connect Kit setups described, focusing on intermittent zero or unread values. Done means false detection no longer triggers mass erase and the Zephyr settings section is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100