HI,

Can an ESP IDF software app running on a DevKitC know if it is running from 5v from a connected USB source or from a 3.8~2.8v source from a battery to the 3.3v pin?

Thanks.

I have noticed that the system keeps a count of the times the NVS has been closed, with a typical information message reading: D (331196) nvs: nvs_close 40 I see this ascending count after the NVS is accessed for some non-volatile information where my app currently opens and closes the NVS. What doe...

Thanks for the quick reply. The reason I started looking at the sample HTTP client is that I had an implementation based on this client working in my app until.... it crashed with a stack overflow after several HTTP POSTs. I wasn't monitoring stack penetration at that point, I only saw the stack ove...

I am building an app that needs to do simple HTTP POSTs to a server in the cloud. I have looked at esp-idf http client example and it runs just fine. Then I instrumented it to look only at POSTs and to check the stack, modifying the task code as shown: static void http_test_task(void *pvParameters) ...

Thanks.

Makes sense. It's the way that printf() can report out of the bootloader before the "real" driver is loaded. Out of curiosity, what's the call that causes printf() to use the "real" driver?

Never mind. Embarrassing as it is to admit, the problem was with my setup of the breadboard for this new dev board I'm using as well as some code that gates whether the uart initialization routine is called. Your question as to whether the uart was initialized got me to thinking about all the things...

Your question: "Are you sure installation of the UART driver succeeded?" Yes, I'm sure. My UART initialization code is: void UartInit(void) { #define TAG "UART" esp_log_level_set(TAG, ESP_LOG_INFO); const int uart_buffer_size = (1024 * 2); /* Configure parameters of an UART driver, communication pin...

Here's a little refinement on my question. In the section of app_main in which I see the problem, I have several calls to printf() in conditionally compiled code which will not be in the product version of my code as well as several calls to output to a terminal using uart_write_bytes(UART_NUM_0, ch...

I have some code that runs quite reliably on at least two versions of ESP32 DevKitC. In trying to run the same code on on a DoIt32 DEVKITV1, I get this error from uart.c in the idf v4.0 components/driver directory. uart_write_bytes(1193): uart driver error What could be causing this error when the E...