- When the power switch of SARADC1, SARADC2, HALL sensor and AMP sensor is turned on,
- * the input of GPIO36 and GPIO39 will be pulled down for about 80ns.
- * When enabling power for any of these peripherals, ignore input from GPIO36 and GPIO39.
- * Please refer to section 3.11 of 'ECO_and_Workarounds_for_Bugs_in_ESP32' for the description of this issue.
- * As a workaround, call sar_periph_ctrl_adc_oneshot_power_acquire() in the app. This will result in higher power consumption (by ~1mA),
- * but will remove the glitches on GPIO36 and GPIO39.
We are currently developing a project using the ESP32 as the main MCU. However, we have encountered a peculiar issue. We are using GPIO36 as an input, configured to trigger an interrupt on the falling edge. Everything works fine, and it triggers the interrupt as expected. Below is the configuration code for the interrupt on that pin:
Code: Select all
static const gpio_config_t g_gpio_in_cfg = {
.pin_bit_mask = BIT64(GPIO_NUM_36),
.mode = GPIO_MODE_INPUT,
.pull_up_en = GPIO_PULLUP_ENABLE,
.pull_down_en = GPIO_PULLDOWN_DISABLE,
.intr_type = GPIO_INTR_NEGEDGE
};
ESP_ERROR_CHECK(gpio_config(&g_gpio_in_cfg));
ESP_RETURN_ON_ERROR(
gpio_isr_handler_add(GPIO_NUM_36, gpio_int_handler, NULL),
g_tag,
"Failed to add interrupt handler"
);
My question is, is there a known issue with the ESP32 chip where the BLE functionality affects the interrupt behavior of the GPIO36 pin? Or could there be another reason causing this issue?
Thank you for your assistance.