Here is the output of a few other commands for reference:

$ python -m esptool --chip esp32 -p /dev/cu.usbserial-1101 flash_id
esptool.py v4.8.1
Serial port /dev/cu.usbserial-1101
Connecting....
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse ...

I cut all the connections to IO12, IO13, IO14, and IO15 (TDI, TCK, TMS, TDO) and verified discontinuity, so they're effectively floating other than how they are connected internally in the WROVER module.

The boot:0x17 message in the console indicates IO12 was low during boot and there isn't ...

I recently produced two prototype boards at JLCPCB with ESP32-WROVER-E modules attached to an FTDI FT2232HL UART chip. I'm currently unable to flash firmware onto either board and the idf.py software tells me:


Connecting....
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core ...

Occasionally when I pause the system for long periods of time while debugging I'll get a spurious panic abort.

The function that crashes is (*s_log_print_func)() in esp_log_writev() in log.c and the calling code seems to be the function wifi_log() in the library libnet80211.a.

The tag is "wifi ...

Hello,

I'm using VSCode 1.91.0 with ESP-IDF 1.8.0 on MacOS Sonoma 14.5.

I've created a new project using blink template and I'm targeting a WROVER-KIT development board. I'm using all the default settings that ESP-IDF created in settings.json and launch.json and the default debugging target is ...

I have a project with a structure like:


- my_project/
- CMakeLists.txt
- components/
- foo/
- CMakeLists.txt
- foo.c


I want the foo subcomponent to require (via PRIV_REQUIRES) a component via absolute path, i.e. I don't want to add the path to foo's required component at the project level ...

Ok, thank you. From the page you linked:

ROM functions as not treated as public APIs

So does this mean I can call public API functions (e.g. esp_*) from a FreeRTOS task with a stack that is in external memory?

The ESP-IDF docs for CONFIG_SPIRAM_ALLOW_STACK_EXTERNAL_MEMORY state:

If you have a task that needs a large amount of stack and does not call on ROM code in any way (no direct calls, but also no Bluetooth/WiFi) ...

What does it mean that the task can "not call on ROM code in any way?"

Thank you for your reply.

I had a look through the source code and it's still not clear to me whether gpio_set_level() is guaranteed to set the output state prior to gpio_set_direction(). Mainly this could be due to my unfamiliarity with the ESP-IDF source code, but it looks like the actual ...

I'd like to ensure that when I configure a GPIO as an output it has a known initial state.

Will gpio_set_level() configure a GPIO properly before it has been set as an output, for example:


gpio_num_t gpio = /* some valid GPIO pin # */;

gpio_set_level(gpio, 0);
gpio_set_direction(gpio, GPIO_MODE ...