Ivan Grokhotkov

The main thing which needs to happen on Arduino end is making decisions :) For example, do we want USB stack running only in second stage bootloader (eboot) or in...

For the bootloader mode, this amount of RAM is not an issue, while for the application the amount of iram required may be a problem. We don't have many options...

I can add esp-usb to our eboot bootloader. It would be nice if there was a way to tell whether USB isn't connected at all (no cable) — and avoid...

As mentioned above, because of IRAM usage it is likely that we integrate esp-idf into bootloader only, but not in the app. In this case we can assume that if...

From bootloader point of view, the following functions are needed: - `is_usb_plugged_in()` should check if cable is connected - `usb_enumerate(void (*cb)(size_t size, const uint8_t* data))` should return when enumeration is...

Since you are using ESP32-S3-WROOM-2, one thing to check: you aren't using GPIO47 and GPIO48 for the SPI bus, right?

> How is the scan time determined using .scan_time.active.min and .scan_time.active.max Just a note, this one of the questions is answered in https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-guides/wifi.html#scan-configuration

Just a tip, enabling CONFIG_PM_PROFILING and using the [esp_pm_dump_locks](https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/power_management.html#_CPPv417esp_pm_dump_locksP4FILE) function may help find the specific lock which prevents the system from going back to sleep. It may be the OS...

@edbek ESP32-P4 doesn't include any wireless peripherals (Wi-Fi or BLE). Regarding the deep sleep current, please wait a bit for the details, they will be available when the datasheet is...

The original issue reported by @ElectricThanhTung is explained by the fact that once the linker finds the function Test in one of the object files, it has no reason to...