Port, board and/or hardware
DF Robot FireBeetle 2 ESP32-C6 V1.2
MicroPython version
MicroPython v1.26.1 on 2025-09-11; ESP32C6 module with ESP32C6
mpremote 1.26.1
Reproduction
- Connect board to USB C port
- Run
mpremote in terminal
Expected behaviour
Expected to give a REPL prompt, respond to commands.
Observed behaviour
Ca 50% of the times the board gets connected, mpremote will output
Connected to MicroPython at /dev/cu.usbmodem101
Use Ctrl-] or Ctrl-x to exit this shell
But >>> never appears.
In this state, the pressing Ctrl-x or Ctrl-d have no effect. Pressing the reset button on the board will instantly throw an error message (ending in OSError: [Errno 6] Device not configured). Pressing Ctrl-] will dutifully terminate the program. Launching it again afterwards will exhibit the same behavior. Running mpremote ls in this state will similarly hang with no output.
Additional Information
I have observed this with multiple boards of the same model, running fresh installations of MicroPython (no additional software or boot scripts installed). This also occurred on the computers of my students (predominantly Apple machines).
I am unsure if this is possibly connected to #17865 (and #17960). I will try to see if an older version makes any difference.
Code of Conduct
Yes, I agree
Port, board and/or hardware
DF Robot FireBeetle 2 ESP32-C6 V1.2
MicroPython version
MicroPython v1.26.1 on 2025-09-11; ESP32C6 module with ESP32C6
mpremote 1.26.1
Reproduction
mpremotein terminalExpected behaviour
Expected to give a REPL prompt, respond to commands.
Observed behaviour
Ca 50% of the times the board gets connected,
mpremotewill outputBut
>>>never appears.In this state, the pressing Ctrl-x or Ctrl-d have no effect. Pressing the reset button on the board will instantly throw an error message (ending in
OSError: [Errno 6] Device not configured). Pressing Ctrl-] will dutifully terminate the program. Launching it again afterwards will exhibit the same behavior. Runningmpremote lsin this state will similarly hang with no output.Additional Information
I have observed this with multiple boards of the same model, running fresh installations of MicroPython (no additional software or boot scripts installed). This also occurred on the computers of my students (predominantly Apple machines).
I am unsure if this is possibly connected to #17865 (and #17960). I will try to see if an older version makes any difference.
Code of Conduct
Yes, I agree