Mbeddr core

Mbeddr

mbeddr aims at creating a different way of developing embedded software systems. Instead of using archaic modeling tools and manually written C code, we use the Open sSurce JetBrains MPS language workbench to create an integrated approach to embedded development, where C programming, DSLs, domain specific extensions to C, product line variability, requirements traceability and model checking are supported directly.

We developed an implementation of C in MPS, which can be used as a basis for domain-specific extensions. The old development progress is documented in our blog page. For some more information about the project, visit http://mbeddr.com/mps-platform-docs/mbeddr/ or the old homepage at http://mbeddr.com.

Old demos

Mbeddr Platform

The mbeddr platform provides various languages and extensions that can be used in all kinds of projects. Many extensions are briefly explained on this page. You most likely want to have com.mbeddr.platform as a dependency and not com.mbeddr. If you can't find a language here, make sure that it wasn't moved to MPS-Extensions. The mbeddr platform currently repackages all languages from MPS-Extensions. Some of the old languages that were moved have also still have the old com.mbeddr prefix Visit the page Issue Tracker | MPS Platform Docs for some more information on how to distinguish the various MPS repositories by package name.

Project Structure

The project consists of the following subprojects in the code/languages subfolder:

• com.mbeddr.build contains all the build scripts except for the platform
• com.mbeddr.cc contains all cross-cutting languages, such as product line engineering or tracing.
• com.mbeddr.core contains the core languages of mbedd,r including all interfaces and the C implementation.
• com.mbeddr.doc.aspect contains the code for the documentation tool at the lower left corner.
• com.mbeddr.doc contains the code for the documentation language.
• com.mbeddr.ext contains extensions to the C language.
• com.mbeddr.platform.build contains the build script for the platform.

The code/solutions folder contains some examples for the mbeddr C languages.

Maven Dependencies

To use mbeddr or the mbeddr platform in your project, you need one of the following dependencies in your Maven or Gradle build script. The latest supported MPS version is 2024.1, the master branch builds against the MPS master.

Mbeddr

MPS version	nexus status
master
2024.1
2023.2
2022.3
2022.2
2021.3
2021.2
2021.1
2020.3
2020.2
2020.1
2019.3

Mbeddr Platform

MPS version	nexus status
master
2024.1
2023.2
2022.3
2022.2
2021.3
2021.2
2021.1
2020.3
2020.2
2020.1
2019.3

Creating a PR

When you open a PR, the build on TeamCity needs to be approved by a colleague at itemis, and a PR review is necessary. If this doesn't happen, please ask in the Slack channel. Often, builds fail at the following step: Check for dirty files. If that happens, some migrations were not executed in the project. Run ./gradlew migrate remigrate or gradlew.bat migrate remigrate on the command line to execute them and commit the changes. You can also copy the diff from the build log and apply it with git apply as a patch. You need to strip the line numbers, though:

• Mac: pbpaste | sed 's/^.\{13\}//' | git apply
• Windows Powershell: Get-Clipboard | ForEach-Object { $_ -replace '^.{13}', '' } | git apply
• Linux solution 1: xclip -o | sed 's/^.\{13\}//' | git apply
• Linux solution 2: xsel --clipboard --output | sed 's/^.\{13\}//' | git apply

Please select the correct target branch for the PR. The master branch builds against the MPS master and is most likely not the branch you want to contribute to. After the PR is merged, a bot will automatically open a PR to merge the changes into the next maintenance branch. You don't have to do anything at the last step.

Contributing to the mbeddr.platform

To contribute your module to the mbeddr platform for reuse, you probably want to add it to the mps utils (com.mbeddr.mpsutils). After some incubation time, it may be considered to move it to the MPS-extensions, if the motivation and implementation have grown mature.

• name your language com.mbeddr.mpsutil.$yourLanguageName
• add it to the MPS project in code/languages/com.mbeddr.mpsutil inside a virtual folder $yourLanguageName
• all dedicated modules (like the ones you create below) should go into this virtual folder $yourLanguageName
• add a test solution with automated tests, named "test.com.mbeddr.mpsutil.$yourLanguageName" and make sure they pass
• If your module is an extension to an MPS language
  • add a language named com.mbeddr.mpsutil.$yourLanguageName.sandbox that demos how to use your language
  • add a com.mbeddr.mpsutil.$yourLanguageName.sandbox.sandbox solution that demonstrates the effect of what the sandbox language implemented
• Open the MPS project "code/languages/com.mbeddr.platform.build"
  • Open the build script named "com.mbeddr.platform"
  • Add a group named "group.$yourLanguageName"
  • Add a plugin that bundles your extension based on this group with the needed dependencies
  • Add your plugin to the default layout
  • Open the test build script at "platform/com.mbeddr.platform/com.mbeddr.platform.mpsutils.ts.tests.build" and add your tests
  • Add your test solution and its dependencies to the group "com.mbeddr.platform.tests"
  • Add it to the default layout
  • Add it to the test modules configuration
• Run the build locally with ./gradlew publishMbeddrPlatformPublicationToMavenLocal and check if your project works with it