neo430 by zerogravity

A very small msp430-compatible customizable soft-core microcontroller-like processor system written in platform-independent VHDL.

# The NEO430 Processor

[![Build Status](](

[![GitHub release](](

[![last commit](](




## Table of Content

* [Introduction](#Introduction)

* [Processor Features](#Processor-Features)

* [Differences to the Original MSP430 Processors](#Differences-to-the-Original-MSP430-Processors)

* [Implementation Results](#Implementation-Results)

* [Performance](#Performance)

* [Quick Start](#Quick-Start)

* [Change Log](#Change-Log)

* [Contact](#Contact)

* [Disclaimer, Proprietary and Legal Notice](#Disclaimer-Proprietary-and-Legal-Notice)

## Introduction

Welcome to __[The NEO430 Processor]( project!

You need a small but still powerful, customizable and microcontroller-like processor system for your next FPGA project?

Then the NEO430 is the right choice for you.

This processor is based on the Texas Instruments MSP430(TM) ISA and provides compatibility with the original

instruction set (see differences below). The NEO430 is not an exact MSP430 clone – it is more like a complete new implementation from the bottom up. The

processor features a very small outline, already implementing standard features like a timer, a watchdog, UART, TWI and SPI

serial interfaces, general purpose IO ports, an internal bootloader and of course internal memory for program code and data.

All of the implemented peripheral modules are optional – so if you do not need them, you can exclude them from synthesis to

reduce the size of the system. Any additional modules, which make a more customized system, can be connected via a

Wishbone-compatible bus interface or directly implemented within the processor. By this, you can built a system,

that perfectly fits your needs.

It is up to you to use the NEO430 as stand-alone, configurable and extensible microcontroller, or to use it as controller

within a more complex SoC design.

The high-level software development is based on the free TI msp430-gcc compiler tool chain. You can either use Windows

(PowerShell or Linux Subsystem) or Linux as build environment for your applications – the project supports both worlds.

This project is intended to work "out of the box". Just synthesize the test setup from this project, upload it to your

FPGA board of choice (the NEO430 uses a FPGA vendor-independent VHDL description) and start exploring the capabilities of

the NEO430 processor. Application program generation works by executing a single "make" command. Jump to the

"Let’s Get It Started" chapter in the NEO430 documentary, which provides a lot of guides and tutorials to make your first

NEO430 setup run: [![NEO430 Datasheet]( NEO430 Datasheet]( "NEO430 Datasheet from GitHub")

## Processor Features

![NEO430 Overview](

(optional modules are marked using dashed lines in the figure above)

- 16-bit open source soft-core microcontroller-like processor system

- Full support of the original [MSP430 instruction set architecture](

- Code-efficient CISC-like instruction capabilities

- Tool chain based on free [TI msp430-gcc compiler]( "TI `msp430-gcc` compiler")

- Application compilation scripts ([makefiles]( for Windows Powershell / Windows Subsystem for Linux / native Linux

- Software requirements (regardless of platform):

  - TI `msp430-gcc` compiler

  - native `GCC` compiler

  - `GNU Make`

- Completely described in behavioral, platform-independent VHDL (no macros, primitives, attributes, etc. used)

- Fully synchronous design, no latches, no gated clocks

- Very low resource requirements and high operating frequency

- Internal [DMEM]( (RAM, for data) and [IMEM]( (RAM or ROM, for code), configurable sizes

- Customizable processor hardware configuration:

  - Optional multiplier/divider unit ([MULDIV](

  - Optional high-precision timer ([TIMER](

  - Optional universal asynchronous receiver and transmitter ([UART](

  - Optional serial peripheral interface ([SPI](, 8 or 16 bit tansfer data size, 6 dedicated CS lines

  - Optional I2C-compatible two wire serial interface ([TWI]( supporting clock stretching

  - Optional general purpose parallel IO port ([GPIO](, 16 inputs & 16 outputs, with pin-change interrupt and PWM option

  - Optional 32-bit Wishbone bus interface adapter ([WB32]( - including bridges to [Avalon (TM]( bus and [AXI4-Lite (TM](

  - Optional watchdog timer ([WDT](

  - Optional cyclic redundancy check unit ([CRC16/32](

  - Optional custom functions unit ([CFU]( for user-defined processor extensions

  - Optional 4 channel PWM controller with 4 or 8 bit resolution ([PWM](

  - Optional Galois Ring Oscillator (GARO) based true random number generator ([TRNG]( with de-biasing and internal post-processing

  - Optional external interrupts controller with 8 independent channels ([EXIRQ](, can also be used for software-triggered interrupts (traps, breakpoints, etc.)

  - Optional internal [bootloader]( (2kB ROM) with serial user console and automatic boot from external SPI flash (like the FPGA configuration storage)

## Differences to the Original MSP430 Processors

- Completely different processor modules with different functionality

- Up to 48kB instruction memory and 12kB data memory

- NEO430 tool chain (makefiles, boot-code and linker script) required for application compilation

- Custom binary executable format

- No hardware debugging interface

- No analog components

- No support of TI's Code Composer Studio

- No support of CPU's DADD instruction (which is never used by the compiler...)

- Just 4 CPU interrupt channels

- Single clock domain for complete processor

- Different numbers of instruction execution cycles

- Only one power-down (sleep) mode

- Wishbone-compatible interface to attach custom IP

- Internal bootloader with text interface (via UART serial port)

- Extended ALU functions (if enabled)

## Implementation Results

Mapping results generated for HW version 0x0320. The full (default) hardware configuration includes

all optional processor modules (excluding the CFU and the TRNG), an IMEM size of 4kB and a DMEM

size of 2kB. The minimal configuration only includes the CPU and the GPIO module. Results generated with Xilinx Vivado 2017.3,

Intel Quartus Prime Lite 17.1 and Lattice Radiant 1.1 (Synplify)

| __Xilinx Artix-7 (XC7A35TICSG324-1L)__  | LUTs       | FFs         | BRAMs    | DSPs   | f_max*  |


| Full (default) configuration:           | 983 (4.7%) | 1014 (2.5%) | 2.5 (5%) | 0 (0%) | 100 MHz |

| Minimal configuration (CPU + GPIO):     | 685 (3.3%) | 290 (0.7%)  | 1 (2%)   | 0 (0%) | 100 MHz |

| __Intel Cyclone IV (EP4CE22F17C6)__  | LUTs      | FFs      | Memory bits | DSPs   | f_max   |


| Full (default) configuration:        | 1648 (7%) | 990 (4%) | 65800 (11%) | 0 (0%) | 122 MHz |

| Minimal configuration (CPU + GPIO):  | 596 (3%)  | 233 (1%) | 49408 (8%)  | 0 (0%) | 126 MHz |

| __Lattice iCE40 UltraPlus (iCE40UP5K-SG48I)__  | LUTs       | FFs        | EBRs     | DSPs   | SRAMs  | f_max* |


| Full (default) configuration:                  | 2600 (49%) | 1152 (21%) | 16 (53%) | 0 (0%) | 0 (0%) | 20 MHz |

| Minimal configuration (CPU + GPIO):            | 1365 (25%) | 493 (9%)   | 12 (40%) | 0 (0%) | 0 (0%) | 20 MHz |

*) Constrained

### Device Utilization by Entity

The following table shows the required resources for each module of the NEO430 processor system. Note that the provided

numbers only represent a coarse overview as logic elements might be merged and optimized beyond module boundaries.

Mapping results generated for HW version 0x0320. The full (default) hardware configuration includes all optional

processor modules (excluding the CFU but including the TRNG), an IMEM size of 4kB and a DMEM size of

2kB. Results were generated using Intel Quartus Prime Lite 17.1.

| __Intel Cyclone IV (EP4CE22F17C6)__    | LUTs | FFs | Memory Bits | DSPs |


| Bootloader Memory (Boot ROM, 2kB)      | 2    | 1   | 16384       | 0    |

| Central Processing Unit (CPU)          | 506  | 171 | 256         | 0    |

| Checksum Unit (CRC)                    | 110  | 94  | 0           | 0    |

| Custom Functions Unit (CFU)*           | -    | -   | -           | -    |

| Data Memory (DMEM, 2kB)                | 6    | 1   | 16384       | 0    |

| External Interrupts Controller (EXIRQ) | 72   | 54  | 0           | 0    |

| High-Precision Timer (TIMER)           | 70   | 55  | 0           | 0    |

| Instruction Memory (IMEM, 4kB)         | 4    | 1   | 32768       | 0    |

| IO Port Unit (GPIO)                    | 49   | 45  | 0           | 0    |

| Multiplier & Divider (MULDIV)          | 184  | 131 | 0           | 0    |

| Pulse-Width Modulation Unit (PWM)      | 80   | 66  | 0           | 0    |

| Serial Peripheral Interface (SPI)      | 57   | 43  | 0           | 0    |

| System Info Memory (SYSCONFIG)         | 15   | 13  | 0           | 0    |

| True Random Number Generator (TRNG)    | 44   | 36  | 0           | 0    |

| Two Wire Interface (TWI)               | 80   | 41  | 0           | 0    |

| Universal Asynchronous Rx/Tx (UART)    | 129  | 89  | 0           | 0    |

| Watchdog TImer (WDT)                   | 49   | 36  | 0           | 0    |

| Wishbone Interface (WB32)              | 128  | 117 | 0           | 0    |

*) Hardware requirements defined by user application

## Performance

In contrast to most mainstream processors the NEO430 processor does not implement a pipelined instruction execution. Instead,

a **multi-cycle instruction execution scheme** is used: Each single instruction is executed in a series of micro instructions

requiring several clock cycles to complete. The main benefit of this execution style is the highly reduced logic overhead as no

complex pipeline hazard detection and resolving logic is required making the NEO430 even sammler - at the cost of a reduced IPC

(instructions per cycle). Also, the MSP430 ISA is not really compatible to the classic (e.g., DLX/MIPS) pipeline scheme due to

its complex operand and adressing modes (e.g., ALU operations executing directly on memory data). However, this concept allows

the processor to use very **dense and powerfull CISC-like operations**.

Furthermore, the multi-cycle architecture features a **very short crtitical path** when compared to other (even 32-bit)

processors. Thus, the NEO430 can operate at very high frequencies even on low-cost (e.g., +120MHz on an Intel Cyclone 4)

and low-power FPGAs (e.g., +20MHz on a Lattice iCE40 UltraPlus).

Depending on the format of the instruction, the actual execution can take 3 to 11 clock cycles. If all possible instruction

types and formates are executed in an eually distributed manner (worse case), the average CPI (clock cycles per instruction)

evaluates to ~8 cycles/instruction resulting in **0.125 instructions per Hertz** of the operating frequency. However, this mix

is quite unrealistic, so the real average CPI will be somewhere below 8 cycles/instruction.

### Coremark Benchmark

The [coremark CPU benchmark]( was executed on the NEO430 and is available in the

project's [sw/example/coremark]( folder This benchmark

tests the capabilities of the CPU itself rather than the functions provided by the whole system / SoC.


Hardware: 100 MHz, 16kB IMEM, 8kB DMEM, HW verison 0x0322, no peripherals used (except for the TIMER and the UART)

Software: Optimization level -Os, msp430-gcc 8.3.0 for Linux, MEM_METHOD is MEM_STACK, 2000 coremark iterations


| __Coremark Score__ | __Relative Score__    |


| 6.38               | 0.064 Coremarks/MHz   |

Even though a score of 6.38 can outnumber certain architectures and configurations (see the score table on the coremark

homepage), the relative score of 0.064 coremarks per second might pretty low. But you have to keep in mind that benchmark

was executed using only the resources of the CPU itself. The CPU consists of only ~500 Intel Cyclone IV LUTs and does not

contain any sophisticated ALU operations like multiplication or barrel shifting. Also, all instructions are executed in a

multi-cycle scheme requiring several clock cycles to complete. When explicitly using the NEO430 MULDIV unit for performing

the matrix-operations benchmark scenario (among other operations, it is based on matrix-scalar, matrix-vector and

matrix-matrix multiplications) the **coremark score is increased to 12.56**. By using additional HW accelerators from the

NEO430 ecosystem (like the CRC unit) or by using the MULDIV unit also for address and index computations the performance

and thus, the coremark score can be further increased

## Quick Start

 * At first, get the most recent version the NEO430 Processor project from GitHub:


   * Clone the NEO430 repository using `git` from the command line (suggested for easy project updates via `git pull`):



     git clone


   * Or download the current version of this project as ZIP file: [](

 * Next, install the free `MSP430-GCC` compiler toolchain from the TI homepage (select the "compiler only" package according to your system OS):

 * Make sure `GNU Make` and a native `GCC` compiler are installed (double check for the newest versions)

 * Follow the instructions from the "Let's Get It Started" section of the NEO430 documentary: [![NEO430 Datasheet]( NEO430 Datasheet]( "NEO430 Datasheet from GitHub")

 * This documentary will guide you to create a simple test setup, which serves as ["hello word" FPGA demo](

![NEO430 Test Example Setup](

 * The NEO430 project also includes some example programs from which you can start your own application: [SW example projects](

 * Have fun! =)

## Change Log

The official change log of this project can be found at the end of the [![NEO430 Datasheet]( NEO430 Datasheet]( "NEO430 Datasheet from GitHub").

## Contact

If you have any questions, bug reports, ideas or if you are facing problems with the NEO430, open a

[new issue]( or directly drop me a line. Also, I'm always happy to

hear what cool projects people are realizing with this core :smiley:

## Citation

If you are using the NEO430 for some kind of publication, please cite it as follows:

> S. Nolting, "The NEO430 Processor",

## Disclaimer, Proprietary and Legal Notice

This is a hobby project released under the BSD 3-Clause license. No copyright infringement intended.

**BSD 3-Clause License**

Copyright (c) 2020, Stephan Nolting. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are

permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of

conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of

conditions and the following disclaimer in the documentation and/or other materials

provided with the distribution.

3. Neither the name of the copyright holder nor the names of its contributors may be used to

endorse or promote products derived from this software without specific prior written











"MSP430" and "Code Composer Studio" are trademarks of Texas Instruments Corporation.

"Windows" is a trademark of Microsoft Corporation.

"Virtex", "Artix" and "Vivado" are trademarks of Xilinx Inc.

"Cyclone", "Quartus" and "Avalon Bus" are trademarks of Intel Corporation.

"iCE40 UltraPlus", "Lattice Radiant" and "Lattice Diamond" are trademarks of Lattice Semiconductor Corporation.

"AXI", "AXI4" and "AXI4-Lite" are trademarks of Arm Holdings plc.

![Open Source Hardware Logo](

This project is not affiliated with or endorsed by the Open Source Initiative ( /

Made with :beer: in Hannover, Germany.

                       Version 3, 29 June 2007

 Copyright (C) 2007 Free Software Foundation, Inc. <>
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

  This version of the GNU Lesser General Public License incorporates
the terms and conditions of version 3 of the GNU General Public
License, supplemented by the additional permissions listed below.

  0. Additional Definitions.

  As used herein, "this License" refers to version 3 of the GNU Lesser
General Public License, and the "GNU GPL" refers to version 3 of the GNU
General Public License.

  "The Library" refers to a covered work governed by this License,
other than an Application or a Combined Work as defined below.

  An "Application" is any work that makes use of an interface provided
by the Library, but which is not otherwise based on the Library.
Defining a subclass of a class defined by the Library is deemed a mode
of using an interface provided by the Library.

  A "Combined Work" is a work produced by combining or linking an
Application with the Library.  The particular version of the Library
with which the Combined Work was made is also called the "Linked

  The "Minimal Corresponding Source" for a Combined Work means the
Corresponding Source for the Combined Work, excluding any source code
for portions of the Combined Work that, considered in isolation, are
based on the Application, and not on the Linked Version.

  The "Corresponding Application Code" for a Combined Work means the
object code and/or source code for the Application, including any data
and utility programs needed for reproducing the Combined Work from the
Application, but excluding the System Libraries of the Combined Work.

  1. Exception to Section 3 of the GNU GPL.

  You may convey a covered work under sections 3 and 4 of this License
without being bound by section 3 of the GNU GPL.

  2. Conveying Modified Versions.

  If you modify a copy of the Library, and, in your modifications, a
facility refers to a function or data to be supplied by an Application
that uses the facility (other than as an argument passed when the
facility is invoked), then you may convey a copy of the modified

   a) under this License, provided that you make a good faith effort to
   ensure that, in the event an Application does not supply the
   function or data, the facility still operates, and performs
   whatever part of its purpose remains meaningful, or

   b) under the GNU GPL, with none of the additional permissions of
   this License applicable to that copy.

  3. Object Code Incorporating Material from Library Header Files.

  The object code form of an Application may incorporate material from
a header file that is part of the Library.  You may convey such object
code under terms of your choice, provided that, if the incorporated
material is not limited to numerical parameters, data structure
layouts and accessors, or small macros, inline functions and templates
(ten or fewer lines in length), you do both of the following:

   a) Give prominent notice with each copy of the object code that the
   Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the object code with a copy of the GNU GPL and this license

  4. Combined Works.

  You may convey a Combined Work under terms of your choice that,
taken together, effectively do not restrict modification of the
portions of the Library contained in the Combined Work and reverse
engineering for debugging such modifications, if you also do each of
the following:

   a) Give prominent notice with each copy of the Combined Work that
   the Library is used in it and that the Library and its use are
   covered by this License.

   b) Accompany the Combined Work with a copy of the GNU GPL and this license

   c) For a Combined Work that displays copyright notices during
   execution, include the copyright notice for the Library among
   these notices, as well as a reference directing the user to the
   copies of the GNU GPL and this license document.

   d) Do one of the following:

       0) Convey the Minimal Corresponding Source under the terms of this
       License, and the Corresponding Application Code in a form
       suitable for, and under terms that permit, the user to
       recombine or relink the Application with a modified version of
       the Linked Version to produce a modified Combined Work, in the
       manner specified by section 6 of the GNU GPL for conveying
       Corresponding Source.

       1) Use a suitable shared library mechanism for linking with the
       Library.  A suitable mechanism is one that (a) uses at run time
       a copy of the Library already present on the user's computer
       system, and (b) will operate properly with a modified version
       of the Library that is interface-compatible with the Linked

   e) Provide Installation Information, but only if you would otherwise
   be required to provide such information under section 6 of the
   GNU GPL, and only to the extent that such information is
   necessary to install and execute a modified version of the
   Combined Work produced by recombining or relinking the
   Application with a modified version of the Linked Version. (If
   you use option 4d0, the Installation Information must accompany
   the Minimal Corresponding Source and Corresponding Application
   Code. If you use option 4d1, you must provide the Installation
   Information in the manner specified by section 6 of the GNU GPL
   for conveying Corresponding Source.)

  5. Combined Libraries.

  You may place library facilities that are a work based on the
Library side by side in a single library together with other library
facilities that are not Applications and are not covered by this
License, and convey such a combined library under terms of your
choice, if you do both of the following:

   a) Accompany the combined library with a copy of the same work based
   on the Library, uncombined with any other library facilities,
   conveyed under the terms of this License.

   b) Give prominent notice with the combined library that part of it
   is a work based on the Library, and explaining where to find the
   accompanying uncombined form of the same work.

  6. Revised Versions of the GNU Lesser General Public License.

  The Free Software Foundation may publish revised and/or new versions
of the GNU Lesser General Public License from time to time. Such new
versions will be similar in spirit to the present version, but may
differ in detail to address new problems or concerns.

  Each version is given a distinguishing version number. If the
Library as you received it specifies that a certain numbered version
of the GNU Lesser General Public License "or any later version"
applies to it, you have the option of following the terms and
conditions either of that published version or of any later version
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.

  If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the

Project Meta

  • Registered 3 years ago
  • Started 3 years ago
  • Last commit 2 years ago



Commits per year



Unique contributors per year


Data not available



Share of languages used

Data Sheet
Project Web Site
Issue Tracker
Last updated 2 years ago
68 commits by 2 contributors
Stephan Stephan Nolting

Activity in last 1 year

Updated 11 days ago