Is there a library available to write to a simple 2X16 LCD? I'm moving from a raspberry pi to an ESP32, but I need support for an LCD. On the pi, I'm running this.

Is there a limit to the number of times I can write to or read from NVS? If I implement a timer with the ESP32 by updating the value total_time in NVS once a second by simply incrementing the value, will this cause problems? If there is a limitation, what are the best practices to avoid over use ...

I'm using libssh2 to ssh into a few devices from the esp32. It works great for my application, but when I enable bluetooth, the ssh session cannot connect. I know there are [ur=https://esp32.com/viewtopic.php?f=2&t=3364&p=15863&hilit=wifi+and+bluetooth&sid=1230275b322ae4fe7bf00058ddd3e94d#p15863l ...

Is bluetooth enabled? I had to disable bluetooth to make OTA work successfully. WIFI and bluetooth can exist at the same time, but it can cause issues.

THANK YOU THANK YOU!


#include "driver/periph_ctrl.h"
void reset_i2c(void){

i2c_reset_tx_fifo(I2C_N);
i2c_reset_rx_fifo(I2C_N);
periph_module_disable(PERIPH_I2C0_MODULE);
periph_module_enable(PERIPH_I2C0_MODULE);
i2c_driver_delete(I2C_N);
init_I2C();
}


This worked perfectly for me ...

I'm using a MCP23017 port expander which uses i2c. Occasionally I get a problem on the lines and the timeout is reached. This throws an error that I read. I simply reset the esp32 and then it starts working again. I've upgraded my IDF to the latest version, and now the reset no longer works. When it ...

I haven't checked for the slowing clock speed, but I got mine to work with the following code. It's nothing perfect, but I don't miss anything. Occasionally I still get stuck on the i2c line, but I just monitor that and reset as necessary.



void initI2C() {
i2c_config_t conf;
conf.mode = I2C ...

If you can pack two int32 variables into an int64 and store that instead of a blob, that will be twice as efficient.

I definitely can pack them together. Should I make an array of the log entries and save that to the blob or should I try to rename each entry?


BlobLog blob_logs[];
...
nvs_set ...

So I see my two options are to keep doing everything in nvs storage or take a big risk with the partition tables. I'll have a new run of boards soon that I can flash with a different partition table. Is there anything wrong with using the blob? My current plan uses a struct with two int32_t ...

(bump)