Close

Firmware 0.7.5 — rendering on both ESP32-S3 cores

A project log for EvilKey: I Needed a FIDO2 Key. Then the Maker Brain Took Over.

ESP32-S3 FIDO2 prototype: touch AMOLED, microSD apps, HID scripts, USB/BLE AirMouse and an IMU BLE Gamepad. A key that got carried away.

michal-wojciechowskiMichal Wojciechowski • 10/09/2026 at 21:42•0 Comments

With the Jet interface in place, firmware 0.7.5 brings changes to how EvilKey draws it.

The GUI and native 3D renderer now share rendering work between both ESP32-S3 cores. The GUI splits the image into horizontal bands, while native scenes distribute alternating rows between the cores.

There are also several changes inside the rasterizer. It calculates the part of each row covered by a triangle, skips invisible geometry earlier, and reuses transformed cube vertices across faces. Frequently used data stays in internal memory, and color and depth are packed together to reduce separate PSRAM accesses. The graphics keep their existing appearance and detail.

Diagnostics now has a Save report button. Instead of checking each screen separately, you can save all seven diagnostic cards to one text file on the SD card. The report includes memory usage, display buffers, rendering times, and activity on both cores. Files are saved in /evilkey/diagnostics/.

Another addition concerns switching the SD card back from the computer to EvilKey. Using Eject on the computer now turns off Manager Drive. EvilKey saves the setting and briefly restarts, reconnecting without the USB storage drive so local apps can access the card again. You can turn Manager Drive back on when you need it.

Existing ABI v4/v5 applications remain compatible. Manager stays at version 1.1.6.

Discussions