I am stummped. On the reciever board, when I call wifi.begin() on a nodeMCU (Wroom32) it drops the espnow packets comming in from a dfrobot esp32C3. If I call wifi.disconnect() or comment out wifi.begin() the packets arrive 100% of the time.

Then I swapped the reciever board to also a dfrobot ...

Ok so after an hour of module testing, I found that 'one line of code' responsible for the bad behaviour I was seeing. I forgot that my battery library I wrote will set the board into hibernation mode (deep sleep without a timer wakeup) if battery voltage was low (no battery was even connected ...

The thing is the serial monitor prints nothing, no boot load, no core dump nor crash report. Sometimes there is a "waiting for download" msg printing tho.

What I do is I take my code apart, upload bit by bit and see what causes this behaviour. It's a pain, but it's the best fix I have so far.

I ...

Every so often the board won't execute its code, and needs a manual reset just to reconnect the usb back onto my pc (win 10). I'm using platformio with the Arduino framework.

I have been using ESP's for a year and a half, I love them, however this C3 mini is a real pain sometimes.

Any ideas what ...

Hm, I can't find a proper datasheet for the C3 version of that board, but assuming it uses the internal USB-serial-JTAG converter, you could have configured one of the USB pins as a GPIO. In this case, you need to force the chip into download mode. Easiest way is to connect GPIO9 to ground and ...

My pc fails to recognize my DFRobot Beetle dev board v 1.0. It uses the ESP32-C3-mini-1. It works out the box then after some uploads no connection or the connection is cycling on-off...

Using Windows 10 OS. Swapping Arduino IDE and VSCode around don't work. Cool term wont connect nor see it on com ...