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
Describe the bug
The debugging interface will not allow for pausing, stepping through code, nor does it highlight code blocks for projects with pxt-jacdac if there is a physical device connected and powered on or if just a bare microbit is connected to makecode
@ross-inksmith, the problem here is the micro:bit has gone into proxy mode, per design with FE, which means the user code is not running. I have forgotten, is it even possible to run code in simulator when a HW micro:bit is on the Jacdac bus? Happy to jump on a call and revisit the design and look into issues with you.
Describe the bug
The debugging interface will not allow for pausing, stepping through code, nor does it highlight code blocks for projects with pxt-jacdac if there is a physical device connected and powered on or if just a bare microbit is connected to makecode
Tested using the Forward Education Climate Action Kit as well as the KittenBot jacdac kit on Windows
Steps
5 . Toggle the power switch on the breakout board
The text was updated successfully, but these errors were encountered: