{"id":4533,"date":"2022-07-01T13:19:26","date_gmt":"2022-07-01T11:19:26","guid":{"rendered":"https:\/\/zen-cori.138-201-132-86.plesk.page\/?page_id=4533"},"modified":"2025-04-15T18:37:05","modified_gmt":"2025-04-15T16:37:05","slug":"mathworks-embedded-coder","status":"publish","type":"test_environments","link":"https:\/\/www.btc-embedded.com\/de\/test_environments\/mathworks-embedded-coder\/","title":{"rendered":"Mathworks Embedded Coder"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Test Environments<\/h4>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

MathWorks Embedded Coder<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Testing model and code in one integrated environment<\/span><\/span><\/p><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Introduction<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

About Embedded Coder<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Embedded Coder\u00ae from TheMathworks generates production C code from Simulink\/Stateflow models. But to take advantage of EmbeddedCoder in an ISO 26262 compliant development workflow, end-users need to also consider\u00a0 model-in-the-loop testing (MIL), software-in-the-loop testing, back-to-back testing, and code coverage analysis. BTC EmbeddedPlatform<\/a> integrates all these different workflows in one simple ISO 26262 certified environment.<\/span><\/p>

Learn more about Embedded Coder on www.mathworks.com<\/a>.<\/p><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

BTC EmbeddedPlatform<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

MIL\/SIL Testing for Embedded Coder<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The creation of a test project occurs automatically, without need for any manual interaction from the user. BTC EmbeddedPlatform analyzes the architecture of the model to detect subsystems, ports, parameters, test points, data types and ranges.<\/p>

As we believe that a test tool should never touch or modify the system-under-test, the test harness creation and test execution happen on a temporary copy of the Simulink model.\u00a0<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

This makes it easy to handle model and test data independently. The test harness creation happens in the background and requires no manual input.<\/span><\/p>

For software-in-the-loop (SIL) Testing, BTC EmbeddedPlatform always uses the original production code with a dedicated and automatically-managed test harness<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Easily test on all subsystem Levels<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Hierarchical Test Approach<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Especially when working with large Embedded Coder models, individual test cases often need to be run on a smaller subsystem or sub function within the model.<\/span>\u00a0<\/p><\/div>

But isolating that subsystem for test harness creation can require time-consuming and error-prone manual labor. And this often leads to additional models and artifacts which need to be stored, managed and maintained.<\/span><\/p><\/div>

With the powerful \u201chierarchical test approach\u201d in BTC EmbeddedPlatform, all these problems are smoothly managed in the background. The needed test harnesses on model and code level are automatically generated \u201con-the-fly\u201d from the original model, so that they don\u2019t need to be stored or manually updated.<\/p><\/div>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Hierarchical\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

BTC TestComposer<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Smart and powerful test authoring<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

In our experience, test cases are too often written in languages which were not designed for that purpose. Examples like Matlab, Python, Excel tables, or even C Code abound.<\/p>

With BTC TestComposer, we provide a powerful editor for functional test cases directly within BTC EmbeddedTester BASE. BTC TestComposer knows all the details of the test architecture and protects users against invalid data entries. If enumerations are used, a drop-down menu is provided that allows direct selection of desired values.<\/p>

Further features include a signal generator, a graphical viewer, flexible tolerance handling, and a formula editor, allowing us to calculate the value of a certain signal based on other variables. „Test Macros“ and „Calibration Sets“ can be used to specify and store reusable sequences for instantiation in multiple test cases. Test cases are executed directly within the editor\u00a0and the results immediately\u00a0visualized<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"BTC\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Sandboxed environment<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Smart Debugging<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

As modern Model-based development projects grow in complexity, the task of debugging failed test cases becomes increasingly difficult and time-consuming. Even more challenges emerge in situations where the function development and testing are separate, and performed by different people or teams. This leads to an important question: What is the most efficient way for a test engineer to provide his test scenario to development for further analysis?<\/p>

BTC EmbeddedPlatform includes a unique debugging approach that generates self-contained sandboxes. These sandboxes contain a copy of the system-under-test as well as the failed test case, including the corresponding calibration values. The sandboxes can be easily shared with colleagues or customers, making it easy to try out modifications without breaking the original files.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t