ESP32 reboots on serial connect, send sensor data over serial

[belveder79]

I have two questions, and for brevity I go with one thread here...

My ESP32 Dev Kit reboots on connecting over serial. I flashed the recent release and everything is fine. However, as soon as I open the serial port on my PC with minicom or screen - just to watch the log - the ESP32 reboots automatically. Interestingly, I have a different dev kit here as well, which does not show this behaviour, and for the other 100 ESP8266 and ESP32 devices I had in my hands so far, I haven't seen this.

Questions:

• is this a behaviour that is known?
• is there anything I can do about that?

The second part relates to the question if I can use the serial port just for reporting. In my case I need the ESP32 to send out the messages over the serial (the USB CP2102 or whatever); my serial should get the MQTT messages which are otherwise sent over the network, ideally without all the rest of the logging (timestamp, etc.)

Question:

• is this doable? I'm almost certain it is...
• if indeed yes, how do I set that up? I'm aware of the SerialLog settings, but I don't think they do what I want to...

Thx...

[arendst]

Well there are an every increasing number of DIFFERENT ESP32.

Dev kits without USB hardware using ESP32-C3 (and others) internal USB interface tend to reboot on serial connection.

So without knowing what kind of Dev Kit it is it's just a guess.

[belveder79]

I can live with that... in this case it's a ESP32-WROOM-32 which is built on a AZDelivery ESP32 NodeMCU Module WLAN WiFi Dev Kit C Development Board with CP2102... it's just weird why this happens

[Jason2866]

"AZDelivery ESP32" is not really a manufacturer of boards. Buys cheapest Chinese boards and does brand with "AZDelivery ESP32" and sells them. So you don't know what you get. If you want quality boards buy the devboards from espressif. All other buys are Chinese hardware Lottery. There is no other reliable brand.

[belveder79]

Ok, thx for the answers...

For my second question, I just figured out (stupid me) that it can't get any easier than doing SerialSend <msg>