Closed dhunink closed 6 years ago
Hi, sorry for the late response! The debug only uses the F macro for storing the strings int he flash instead of the memory, so it can save some RAM, similar to PROGMEM you defined for your icon, so it should no cause any issue, except it takes space for your sketch.
What hardware are you using? I have tested to compile a similar example for an Arduino and ESP8266 board, and both seems to compile fine. Do you have an isolated example to test what is happening?
Hi,
while playing around with Thinger.io a lot ore the past few days, I found a possible bug. I've spend several hours googling but I believe my level of knowledge of AVR behaviour is insufficient to really understand what's going on here.
Basically the situation is as follows:
#define _DEBUG_
on the very first line of the sketch. Works greatconst char WiFi_Logo_bits[] PROGMEM = {
and compile errors will occurLooking at the Thinger source code I believe some enhancements are possible; after reading a lot of other topics on other platforms the Serial.println(F()) statement comes up a lot. This one could be used differently to play nicer with the PROGMEM function. But again, this may be a complete misinterpretation since my leve of knowledge of deep-level-AVR-behaviour is not sufficient at this time.
For reference: here are the pieces of code and the compiler error. I'm very interested in further thoughts on this issue!
Compiler error one
Compiler error two
Code added that causes the compiler errors, when Debug is enabled: