You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello everyone, I am doing research in the area of data-driven optimal control and currently use the qpOASES solver. In the course of initial tests, I want to run the minimal example example_QProblemB.mdl on the speedgoat hardware via the Simulink interface. Both code generation and compilation work after I have included the corresponding header files and source files in Simulink Real Time settings. Here I orientated myself on chapter 6.7 in the qpOASES manual. As soon as the real time application is to be uploaded to the target, the following error message appears:
Error running example_QProblemB on target computer: Unable to load example_QProblemB on target computer 'TargetPC1': WTERMSIG: 11 WCOREDUMP: 128
Does anyone know what this error means or how to fix it?
Or knows how to get the qpOASES solver onto the speedgoat hardware?
Many thanks in advance.
The text was updated successfully, but these errors were encountered:
Hello everyone, I am doing research in the area of data-driven optimal control and currently use the qpOASES solver. In the course of initial tests, I want to run the minimal example
example_QProblemB.mdl
on the speedgoat hardware via the Simulink interface. Both code generation and compilation work after I have included the corresponding header files and source files in Simulink Real Time settings. Here I orientated myself on chapter 6.7 in the qpOASES manual. As soon as the real time application is to be uploaded to the target, the following error message appears:Error running example_QProblemB on target computer: Unable to load example_QProblemB on target computer 'TargetPC1': WTERMSIG: 11 WCOREDUMP: 128
Does anyone know what this error means or how to fix it?
Or knows how to get the qpOASES solver onto the speedgoat hardware?
Many thanks in advance.
The text was updated successfully, but these errors were encountered: