When calling the pinMode function specify mode INPUT_PULLUP to enable the internal pullup resistor or specify mode INPUT_PULLDOWN to enable the internal pulldown resistor.

For example, to enable the pullup resistor for GPIO17 do this:
pinMode(17, INPUT_PULLUP);

To enable the pulldown resistor ...

And there's also the esp_timer API described at https://docs.espressif.com/projects/esp ... timer.html with an example of it's usage at https://github.com/espressif/esp-idf/tr ... /esp_timer

Hi,

is there any example code related to os_tick_start and os_tick_handler.

thanks,
Madhu


I'm not aware of functions called os_tick_start and os_tick_handler in an esp-idf context.

If the goal is to use timers then esp-idf does offer timer support. See https://docs.espressif.com/projects ...

The DFRobot log shows the following: Are the SSID and password for the access point really 1 and 123456? Or did you forget to modify the code and set the SSID and password to the correct values?

I'm not sure if it's exactly the same but the esp32_azure_iot_kit example in the esp-iot-solution project look like the demo that runs on a stock ESP32-Azure IoT Kit.

See https://github.com/espressif/esp-iot-so ... adme_en.md

If the following line is added directly before the call to vTaskDelete, does it print the name of the task that should be removed?

ESP_LOGI(TAG, "deleteting task with name %s", pcTaskGetTaskName(todel->task));

If the correct name is not printed, todel->task doesn't contain the correct handle.

There's an esp-idf example called "UART Asynchronous Example with Separate Receive and Transfer Tasks" at https://github.com/espressif/esp-idf/tr ... _rxtxtasks so it looks like it can be done.

Which version of these two 3.3 branches of the IDF is the most recent and up to date?

v3.3-dev-278, or v3.3-beta1-223?

I'm not sure where the numbers 278 and 223 are from but the esp-idf git repository has two tags called v3.3-dev and v3.3-beta1. v3.3-beta1 is newer than v3.3-dev. All the tags ...

For a new design shall we choose ESP32-WROVER-I or ESP32-WROVER-IB?


The Espressif Product Ordering Information lists the ESP32-WROVER-IB as "*Recommend" but it doesn't list the ESP32-WROVER (IPEX) as "*Recommended". My personal interpretation of this is that the ESP32-WROVER-IB should be used ...

@Alen59 To the best of my knowledge no additional resistors are needed. Is the latest version of esp-iot-solution being used and was the menuconfig option "Select Backlight Active Level" set to "Backlight Level Low"?