Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

I've been running into some 030 errors on the micro:bit V2 recently (microbit-foundation/micropython-microbit-v2#228) which I believe are from the underlying codal layer. Is there any (easy!) way to have this displayed for 60 seconds and then automatically restart MicroPython as if the reset button had been pressed? Or just restart? That would allow my program to recover (as a workaround) and for my particular application that would be a reasonable solution.

While I'm here does anyone know of a bit of hardware that can sit inbetween a micro:bit's edge connector and a socket to allow access to the pins for troubleshooting? I've only found the ElecFreaks edge:bit so far and I've found it in stock so far...

I noticed this forum area is called nRF. This might not be obvious for novices seeking to post questions about MicroPython on the micro:bit (V1 and V2).

You must be logged in to vote

Replies: 1 comment

Comment options

For the hardware troubleshooting digression I've just found the 4tronix Bit:Zero Breakout for BBC Micro:Bit.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
🔌
nRF
Labels
None yet
1 participant
Morty Proxy This is a proxified and sanitized view of the page, visit original site.