The most powerful environmentally-friendly computing hardware that can run independently of grid power and data. An advanced polyForth development board where programming machine intelligence and other autonomous applications leverages the extreme low-power (1.8 VDC) compute of 16MB (1-bit precision) SPI and 128MB SRAM with 144-asynchronous nodes configured in HOST and TARGET chips where much of their I/O are connected as header-pins.



Introducing Volatco
The first widely-available multicomputer and multiprogrammer for machine-intelligent ideal applications in a compact 6 cm x 4 cm x 1.5 cm form-factor.
What is a Volatco?
A machine-intelligent capable off-power board that provides compute to explore embodied AI, neuromorphic experimentation, and ultra‑low‑energy inference, with robust hardware that is massively parallel, energy‑frugal, and easily extensible with certified plug-ins.
The Volatco multicomputer packs two GA144A12 mesh‑processor chips, 16 MB of SRAM, 16 MB of SPI flash, and a flexible off‑board I/O architecture into a board smaller than a credit card that draws only milliwatts of power when idle.
Plug-ins: Dedicated power, Ethernet, and Bluetooth.
polyForth: On-board operating system that is lightweight, dual-stack operating system and programming environment.
Key Features
| Feature | Benefit |
|---|---|
| Dual GA144A12 Cores (144 × 2 = 288 cores) | Run 288 concurrent threads -ideal for parallel algorithms, machine-intelligence, and evolutionary computing. |
| polyForth® Runtime | A lightweight, stack‑based language that lets you prototype, debug, and iterate on AI kernels in minutes-no heavyweight SDKs required. |
| 16 MB SRAM + 16 MB SPI Flash | Fast volatile memory for model parameters and large non‑volatile storage for firmware, datasets, and compiled Forth programs. |
| Zero On‑Board Regulation | Power is supplied externally, eliminating regulator quiescent draw and shrinking the PCB. Choose the most efficient supply for your experiment. |
| Rich Off‑Board I/O | All GPIO, analogue‑in/out, and power pins are exposed on a standard breadboard‑compatible header. Plug in sensors, actuators, or custom expansion boards without soldering. |
| Watchdog & Reset Circuitry | Automatic recovery from software hangs, essential for long‑running experiments. |
| Modular Expansion Row | Connect external power modules, additional memory, Bluetooth, Ethernet, or bespoke I/O boards via header rows. |
| Compact Form Factor | Designed to fit into tight enclosures, drone payload bays, or multi‑board racks for scalable clusters. |
The information below pertains to the technical details of a Volatco.
The Volatco pin-set
All connections are made on the top of the PCB. The model ‘c’ dialect has pins out both the top and bottom of the board.

