-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
This means your JavaScript app attempted to allocate more memory than the ESP32 had available (usually >90KB). Fix:
- Reduce the size of arrays in your JS.
- Do not use
FS.readTextFile()on files larger than 10-15KB. - Ensure you are calling
System.delay(10)in your animation loops so the Garbage Collector can run! - If doing heavy 3D graphics, use the Sliced Double-Buffering technique instead of full-screen buffers.
If the device immediately crashes and reboots (without even showing the red "Out Of RAM" error screen) when launching an app, it means the ESP32 suffered a hard hardware reset due to extreme, instantaneous RAM exhaustion. Fix:
- The standard ESP32 (WROOM-32) has very limited contiguous RAM. The internal Wi-Fi stack consumes a massive amount of this RAM in the background. Ensure you turn OFF Wi-Fi in the OS Settings before launching memory-heavy JavaScript apps or 3D games!
- Check if your app is trying to allocate a massive array or
System.createSprite()buffer immediately upon boot.
This means the OS cannot talk to your display over SPI.
Fix:
If you are NOT using an ESP32 Marauder v4/v6, your pins likely don't match the defaults. You must open the source code, edit platformio.ini to match your specific wiring, and recompile.
No. KryonOS strictly requires the RAM and Processing power of the ESP32 architecture (WROOM-32, S2, S3, C3). The Duktape engine cannot fit on older 8-bit microcontrollers.
Your SD Card must be formatted to FAT32. The ESP32 LittleFS/SD drivers cannot read exFAT or NTFS. We recommend using an SD card of 32GB or less.
No. Wi-Fi is only required to use the built-in App Store to download new apps or to fetch OTA OS updates. All core features, local JS apps, graphics, and hardware APIs run entirely offline.