This case study uses a simple helicopter control system to demonstrate a workflow compatible with ARP4754A, DO-178C and DO-331. The case study starts with system level requirements and provides the workflow all the way through executable object code verification. Although the demo uses many MathWorks toolbox licenses, in addition to MATLAB and Simulink, pre-generated artifacts are available for viewing without having to have all of those toolboxes installed on top of MATLAB and Simulink.
Bill Potter (2020). DO178_case_study (https://github.com/wfpotter/DO178_Case_Study/releases/tag/1.3), GitHub. Retrieved .
I found the solution regarding my previous problem. If you go in the model advisor and run the Simulink Code Inspector checks on the AHRS_voter, some fails will came out.
Solve these fails as suggested in the results and everithing will work fine.
I followed the case study and I see that Simulink Code Inspector verification FAILS on the AHRS_voter.
Looking at the report I see a lot of "Failed to trace" and "Unable to process".
The big question is: How to debug and fix this?
I have downloaded and installed the toolbox file but cannot figure out how to access it
Very Helpful. Thanks.
This is great. Thanks.
Great job putting this all together! Would be great to see more information regarding robustness testing and automatic test generation.
See release notes for this release on GitHub: https://github.com/wfpotter/DO178_Case_Study/releases/tag/1.3
Updated for R2019a to use Simulink Requirements, system Composer and Simulink Projects.