How to place code generated from subsystem into RAM on Ti C2000?

I am trying to plase parts of the code generated from one of the subsystems into RAM to speed up execution. The help provided in Control Data and Function Placement in Memory by Inserting Pragmas is not sufficient.

Is there a better explanation on how to add #pragma CODE_SECTION(myCriticalTask, "ramfuncs") to the generated function?

Do I need to edit linker command file?

Do I need to add code to copy function from flash to RAM on power up?

Thanks.

Answer 1

[Umar]

Hi @Valeriy,

Good question — this trips up a lot of people because the MathWorks documentation focuses on the pragma setup but glosses over the full picture. Let me try to fill in the gaps.

1. Adding the pragma to generated code

If you're on the C2000 Blockset, the easiest route is already built in. Run `cscdesigner` in MATLAB, select the `tic2000demospkg` package, and check the Memory Sections tab — you'll see `code_ramfuncs` already defined. To apply it to your subsystem, just right-click the subsystem → Block Parameters → Code Generation tab, and select `code_ramfuncs` under the execution functions memory section. No manual pragma writing needed.

If you're on a different target or want full control, you can create a custom memory section in the Embedded Coder Dictionary. Set the Pre Statement to `#pragma CODE_SECTION($N, "ramfuncs")` — the `$N` is a token that automatically gets replaced with the actual function name at code generation time.

2. Linker command file

You probably don't need to write one from scratch. The shipping `.cmd` file for your specific C2000 device already has a `ramfuncs` section defined. You can find and inspect it in Configuration Parameters → Hardware Implementation → Build Options → Linker command file → Edit. Just make sure the section name in your pragma matches what's in the `.cmd` file exactly.

3. Copying from flash to RAM at startup — yes, this is required This is the part that catches most people. The pragma and linker script set up the load/run addresses, but nothing moves the code automatically. You need to call memcpy in your startup code before any of those functions are ever invoked:

`memcpy(&RamfuncsRunStart, &RamfuncsLoadStart, (Uint32)&RamfuncsLoadSize);`

The symbols `RamfuncsRunStart`, `RamfuncsLoadStart`, and `RamfuncsLoadSize` are generated automatically by the linker based on your `.cmd` file. In a Simulink workflow, drop this into Configuration Parameters -> Code Generation -> Custom Code -> Initialize function section.

Hope this helps!

Answer 2

[Valeriy]

Umar,

Thank you for the prompt and detailed answer. You put me on the right path, but I am missing one step.

How do I get the values from tic2000demospkg to show in the memory selection field of my subsystem? I only have selection from the Simulink package:

[Umar]

Hi @Valeriy,

Glad you're making progress! The reason you're only seeing the Simulink package options (MemConst, MemVolatile, etc.) is that the tic2000demospkg package hasn't been loaded into your model yet — the dropdown only shows sections from packages that are actively registered with the model.

Here's how to fix it:

Step 1 — Load the package into your model

Open the Embedded Coder app, then go to C Code → Code Interface → Embedded Coder Dictionary. Inside the dictionary window, look for a "Manage Packages" option. If tic2000demospkg doesn't appear in the list, click Refresh to scan for installed packages, then load it.

Step 2 — Check "Function with separate data"

Looking at your screenshot, I can see the "Function with separate data" checkbox is unchecked. You'll want to tick that box — without it, the memory section fields for subsystem data either stay limited or inherit from the model level, and some options won't show up. Once checked, you'll get the full set of memory section dropdowns for both initialize/terminate and execution functions.

After both steps, code_ramfuncs should appear in the dropdown and you can apply it directly to the subsystem.

Let me know if it shows up after the refresh!

[Umar]

Hi @Valeriy, Please let me know if you need any further assistance.

[Valeriy]

Umar,

I got the tic2000demospkg package added to my project mappings. The "Manage Packages" button is actually inside dictionary window under "Memory" section.

Now my next sticking point is in adding `memcpy(&RamfuncsRunStart, &RamfuncsLoadStart, (Uint32)&RamfuncsLoadSize);` to my code. Because I already have initialize blocks in my code I cannot put this statement into Configuration Parameters -> Code Generation -> Custom Code -> Initialize function section.

What is a good way to add the statement inside the Initialize block?

Thanks.

[Valeriy]

I found that "System Initialize" block works quite well for adding memcpy statement to the code.

[Umar]

Hi Valeriy, Glad you got it working! It looks like you found the last couple of details yourself — great troubleshooting. Could you post your findings as a formal Answer so the thread is properly closed? Specifically the location of the 'Manage Packages' button and using the System Initialize block for the memcpy statement. It will be very helpful for anyone else hitting the same issue. Thanks!

Answer 3

[Valeriy]

Umar,

You are correct. It took me a little to find the "Manage Package" button. This button is well hidden at the bottom on any of the three tabs under Memory view:

Also took me a while to figure out that using cval inside MATLAB function to incert`memcpy(&RamfuncsRunStart, &RamfuncsLoadStart, (Uint32)&RamfuncsLoadSize);` is not easy at all. The best way I found is to use "System Initialize" block from Simulink Coder >> Custom Code >> System Initialize. You can put C code directly into the block: