tock / tock/tockloader

Microbit_v2 doesn't reset after flashing

Open
#76 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
44
Forks
59
Avg merge
20h 33m
Merged PRs (30d)
2

Description

When you use Tockloader to install an application or kernel on a Microbit_v2, you must also manually press the reset button afterwards to make the app start. It's not really a bug, but it seems undesirable to me.

So my question: do other boards automatically restart after flashing?

This is solved by adding the flag --openocd-options resume, although that restarts the running application many times, not just once after finishing the program upload. Should that flag be added as a default for the Microbit_v2?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with Tockloader's Microbit_v2 flashing path and the handling of --openocd-options resume; compare whether other boards restart after flashing. Done means the expected post-flash reset behavior is decided and implemented consistently, with the repeated-restart concern addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli, embedded-iot
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.