Once again I encountered a strange problem, which makes no sense for me.
In the Setup-Routine I'm calling a function which checks a database if its available. No problems with that.
But now I've defined a new function and without actually calling it anywhere, the ckeck-db-function hangs on startup (No compilation error). I've debugged the new function to that point:
Serial.print("...");
If that line is commented out, everything works fine.
Just a reminder: The new function was only defined, not even called anywhere (It is supposed to be called before check-db). How can that be?
I've waited for that question
Sure I had called the function. But when the sketch didn't work any longer I removed the reference. It still didn't work so I removed the definition too - that finally did it.
Here is the code. It might be a little unstructured but I'm not finished yet...
I'm getting more and more sure that it's really getting out of memory. It must be the EEPROM-crc check.
There REALLY is no reason to piss away memory like that. char * will work just as well.
void DisplayText(String Line1, String Line2)
This function REALLY does not need to take Strings.
There should be a means of displaying data that can accommodate the use of the F() macro, so that you can do:
DisplayText(F("Bitte Konfigu-"), F("ration pr\365fen."));
Oh nooooo! Shame on me :-[
That happens when you do your daily business with Visual Basic and C# - No thoughts about limited resources...
Ok I will revise my code with priority on memory usage. Thank you guys