Product news |
| Version 5.4 of IAR visualSTATE includes the following news and enhancements: |
C-SPY® debugger integration with visual state machine feedback |
| Comprehensive graphical state machine debugging on the target device. Due to the new integration with the C-SPY Debugger in IAR Embedded Workbench, it is now possible to see what is going on on-target at the state machine design level. It is now possible to view received event triggers, executed action functions and the resulting global system state directly in C-SPY. |
Major speed up of API functions |
It is now possible to let the code generator allocate some internal data on the stack for the Basic API instead of using static allocation, by setting the coder option Use auto variables. This has three benefits:
- Decreased cycle count for the complete event loop. The savings vary with model, typical event sequences and target compiler, but representative values fall in the range 15-45%.
- Decreased run-time memory requirements. Temporary used memory is now allocated on the stack, instead of statically allocated. This is most noticeable for projects with more than one system or more than one instance.
- Decreased code size for the API. The compiled size of the API files is reduced by approximately 10% for most compilers.
|
Improved run-time performance of the Verificator |
| A set of safe optimizations have been implemented in the Verificator. The resulting decrease in running time has been observed to be up to 35%. (Measured as total running time on internal test suites.) The exact performance increase varies with the model. |
Further increased MISRA C compliance of the Basic API |
| Warnings for MISRA rule nr 83 has been removed. It is now default for the code generator to insert C style casts in guard expression functions to properly match function return type to guard expression type. For a good compiler the generated code is exactly the same, but the intention of the code is made clearer. |
Improved OO structure of generated C++ code |
| When generating code for the Basic API with C++ output enabled the Coder will now generate all action functions as pure virtual members of the system classes. You will need to subclass the visualSTATE system classes and implement the pure virtual methods in subclasses. |
Integration with Altia Design |
| The Validator can now connect to GUI designs created in Altia Design, a design environment for user interface design and simulation. This enables high-level prototyping and validation of application behavior long before the hardware is finalized or even existing. |
Added documentation |
| The C-SPY integration is described in the visualSTATE C-SPY®Link User Guide. This document is also available from the Navigator help menu. |
| |
| See more details in readme.htm. |
| |
| |
