Skip to content

An interpreter for a concurrent lisp-like language with message-passing and pattern-matching implemented in C.

License

Notifications You must be signed in to change notification settings

svenssonjoel/lispBM

Repository files navigation

lispBM (LBM)

LispBM is a lisp or scheme like programming language for microcontrollers. LispBM also borrows a couple of ideas from Erlang when it comes to concurrency, message passing, pattern matching and process monitoring. The LispBM runtime system can be compiled for either 32 or 64 bit platforms and runs on a wide range of hardware such as for example STM32, NRF52, ESP32 or X86. When running the LispBM runtime system on a microcontroller it can be built on top of ChibiOS, FreeRTOS or ZephyrOS or, if you are adventurous, on bare-metal. LispBM can also be built to run on top of a regular linux.

LispBM mascot

The LispBM mascot, Lispy the llama, was created by PixiLadyArt. Thank you, Pixi!

Want to get involved and help out?

There are lots of interesting things to code on in and around the LispBM runtime system. I would love to interact with people who are interested in high-level programming languages on microcontrollers (or elsewhere) so please do not be shy to make contact. Together we can make great stuff happen ;)

  1. Are you interested in microcontrollers and programming languages?
  2. You find it fun to mess around in C code with close to zero comments?
  3. Then join in the fun. Lots to do, so little time!
  4. Poke me by mail bo(dot)joel(dot)svensson(whirly-a)gmail(dot)com.

There are areas where insights and help would matter greatly. Some I can think of are:

  1. Running LispBM on system simulators.
  2. LispBM efficiency, compilation, byte-code and real time garbage collection.
  3. Code size optimisation. Do more with less, while maintaining performance.
  4. Documentation and testing.
  5. Useful extension libraries.
  6. Lisp scriptable home automation.
  7. Lisp scriptable MIDI sequencers.
  8. Lisp scriptable Audio synthesizers.
  9. ...

Getting started

The easiest way to get started with LispBM programming is to use VESC-Tool together with the VESC EXPRESS Firmware on an esp32c3.

VESC-Tool gives you access to a very capable IDE for lisp programming on embedded systems and the VESC Express firmware provides built in functionality to interface with CAN, WIFI, BLE and UART as well as GPIO and display drivers.

If you are looking for a more bare-bones way to add scripting capabilities to your embedded system, LispBM is quite platform independent and can be compiled for many different MCUs and systems. LispBM can tie into the rest of your application via what we call "extensions" which are C functions that can be called from your LispBM scripts.

Documentation

The LBM REPL

There is an example REPL implementation that runs on X86 32 or 64bit in the repl directory. The REPL depends on libreadline.

REPL Dependencies for 32Bit executable on 64Bit linux:

  • libreadline
  • lib32readline
  • gcc-multilib
  • libpng

On Ubunty you can obtain the depencies by:

sudo apt-get install gcc-multilib libreadline-dev lib32readline-dev libpng-dev libpng-dev:i386

Then issue command make in the repl directory.

There is also a Nix flake (see details below). You can build and run the repl using nix run. This will build the 32 bit version. For the 64 bit repl you instead run nix run .#repl64.

Editor support

Development

There is a Nix flake to help you build the repl and documentation. It outputs packages for the 32 and 64 bit repl: repl and repl64, the documentation: doc, and the doxygen source code documentation: c-doc. Assuming you have Nix installed, you can build these using

nix build .#<package>

The generated output is then placed in the result/ directory. However doc and c-doc packages might not make much sense to build in this way because they are supposed to generate files inside the repository tree. Therefore, it makes more sense to instead enter their respective development environment with nix develop .#<package>. This places you in a new shell with the required dependencies installed where you can build them with make.