Virtuino Forum

This is not a bug report, but an observation. The same sketch compilation has been done for ESP32 Devkit V1 and Raspberry Pico W. This is the compiler's (Arduino IDE 2.3.2) report for ESP32:
"Sketch uses 772533 bytes (58%) of program storage space. Maximum is 1310720 bytes.
Global variables use 45480 bytes (13%) of dynamic memory, leaving 282200 bytes for local variables. Maximum is 327680 bytes."
And accordingly, for Pico W:
"Sketch uses 369120 bytes (18%) of program storage space. Maximum is 1961984 bytes.
Global variables use 74000 bytes (28%) of dynamic memory, leaving 188144 bytes for local variables. Maximum is 262144 bytes."

---

(04-05-2024, 06:16 AM)Araqel Wrote: [ -> ]This is not a bug report, but an observation. The same sketch compilation has been done for ESP32 Devkit V1 and Raspberry Pico W. This is the compiler's (Arduino IDE 2.3.2) report for ESP32:
"Sketch uses 772533 bytes (58%) of program storage space. Maximum is 1310720 bytes.
Global variables use 45480 bytes (13%) of dynamic memory, leaving 282200 bytes for local variables. Maximum is 327680 bytes."
And accordingly, for Pico W:
"Sketch uses 369120 bytes (18%) of program storage space. Maximum is 1961984 bytes.
Global variables use 74000 bytes (28%) of dynamic memory, leaving 188144 bytes for local variables. Maximum is 262144 bytes."

By the way, either apps, on Android and Windows are unable to connect to the server on Pico W. Meanwhile the WiFi is on and the Access Point is visible & connectable. Now I do some debug to see what is going on under hood.

Seems, it is PicoW related issue: https://github.com/earlephilhower/arduin...2039168890

---

Hello, Mr. Ilias.
Could you please pass any test sketch on PicoW board?

Hi,
I am sorry but I can't fix this problem because it's not due to the app. 
I don't have an example for PicoW board

Spice Up Your Life with Casual Dating Opportunities in Your City

Most realistic sex game

While the ESP32 Devkit V1 uses more program storage, it retains more dynamic Melon Playground memory for local variables. Conversely, the Raspberry Pi Pico W demonstrates a smaller flash usage but consumes more RAM for global variables. These differences are not indicative of performance issues but rather reflect the underlying architecture and memory management strategies of each board.