< Previous

Lesson 4: Generating ARXML and implementation C code

To generate arxml and C code use “re-generate” on the desired ARMBT configuration.

Rhapsody® will generate AR internal behavior elements and AR implementation elements related to the RIMB and in sync with the generated code of the RIMB. Rhapsody will either generate new AR elements or augment existing ones.

  1. To generate ARMXL and C code, in the browser, highlight the configuration for which you want to generate C code.
  2. Select Code > Re Generate > Entire Project. The Export window for AUTOSAR opens.
  3. Browse to and select the directory and XML file to receive the exported XML code. Click Export.
By default, new AUTOSAR elements are generated. However, for the elements in the following table, it is possible to use, or “connect to,” existing elements in the AUTOSAR design.
Table 1. AUTOSAR implementation elements
Connectable AR element How the connection is specified
InternalBehavior IB IB points to the implemented SWC type with l_component
Runnable RE

RE points with l_RIMBO to a RIMBO and with

l_runnableFunction to an active element in the RIMB typing the RIMBO

Exclusive area x x points with l_guardedRIMBO to a RIMBO
Inter Runnable Variable x x points with l_RIMBO to a RIMBO and with l_IRVAttribute to an attribute in the RIMB typing the RIMBO
For example, if there is in the AR design an internal behavior pointing with l_component to the SWC type being implemented then Rhapsody will use it instead of generating a new one.

Similarly, if there is a runnable in the AR design pointing with l_RIMBO to a RIMBO and with l_runnableFunction to an active element in the RIMB typing the RIMBO, then Rhapsody will not generate a runnable for that active element per that RIMBO and instead use the pointing runnable.

We have seen how Rhapsody supports the implementation of an AUTOSAR SW/C Type. The implementation can be Explicit, meaning explicit definition of the various artifacts composing the Implementation with
  • Internal Behavior, Implementation and Code sections,
  • XFiles and the RunnableEntities implementation Code with Rhapsody
Alternatively, implementation can leverage RIMB and integrate with Rhapsody and MicroC design.
< Previous

Feedback