Wemos S2 mini failed to connect: Cannot configure port
Posted: Thu May 02, 2024 9:03 am
Hi,
recently, I've started testing Wemos S2 mini boards and I've encountered a bit weird behaviour. Esptool operations are failing due to COM port number being changed.
Let me describe it in more detail
1.When I connect board to USB, my PC shows that USB Serial Device COM3 has been connected.
2. Then esptool chip_id or esptool upload fails with
COM3 failed to connect: Cannot configure port, something went wrong. Original message: OSError(22, 'A device which does not exist was specified.', None, 433)
and board is reconnected as COM4
3. With board connected as COM4, esptool chip_id or esptool upload finishes successfully.
After commands exits, board reconnects as COM3 , which means, that subsequent chip_id/upload is going to fail
I've two Wemos S2 mini boards and they both behave the same.
Older ESP32 board I've in my part's bin don't exhibit this issue, their COM port remains the same.
Let me know if you know how to prevent this issue. It can be easily worked around by running upload twice, but still it's a bit annoying.
recently, I've started testing Wemos S2 mini boards and I've encountered a bit weird behaviour. Esptool operations are failing due to COM port number being changed.
Let me describe it in more detail
1.When I connect board to USB, my PC shows that USB Serial Device COM3 has been connected.
2. Then esptool chip_id or esptool upload fails with
COM3 failed to connect: Cannot configure port, something went wrong. Original message: OSError(22, 'A device which does not exist was specified.', None, 433)
and board is reconnected as COM4
3. With board connected as COM4, esptool chip_id or esptool upload finishes successfully.
After commands exits, board reconnects as COM3 , which means, that subsequent chip_id/upload is going to fail
I've two Wemos S2 mini boards and they both behave the same.
Older ESP32 board I've in my part's bin don't exhibit this issue, their COM port remains the same.
Let me know if you know how to prevent this issue. It can be easily worked around by running upload twice, but still it's a bit annoying.