EEvar icon indicating copy to clipboard operation
EEvar copied to clipboard

Add support for ESP32

Open WeeJeWel opened this issue 1 year ago • 2 comments

I don't think there's a reason why the ESP32 shouldn't work. Maybe support for the ESP32 can be added?

WeeJeWel avatar Feb 12 '24 20:02 WeeJeWel

May be! Needs to be tested though.

AlexIII avatar Feb 13 '24 08:02 AlexIII

Hey @WeeJeWel @AlexIII. I would also like ESP32 support. I forked the library and attempted to add ESP32 support using ChatGPT (my coding experience is limited), which you can see here.

My fork compiles but it does not work properly. The eeVar objects are not initialised with the default values specified, and they always return the same 0 or nonsense characters (in the case of string), even after writing and reading to them again. The test works fine for AVR based Arduino.

In addition, I receive the error [ 1][E][EEPROM.cpp:70] begin(): Unable to open NVS namespace: 4353 and found this issue and thus tried including initArduino() in my code but it made no difference.

I am testing on the Wokwi platform (ESP32 not arrived yet), but incidentally the Espressif exmple of EEPROM write works fine and does not cause a namespace error, and it also does not need initArduino() to function properly.

I am emulating an esp32-s2-m1 on Wokwi with VSCode/Platform.io.

@AlexIII would you be able to assist here? Thank you.

simonmetcalfe avatar Aug 11 '24 16:08 simonmetcalfe