-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Example EchoBot takes up a lot of memory in ESP32 #125
Comments
Could you provide more detail for your request? You should then compare by including as few external libraries as possible. SSLClient.h is a library that makes heavy use of SRAM for example, try without. Anyway, I also tried with these configurations: However, rather than the message provided by the compiler, you should shift your attention to the amount of SRAM that remains free during program execution. |
Version of ESP32 Arduino: |
Now I have updated the ESP32 core version to 2.0.11 in Arduino 2.2.0. Here's my entire sketch: #include <time.h> #include <SSLClient.h> AsyncTelegram2 myBot(client); const char* ssid = ""; // SSID WiFi network int64_t userid = ********; void setup() { Serial.begin(9600); WiFi.mode(WIFI_STA); configTzTime(MYTZ, "time.google.com", "time.windows.com", "pool.ntp.org"); myBot.setUpdateTime(2000); myBot.begin(); } void loop() { static uint32_t ledTime = millis(); TBMessage msg; if (myBot.getNewMessage(msg)) { |
Hello, dear Tolentino.
This is not a problem or a bug, but rather a question, sorry if I posted it incorrectly.
I'm using the echoBot example, on an ESP32, CLIENTSSL connection.
On Arduino IDE 2.2.0. AsyncTelegram2 version 2.2.2.
I can't figure out why this example sketch takes up 59% of memory (773949 byte).
The fact is that earlier I used the version of the AsyncTelegram2 2.0.8 library, while using the Arduino IDE 1.8.19. And with the same controller, the sketch, which is much larger and has many other functions besides Telegram, takes up about 48% of the memory.
What could be the reason?
Thank you!
The text was updated successfully, but these errors were encountered: