Electronics and Semiconductors
Non-consumer electronics devices such as medical implants, transportation systems, and security systems must work reliably over time and under a variety of operating conditions, because errors can be very expensive and potentially dangerous. MATLAB and Simulink enable better design and more thorough verification for these devices.
MATLAB and Simulink models serve as executable specifications for the entire team so engineers can verify early on that the design works. To eliminate errors introduced by hand coding, engineers can generate C or HDL code from their models. They can test their code using IDE links to third-party embedded software tools such as TI’s Code Composer Studio, or EDA links to tools such as Cadence Incisive®. These links enable software-in-the-loop and hardware-in-the-loop testing.
Because Simulink can simulate systems containing analog, digital, mechanical, and other components, engineers can construct complete test harnesses for verifying the full range of system behaviors. For example, a model might contain a DSP-in-the-loop, enabling algorithms running on a DSP chip to be tested using analog system behavior simulated in Simulink.
When testing medical devices and other high-integrity systems, engineers need to go a stage further in proving the system behaves correctly. They use MathWorks code verification tools to verify the absence of errors in hand-written C/C++ code, as well as code generated from MATLAB and Simulink.
The code verification tools are also used for DO qualification, MISRA-C qualification, and IEC 61508 and ISO 26262 certification. Engineers have used these code generation and verification technologies in areas as diverse as medical devices, automotive engine control units, and aerospace systems.
Nissan Increases ECU Software Reliability (User Story)
"We surpassed our goal of doing 90% of the debugging in Simulink. The first time we targeted the FPGA we had our design up and running in five days, a task that used to take three weeks or more. Because we had verified the system in Simulink, we knew that any remaining problems were due to the VHDL implementation, not the architecture."Read the story