Can I modify how a native Simulink block is auto-coded?

My Simulink model uses native Simulink blocks within multiple atomic subsystems that are defined as reusable functions with unique file names. When I auto-code my model, the native Simulink blocks get auto-coded as in-lined functions within the atomic subsystem's auto-generated function file. The problem comes when another atomic subsystem also uses this same native Simulink block, but, this time, the MATLAB Coder placed just a function call out to the code that is now in-lined within the other atomic subsystem's reusable function. This creates a dependency between the two subsystems' functions and the order in which they are compiled. Is there a setting either on the native Simulink block or within the model code generation configuration parameters that will allow me to specifify exactly how I want the native Simulink blocks to be auto-coded. I would like to have them coded as reusable functions within their own uniqe files which can be called by my other code.

Answer 1

[Guy Rouleau]

The Code Replacement Library seems to be what you are looking for. See this example:

http://www.mathworks.com/help/coder/examples/replacing-math-functions-and-operators.html

[Jeffrey]

It turned out that what I needed was even simpler than this suggestion, but, this suggestion lead me to the solution. By reading about this Code Replacement Library, I noticed that there is a setting within the Configuration Parameters Code Generation section where you can set the "shared code placement" to either "shared location" or "auto". By setting it to "shared location", all of the native Simulink blocks that were previously inlined within the parent functions were generated as static, stand-alone utility functions able to be shared and called by other functions.

Answer 2

[Valmir Sadiku]

One possible way to do that are:

1. Right-Click on your subsystem -> select 'Block Parameter (Subsystem)'
2. Select 'Treat as atomic unit'
3. Go to the 'Code Generation' page and choose the 'Function packaging' as Reusable function.

hopefully this will help you.

[Jeffrey]

Yes, that is how I have setup my subsystem blocks so that they are coded as reusuable functions. The problem I am having, however, is specifically with the "mod" native Simulink block within my subsystem blocks. The "Subsystem Parameters" option does not appear with the native Simulink blocks, therefore, I can not specify a reusable function name.