Lisp for the Arduino and MSP430
Version 2.1 released
uLisp Version 2.1 reduces the amount of workspace memory used by programs by about 25%. More of the example programs can now be run on an Arduino Uno.
Version 2.1 also adds a sleep function, which puts the processor into low-power mode for a specified time. So you can now create battery-powered applications in uLisp such as a data logger that reads a sensor once a minute.
uLisp® is a version of the Lisp programming language specifically designed to run on processors with a limited amount of RAM. It currently supports the ATmega-based Arduino boards, SAM/SAMD-based Arduino boards, and MSP430-based LaunchPad boards. You can use exactly the same uLisp program, irrespective of the platform.
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 a rich language, with many advanced features that make it easier to program in than C or C++, so it's ideal for learning about fundamental programming concepts. It's also an ideal 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 (the program currently uses about 29 Kbytes of program memory on the Arduino and 31 Kbytes on the MSP430).
EEPROM, flash, or FRAM memory: Used for saving and loading the uLisp workspace.
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.
Arduino Due. This board is based on the AT91SAM3X8E ARM Cortex-M3 core and provides 512 Kbytes of flash, 96 Kbytes of RAM, and an 84 MHz clock. It's currently the fastest uLisp platform.
Arduino Zero. This board is based on the SAMD21 ARM Cortex-M0+ core and provides 256 Kbytes of flash and 32 Kbytes of RAM.
Arduino MKRZero. This is similar to the Arduino Zero, based on the SAMD21 ARM Cortex-M0+ core and with 256 Kbytes of flash and 32 Kbytes of RAM. It incorporates an SD-card socket, allowing you to use an SD card for saving and loading uLisp images.
MSP430 F5529 LaunchPad. This uses the flash memory for saving images, and provides enough memory for a fairly complex application; for examples see Animals, Tweetmaze, Route finder, and Infinite precision arithmetic.
MSP430 FR5969 LaunchPad. This version uses the FRAM for the workspace, and for saving images, giving a generous amount of memory.
The following table gives a summary of the different versions:
|Platform||Processor||Long symbols||Cells||Image||GC time||Benchmark|
|Arduino Uno, Arduino Nano||ATmega328||No||317||254||1 msecs||72 secs|
|Arduino Mega 2560||ATmega2560||Yes||1216||893||2.1 msecs||54 secs|
|Tiny Lisp Computer||ATmega1284||Yes||2816||893||5.3 msecs||60 secs|
|Arduino Due||SAM3X8E||Yes||10240||*||4.5 msecs||7 secs|
|Arduino Zero||SAMD21||Yes||3072||*||1.2 msecs||12 secs|
|Arduino MKRZero||SAMD21||Yes||3072||*||1.2 msecs||15 secs|
|MSP430 F5529 LaunchPad||MSP430F5529||Yes||1280||1280||8.2 msecs||30 secs|
|MSP430 FR5969 LaunchPad||MSP430FR5969||Yes||3328||1664||14.4 msecs||60 secs|
Cells gives the number of Lisp cells of storage available, equivalent to 4 bytes (8 bytes on the SAM/SAMD platforms).
Image gives the number of cells that can be saved to non-volatile storage using save-image.
* On the Arduino Due, Zero, and MKRZero you can save images to an SD card.
GC time gives the time taken for a garbage collection.
Benchmark gives the time taken to run the tak benchmark; see Benchmarks.
I don't currently recommend the ATmega32U4-based boards as there is an unresolved problem interfacing uLisp via the serial interface with these boards.
The language is generally a subset of Common Lisp, and uLisp programs should also run under Common Lisp.
Types supported: list, symbol, integer, character, string, and stream.
An integer is a sequence of digits, optionally prefixed with "+" or "-". Integers can be between -32768 and 32767 (or between 2147483647 to -2147483648 on the SAM/SAMD platforms). You can enter numbers in hexadecimal, octal, or binary with the notations #x2A, #o52, or #b101010, all of which represent 42.
On platforms with more than 2 Kbytes of RAM arbitrary user-defined symbol names are supported. Any sequence that isn't an integer can be used as a symbol; so, for example, 12a is a valid symbol. On platforms with only 2 Kbytes symbol names can have up to three characters consisting of a-z and 0-9.
There is one namespace for functions and variables; in other words, you cannot use the same name for a function and a variable. uLisp provides tail-call optimization, so applications written using recursive functions can be as efficient as using iteration.
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 above table).
The following example illustrates how you might use uLisp.
After uploading uLisp to your Arduino board or ATmega chip you communicate it via the Serial Monitor. 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.