Restrictions

• modelling. Rhapsody in C supports the so-called Operating System Abstraction Layer, but OSAL also includes services for which no code is generated like semaphores.
• generated C code. The C code generated by Rhapsody is not using the Object eXecution Framework by IBM Rational, but the RXF by Willert Software Tools instead. The Framework by Willert Software Tools uses slightly different data structures and a different organized set of include files, which is why we need to use those instead.
• files for properties and profiles.
• if this product comes with an implemented IDE interface the generated files will be deployed into your IDE project.

Modelling

• Activity Diagrams associated to Operations:
  Code generation is only supported for activity diagrams and statecharts which are associated with a class, an object or a file. Activity diagrams can also be assigned to operations, but no C code can be generated from them by Rhapsody.
• Ports:
  Communication via UML ports is not yet implemented for C code generation in Rhapsody 6.2, but as of Rhapsody 7.0. In products based on the RXF and an RTOS, the constant WST_PORTS_DISABLED is set to disable support for UML ports in the RXF because Ports are not implemented.
  
  
  
• Timers. The Framework uses its own RiCOSTimer object for the Bridge Task, which handles the timeout events. The Framework does not support further timers.
• Destroying objects remotely from another task: Having two active classes Controller and ToBeDestroyed, it is not possible to destroy ToBeDestroyed by just calling ToBeDestroyed_Destroy() from Controller. It would not always remove the waiting timeouts and events from the queues, which could cause an undefined behavior. However, there is a simple workaround how Controller can get ToBeDestroyed to destroy itself. Controller can send en evDestroy to ToBeDestroyed . The statechart of ToBeDestroyed must in any state be able to reacto to that event, which is possible by surrounding the actual statechart with one root state. The transition triggered by evDestroy must connect the root state (defaultState) to the termination connector.
  
  Although not a restriction but merely a remark: depending on the RTOS used, any resources allocated for the task or thread being terminated, are not destroyed:
  
  

  void ToBeDestroyed( ToBedestroyed * me ) {         if ( me != NULL )         {                  ToBeDestroyed_Cleanup( me );           /* This will terminate the task or thread */          }          free( me );                                                    /* This statement will never be reached */ }

  
  
  
  
  
  
  

 Renesas M16C only

• Known Issue #1355: the IBM Rational Container Class RiCString does not support far string constants for M16C. As a workaround, the macros STR_ARGUMENT_TYPE and STR_RETURN_TYPE are introduced in WSTCompiler.h. The use of the RiCString Class is disencouraged.
• Known Issue #1440: the Renesas toolchain uses the keyword _far for dynamic memory using malloc(), free() etc. We advice to use the StaticComponent stereotype which prevents usage of these dynamic memory functions
  

RXF

• Sockets
  The RXF does not support communication via TCP/IP due to the heavy overhead. As a consequence there is no support for animation. There is no RiCOSSocket class. But the Embedded UML Target Debugger allows to animate the behavior on target.
• some UML elements can't be used together with C code generation. These are:
• • Inheritance
    To allow inheritance in the C language, all operations would need to be implemented as callbacks or in a virtual function table. This would increase the code size, RAM needs, runtime and calling operations from user code would be more complicated. Thus no inheritance is available in Rhapsody in C.
  • Activity Diagrams associated to operations:
    Code generation is only supported for activity diagrams and statecharts which are associated with a class, an object or a file. Activity diagrams can also be assigned to operations, but no C code canbe generated from them.
  • Ports
    Communication via UML ports is not yet implemented for C code generation in Rhapsody 6.2, but as of Rhapsody 7.0.
    The constant WST_PORTS_DISABLED is set to disable support for UML ports in the RXF in a profile which comes with your release.
  • Timers. The Framework uses its own RiCOSTimer object for the Bridge Task, which handles the timeout events. The Framework does not support further RiCOSTimer objects.

Animation

• Only instances of "Object" with the same name of the object are supported. This means if struct "Object_t" exists, the instance must be named "Object".
• Class instances daclared statically inside a user function will not be animated correctly. If a user does something like this:
  
  
  void Object_anyUserFunc( struct Object_t* const me )
  {
          Class myLocalInstance;
          Class_foo( &myLocalInstance );
  }
  
  
  it will not be animated correctly, as we do not parse the generated sources when generating the XML intermediate file.
  
• Only rective classes (with statecharts) can be animated.
• Statically preallocated event arrays are not supported for animation. These are used for example for calling CGEN_ISR to send an event from an interrupt.

IDE

All IDEs except uVision

CodeComposer and MPLAB IDEs only

Renesas HEW IDE only

IAR Embedded Workbench only