MATLAB Answers

TLC for C++ S-Function

23 views (last 30 days)
I have an S-function that needs to be nested inside of a for-each loop, which itself needs to be inside a reference model in accelerator mode. The S-function is written in C++ and makes heavy use of external libraries, classes, and the PWork and DWork vectors. It is also built to work with multiple instances and inside of iterator blocks (for, while). I'm new to TLC, and this seems a bit daunting due to the lack of clear documentation, but is writing a TLC file for such an S-function even possible?
For starters, I made a simple S-function in C and TLC that has one input and two outputs with very simple math in between. That was simple enough, but converting it to C++ immediately posed the issue of not being able to specify C++ as the target language because the simulink target was C. Is this avoidable?


Sign in to comment.

Accepted Answer

Mark McBroom
Mark McBroom on 20 Apr 2019
If the Simulink target is C, then the code that is emitted from your TLC will be placed into C files generated by Simuilnk and therefore will have to be C code. A common approach to interfacing with C++ code is to manually write a C++ file that contains a function to wrap your C++ code ( constructing objects, calling member functions, etc) and the use extern "C" to make your wrapper C++ function callable from the C code generated by Simulink.
#ifdef __cplusplus
extern "C" {


Thomas Satterly Satterly
Thomas Satterly Satterly on 24 Apr 2019
That's what I ended up doing, along with making use of a rtwmakecfg() function to link up the dependancies. It compiles in both normal and accelerated mode, but errors out at some point during the first call to the Output function in accelerated mode. Is there any support for debugging TLC files?
Mark McBroom
Mark McBroom on 24 Apr 2019
Yes, there is a TLC debugger that you can use to set break points, look at variables, single step, etc. It is a command line debugger but works pretty good.
Start by setting a breakpoint in your TLC code. Easiest way is to just add
to your TLC code. This link provides list of available debugger commands

Sign in to comment.

More Answers (0)

Sign in to answer this question.