Option Jumpers
J6is “No boot”. Insert to preventchip 0from booting SPI flash on reset.J5selects development mode (pins 1 and 2 jumpered) or production (pins 2 and 3). In the latter case the watchdog/reset circuit is enabled. Development mode is required whenever “No boot” is installed.J4is shorted to produce a manual reset. This may also be done by the system providing IDE service throughJ8. Either of these reset methods works in either development or production mode.
Connection Headers
J1is external power and ground input.J8is for serial IDE input (including reset).J7is for polyFORTH terminal input - including watchdog signal, normally supplied from on the board. BothJ7andJ8carry both ground andV1P8for devices such as FTDI chips that can accept our supply to power their I/O pins.J9andJ10are signals from chip 0 plus two pins from chip 1.J11,J12, andJ13all carry signals fromchip 1. Each of these 12-pin headers carries 9 signals and 3 grounds, for a total of 45 signals. See following table for the pinout description.
Power control
| External 1V8 input | J1 | |||
|---|---|---|---|---|
| GND | 1 | 2 | V1P8 | |
| GND | 3 | 4 | V1P8 |
Note that the ground pins are those nearest the PCB edge.
| Chip 0 (Host) shunts | J2 | |||
|---|---|---|---|---|
| V1P8 | 1 | 2 | VC0-Core | |
| V1P8 | 3 | 4 | VC0-I/O |
Jumpers are shown for normal operation. Substitute a shunt resistor to measure voltage drop across the resistor and calculate current. Be sure to use a small enough value that the expected current will not cause a voltage drop setting the supply below specs for the chip (typically 1.62V).
| Chip 1 (Target) shunts | J3 | |||
|---|---|---|---|---|
| VC1-Core | 1 | 2 | V1P8 | |
| VC1-I/O | 3 | 4 | V1P8 |
Note that unlike J2 the incoming supply is on the right side of this jumper block. The polarity of the drop will be reversed accordingly.
Manual reset
| J4 | |
|---|---|
| 1 | Manual reset |
| 2 | GND |
Short these pins together to assert reset on chip 0. Works in whether or not watchdog is enabled.
Operating modes
| Watchdog enable | J5 | |
|---|---|---|
| 1 | Manual/external | |
| 2 | Host chip RST | |
| 3 | Watchdog chip |
The manual/external reset always goes to the reset input of the watchdog chip. This jumper selects which signal goes to chip 0: The manual/external reset signal, or the output of the watchdog. Normal field production mode, enabling watchdog, is shown as the default. The watchdog should be disabled by moving the jumper to pins 1 and 2, when not running the production code on the chips.
No boot
| J6 | |
|---|---|
| 1 | Host 705.17 |
| 2 | 1k pullup to 1v8 |
Install this jumper to prevent program booting from the SPI flash. When this is installed, the watchdog must be disabled by connecting pins 1 and 2 of J5.
Programmer access
| polyForth serial terminal | J7 | |||
|---|---|---|---|---|
| GND | 1 | 2 | V1P8 | |
| Output from chip | 3 | 4 | Input to chip | |
| GND | 5 | 5 | Input to watchdog |
This serial port supports an asynchronous serial terminal for polyFORTH running on chip 0. Pin 6 must be jumpered or wire wrapped to a pin generating watchdog pulses before the watchdog may be enabled.
| IDE serial | J8 | |||
|---|---|---|---|---|
| GND | 1 | 2 | V1P8 | |
| Output from chip | 3 | 4 | Input to chip | |
| GND | 5 | 5 | RESET |
This serial port is used to talk to nodes on one or both chips directly using the Interactive Development Environment via node 708 of chip 0. Its reset pin is effective in both operating modes. Once the SPI flash has been initialized with boot code, this port is not necessary to run polyFORTH.
Signal access
| Chip 0 part 1 | ||||
|---|---|---|---|---|
| J9 | ||||
| GND | 1 | 2 | 117.ai | |
| 117.a0 | 3 | 4 | 217.17 | |
| GND | 5 | 6 | 317.17 | |
| 617.ao | 7 | 8 | 617.ai | |
| GND | 9 | 10 | 517.17 | |
| 417.17 | 11 | 12 | 717.ai |
| Chip 0 part 2 and two pins for chip 1 | ||||
|---|---|---|---|---|
| J10 | ||||
| GND | 1 | 2 | 717.ao | |
| 715.17 | 3 | 4 | 713.ao | |
| GND | 5 | 6 | 713.ai | |
| 709.ai | 7 | 8 | 709.ao | |
| GND | 9 | 10 | 600.17 | |
| 10100.17 | 11 | 12 | 10200.17 |
| Chip 1 part 1 | ||||
|---|---|---|---|---|
| J11 | ||||
| GND | 1 | 2 | 10600.17 | |
| 10500.17 | 3 | 4 | 10008.17 | |
| GND | 5 | 6 | 10008.5 | |
| 10008.3 | 7 | 8 | 10008.1 | |
| GND | 9 | 10 | 10117.ai | |
| 10117.ao | 11 | 12 | 10217.17 |
| Chip 1 part 2 | ||||
|---|---|---|---|---|
| J12 | ||||
| GND | 1 | 2 | 10317.17 | |
| 10517.17 | 3 | 4 | 10417.17 | |
| GND | 5 | 6 | 10617.ai | |
| 10717.ai | 7 | 8 | 10617.ao | |
| GND | 9 | 10 | 10717.ao | |
| 10113.ao | 11 | 12 | 10715.17 |
| Chip 1 part 3 | ||||
|---|---|---|---|---|
| J13 | ||||
| GND | 1 | 2 | 10713.ai | |
| 10709.ao | 3 | 4 | 10709.ai | |
| GND | 5 | 6 | 10708.17 - Boot receive | |
| 10705.1 | 7 | 8 | 10708.1 | |
| GND | 9 | 10 | 10705.3 | |
| 10705.5 | 11 | 12 | 10715.17 - Pulled-up |
Be aware that pin 9 10708.17 is input to a boot node. If pin is being driven high by another device when chip 1 is reset, node 10708 will delay for a long time during boot which may cause problems with watchdog. If being used as an output and driven high on reset, the RC time constant of load capacitance and weak pull down resistance may be long enough to delay booting. The same is true of 10705.17 if being used as an input and driven low by another device during reset.