RTOS/J6EVM5777: Memory footprint of RTOS in dra7x

Hi Madhu,

The memory footprint is heavily dependent on your system configuration, including:

• Number of CPU cores used in the application(s). As more CPUs are active, more binaries will need to be included in the AppImage
• Which RTOS modules are needed and enabled in each core. SYS/BIOS configuration consumes the RTSC modules, which by design aid to help create a completely scalable kernel. Excluding unneeded configuration elements can reduce For instance, if no mutual exclusion is needed, you can eliminate any gate instances.
• Whether the configuration is static (build-time defined and allocated modules) or dynamic (requiring run-time support for module creation and deletion). Run-time support requires extra code to handle the module create/init/delete and requires memory operations to support this. If the modules (i.e. Tasks, Semaphores, Heaps, etc.) are declared statically in the application configuration, run-time support can be disabled and reduce code size.

It's not really possible to define a minimum possible OS size. I could say you should only run a single CPU with an application which does nothing but run an idle thread, and that would get you very close, but of course that isn't practical.

Do you have any constraints or requirements you need to meet for your application? I could maybe suggest something more helpful if I had more information.

Thanks,
Stephen

Hi Stephen,
Thanks a lot for your detailed information. Senior engineer from my concern will reply to your thread soon.

Thanks,
Madhu