Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD_V6.02 Release Notes
About Release Notes
This document lists all changes that have been applied to the RXF product Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD 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_Keil5_ARM_MCB1700_TC_TD
== Product Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD == RXF ............... : Willert OORTX IDE ............... : Keil uVision 5 Debugger .......... : Keil uVision Modelling ......... : IBM Rational Rhapsody Language .......... : ANSI C RTOS .............. : Willert OORTX CompilerAndTarget . : Keil MDK-ARM Board ............. : Keil MCB1700 Extension ......... : BTC Test Conductor Interface Extension ......... : Embedded UML Target Debugger
New in Version V6.02
Changes introduced in Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD_V6.02 which was released on 2017-01-24.
|Case 4633||WSTModelling.h used to check the define WST_COMPILER_KEIL when defining the FIRE macros. This is not needed anymore and the #ifdef path could be removed.|
|Case 4634||The Stereotype MonitorForTC for using the TestConductor with the RXF and Target Debugger had a fixed GUID in the product specific RXF profile. This can cause problems when multiple RXF product profiles should be loaded at the same time into a model. Now it has a product and version specific GUID.|
|Case 4711||Corrected tick calculation. In previous RXF releases tm()-timeouts could expire up to two ticks too early. In tm(value) the value now specifies the time that at least needs to elapse, before the timeout expires. This means a tm(0) will expire at the next tick. Because of the tick granularity, a tm(1…WST_MS_PER_TICK) will expire after two ticks (which makes sure at least a full tick-cycle, lasting WST_MS_PER_TICK milliseconds, has elapsed).|
|Case 4836||Properties under C_CG::Configuration are not net via WST_RXF_V6.prp file anymore, but in the RXFComponent stereotype|
|Case 5142||On busy systems longer timeouts took longer then expected.|
|Case 5246||Improvement of the make file to prevent unnecessary regeneration of RXFConstants.h and RXFDimensions.h|
|Case 5465||OORTX implementation of WST_OSW_MSQ_cancelEvents did not handle static events correctly when destroying an object which still has events waiting in the queue|
|Case 5526||Target Debugger Simplification in C needs to generate WSTMonitor_sendTypes.c for Eval Releases also with deactivated animation. Also added warning about partial generate instead of regenerate when using animation. A full regenerate is needed to generate an XML file including all relevant class data for the Embedded UML Target Debugger.|
|Case 5631||Fixed a bug where Data send from UML Target Debugger to Target is not handled correct. Data was lost.|
|Case 5811||Fixed a bug where objects are initialized before the main Task was initialized which results in owner task == NULL. CPP|
|Case 4560||Added user Hooks before event processing and after event processing. Hooks are defined in WSTTarget.h.|
|Case 4635||The WSTDeployer now allows to override RXF files with generated files from the Model by using the same file name. For example it is now possible to override the RXF adaptation file WSTTarget.c by just adding a file with the same name somewhere in the model so that it generates. The WSTDeployer will then stop to deploy WSTTarget.c from the RXF source folder and will only add the file from the model. This behavior can be deactivated manually by setting ModelOverridesByFilename = false in WSTDeployer.properties.|
|Case 4787||#defines of the RXF have been moved into the Model. You can find it inside C_CG/CPP_CG::Configuration.|
|Case 5149||Moved Rhapsody Run into Rhapsody Make to have a sequential execution. This is needed to atomize the build steps.|
|Case 5636||By setting the Stereotype TC_WrapPrivateOperations to the active Component or Configuration all private Operations of the model will get a public wrapper operation named __wrapper().
This is needed to test private operations with the TestConductor.
Changes in Behavior
|Case 2035||WSTDeployer now uses the default name “GeneratedModel” (without space character) instead of “Generated Model” as a subfolder or group name in IDE sample projects to avoid problems with the space character.|
|Case 2849||Further improvements for MISRA-C 2004 compliance of the RXF|
|Case 4637||Willert changed the JDK version for developing Java tools like the WSTDeployer from JDK1.6 to JDK1.7 (Java 7). This requires customers to have JRE1.7 available to allow execution of these tools.|
|Case 4743||handleEventNotConsumed and handleTONotConsumed in WST_FSM now use the same function pointer typedef “WSTHandleNotConsumed”.|
|Case 5040||Keil5-ARM Evaluation Releases now only have one RXFR lib (an no extra AnimationR lib)|
|Case 5063||Using type WST_TimeUnit_t consistently for time values in the RXF instead of timeUnit which was then typedefed to WST_TimeUnit_t|
|Case 5064||Improved WST code generation simplifier robustness and diagnostic messages in Rhapsody.|
|Case 5068||RXF Profiles now only contain the RXF product name, and not the version number of the RXF release anymore. Also GUIDs contained (e.g. for stereotypes) are not specific per release version anymore, but just per RXF product.
This makes updating an existing UML project to a newer RXF version is much easier. It it not necessary anymore to go through all instances where RXF stereotypes are used to switch them to a newer version number of the same RXF product.Please note this also involves the following changes:
Only the profile of one version of an RXF profile for a product may be referenced at a time in a UML model (but different products in one model are still ok).
The Rhapsody\Share\Profiles\WST_RXF_V6 folder will only contain the RXF profile of the latest installed RXF per each product.
|Case 5099||The RXF for Rhapsody in C now uses the Java JRE delivered with Rhapsody for all Java based tools coming with it (and does not require java.exe to be found in the PATH environment variable anymore).|
|Case 5100||Updated supported Keil MDK-ARM version|
|Case 5195||The build step in Rhapsody used to execute a makefile, only to generate files like RxfDimensions.h and RxfConstants.h. Now for this step a much simpler batch file is generated and executed instead of the makefile, as there are no dependencies that need to be evaluated by make. The actual build step is still performed in the external IDE, as usual with the RXF.|
|Case 5207||Removed tags “rootDescription”, “rootTitle”, “toolchainProjectFile”, “relativeGeneratedFilePath” and “relativeRxfPath” from the RXFComponent Stereotype. They were only used for old RXF V5 Deployer compatibility.|
|Case 5250||Added support for Rhapsody 8.1.5, which uses a new Java location (including JDK instead of JRE).|
New in Version V6.01
Changes introduced in Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD_V6.01 which was released on 2015-04-13.
|Case 4502||WST_FSM takeEvent() had a NULL pointer reference when used with the Embedded UML Target Debugger and Triggered Operations. Solved by proper initialization of event->destination and by setting event->source to me->owner as a workaround (we do not know the actual sender of a triggered operation as the calling code is not instrumented) in WST_FSM_handleSyncEvent().|
|Case 4525||Possible enterCriticalRegion without exitCriticalRegion if a WST_MEM_Pool runs empty.|
|Case 4569||The RXF now uses Rhapsody Simplified Model Manipulation via Rhapsody Plugins to improve Code Generation and allow New Features|
Changes in Behavior
|Case 2808||Added 32 vs 64 bit API/Java consistency check to WSTDeployer.bat. This should assist solving problems especially related to Rhapsody 64-Bit configurations.|
|Case 4555||Minor MISRA-C 2004 Improvements|
|Case 4568||WSTDeployer helpers (e.g. to open the deployment configuration dialog) are now associated with the release specific RXF profiles instead of being added to Tools menu via rhapsody.ini. This has the advantage that only the tool menu entries which are useful for the currently loaded profiles are shown. Also, you may now right-click the component (which has the RXFComponent stereotype assigned) and select options for deployment.|
|This is the first release of the product “Rpy_C_OORTX_Keil5_ARM_MCB1700_TC_TD”.|
|A list of changes will be contained in the release notes of future product updates.|