For all users using the RXF C V8.0.7 and prior V8 versions, it is highly recommended to update to version 8.0.8 or newer because of a bug inside the timer manager.

The bug could occur when stopping an UML timer with another UML event. While stopping the timer by a user task, the timer task driving the UML timer could interrupt the stop operation of the user task and corrupt the linked list of timeouts in use and the depending message queue of an expiring UML timer.

The bug could cause problems very rare, what is the reason why it is discovered that late.

For any questions regarding this problem please contact the support @ support@sodiuswillert.com.

Our frameworks for UML code generation from IBM Rhapsody are developed in a way that they can be adapted easily to different RTOSes or targets and there is a huge list of supported environments. But there is a big difference between our version 6 frameworks and our version 7 generic framework.

RXF V7

Version 7: For our generic C++ framework there is just one download “containing it all” and allowing all combinations that make sense. That’s why we call it generic. Continue reading →

The property RXF_Rpy_CPP::Configuration::WST_TMR_PROTECTION contains a typo that will lead to a generated define that is not matching the #ifdef tests for timeout protection.
It is:
WST_TMR_USE_CRITICAL_SECION
It should be:
WST_TMR_USE_CRITICAL_SECTION

This is only a problem, when RXF_Rpy_CPP::Configuration::WST_TMR_PROTECTION is set to WST_TMR_USE_CRITICAL_SECION. It is not a problem, it is is set to WST_TMR_USE_MUTEX.

In the Cert framework (RXF_Rpy_CPP_OORTX_Cert), in C frameworks and in V6 releases this problem does not exist.

Workaround

The problem can be fixed by editing the file “<RXF_Rpy_CPP folder>\RXF\Config\Profiles\RXF_Rpy_CPP_Profile.prp”. In that file search for “WST_TMR_USE_CRITICAL_SECION” and replace the one occurrence by “WST_TMR_USE_CRITICAL_SECTION”.

An official release V7.11 that will fix this problem is planned and will be published soon.

On December 4, 2017 IBM released Rhapsody 8.3. This release contains a lot of fixes and some changes. It is good to take a look at these changes to see what impact they have on your development environment.

iFix 2 Absolutely Required

Major changes in Rhapsody’s repository data, see next section, unfortunately introduced some problems that will be fixed again with the iFix 2 for Rhapsody 8.3 (32-bit).

Please take care when upgrading to Rhapsody 8.3 to directly also install iFix2.

Continue reading →

Hi!

IBM has released the first iFix for the fresh Rhapsody 8.3. This is a good moment to give an overview of the available iFixes and versions.

Continue reading →

IBM released a new version of Rhapsody: 8.3

It is available for support customers of Willert Software Tools in the download area, but all guests can read the Release notes there.

Willert Software Tools will, in the next days, check if this release can be used by RXF customers.

One of the changes is the change from the old rhapsody file format to the new XML format.

IBM released a new version of Rhapsody: 8.2.1.

It is available for support customers of Willert Software Tools in the download area, but all guests can read the Release notes there.

Willert Software Tools will, in the next days, check if this release can be used by RXF customers.

Sometimes Rhapsody is not working as it should. Many “problems” can be solved by installing Rhapsody in the right way and by using it the right way.

Here are some quick solutions that might help improving your Rhapsody Experience:

Continue reading →

Since a few versions, IBM creates Fixes for actual versions of Rhapsody.

Customers with a valid support contract can download them from this site.

There are several fixes, for 8.2, 8.1.5 and 8.1.4

Fixes are only available on this site for the 32-bit version

Fixes and downloads for 64-bits or for Linux are available on request (support@willert.de)