Speedgoat IO601 library blocks in Polyspace Bug Finder

When the code from Speedgoat IO601 library(S-functions) is analyzed, it displays so many errors due to the MISRA C 2004 standards. How to modify the code in order to prevent those warnings and make the code more efficient?

Answer 1

[Diego Kuratli]

Currently, Speedgoat I/O drivers are not certified for any specific standard. Although we ensure high quality products, Simulink Real-Time and Speedgoat real-time target machines are not intended to be used in safety critical applications.

[Birdman]

Diego,

It is nice to learn that they are not certified but I think we can decrease the effect of those drivers in the generated code since they produce SimStruct data to call the output every single time. As far as I know, by a single tlc file, those s-functions can be inlined and the code can be more efficient. Do you have any idea about it?

[Diego Kuratli]

Yes, you are right. The driver parameters can be fully inlined with a TLC file. However, that would be a very limited improvement on the overall driver performance for a x86 system, considering that the major delay is added by the PCI read/write operations, which are in the microseconds range.

[Birdman]

That sounds reasonable. How the tlc file for those driver blocks would be written anyway? Can you provide an example? I have some knowledge but not enough I'm afraid.

[Diego Kuratli]

I would not recommend that you add the TLC file for the driver blocks, as that may potentially affect the driver functionality. Instead, I'm going to review your request with our development team. Many thanks for your feedback! - Diego

[Birdman]

You are welcome. I look forward to hearing from you as soon as the development team says something new. -Çevikalp