Choosing a firmware stack for a memory-constrained microcontroller usually comes down to aggregate binary sizes, which tell you how much SRAM a build uses but not where it goes or why. This paper from arXiv addresses that gap with a per-symbol attribution method, breaking down static memory consumption to individual symbols in the firmware.

The authors apply their approach to two IoT firmware stacks—FreeRTOS in C and Embassy in Rust—running on a 64 KB RISC-V microcontroller. By attributing SRAM usage per symbol, the method aims to give developers a clearer picture of memory allocation than a single total number can provide.

Since this is a single preprint, there are no conflicting sources to compare. The abstract does not include results or conclusions, so the article focuses on the proposed methodology rather than any findings about which stack is more memory-efficient.