Migration from V7 to V8

V8 products come with a number of changes which are not backwards compatible with respect to V7.

the section Changes between V7 and V8 in ARXF-CP product
the section How to Migrate a Project a Project shows the required steps

Changes between V7 and V8

Profiles

In V7, the ARXF-CP was released with a profile which had the name of the product, like RXF_Rpy_C_AutosarCp_Profile.

In V8, the ARXF-CP is released with a profile RXF.

Properties

The property RXF_Rpy_C_AutosarCP::DeployerFolders::Target used by the V7 Deployer has been removed.

Runnables

There are two changes which effect existing models

the 'timerTick' runnable is no longer used in the examples and Best Practices. The code inside the 'timerTick' runnable and 'eventDispatcher' runnable are combined. This also effected Standard Content.
the classes used inside the ARXF-CP are no longer prefixed with WST but RXF and are sometimes renamed. This effects both code inside runnables and Standard Content.

Constants

Error Codes

The table below shows V7 and V8 error codes:

V7	V8
WST_ERR_EMPTY_ME_PTR	RXF_ERROR_EMPTY_ME_PTR
WST_ERR_TSK_INIT_FAILED	RXF_ERROR_TASK_INIT_FAILED
WST_ERR_TSK_START_FAILED	RXF_ERROR_TASK_START_FAILED
WST_ERR_TSK_DELETE_FAILED	RXF_ERROR_TASK_DELETE_FAILED
WST_ERR_EMPTY_TASK_PTR	-
-	RXF_ERROR_TASK_SUSPEND_FAILED
-	RXF_ERROR_TASK_RESUME_FAILED
RXF_ERROR_TIMER_CREATE_FAILED	RXF_ERROR_TIMER_CREATE_FAILED
WST_ERR_TMR_START_FAILED	RXF_ERROR_TIMER_START_FAILED
WST_ERR_MTX_CREATE_FAILED	RXF_ERROR_MUTEX_CREATE_FAILED
WST_ERR_MTX_CLEANUP_FAILED	RXF_ERROR_MUTEX_CLEANUP_FAILED
WST_ERR_MTX_LOCK_FAILED	RXF_ERROR_MUTEX_LOCK_FAILED
WST_ERR_MTX_UNLOCK_FAILED	RXF_ERROR_MUTEX_UNLOCK_FAILED
WST_ERR_MTX_EMPTY_PTR	RXF_ERROR_MUTEX_EMPTY_PTR
RXF_ERROR_MEMORY_ALLOC_TOO_LARGE	RXF_ERROR_MEMORY_ALLOC_TOO_LARGE
WST_ERR_MEM_CONFIG_ERROR	RXF_ERROR_MEMORY_CONFIG_ERROR
WST_ERR_MEM_INVALID_RETURN_PTR	RXF_ERROR_MEMORY_INVALID_RETURN_PTR
WST_ERR_FSM_EVENT_NOT_CONSUMED	RXF_ERROR_REACTIVE_EVENT_NOT_CONSUMED
WST_ERR_FSM_FSM_EVENT_REUSE_DETECTED	RXF_ERROR_REACTIVE_EVENT_REUSE_DETECTED
WST_ERR_FSM_EMPTY_VTBL_PTR	RXF_ERROR_REACTIVE_EMPTY_VTBL_PTR
WST_ERR_FSM_VTBL_EMPTY_DISPATCHEVENT_PTR	RXF_ERROR_REACTIVE_VTBL_EMPTY_DISPATCHEVENT_PTR
WST_ERR_TOO_FEW_NULL_CONFIGS	RXF_ERROR_TOO_FEW_NULL_CONFIGS
WST_ERR_INFINITE_NULL_TRANSITIONS	RXF_ERROR_INFINITE_NULL_TRANSITIONS
WST_ERR_EVT_DESTINATION_NULL	RXF_ERROR_EVENT_DESTINATION_NULL
WST_ERR_ITF_EMPTY_VTBL_PTR	-
WST_ERR_ITF_VTBL_EMPTY_GEN_PTR	-
WST_ERR_RTOS_INIT_FAILED	RXF_ERROR_RTOS_INIT_FAILED
WST_ERR_EMPTY_SWC_PTR	-
WST_ERR_WIN_EVENT_FAILED	RXF_ERROR_WIN_EVENT_FAILED
WST_ERR_WIN_THREAD_FAILED	RXF_ERROR_WIN_THREAD_FAILED
WST_ERR_AUTOSAR_SWC_INIT_ERROR	RXF_ERROR_AUTOSAR_SWC_INIT_ERROR

