On Wed, May 06, 2026 at 12:58:10PM +0530, Sparsh Kumar wrote: > Hi Ernest, > > Apologies for the delayed response. > > The M4 core that runs TIFS has far less memory available (176KB) than the > WKUP/DM R5 core. To keep the memory footprint as small as possible we trim > the full RM board configuration down to only the entries that TIFS needs and > store the result in `tifs‑rm‑cfg.yaml`. > > A couple of important points: > > 1. Both `rm‑cfg.yaml` and `tifs‑rm‑cfg.yaml` are generated automatically. > We use the K3 Resource Configuration Tool (formerly the K3 Resource > Partitioning Tool) to generate the files from the SysConfig file and then > copy the generated YAML files into U‑Boot. No manual editing is involved. > > 2. By using a smaller board‑config file we free up RAM on the M4, preserving > space for future features or extensions. > > 3. Secure‑boot relevance - The `tifs‑rm‑cfg.yaml` does not play any direct > role in the secure‑boot process; it is simply a streamlined copy of > `rm‑cfg.yaml` that contains only the TIFS‑specific resources. > > Please let me know if any part of this explanation is unclear or if you need > more detail on a specific step. Happy to elaborate! > > -- > Best Regards, > Sparsh
Hi Sparsh, Thanks a lot for the extra explanation here, this clears up our questions! Kind regards, Ernest
