Bridges

The Embedded UML Studio can be used in many different working environments, using different toolchains, targets, RTOSses and debuggers. In order to prevent enormous maintenance effort and to minimize effort required to adapt a product to a different toolchain, target, RTOS or debugger, we have defined the concept of Bridges. A Bridge fills the gap between the common or generic Embedded UML Studio and its outer world.

The RXF is maintained using a common source code base, with well defined interfaces towards compiler dependancies (support for memory models and keywords), target dependancies (sizes of certain data types) and OO RTX which can be seen as a special RTOS.

The demo versions of our products use an internal build process. Non-demo versions of our products support an external build process inside the IDE of the respective toolchain. For some products and adaptations the IDE integration uses a Deployer which not only copies the files to an IDE project but also adds the names of the files in the IDE project file. Several non-demo versions of our products therefore support a Deployer component and IDE Bridge.

For some products, we add features or apply changes in the existing source code. Instead of modifying the actual common code base, we use a build environment which copies files in a defined order from a development environment to a production environment so Rhapsody can use it. The files which shouild be added or override existing common files, are maintained in a PMF (pimp my Framework) directory structure: during the copying of files these are copied after the common files have been copied, so they override an existing code base.
Such PMF files may interface with an RTOS adapter and debugger, for example for the target tracing.

The Deployer is implemented using an interface in such way, that one is capable of adapting the Deployer for virtually any IDE.

Please note: The IDE integration is not part of all products or adaptations.