suda-morris
suda-morris
@MrSurly Are you calling `ledc_set_fade_time_and_start` in the LEDC's fade callback function?
The error log comes from `ESP_RETURN_ON_FALSE(handle, ESP_ERR_INVALID_STATE, ADC_TAG, "The driver isn't initialised");` Are you passing a `NULL` as the **handle** to the `adc_continuous_read` by accident?
With ESP32-C3-DevKitM board, I didn't see a glitch on the GPIO4, after manually pushed the "RST" button. Not sure if it's related to chip revision, could you tell what chip...
I would suggest not rely on the default values that were documented in the TRM, because it may be changed in the ROM code if these GPIOs have another special...
one workaround is, `.clk_cfg = LEDC_AUTO_CLK` -> `.clk_cfg = LEDC_USE_XTAL_CLK`
But even the driver returned "I'm currently in running state", at the time the function returns, the state may be changed by another task where called the stop function. So...
Do you want the start/stop function to be idempotent? By relaxing the FSM check, allow calling stop/start when it's already in stop/start. If so, do you still want a get...
The backport has merged in our internal Gitlab server. It just needs some time to get synced to Github.
Fixed in https://github.com/espressif/esp-idf/commit/0903bcca1bb1999b0431b68d9b496f5f406775ec
Hope this doc can give you some help: https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/flash_psram_config.html#how-to-configure-flash-and-psram