Need solutions for integrating auto-generated code into embedded system environment

2 views (last 30 days)
I am looking for some solutions or tools that can manage the integration of auto-generated model code into a legacy C-code embedded environment.
I have previously worked with an in-house tool that uses an Excel spreadsheet as the DD (Data Dictionary). The DD is parsed with a custom command-line parser or Matlab script to automatically generate the header files containing the necessary accessor functions and other elements required to interface between the auto-generated code and the legacy C-code embedded environment.
The DD defines the Data Flow Architecture for the entire system by specifying all the signal names, their sizes and types, who can write (publish), who can read (subscribe) and any other attributes that can control the auto-generated header file output. The DD can also be used to auto-generate special things like global Constants, Enumerators, data structures, etc. Everything is located and managed in one central place using the DD.
For our typical embedded application we could have hundreds of tiny model pieces that need to be sewn together in a very controlled manner. The connections between all these pieces use signals that are configured and specified in the DD. The accessor function names are configured on Simulink inputs/outputs and appear in the auto-generated code. The DD tool then generates all the header files containing the accessor functions for these signals. The accessor functions are typically just #defines or something similar that are ultimately just global variables in the end, which the compiler uses to link everything together.
The purpose of using accessor functions is that it allows you to keep the interfaces very simple, or you can throw a switch and generate more complex accessor functions that allow you to do things such as break signals, insert your own values, override values, monitor things, etc.
I am looking for some professional tools that can do some of this automation. It is never easy to manage and integrate auto-generated model code into a legacy C-code embedded environment. When you have hundreds of auto-generated files to deal with, it can get overwhelming and be prone to errors if not managed carefully. I haven’t seen much in the way of professional tools, so I think each company has their own in-house solution for the problem.

Answers (0)

Categories

Find more on Deployment, Integration, and Supported Hardware in Help Center and File Exchange

Products

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!