Rpy_C_OORTX_Keil_ARM_MCB1700_RC_V6.00 Release Notes
About Release Notes
This document lists all changes that have been applied to the RXF product Rpy_C_OORTX_Keil_ARM_MCB1700_RC from version to version.
Changes can be new features which have been implemented, functional changes, fixed problems or new known issues.
If a change has been implemented for one parts this product consists of, if will be listed here. Rpy_C_OORTX_Keil_ARM_MCB1700_RC
=== Product Rpy_C_OORTX_Keil_ARM_MCB1700_RC ===
RXF ................. : Willert OORTX
IDE ................. : Keil uVision 4
Debugger ............ : Keil uVision 4
Modelling ........... : IBM Rational Rhapsody
Language ............ : ANSI C
RTOS ................ : Willert OORTX
CompilerAndTarget ... : Keil MDK-ARM
Board ............... : Keil MCB1700
Extension ........... : Rhapsody OXF Container classes
New in Version V6.00
Changes introduced in Rpy_C_OORTX_Keil_ARM_MCB1700_RC_V6.00 which was released on 2012-09-19.
||Improvements in NULL pointer checks made after reviewing Klocwork report
||Improved V6 Documentation
||Improved RXF documentation
||Solved problem with FIRE, FIRE_S, FIRE_ISR and FIRE_ISR_S macros for sending events.
||Corrected handling of null transitions by solving problem with the Null_id identifier
||Setup is now adding a tools menu entry to Rhapsody to make it possible to start the IDE project, which is associated with the currently active component in the model.
||Implemented linked list container class WST_CON_LST to allow ordered one-to-many relations in UML models.
||Implemented macros to support easier initializing and sending of static events from an array. This mechanism is usually necessary when sending events from an ISR. The new macros are WST_EVT_initStaticEventArray( EVENT, EVENT_ARRAY, SIZE ), WST_EVT_initStaticEventArray_S( SOURCE, EVENT, EVENT_ARRAY, SIZE ) and FIRE_ISR_ARRAY( DESTINATION, EVENT_ARRAY, INDEX, SIZE ).
Changes in Behavior
||Added possibility to force WST error handler calls on memory allocation problems also in Release buildsets via defines WST_FORCE_ERRORHANDLER_IN_RELEASE or WST_FORCE_ALLOC_FAILED
||Under Windows 7 the setup will propose a Willert installation path located under the user files directory to make sure read and write access is possible.
||WSTDeployer now saves the IDE destination path in relation to the generated sources path of the active configuration. The deepest three directory levels are used as a key to identify model, component and configuration the IDE project is related to. For details please read the WSTDeployer Configuration documentation.