Exported Firmware
Export Architecture
Understand the boundary between generated LVGL, stable hooks, developer logic and ESP-IDF.
Architecture flow
text
ForgeUI Studio
→ generated LVGL UI
→ stable event and control API
→ developer application logic
→ ESP-IDF
→ ESP32-P4File roles
| File | Role |
|---|---|
| 90_Studio_Export.c / .h | Generated native LVGL object creation, initial presentation and event adapters. |
| 95_UserEvents.c / .h | Generated stubs in live firmware; developer-owned input integration in a standalone export. |
| 96_FiRuntime.c / .h | Feature-gated generated Fi presentation APIs and retained state; generated and replaceable. |
| app_main.c or main.c | Application startup and developer-owned integration, depending on the exported template. |
| CMakeLists.txt | ESP-IDF source, asset and dependency registration generated by the exporter. |
| assets/**/*.c | Converted image data and LVGL descriptors compiled into firmware. |
API direction
Generated inputs call developer code through FG_On_* hooks. Developer code controls generated state through silent FG_Set_* functions and related commands. This directional contract prevents product behavior from being embedded inside replaceable UI generation.