Factory reset function seem to be broken

The official pyboard running MicroPython.
This is the reference design and main target board for MicroPython.
You can buy one at the store.
Target audience: Users with a pyboard.
Post Reply
Iriya
Posts: 2
Joined: Thu Jun 02, 2022 1:20 am

Factory reset function seem to be broken

Post by Iriya » Thu Jun 02, 2022 2:07 am

(only) when using Threading Firmware.

I use an unmodified Pyboard v1.1 and latest nightly firmware (v1.18-527-gea9a904b7 (2022-05-27) .dfu) downloaded from https://micropython.org/download/pybv11/, but I found it works incorrectly when using firmware with threading feature.

The manifestation of problems:
When I try to enter the safe mode or factory reset the filesystem, the pyboard would crash, and the green LED would be lit up unsteadily.
Or in another word, when the pyboard boot with USR button pressed, the boot would be failed. Unlike the manifestation described in http://docs.micropython.org/en/latest/p ... reset.html.

I tried the following comparison:
Using older version firmware: In v1.16 or earlier, it works correctly. But all newer release or nightly version have this problem.
Using firmware without threading feature: It works correctly in any version. (But I really need the threading feature.)

Could somebody tell me how to fix this problem? There are some new features in newer firmware which are helpful to my application, so I don't want to keep stay in v1.16

User avatar
pythoncoder
Posts: 5956
Joined: Fri Jul 18, 2014 8:01 am
Location: UK
Contact:

Re: Factory reset function seem to be broken

Post by pythoncoder » Sat Jun 04, 2022 11:06 am

I can confirm that this fails with the release build V1.18 (threaded).

I have raised this ticket. The maintainers will doubtless fix this in due course.
Peter Hinch
Index to my micropython libraries.

Iriya
Posts: 2
Joined: Thu Jun 02, 2022 1:20 am

Re: Factory reset function seem to be broken

Post by Iriya » Fri Jun 17, 2022 1:19 am

pythoncoder wrote:
Sat Jun 04, 2022 11:06 am
I can confirm that this fails with the release build V1.18 (threaded).

I have raised this ticket. The maintainers will doubtless fix this in due course.
It's already 1.19 release now, but the bug is still there.
Actually I raised a ticket before, but it seems to be ignored too.

Post Reply