What about next versions of esp32 (chip itself) and new versions of ESP-modules?
In December there were rumors about the next version: with the antenna connector, larger number of pins, larger memory.

Indeed, adding pullup resistors solved the problem. However my question is why pullups resistors are needed at all: each SD card has internal pullup approx. 47k and we have internal pullup that are possible to turn on. Whats more, pull up mustn't be inserted on DATA2 (GPIO12) because spi flash volta...

Mine doesnt start: sdmmc_cmd: sdmmc_card_init: send_scr returned 0x109 sd_card: Failed to initialize the card (265). Make sure SD card lines have pull-up resistors in place. I have no idea what do more. Connections are OK, resistors are also connected (even if not needed) IO13 - SD_DATA3, IO2 - SD_D...

xTaskCreate has 3rd argument const uint16_t usStackDepth . It is the number of words to allocate for use as the task's stack. configMINIMAL_STACK_SIZE is 1024, and it is lots of memory. Nevertheless it is minimum: it isn't enough to start a task and allocate anything inside. Why? What this memory is...

I don't get it you not know, when who or how the var was changed. it can be that an ealier process have change the var, the next process change too, then you miss the prev val. I pass data to a display. User wouldnt see a difference between data refreshed every 5ms and 200ms. Moreover when I refresh...

@rudi You have const string in memory so you can change the pointer. I have new data, so I would have a variable and change its value.
Anyway, if changing 1 word pointer is ok, changing 1 word variable wold be also.
Where is the key that "it is described everywhere as a bad idea"?

I absolutely know what queues are. Take a look: I would like to show values from all sensors at some time on a display. After pressing a button, changing a view and presenting some text. After pressing another, going back to values. If I used Queues (xQueueCreate, xQueueReceive, xQueueSend), I would...

Lets say I have 3 tasks: 1. for display and keyboard, 2. and 3. for ADC measurements. How should I pass data between them? int ADC_VALUE_1 = 0; int ADC_VALUE_2 = 0; void display_and_keyboard_task(void *pvParameters) { while (1) { if (shouldInit()) { init(); } if (xSemaphoreTake(display_semaphore, 10...

How to wait eg. 40 microsecond inside a task? Time can be longer (interrupts execution), but shouldn't be shorter.

Is this optimal?

What is more optimal way to use UART: using xQueueReceive or not and read one by one byte? I wont use any other event.type. while (1) { if (xQueueReceive(m_uart_queue, (void *)&event, 10 / portTICK_PERIOD_MS)) { if (event.type == UART_DATA) { uint32_t len = bufferEnd - ptr; if (len > event.size) len...