FlashEraseFailure with new microbit v2 (nrf52833)
Open
Nobody has claimed this yet.
target
under-investigation
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
PyOCD v0.32 with python 3.9.6 on Windows 10
Hi, I am trying to flash a binary to my new MicrobitV2 using pyocd, but I get the error below.
The workaround is to drag an drop the binary in the Microbit v2 drive after which it reboots and flashing with pyocd works as normal. Any idea if I can set a flag to force the flashing of a new Microbit v2?
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
Reproduce the failure with pyOCD v0.32, Python 3.9.6, Windows 10, and a new Microbit V2 using the nRF52833. Investigate the flash and erase path for this target; done means a new board can be flashed directly without first dragging a binary onto its drive, or the required flag is documented.
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