You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This does not reproduce with v1 board. Could it be a DAPLink issue?
We are not having this issue with the Python Editor WebUSB implementation, so while I wouldn't discard an issue with DAPLink, it's worth looking into MakeCode first.
In case it helps, see
microbit-foundation/codal-microbit#89 (comment)
"After a USB flash... The bootloader is rebooting once before the application runs. I'm not sure if the reboot happens when there is no display. I'm pretty sure the bootloader is not rebooting on purpose, just that the first jump to 0x27000 ends up running the bootloader again."
This seems to reproduce for any program, whether we use the display or not. I can confirm it does not happen in the Python Eidtor when using webUSB
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
micro:bit only resets once.
This does not reproduce with v1 board. Could it be a DAPLink issue?
We are not having this issue with the Python Editor WebUSB implementation, so while I wouldn't discard an issue with DAPLink, it's worth looking into MakeCode first.
In case it helps, see
microbit-foundation/codal-microbit#89 (comment)
"After a USB flash... The bootloader is rebooting once before the application runs. I'm not sure if the reboot happens when there is no display. I'm pretty sure the bootloader is not rebooting on purpose, just that the first jump to 0x27000 ends up running the bootloader again."
This seems to reproduce for any program, whether we use the display or not. I can confirm it does not happen in the Python Eidtor when using webUSB
The text was updated successfully, but these errors were encountered: