Lisp for microcontrollers
Lisp for Arduino, Adafruit M0/M4, Micro:bit, ESP8266/32, RISC-V, and Teensy 4.x boards.
uLisp Version 4.3 - with built-in documentation
uLisp Version 4.3 now includes integral documentation for all the built-in functions, which you can display in the Arduino Serial Monitor or a terminal used with uLisp. You can also add documentation to the functions you define in uLisp, in the same format as the built-in documentation. The documentation for the built-in functions is stored in flash memory, and has no impact on the performance of uLisp. For more information see Built-in documentation.
In addition to the new documentation features, the AVR version of uLisp now includes the multi-dimensional array handling previously only included in the 32-bit versions of uLisp. A new AVR-Nano version, excluding these new features, continues to support the smallest AVR platforms: the Arduino Uno, Arduino Nano, and Arduino Nano Every.
uLisp® is a version of the Lisp programming language specifically designed to run on microcontrollers with a limited amount of RAM, from the Arduino Uno based on the ATmega328 up to the Teensy 4.0/4.1. You can use exactly the same uLisp program, irrespective of the platform. For the performance of each platform see Performance.
Because uLisp is an interpreter you can type commands in, and see the effect immediately, without having to compile and upload your program. This makes it an ideal environment for learning to program, or for setting up simple electronic devices.
Lisp is also an ideal language for learning about fundamental programming concepts. It incorporates string handling, list processing, and garbage collection, and so is also an excellent language for expressing complex ideas, such as teaching a robot to solve mazes or finding the shortest route on a map. As well as supporting a core set of Lisp functions uLisp includes Arduino extensions, making it ideal as a control language for the Arduino.
You can download the current version of uLisp free from the Download uLisp page.
RAM: At least 2 Kbytes.
Program memory: At least 32 Kbytes.
EEPROM, flash, or FRAM memory: If available, used for saving and loading the uLisp workspace.
The versions of uLisp for 8-bit and 16-bit platforms support integers between -32768 and 32767.
The AVR version of uLisp supports the following boards:
Arduino Uno and Nano or other ATmega328-based cards. These will give you enough memory for a simple uLisp application using short symbol names. All the Simple examples will run on the Arduino Uno.
Arduino Mega 2560 or other ATmega2560-based boards. These will give you enough memory for a fairly complex application; for examples see Animals, Tweetmaze, Route finder, and Infinite precision arithmetic.
ATmega1284. Although there isn't an official Arduino board based on it, the ATmega1284 is easy to wire up on a prototyping board, and provides a generous 16 Kbytes RAM.
ATmega4809 boards. The Arduino Nano Every and Microchip Curiosity Nano evaluation board are low-cost platforms based on the ATmega4809.
The versions of uLisp for 32-bit platforms support integers between 2147483647 and -2147483648, and 32-bit floating-point numbers.
The ARM version of uLisp supports the following boards:
Arduino M0 Boards. The Arduino Zero and Arduino MKRZero are based on the SAMD21 ARM Cortex-M0+ core and provide 256 Kbytes of flash and 32 Kbytes of RAM. They save images to the program flash. The Arduino MKRZero incorporates an SD-card socket which allows you to use an SD card for saving and loading uLisp images and files.
Adafruit M0 boards. The Adafruit Feather M0 Express, Adafruit Feather M0, Adafruit ItsyBitsy M0, Adafruit Gemma M0, and Adafruit QT-Py M0 are each based on the ATSAMD21 48 MHz ARM Cortex M0+ microcontroller. They have similar features and performance. The Adafruit Feather M0 Express uses the on-board DataFlash to save Lisp images; the other boards save images to the program flash.
Adafruit QT-Py and Seeduino XIAO. The Adafruit QT-Py M0 and Seeduino XIAO are each based on the ATSAMD21 48 MHz ARM Cortex M0+ microcontroller, with 256 Kbytes of flash and 32 Kbytes of RAM. They save images to the program flash.
Adafruit M4 boards. The Adafruit Metro M4 Grand Central, Adafruit Metro M4, Adafruit Feather M4, and Adafruit ItsyBitsy M4 are each based on the ATSAMD51 120 MHz ARM Cortex M4 microcontroller. They all include on-board DataFlash which is used to save Lisp images.
Adafruit PyGamer and PyBadge. The Adafruit PyGamer and PyBadge are handheld game platforms based on the ATSAMD51 120 MHz ARM Cortex M4 microcontroller and incorporating a 160x128 colour TFT display. They include on-board DataFlash which is used to save Lisp images.
Adafruit nRF52840 boards. The Adafruit CLUE and Adafruit ItsyBitsy nRF52840 are each based on the Nordic Semiconductor nRF52840 64 MHz ARM Cortex-M4 microcontroller, with 1 Mbyte of flash program memory and 256 Kbytes of RAM. They include on-board DataFlash which is used to save Lisp images.
BBC Micro:bit. The BBC Micro:bit is based on a Nordic Semiconductor nRF51822 ARM Cortex-M0 microcontroller. It runs at 16 MHz and provides 256 Kbytes of flash program memory and 16 Kbytes of RAM. The BBC Micro:bit V2 is based on a Nordic Semiconductor nRF52833 ARM Cortex-M4 microcontroller, running at 64 MHz, and provides 512 Kbytes of flash program memory, and 128 Kbytes of RAM. They don't support save-image.
Maxim MAX32620FTHR. This is based on a Maxim MAX32620 ARM Cortex-M4F microcontroller running at 96 MHz, with 2048 Kbytes of flash memory and 256 Kbytes of RAM. It doesn't support save-image.
Teensy 4.0 and 4.1. These are based on the NXP iMXRT1062 ARM M7 processor running at 600 MHz, and with 1 Mbytes of RAM.
RP2040 boards. These are based on the Raspberry Pi RP2040 microcontroller, which is a dual-core ARM Cortex M0+ running at 125 MHz which provides up to 16 MB of off-chip flash and 246 KB on-chip RAM.
The ESP8266/ESP32 version of uLisp supports the following boards:
ESP8266 boards. These boards are based on the 32-bit Tensilica Xtensa L106 microprocessor running at 80 MHz, with 4 Mbytes of flash and 80 Kbytes of RAM. They include integrated Wi-Fi.
ESP32 boards. These boards are based on the 32-bit Tensilica Xtensa LX6 microprocessor running at 160 or 240 MHz, with 4 Mbytes of flash and 520 Kbytes of RAM. They include integrated Wi-Fi and dual-mode Bluetooth.
The RISC-V version of uLisp supports the following boards:
Sipeed MAiX RISC-V boards. These boards are based on the Kendryte K210 RISC-V Dual Core 64 bit 400 MHz processor and provide 8 Mbytes RAM and 16 Mbytes flash. They are similar in performance.
For additional platforms supported by earlier versions of uLisp see: Older versions.
The language is generally a subset of Common Lisp, and uLisp programs should also run under Common Lisp. But note that there is one namespace for functions and variables; in other words, you cannot use the same name for a function and a variable.
All platforms provide lists, symbols, integers, characters, strings, streams, and arrays, including bit-arrays. In addition the 32-bit platforms provide floating-point numbers.
All platforms provide Arduino extensions for accessing ports, running timers, and serial I/O.
Some platforms provide additional Wi-Fi extensions, graphics extensions, and an assembler.
An integer is a sequence of digits, optionally prefixed with "+" or "-".
- On the 8/16-bit platforms integers can be between -32768 and 32767.
- On the 32-bit platforms integers can be between 2147483647 and -2147483648.
You can enter integers in hexadecimal, octal, or binary with the notations #x2A, #o52, or #b101010, all of which represent 42.
Symbols and strings
All platforms support long user-defined symbol names. Almost any sequence of characters that doesn't represent a number can be used as a symbol; so, for example, 12a and *2 are valid symbols.
Strings can consist of an arbitrary sequence of ASCII characters. Strings can be unlimited length, and are automatically garbage-collected.
uLisp includes a mark and sweep garbage collector. Garbage collection takes under 1 msec on an Arduino Uno or under 3 msec on an Arduino Mega 2560 (see Performance).
uLisp provides tail-call optimization, so applications written using recursive functions can be as efficient as using iteration.
Saving the workspace
On most platforms you can save the workspace, containing the functions and variables you have defined, using the save-image function, and then reload it with load-image. These functions take advantage of whatever non-volatile storage is available on each platform:
- On platforms with a DataFlash chip, such as Adafruit's ATSAMD21, ATSAMD51, and nRF52840 Express boards, you can save the entire workspace to DataFlash.
- On the AVR128DA48 and AVR128DB48, the Raspberry Pi Pico, and platforms based on the ATSAMD21 such as the Arduino Zero and Seeeduino XIAO, you can save the workspace to the flash program memory.
- On older AVR-based platforms, such as the Arduino Uno and Arduino Mega 2560, you can save the workspace to EEPROM.
- On the ESP8266 and ESP32 boards you can save the workspace to flash memory using the EEPROM emulation.
- On any platform you can add an SD-card interface, and then save the workspace to an SD card.
The following example illustrates how you might use uLisp.
After uploading uLisp to your microcontroller board you can communicate it via by typing or pasting commands into the Serial Monitor, or using a serial terminal. For more information see Using uLisp.
Suppose you have a red LED connected to the analogue output pin 9 on an Arduino Uno. Then you can type in the Lisp command:
(analogwrite 9 128)
to set the LED to 128, which corresponds to half brightness.
To save having to write this command every time you want to set the red LED you can define a function called red:
(defun red (x) (analogwrite 9 x))
Now you can achieve the same effect simply by writing:
In each case the LED changes immediately, as soon as you type in the command.
Suppose you've got a potentiometer connected to vary the voltage on the analogue input A0. You could define a function dim to make the potentiometer adjust the brightness of the LED with:
(defun dim () (loop (red (/ (analogread 0) 4)))
and run it by typing:
Finally, you could save the uLisp image to EEPROM, and specify that dim should be run on load, by entering:
When you reset the Arduino dim will now load and run automatically.
This is a simple example showing how uLisp allows you to build up complex programs from simpler components, testing each of the components as you go along.