While running the Simulink HDL Coder (R2016a) on Windows 7, I got an error message from Windows that "mwdot stopped working". I killed the process and HDL coder continued, eventually creating a HDL Code Generation Report Summary.
I replicated the problem by running HDL Coder on the same Simulink model in a RHEL 6 environment. While mwdot did not experience a problem, it ran for over 40 min. After killing the process, code generation appears to have continued normally with a HDL Code Generation Report Summary returned.
What is the purpose of calling mwdot? Is it essential to correct HDL coder output or is it used for other purposes such as documentation? Thanks!
Best Answer