josef2600
commented
1 year ago i forgot what was the number of issue, but with old code, it wouldn't compile it because of the preferences.putString(PREFERENCES_AUTOMATION, getAutomationsJson()); . then i changed it to my new code and it compiled.
put this in code char my_stringbuffer_[500];
PreferenceHandler.cpp
else if (strcmp(preference, PREFERENCES_AUTOMATION) == 0) { // Note: saving a string instead of bytes. // The struct for AutomationFlash does not seem to work properly with the putBytes. // Need further investigation preferences.putString(PREFERENCES_AUTOMATION, getAutomationsJson());
i changed it (and more!) to this:
getAutomationsJson(); preferences.putBytes(PREFERENCES_AUTOMATION, &my_stringbuffer_, sizeof(my_stringbuffer_)); . . . String PreferenceHandler::getAutomationsJson() { DynamicJsonDocument doc(AUTOMATIONS_JSON_CAPACITY); for (AutomationFlash& a : automations) { if (a.id) { doc.add(serialized(automationToJson(a))); } } // String output; my_stringbuffer_.remove(0); serializeJson(doc, my_stringbuffer_); return my_stringbuffer_; }
RomeHein
Guru Meditation Error: Core 0 panic'ed (Load access fault). Exception was unhandled.now, it runs, works, and suddenly, panics! i setup 3 analog input pins and read them. if the an2 is over 0, it send a massage in serial port (i am using USB inside the chip as serial port). after awhile, it panics, then hangs, then reboot itself.for now i am working on changing strings on air to a global register. again, please when programming for microcontrollers, never use C++ as it is the worst language for it. read a datasheet, any micro from last 25 years that still exist. if they support any high language, it is always C and never C++. there are many reasons for it. eg: what is the difference between array and string? in C, nothing! and that is logic answer. BUT A "C" string:
char *myString = "This is my string";is an array of characters. It is no different to an "array".
However, a "C++ String Object" is vastly different.
String myString = "This is my string";That is an entire object with methods and properties which, while it makes programming easier, is not advised when working with microcontrollers. The memory usage when you're not doing much with it is only slightly more than a "C" string. However, a lot of the methods involve the allocation and deallocation (freeing) of memory, which leads to memory fragmentation.
"C" strings take a bit more working with, but the benefits from a memory management point of view are worth the time taken to learn about working with them.