For the record, this is the earlier topic where this was discussed: https://esp32.com/viewtopic.php?f=13&t=1908

The issue identified in that topic isn't fixed yet, but we'll update the topic once it is.

Based on the varying crash cause, this looks very much like a brownout... unfortunately brownout detector support hasn't been merged yet, so hard to tell for sure. Do you have a different USB cable to try? It doesn't happen very often, but I remember there were a few reports of brownout like issues ...

On hold for a while — we are working on improvements to OpenOCD.

Can you show the part of the code where you register /dev/console via esp_vfs_register?

NVS functions (C API) do locking internally, preventing concurrent access.

Actually it doesn't need d2xx API. It's an option, but the default (libusb1.0) also works well.
You still need a udev rule to avoid loading serial port driver though.

Could you give a bit more info about the hardware? ESP-WROOM32 is a module which isn't normally connected to USB port directly. Usually there is some board involved which has a voltage regulator and USB/UART converter.

Would be very interested in the steps to reproduce, or any clues related to network setup/equipment. If anything, that's a very neat undocumented feature </espressif hat off>

Could you please describe the connections you have to the module and measurement method? WROOM32 should not need any software mods to achieve 5uA deep sleep current.

It seems to be working without the powerdown command? How necessary is that command and is there an API to do that? Depending on the flash chip specs, with powerdown you can get even lower current consumption. There's no API for this since this hasn't been a very common requirement/feature. It's fa...