How about viewtopic.php?t=4978

Which partition you select is up to you based upon your applications requirements.

Humm. So you had an ESP32 and you replaced it with a ESP32 WROOM and you now expect to get more memory available but a ESP32 DEV is a ESP32 WROOM. If you want more ram from an ESP32 you'd want to go with a ESP32 WROVER. Many WROVER's come with 8+ MB ram. Using the Arduino IDE with a Wrover you can a...

https://docs.espressif.com/projects/esp ... /gpio.html

GPIO34-39 can only be set as input mode and do not have software pullup or pulldown functions.

100% what he said^^^^^^^^^^^ I know complete waste of an ESP but that all I am using at the moment: #include "sdkconfig.h" #include "esp32/ulp.h" #include "driver/rtc_io.h" #include "esp_system.h" //This inclusion configures the peripherals in the ESP system. #include "freertos/FreeRTOS.h" #include ...

One can use the EEPROM library to store data in flash.

You might want to hunt down and install the "esp exception decoder arduino", it could provide some help with hunting down the issue.

Buffer. My current thing do is about using a Ring Buffer. void fSendSerialToBrain( void *pvParameters ) { CAN_frame_t rx_frame; xSemaphoreGive ( sema_SendSerialToBrain ); bool PassTwo = false; for (;;) { xEventGroupWaitBits (eg, evtSendSerialToBrain, pdTRUE, pdTRUE, portMAX_DELAY); size_t item_size;...

Also, I found that by sampling the ADC regularly once a mS or so, and applying the Simple Kalman filter to the results https://github.com/denyssene/SimpleKalmanFilter , the output gets real smooth. Even if the A:D converter values are not displayed regularly, like once a second, getting several read...

This is not true // For ESP32 the GPIO pwm pins are: 0,1,2,3,4,6,7,8,9,10,11,12,14,16,17,18,19,21,22,23,25,26,27,32,33,34,35,36,39 All the GPIO pins above 32 are input only // For ESP32 the GPIO pwm pins are: 0,1,2,3,4,6,7,8,9,10,11,12,14,16,17,18,19,21,22,23,25,26,27,32 is correct. Anyway, not used...