-
Notifications
You must be signed in to change notification settings - Fork 944
Description
Hello,
We are using esp-elf-loader to load and run a dedicated software module B in real time from a main application A.
Both applications can run simultaneously. Through callbacks, software A can call functions from software B, and conversely software B can call functions from A using the exported symbol table.
Our main concern is RAM isolation and memory management. The two software components are developed by different teams, and we would like to avoid memory conflicts, unexpected allocations, or memory leaks.
Specifically, we would like to:
Reserve a dedicated RAM region for software B
Prevent software A from allocating memory in this region
Ensure that all dynamic allocations made by software B are confined to its own RAM area
What is the recommended way to define a specific RAM region for software B when using esp-elf-loader?
Is it possible to enforce such memory isolation at link time or runtime, and prevent software A from accessing or allocating memory in that region?
Any guidance or best practices would be greatly appreciated.
Thank you.