Generated Configuration Files

When generating code for your Rhapsody model, also configuration details are generated into include files.

In V7, the file WST_CFG.h was generated. In V8, this is RXF_Config.h

In V8, there is a new file RXF_VirtualTable.h generated which defines a virtual table used by Rhapsody's code generator to be able to call operations for dispatching events, processing statecharts, etc.

Property Perspectives

In V7, there was one property perspective specific for the product:

SodiusWillert RXF C

In V8, there are two property perspectives specific for the product:

RXF which is used to access any RXF property, like Deployer, Configuration, Interface Code Generation, User Hooks and Memory Pools
ARXF CP which is used to access any specific properties used for code generation targeted at AUTOSAR Classic Platform

Deployer

In V7, the Deployer stored information in a file per component, for example Blinky_AutosarTarget_Debug.dxc
In V8, the Deployer uses information of the properties RXF::Deployer::IDEProject and RXF::DeployerFolders

See section Usage | Deployment on how to configure paths for deployment and optionally update IDE project files.

How to Migrate a Project

At large, migrating a project comes down to replacing RXF profiles, dealing with overridden RXF related properties and fixing some code.

Open your model and click on Ignore All when Rhapsody complains it can not find a profile, for example WSTProfileAutosarCp.sbsx
This will result in a model with many unresolved references and a weird layout in the treeview. Following the next steps will help you:

use File | Add to Model.. to add the profile X and select Replace...
Do this for the profiles: RXF, RXFStereotypesC, RXFTypesC, ArUML_ARXF_CP and ArUML_ARXF
use File | Add to Model.. to add an error handler, see section Error handling
- merge the contents of your old error handler into the new one and delete your own error handler from your model.
- search in your model for error codes using the prefix WST_ERR_ and replace these with the new error codes, see table above.
V8 frameworks support multiple RTOSses out of the box, which is why a property for the Target is obsolete and a property RTOS is used. Also, Deployment has been adapted to support multiple build environments more easily. This can have effect on the organization of Components and Configurations for your Build Environment.
Per Component and Configuration
- in the RXF Configuration property perspective, set the property RXF::DeployerFolders::RTOS to Autosar
- in the ARXF-CP Configuration property perspective, set the property ARXF_CP::Configuration::AdditionalDefines to for example #define WINDOWS_SIMULATION
determine if you want to combine the 'timerTick' runnable and 'eventDispatcher' in your model. If you do so:
- the code in the 'eventDispatcher' can be updated. You can have a look at the Standard Content or Blinky example
- the 'timerTick' runnable can be removed from your model
- the property ARXF_CP::CpSWC::RTEtriggerUMLeventDispatcherSWC can be un-overridden (previously known as RXF_Rpy_C_AutosarCP::CpSWC::RTEtriggerUMLeventDispatcherSWC)
  This also effects the AUTOSAR configuration: the 'timerTick' runnable must be removed and the 'eventDispatcher' runnable must be triggered by te RTE at a regular interval.
- replace the content of existing runnables. You can have a look at the Standard Content or Blinky example
- replace any overridden properties, typically on
  - Components and Configurations
  - SWCs and active classes:
- search for active classes and fix argument to Init() from WST_SWC * to RXF_SWC * by selecting the class operation, Argument tab, doubleclick symbol and fix the C declaration