Skip to content

alpsayin/mbed-simulator

 
 

Repository files navigation

Modded fork of the experimental simulator for Mbed OS 5.10 applications

Motivation

  • While some of the instructions from the original readme work, most of them don't anymore because of version mismatches and whatnot.
  • What's extra frustrating is that even the docker image doesn't work
    • I mean is anyone really surprised? That a docker image doesnt "just works out of the box"?
  • Not all the demos that are online exist in the original repository nor the originally original repository.
  • I need my Embedded Systems students to have an independent (of internet, arm server outages etc.) development environment.

What's new?

  • Has a stdin serial demo also thanks to @janjongboom
  • We almost made the MQTT demo work (but socket.recv function does not timeout so the program hangs).
  • Dockerfile fixed, local installation scripts for Ubuntu/Debian & Manjaro/Arch is included.
  • Readme below is modified to reflect updated/advised setup methods.

Documentation

TL;DR ?

  • Run setup-ubuntu.bash OR
  • Run setup-manjaro.bash OR
  • Run docker build . -t mbed-simulator && docker run -dp7829:7829 -it mbed-simulator

Video links

mbed and mbed Simulator Introduction

mbed and mbed Simulator Introduction

Hosting and Running mBed Simulator (api v5.10) on a VM

Hosting and Running mBed Simulator (api v5.10) on a VM

Original readme ensues ...

(whatever's left of it from my modifications...)

Experimental simulator for Mbed OS 5 applications

Demo: https://mbed-simulator.alpsayin.com

Demo (dark): https://mbed-simulator-dark.alpsayin.com

(I had to take them down because they expose potential security holes in my network, I'll start hosting them again if I can find a throwaway host)

Screenshot

While we have worked hard to improve embedded development tooling in Mbed (e.g. via the Online Compiler), the development for microcontrollers is still very similar to how it was in the 90s. Compilation is slow, and flashing is even slower. When fixing a bug, you need to get the device into the exact state as before encountering the bug. This makes for a very slow feedback loop, which hinders productivity and often pulls you out of the zone.

To make this feedback loop much shorter, we're releasing an alpha version of the Mbed Simulator. The simulator allows you to run your Mbed OS 5 applications directly on your computer, so that you can quickly test and verify applications without flashing them on a real board. This is a valuable learning tool, as you quickly learn how Mbed works. It is also very useful for developing complex applications. Within Arm, we have been using the simulator for work on mbed-http, the Mbed LoRaWAN stack and uTensor.

Note: The Mbed Simulator is part of Mbed Labs. The Mbed Labs projects showcase interesting side projects developed by Mbed engineers. However, these projects are not actively supported by Arm, and may be added, removed or break at any time.

More information in the introductionary blog post

Docs

Installation

Docker installation

  1. Install Docker
  2. Build the Docker image (run below command from inside repository folder):
    docker build . -t mbed-simulator
  3. Run the Docker image:
    docker run -dp7829:7829 -it mbed-simulator
  4. The simulator can now be accessed at:
    http://localhost:7829

Local installation

Note that setup scripts will download all dependencies (including Mbed OS) and will build the common libmbed library so this'll take some time. I highly advise to give the scripts a quick skim before running;

  • They'll call sudo,
  • They'll install nvm, npm and emsdk environments. While this is great for a student with a fresh VM, may be disastrous if you've a finely aged development environment (but then you should also know better than running arbitrary scripts from internet :)).

Arch Linux (Manjaro advised for students)

  1. Run the setup script and follow the prompts.

    $ ./setup-manjaro.bash
    
  2. Run the simulator (this will activate some environment variables):

    $ ./start_mbed_simulator.bash
    

Debian (Ubuntu advised for students)

  1. Run the setup script and follow the prompts.

    $ ./setup-ubuntu.bash
    
  2. Run the simulator (this will activate some environment variables):

    $ ./start_mbed_simulator.bash
    

Windows

  1. Use the docker image with:
    1. Docker Desktop for Windows (easiest)
    2. Docker daemon running inside WSL2 instance provided by Windows Subsystem for Linux
  2. Or follow the above instructions inside
    1. An ubuntu instance provided by Multipass by Canonical (easiest)
    2. WSL instance provided by Windows Subsystem for Linux (WSL) and follow the commands inside (untested)
    3. Or any other Virtualisation choice (e.g. Virtualbox)

MacOS

Get a real computer or use the docker image?

p.s. this is still unlikely to work properly in M1 macs. You really need to get a proper development computer, not an overglorified smartphone.

After local installation

You must either port forward 7829 from your instance to your host machine, or your guest machine's 7829 must be accesible.

  1. If it's the former; open http://localhost:7829 in your browser.
  2. If it's the latter; open http://<ip.address.of.guest>:7829 in your browser
  3. If it's the latter; alternatively, open http://[guest-hostname].local:7829 in your browser
  4. Blinky runs!

CLI

The simulator comes with a CLI to run any Mbed OS 5 project under the simulator.

Running

To run an Mbed OS 5 project:

mbed-simulator .

The project will build and a web browser window will open for you.

To see if your program runs in the simulator, check the TARGET_SIMULATOR macro.

Running in headless mode

You can also run the simulator in headless mode, which is great for automated testing. All output (through printf and traces) will be routed to your terminal. To run in headless mode, add the --launch-headless option. You might also want to limit the amount of logging the server does through --disable-runtime-logs to keep the output clean.

Changing mbed-simulator-hal

After changing anything in the simulator HAL, you need to recompile the libmbed library:

  1. Run:

    rm mbed-simulator-hal/libmbed.bc
  2. Rebuild your application. libmbed will automatically be generated.

Updating demos

In the out folder a number of pre-built demos are listed. To upgrade them:

npm run build-demos

Troubleshooting

No WebAssembly support found. Build with -s WASM=0 to target JavaScript instead. This error is thrown in new Microsoft Edge browser when you enable "Enhance your security on the web". You need to add an exception for your guest vm/docker etc. address. Firefox has not caused this issue so far.

The connection for this site is not secure This error is thrown when you try to access the simulator guest via its bonjour/avahi/mdns hostname. Most of the modern browsers don't like when you try to establish an unsecured HTTP connection to a hostnamed address so they try to upgrade connection. This does not occur if you use IP addresses. Sometimes they will ask if you'd like to proceed, sometimes they won't allow you to proceed at all. It's clear that disallowing plain HTTP connections will be the norm, so easiest way around is to find the ip address of the guest and use it. A trick is to ping the hostname and grab its IP by response as shown below.

PS C:\Users\alpsa> ping -4 mbedsimulator.local

Pinging mbedsimulator.local [192.168.111.6] with 32 bytes of data:
Reply from 192.168.111.6: bytes=32 time<1ms TTL=64
Reply from 192.168.111.6: bytes=32 time<1ms TTL=64
...

Pointer_stringify Issues This error is thrown when you use too high an emscripten version. According to release notes 1.38.27 version of Emscripten aborts by default when Pointer_stringify is called. I tried 1.38.26 which didn't quite compile. So I decided to use 1.38.21 as per the original docs. Further reading below:

Windows: [Error 87] The parameter is incorrect

This error is thrown on Windows systems when the path length limit is hit. Move the mbed-simulator folder to a folder closer to root (e.g. C:\mbed-simulator).

Attribution

Releases

No releases published

Packages

 
 
 

Languages

  • C 76.7%
  • JavaScript 11.2%
  • C++ 10.7%
  • CSS 0.6%
  • HTML 0.6%
  • Shell 0.1%
  • Dockerfile 0.1%