Migration from V7 to V8

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

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
Constants
Error Codes
The table below shows V7 and V8 error codes:
V7V8
WST_ERR_EMPTY_ME_PTRRXF_ERROR_EMPTY_ME_PTR
WST_ERR_TSK_INIT_FAILEDRXF_ERROR_TASK_INIT_FAILED
WST_ERR_TSK_START_FAILEDRXF_ERROR_TASK_START_FAILED
WST_ERR_TSK_DELETE_FAILEDRXF_ERROR_TASK_DELETE_FAILED
WST_ERR_EMPTY_TASK_PTR-
-RXF_ERROR_TASK_SUSPEND_FAILED
-RXF_ERROR_TASK_RESUME_FAILED
RXF_ERROR_TIMER_CREATE_FAILEDRXF_ERROR_TIMER_CREATE_FAILED
WST_ERR_TMR_START_FAILEDRXF_ERROR_TIMER_START_FAILED
WST_ERR_MTX_CREATE_FAILEDRXF_ERROR_MUTEX_CREATE_FAILED
WST_ERR_MTX_CLEANUP_FAILEDRXF_ERROR_MUTEX_CLEANUP_FAILED
WST_ERR_MTX_LOCK_FAILEDRXF_ERROR_MUTEX_LOCK_FAILED
WST_ERR_MTX_UNLOCK_FAILEDRXF_ERROR_MUTEX_UNLOCK_FAILED
WST_ERR_MTX_EMPTY_PTRRXF_ERROR_MUTEX_EMPTY_PTR
RXF_ERROR_MEMORY_ALLOC_TOO_LARGERXF_ERROR_MEMORY_ALLOC_TOO_LARGE
WST_ERR_MEM_CONFIG_ERRORRXF_ERROR_MEMORY_CONFIG_ERROR
WST_ERR_MEM_INVALID_RETURN_PTRRXF_ERROR_MEMORY_INVALID_RETURN_PTR
WST_ERR_FSM_EVENT_NOT_CONSUMEDRXF_ERROR_REACTIVE_EVENT_NOT_CONSUMED
WST_ERR_FSM_FSM_EVENT_REUSE_DETECTEDRXF_ERROR_REACTIVE_EVENT_REUSE_DETECTED
WST_ERR_FSM_EMPTY_VTBL_PTRRXF_ERROR_REACTIVE_EMPTY_VTBL_PTR
WST_ERR_FSM_VTBL_EMPTY_DISPATCHEVENT_PTRRXF_ERROR_REACTIVE_VTBL_EMPTY_DISPATCHEVENT_PTR
WST_ERR_TOO_FEW_NULL_CONFIGSRXF_ERROR_TOO_FEW_NULL_CONFIGS
WST_ERR_INFINITE_NULL_TRANSITIONSRXF_ERROR_INFINITE_NULL_TRANSITIONS
WST_ERR_EVT_DESTINATION_NULLRXF_ERROR_EVENT_DESTINATION_NULL
WST_ERR_ITF_EMPTY_VTBL_PTR-
WST_ERR_ITF_VTBL_EMPTY_GEN_PTR-
WST_ERR_RTOS_INIT_FAILEDRXF_ERROR_RTOS_INIT_FAILED
WST_ERR_EMPTY_SWC_PTR-
WST_ERR_WIN_EVENT_FAILEDRXF_ERROR_WIN_EVENT_FAILED
WST_ERR_WIN_THREAD_FAILEDRXF_ERROR_WIN_THREAD_FAILED
WST_ERR_AUTOSAR_SWC_INIT_ERRORRXF_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:
In V8, there are two property perspectives specific for the product:
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: