thanks for your response. OK, so if I get this right, an INPUT/OUTPUT pin is really just an output pin where you can use a read operation on the same pin that will simply return the value you have written. It doesn't mean that you can read from an external device connected to that pin. Is this corr...

I've seen some issues with RMT on the ESP-IDF v3.0rc1 branch recently. In particular, RMT-heavy operations (such as reading from multiple DS18B20 devices regularly) seems to work well, until something unrelated causes the ESP32 to crash and reset. Then when the device boots up and tries to initialis...

Yes i have seen a lot of i2c problems on the interweb. I did consider putting on a i2c io expander and a RTC also on i2c. I might end up using a thrusty old arduino mega and only use the esp32 as a wifi module. Some projects as my current one requires reliability. Just in case it's not clear, the D...

Usually on microcontrollers/CPUs there are two separate electrical paths on the pin's hardware driver, the output path and the input path. They are connected to each other at the pin. When set to input-only, the output is put into a high-impedance tri-state, so it does not drive the pin. Depending o...

Looks like this might be fixed with https://github.com/espressif/esp-idf/co ... b190eff1ad

I've tested it on my boards and the problem is no longer occurring, however I'm also running a long-term test to be sure.

You can also use vTaskDelayUntil() in ESP-IDF v3.0rc for a slightly more accurate delay, if you need to take into consideration some processing between reading the current time and the task actually going to sleep, although note that your task is only going to start running on a scheduler tick bound...

I found a lot of JTAG debuggers that could be used with the ESP32. But most of them are out of stock or discontinued. Others too expensive. Cool project! I'm curious though - what do you consider "too expensive"? I have a C232HM that works well with the ESP32, and they are US$26 (ex. shipping) each...

Just curious about this. The OP does not give enough information to actually help you. What sensor are you trying to talk to. Are you using IDF or Arduino, What ESP32 are your using. Do you have pullup resistors on the I2C lines and what are there values. You have not shared any of your code so tha...

esp_timer_get_time returns 64-bit time since startup, in microseconds. Oh, now that IS useful! - now I wish I hadn't just spent the last hour implementing the exact same thing :) By my calculations that should last for about 584,000 years before overflow. Should be sufficient for most IoT applicati...

xTaskGetTickCount will probably do the trick. P.S: The tickcount will wrap every 49 days I guess. You'll have to check it periodically and adjust your uptime calculation. With a default tick rate of 100 Hz and TickType_t being a uint32_t, wouldn't it overflow every ~497 days? In [7]: 2**32 / 100 / ...