TMS320F28P650DK: SysConfig CMD tool. Warning: memcfg module and Custom address memory space

Tool/software:

Hi everyone,

I'm using SysConfig to generate the CMD (linker command) file for my project. While it works overall, I'm running into a few issues and warnings that I'd like help resolving.

1. Flash Assignment Warnings

I've defined a custom memory region that currently maps only to FLASH BANK 1, and I plan to extend it later to include BANK 2 as well. I'm assigning this region to standard sections like .text, .binit, .ovly, .cinit, .init_array, .const, switch, and some user-defined sections.

However, SysConfig generates multiple warnings like:

"The memcfg module is needed on CPU1 to assign FLASH."

This is confusing because I have already configured the memcfg module:

• FLASH BANKS 0, 1, and 2 are assigned to CPU1

• FLASH BANKS 3 and 4 are assigned to CPU2

Strangely, when I use predefined flash regions (like the default ones SysConfig provides), these warnings disappear. Is this a known issue with custom memory regions? Or is there something I’m missing in the configuration?

2. CPU-to-CLA Message RAM Warning

I'm also seeing a warning related to CPU to CLA message RAM configuration, but the setup seems correct from my end.

Memcfg module must be enabled for complete error checking.

3. Assigning a Symbol to a Fixed Memory Address

Unrelated to the above, but I’m also trying to replicate this kind of memory definition in my linker script:

MAIN_FIRMWARE_VERSION : origin = 0x0FFFD0, length = 0x000010

Is there a clean way to declare this using SysConfig, or is it better to define such regions manually in a separate CMD file?

Thanks in advance for your help! Let me know if more details are needed.