Debug in coder.extrinsic

4 visualizaciones (últimos 30 días)
Qingyu
Qingyu el 15 de Jun. de 2020
Respondida: Denis Gurchenkov el 14 de Jul. de 2023
Hi, I use 'coder.extrinsic' in the 'Matlab function' block of Simulink.
However, the debugging is inconvenient.
Here is a simple example.
coder.extrinsic('abcd')
[c,d]=abcd(a,b)
If there is a bug in 'abcd.m', then the Simulink Diagnostic Viewer will show the corresponding error, say, 'size mismatch'. However, it does not show in which line the error is. If 'abcd.m' is a huge function, it would take a long time to locate the bug.
Is there a better way to debug extrinsic functions in Simulink?

Respuestas (1)

Denis Gurchenkov
Denis Gurchenkov el 14 de Jul. de 2023
There are two possible causes for an error in the extrinsic call.
  1. The error is in the body of this function.
  2. The error (size mismatch) happens when the return values of the function are assigned to the variables c and d.
For the first case, the way to debug is to put a breakpoint in the body of abcd, and then step through this function in MATLAB debugger. Note that because the call to abcd is extrinsic, this function is not generated to C code, and insted its source code is executed in the matlab interpreter, so breakpoints would work.
For the second case, you can just compare the return values of abcd (as you see in the debugger) to the sizes of c and d (those you can see in the compilation report). If the return values have bigger size (for instance, abcd returns a 3x3 array, whereas c is a scalar variable), that would explain the size mismatch error. To fix such an error, mark c as "coder.varsize" or pre-assign it to have the right size.

Categorías

Más información sobre Simulink PLC Coder en Help Center y File Exchange.

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by