Getting Started Example

If you have not created the Framework libraries already, please do so.

Rhapsody in C

Please verify the implementation of your compiler bridge and target bridge, in particular the function WSTTarget_Init(). The function WSTTarget_incrementRxfTicks() must be called peridically, so either during board initialization within startup code, or within WSTTarget_Init() you must use a Interrupt Service Routine like WSTTarget_timerInterrupt().

Open the Rhapsody project Blinky at the directory <your Rhapsody>\Share\WST_RXF_V5\<your product>\Samples\Model\Blinky:

TargetComponent is using the stereotype RXFComponent which is defined in the profile Kimberger. Each RXF by Willert Software Tools comes with its own profile with the stereotype RXFComponent. RXFComponent sets the proper environment, some properies for the RXF and defines some Tags. These Tags are used by the Deployer so it will use relative paths inside your EDE project. The other profile referenced, WSTProfile, is used to set Rhapsody GUI details which makes it easier for you to view and maintain your models.

ExamplePkg has two objects:

LED which has an Init(), on() and off() operation
Controller which has a simple statechart which toggles the states on and off in LED every 300 msec.

Select the proper environment via the Features and do this for both Configurations Debug and Release:

The Deployer which will deploy Rhapsody generated source files and some generated configuration files, needs information from your model on relative paths inside an EDE project:

It uses Tags from the stereotype RXFComponent which you must specify for your Component:

the Tag relativeGeneratedFilePath defines the path inside the GettingStarted EDE Project Space to deploy Rhapsody model generated files to
the Tag relativeRxfPath defines the path inside the EDE Project Space to deploy framework files to
the Tag toolchainProjectFile defines the name of the BlinkyD EDE project file to update (the deployed files must be added to the project). Set it to BlinkyD.pjt
the Tag rootDescription will be is displayed in the WSTDeployer GUI. It is a short text to inform developers working on the model, to what kind of build environment the model should be deployed. It can also include a non machine dependent hint, where the BlinkyD EDE project's root directory can be found.
the Tag rootTitle is also displayed in the WSTDeployer GUI. It is a short title for the EDE project's machine specific root path.

Note

Each Rhapsody model must have a reference to the Kimberger profile and use the stereotype RXFComponent.
This will allow you to use the Tags. You can set them via the Features dialog for your component. Kimberger.sbs is installed in <Rhapsody>\Share\WST_RXF_V5\<product>\Config\Profiles\Kimberger_Profile_rpy

Use Code | Generate Debug to generate C code from this model, and accept the question to have the directory created for the Debug Configuration:

Use Code | Build TargetComponent.dat to generate

the file RhapsodyRun.bat to launch the deployer later on.
the file RxfDimensions.h which is an include file which contains constants which are derived from properties set in the Rhapsody model like RIC_MAX_EVENTS, RIC_MAX_TIMEOUTS, RIC_SMALL_BUFFER_SIZE etc.
These all deal with dimensions for the RXF, and because these are inserted in an include file you do not need to set these constants in your EDE later.
the file RxfConstants.h which sets constants with respect to the version of the RXF and Rhapsody and sets _DEBUG, WST_HIGHWATERMARKS and NO_MALLOC used in a Debug configuration or Buildset.
the file WSTMemoryTypes.h which is used for Memory Section Management so you can locate code and data exact where you like it.

Now you can deploy the generated files. The model does not contain the location of your GettingStarted ? project on your PC; the Deployer will maintain that information instead. This enables one to have the same project used by different persons at different locations; the installation of the Tasking toolchain on various PCs may differ.

Deployer

The very first time that the Deployer must deploy a project, it will automatically launch in configuration mode and ask for path(s). Select Code | Run TargetComponent.dat to start the Deployer:

The Deployer will prompt for the path to your GettingStarted workspace or project, so you must specify Rhapsody\Share\WST_RXF_V5\<your product>\Samples\Code\GettingStarted:

The Deployer knows from your model that it must search for a ? project file in that directory, which it will update with the names of the files it deploys:

After you saved the path to GettingStarted, the files are deployed to the ? project:

EDE

You must close the project in the EDE and reopen it before you can see the files added to your project. We are working on this Known Issue #778.

Now open the GettingStarted Project Space in the EDE, which is installed in the directory <your Rhapsody>\Share\WST_RXF_V5\<your product>\Samples\Model\Code\GettingStated:

Now we can build the application and test it.

Note	You must add an entry in the Rhapsody Tools menu, which launces the Deployer in Configuration Mode. This allows you to change the path used by the Deployer for your EDEn project in case you want to use a different EDE project for your Rhapsody project, or in case you moved the EDE project.

Buildsets

In the Rhapsody model you can choose between a Debug and Release buildset. Please note that the Tasking EDE uses a different project file per project in the EDE: if you want to use the Release buildset, you must also change the name of the toolchainProjectFile Tag to BlinkyR.pjt: