Modify VDK Configuration

If you want to use a different target derivate for the RTOS integration which comes with your product, please consult the documentation of your RTOS manufactorer.

VDKConfig

The VDK RTOS Adapter consists of some files which are installed for this RTOS:

RiCOSMainTask.c and RiCOSMainTask.h which are used by the VDK RTOS to run the Rhapsody generated function WST_RXF_Main(). This thread is used to run all non-active classes of your Rhapsody model.
RiCOSActiveClassTask.c and RiCOSActiveClassTask.h which is used to run all active classes of your Rhapsody model: for each active class a separate thread is created.
RiCOSBridgeTask.c and RiCOSBridgeTask.h which is used as a heartbeat of the RXF. This is a small thread which is scheduled at periodic intervals to schedule events within the RXF.

The VDK configuration must match your hardware and Rhapsody application. VisualDSP++ only supports a project which results in an executable to specify VDK details, so we created a separate project VDKConfig for this which you find in <your Rhapsody>\Share\WST_RXF_V5\<your product>\Samples\Code where you can configure the VDK:

This project can generate the files VDK.h and VDK.cpp which are used by the RXF libraries in the CreateRXFLibrary project.

There are some hardware details you can configure plus some RXF specifics which you may want to modify:

the maximum number of threads. For each active class in your Rhapsody model, a new thread is created when a corresponding object is created. When VDK runs out of threads the function RiCErrorHandler_error() is called with the code OXF_TASK_CREATE_FAILED.
the priority of the RiCOSMainTask, RiCOSActiveTask and RICOSBridgeTask. The values used must match the constants RTOS_PRIORITY_NORMAL and RTOS_PRIORITY_HIGH respectively.
Note that these priorities are specified as VDK_kPriority15 and VDK_kPriority1 by default: you must use a VDK_kPriorityXX constant here. In a Rhapsody model you can use a number which is translated in the RTOS adapter using the macro RTOS_PRIORITY_NUMBER2SYMBOL(N).
the stacksize of threads. We created a separate thread type for the Bridge Task and Main Task so you can use any stacksize and priority. If you are not satisfied with using default values for the stacksize or priority of a thread for active classes, you can use the properties CG::Class::ActiveStackSize and the other is C_CG::Class::ActiveThreadPriority. Please read the application note Application Note: Strauss Stack Size Configuration at www.uml-forum.de for more details even if this is an Application Note on a different RTOS adapter.
the heapsize of threads.
the maximum number of messages. Messages sent within the RXF use the payload type RTOS_MSGPAYLOAD_TYPE.
The function RiCErrorHandler_error() is called with the code OXF_MSGQ_CREATE_FAILED if VDK can not create a new message. The number of messages needed depends on your model and its runtime behaviour:

for each event sent from one object to another, a message is used. It is created using VDK_CreateMessage() and destroyed using VDK_DestroyMessage() when the event is consumed.
a timeout results in an event and is created and destroyed as any event.

the maximum number of semaphores. The function RiCErrorHandler_error() is called with the code OXF_SEMA_CREATE_FAILED if VDK can not create a new semaphore. Although the Rhapsody generated code does not use a RiCOSSemaphore class, the VDK RTOS adapter uses semaphores for the RiCOSMutex class - which is generated and also semaphores in the RiCOSEventFlag class - which is not generated. So you may expect error codes OXF_MUTEX_INIT_FAILED and OXF_EVFLAG_INIT_FAILED in the function RiCErrorHandler_error().

See below:

Notes	You are not allowed to use different names for the Thread Types. The names are used in the RXF code and the RXF will no longer compile or function if you change them.
	You must have a Round-Robin Priority configured for the priority used by the RiCOSMainTaskType to have it scheduled.