URL https://opencores.org/ocsvn/neorv32/neorv32/trunk

Subversion Repositories neorv32

[/] [neorv32/] [trunk/] [docs/] [userguide/] [content.adoc] - Blame information for rev 68

Go to most recent revision | Details | Compare with Previous | View Log


Let's Get It Started!
 
This user guide uses the NEORV32 project _as is_ from the official `neorv32` repository.
To make your first NEORV32 project run, follow the guides from the upcoming sections. It is recommended to
follow these guides step by step and eventually in the presented order.
 
[TIP]
This guide uses the minimalistic and platform/toolchain agnostic SoC test setups from
`rtl/test_setups` for illustration. You can use one of the provided test setups for
your first FPGA tests. Alternatively, have a look at the `setups` folder,
which provides more sophisticated example setups for various FPGAs/FPGA boards and toolchains.
 
 
:sectnums:
== Software Toolchain Setup
 
To compile (and debug) executables for the NEORV32 a RISC-V toolchain is required.
There are two possibilities to get this:
 
1. Download and _build_ the official RISC-V GNU toolchain yourself.
2. Download and install a prebuilt version of the toolchain; this might also done via the package manager / app store of your OS
 
[NOTE]
The default toolchain prefix (`RISCV_PREFIX` variable) for this project is **`riscv32-unknown-elf-`**. Of course you can use any other RISC-V
toolchain (like `riscv64-unknown-elf-`) that is capable to emit code for a `rv32` architecture. Just change `RISCV_PREFIX`
according to your needs.
 
 
:sectnums:
=== Building the Toolchain from Scratch
 
To build the toolchain by yourself you can follow the guide from the official https://github.com/riscv-collab/riscv-gnu-toolchain GitHub page.
You need to make sure the generated toolchain fits the architecture of the NEORV32 core. To get a toolchain that even supports minimal
ISA extension configurations, it is recommend to compile for `rv32i` only. Please note that this minimal ISA also provides further ISA
extensions like `m` or `c`. Of course you can use a _multilib_ approach to generate toolchains for several target ISAs at once.
 
.Configuring GCC build for `rv32i` (minimal ISA)
[source,bash]
----
riscv-gnu-toolchain$ ./configure --prefix=/opt/riscv --with-arch=rv32i --with-abi=ilp32
riscv-gnu-toolchain$ make
----
 
[IMPORTANT]
Keep in mind that - for instance - a toolchain build with `--with-arch=rv32imc` only provides library code compiled with
compressed (`C`) and `mul`/`div` instructions (`M`)! Hence, this code cannot be executed (without
emulation) on an architecture without these extensions!
 
 
:sectnums:
=== Downloading and Installing a Prebuilt Toolchain
 
Alternatively, you can download a prebuilt toolchain.
 
:sectnums:
==== Use The Toolchain I have Build
 
I have compiled a GCC toolchain on a 64-bit x86 Ubuntu (Ubuntu on Windows, actually) and uploaded it to
GitHub. You can directly download the according toolchain archive as single _zip-file_ within a packed
release from https://github.com/stnolting/riscv-gcc-prebuilt.
 
Unpack the downloaded toolchain archive and copy the content to a location in your file system (e.g.
`/opt/riscv`). More information about downloading and installing my prebuilt toolchains can be found in
the repository's README.
 
 
:sectnums:
==== Use a Third Party Toolchain
 
Of course you can also use any other prebuilt version of the toolchain. There are a lot  RISC-V GCC packages out there -
even for Windows. On Linux system you might even be able to fetch a toolchain via your distribution's package manager.
 
[IMPORTANT]
Make sure the toolchain can (also) emit code for a `rv32i` architecture, uses the `ilp32` or `ilp32e` ABI and **was not build** using
CPU extensions that are not supported by the NEORV32 (like `D`).
 
 
:sectnums:
=== Installation
 
Now you have the toolchain binaries. The last step is to add them to your `PATH` environment variable (if you have not
already done so): make sure to add the _binaries_ folder (`bin`) of your toolchain.
 
[source,bash]
----
$ export PATH:$PATH:/opt/riscv/bin
----
 
You should add this command to your `.bashrc` (if you are using bash) to automatically add the RISC-V
toolchain at every console start.
 
:sectnums:
=== Testing the Installation
 
To make sure everything works fine, navigate to an example project in the NEORV32 example folder and
execute the following command:
 
[source,bash]
----
neorv32/sw/example/blink_led$ make check
----
 
This will test all the tools required for generating NEORV32 executables.
Everything is working fine if `Toolchain check OK` appears at the end.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== General Hardware Setup
 
This guide shows the basics of setting up a NEORV32 project for FPGA implementation (or simulation only)
_from scratch_. It uses a _simplified_ test "SoC" setup of the processor to keeps things simple at the beginning.
This simple setup is intended for evaluation or as "hello world" project to check out the NEORV32
on _your_ FPGA board.
 
[TIP]
If you want to use a more sophisticated pre-defined setup to start with, check out the
`setups` folder, which provides example setups for various FPGA, boards and toolchains.
 
The NEORV32 project features two minimalistic pre-configured test setups in
https://github.com/stnolting/neorv32/blob/master/rtl/test_setups[`rtl/test_setups`].
Both test setups only implement very basic processor and CPU features.
The main difference between the two setups is the processor boot concept - so how to get a software executable
_into_ the processor:
 
* **`rtl/test_setups/neorv32_testsetup_approm.vhd`**: this setup does not require a connection via UART. The
software executable is "installed" into the bitstream to initialize a read-only memory. Use this setup
if your FPGA board does _not_ provide a UART interface.
* **`rtl/test_setups/neorv32_testsetup_bootloader.vhd`**: this setups uses the UART and the default NEORV32
bootloader to upload new software executables. Use this setup if your board _does_ provide a UART interface.
 
.NEORV32 "hello world" test setup (`rtl/test_setups/neorv32_testsetup_bootloader.vhd`)
image::neorv32_test_setup.png[align=center]
 
.External Clock Source
[NOTE]
These test setups are intended to be directly used as **design top entity**. Of course you can also instantiate them
into another design unit. If your FPGA board only provides _very fast_ external clock sources (like on the FOMU board)
you might need to add clock management components (PLLs, DCMs, MMCMs, ...) to the test setup or to the according top entity
if you instantiate one of the test setups.
 
[start=1]
. Create a new project with your FPGA EDA tool of choice.
. Add all VHDL files from the project's `rtl/core` folder to your project.
 
.Internal Memories
[IMPORTANT]
For a _general_ first setup (technology-independent) use the `*.default.vhd` memory architectures for the internal memories
(IMEM and DMEM). These are located in `rtl/core/mem` so make sure to add the files to your project, too. +
 +
If synthesis cannot efficiently map those default memory descriptions to the available memory resources, you can later replace the
default memory architectures by optimized platform-specific memory architectures. **Example:** The `setups/radiant/UPduino_v3`
example setup uses optimized memory primitives. Hence, it does not include the default memory architectures from
`rtl/core/mem` as these are replaced by device-specific implementations. However, it still has to include the entity
definitions from `rtl/core`.
 
[start=3]
. Make sure to add all the rtl files to a new library called `neorv32`. If your FPGA tools does not
provide a field to enter the library name, check out the "properties" menu of the added rtl files.
 
.Compile order
[NOTE]
Some tools (like Lattice Radiant) might require a _manual compile order_ of the VHDL source files to identify the dependencies.
The package file `neorv32_package.vhd` should be analyzed first followed by the memory image files (`neorv32_application_imagevhd`
and `neorv32_bootloader_image.vhd`) and the entity-only files (`neorv32_*mem.entity.vhd`).
 
[start=4]
. The `rtl/core/neorv32_top.vhd` VHDL file is the top entity of the NEORV32 processor, which can be
instantiated into the "real" project. However, in this tutorial we will use one of the pre-defined
test setups from `rtl/test_setups` (see above).
 
[IMPORTANT]
Make sure to include the `neorv32` package into your design when instantiating the processor: add
`library neorv32;` and `use neorv32.neorv32_package.all;` to your design unit.
 
[start=5]
. Add the pre-defined test setup of choice to the project, too, and select it as _top entity_.
. The entity of both test setups
provide a minimal set of configuration generics, that might have to be adapted to match your FPGA and board:
 
.Test setup entity - configuration generics
[source,vhdl]
----
  generic (
    -- adapt these for your setup --
    CLOCK_FREQUENCY   : natural := 100000000; <1>
    MEM_INT_IMEM_SIZE : natural := 16*1024;   <2>
    MEM_INT_DMEM_SIZE : natural := 8*1024     <3>
  );
----
<1> Clock frequency of `clk_i` signal in Hertz
<2> Default size of internal instruction memory: 16kB
<3> Default size of internal data memory: 8kB
 
[start=7]
. If you feel like it - or if your FPGA does not provide sufficient resources - you can modify the
_memory sizes_ (`MEM_INT_IMEM_SIZE` and `MEM_INT_DMEM_SIZE` - marked with notes "2" and "3"). But as mentioned
above, let's keep things simple at first and use the standard configuration for now.
. There is one generic that _has to be set according to your FPGA board_ setup: the actual clock frequency
of the top's clock input signal (`clk_i`). Use the `CLOCK_FREQUENCY` generic to specify your clock source's
frequency in Hertz (Hz).
 
[NOTE]
If you have changed the default memory configuration (`MEM_INT_IMEM_SIZE` and `MEM_INT_DMEM_SIZE` generics)
keep those new sizes in mind - these values are required for setting
up the software framework in the next section <<_general_software_framework_setup>>.
 
[start=9]
. Depending on your FPGA tool of choice, it is time to assign the signals of the test setup top entity to
the according pins of your FPGA board. All the signals can be found in the entity declaration of the
corresponding test setup:
 
.Entity signals of `neorv32_testsetup_approm.vhd`
[source,vhdl]
----
  port (
    -- Global control --
    clk_i       : in  std_ulogic; -- global clock, rising edge
    rstn_i      : in  std_ulogic; -- global reset, low-active, async
    -- GPIO --
    gpio_o      : out std_ulogic_vector(7 downto 0) -- parallel output
  );
----
 
.Entity signals of `neorv32_testsetup_bootloader.vhd`
[source,vhdl]
----
  port (
    -- Global control --
    clk_i       : in  std_ulogic; -- global clock, rising edge
    rstn_i      : in  std_ulogic; -- global reset, low-active, async
    -- GPIO --
    gpio_o      : out std_ulogic_vector(7 downto 0); -- parallel output
    -- UART0 --
    uart0_txd_o : out std_ulogic; -- UART0 send data
    uart0_rxd_i : in  std_ulogic  -- UART0 receive data
  );
----
 
.Signal Polarity
[NOTE]
If your FPGA board has inverse polarity for certain input/output you can add `not` gates. Example: The reset signal
`rstn_i` is low-active by default; the LEDs connected to `gpio_o` high-active by default.
You can do this in your board top if you instantiate the test setup,
or _inside_ the test setup if this is your top entity (low-active LEDs example: `gpio_o <= NOT con_gpio_o(7 downto 0);`).
 
[start=10]
. Attach the clock input `clk_i` to your clock source and connect the reset line `rstn_i` to a button of
your FPGA board. Check whether it is low-active or high-active - the reset signal of the processor is
**low-active**, so maybe you need to invert the input signal.
. If possible, connected _at least_ bit `0` of the GPIO output port `gpio_o` to a LED (see "Signal Polarity" note above).
. Finally, if your are using the UART-based test setup (`neorv32_testsetup_bootloader.vhd`)
connect the UART communication signals `uart0_txd_o` and `uart0_rxd_i` to the host interface (e.g. USB-UART converter).
. Perform the project HDL compilation (synthesis, mapping, bitstream generation).
. Program the generated bitstream into your FPGA and press the button connected to the reset signal.
. Done! The LED at `gpio_o(0)` should be flashing now.
 
[TIP]
After the GCC toolchain for compiling RISC-V source code is ready (chapter <<_general_software_framework_setup>>),
you can advance to one of these chapters to learn how to get a software executable into your processor setup:
* If you are using the `neorv32_testsetup_approm.vhd` setup: See section <<_installing_an_executable_directly_into_memory>>.
* If you are using the `neorv32_testsetup_bootloader.vhd` setup: See section <<_uploading_and_starting_of_a_binary_executable_image_via_uart>>.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== General Software Framework Setup
 
To allow executables to be _actually executed_ on the NEORV32 Processor the configuration of the software framework
has to be aware to the hardware configuration. This guide focuses on the memory configuration. To enabled
certain CPU ISA features refer to the <<_enabling_risc_v_cpu_extensions>> section.
 
[TIP]
If you have **not** changed the _default_ memory configuration in section <<_general_hardware_setup>>
you are already done and you can skip the rest of this guide.
 
[start=1]
. Open the NEORV32 linker script `sw/common/neorv32.ld` with a text editor. Right at the
beginning of this script you will find the `MEMORY` configuration listing the different memory section:
 
.Cut-out of the linker script `neorv32.ld`: `ram` memory section configuration
[source,c]
----
MEMORY
{
  ram  (rwx) : ORIGIN = 0x80000000, LENGTH = DEFINED(make_bootloader) ? 512 : 8*1024 <1>
...
----
<1> Size of the data memory address space (right-most value) (internal/external DMEM); here 8kB
 
[start=2]
. We only need to change the `ram` section, which presents the available data address space.
If you have changed the DMEM (_MEM_INT_DMEM_SIZE_ generic) size adapt the `LENGTH` parameter of the `ram`
section (here: `8*1024`) so it is equal to your DMEM hardware configuration.
 
[IMPORTANT]
Make sure you only modify the _right-most_ value (here: 8*1024)! +
The "`512`" are not relevant for the application.
 
[start=3]
. Done! Save your changes and close the linker script.
 
.Advanced: Section base address and size
[IMPORTANT]
More information can be found in the datasheet section https://stnolting.github.io/neorv32/#_address_space[Address Space].
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Application Program Compilation
 
This guide shows how to compile an example C-code application into a NEORV32 executable that
can be uploaded via the bootloader or the on-chip debugger.
 
[IMPORTANT]
If your FPGA board does not provide such an interface - don't worry!
Section <<_installing_an_executable_directly_into_memory>> shows how to
run custom programs on your FPGA setup without having a UART.
 
[start=1]
. Open a terminal console and navigate to one of the project's example programs. For instance, navigate to the
simple `sw/example_blink_led` example program. This program uses the NEORV32 GPIO module to display
an 8-bit counter on the lowest eight bit of the `gpio_o` output port.
. To compile the project and generate an executable simply execute:
 
[source,bash]
----
neorv32/sw/example/blink_led$ make clean_all exe
----
 
[start=3]
. We are using the `clean_all` target to make sure everything is re-build.
. This will compile and link the application sources together with all the included libraries. At the end,
your application is transformed into an ELF file (`main.elf`). The _NEORV32 image generator_ (in `sw/image_gen`)
takes this file and creates a final executable. The makefile will show the resulting memory utilization and
the executable size:
 
[source,bash]
----
neorv32/sw/example/blink_led$ make clean_all exe
Memory utilization:
   text    data     bss     dec     hex filename
   3176       0     120    3296     ce0 main.elf
Compiling ../../../sw/image_gen/image_gen
Executable (neorv32_exe.bin) size in bytes:
3188
----
 
[start=5]
. That's it. The `exe` target has created the actual executable `neorv32_exe.bin` in the current folder
that is ready to be uploaded to the processor.
 
[TIP]
The compilation process will also create a `main.asm` assembly listing file in the current folder, which
shows the actual assembly code of the application.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Uploading and Starting of a Binary Executable Image via UART
 
Follow this guide to use the bootloader to upload an executable via UART.
 
[NOTE]
This concept uses the default "Indirect Boot" scenario that uses the bootloader to upload new executables.
See datasheet section https://stnolting.github.io/neorv32/#_indirect_boot[Indirect Boot] for more information.
 
[IMPORTANT]
If your FPGA board does not provide such an interface - don't worry!
Section <<_installing_an_executable_directly_into_memory>> shows how to
run custom programs on your FPGA setup without having a UART.
 
[start=1]
. Connect the primary UART (UART0) interface of your FPGA board to a serial port of your host computer.
. Start a terminal program. In this tutorial, I am using TeraTerm for Windows. You can download it for free
from https://ttssh2.osdn.jp/index.html.en . On Linux you could use GTKTerm, which you can get here
https://github.com/Jeija/gtkterm.git (or install via your package manager).
 
 
[NOTE]
_Any_ terminal program that can connect to a serial port should work. However, make sure the program
can transfer data in _raw_ byte mode without any protocol overhead around it.
 
[start=3]
. Open a connection to the the serial port your UART is connected to. Configure the terminal setting according to the
following parameters:
 
* 19200 Baud
* 8 data bits
* 1 stop bit
* no parity bits
* _no_ transmission/flow control protocol
* receiver (host computer) newline on `\r\n` (carriage return & newline)
 
[start=4]
. Also make sure that single chars are send from your computer _without_ any consecutive "new line" or "carriage
return" commands (this is highly dependent on your terminal application of choice, TeraTerm only
sends the raw chars by default).
. Press the NEORV32 reset button to restart the bootloader. The status LED starts blinking and the
bootloader intro screen appears in your console. Hurry up and press any key (hit space!) to abort the
automatic boot sequence and to start the actual bootloader user interface console.
 
.Bootloader console; aborted auto-boot sequence
[source,bash]
----
<< NEORV32 Bootloader >>
 
BLDV: Mar 23 2021
HWV:  0x01050208
CLK:  0x05F5E100
MISA: 0x40901105
ZEXT: 0x00000023
PROC: 0x0EFF0037
IMEM: 0x00004000 bytes @ 0x00000000
DMEM: 0x00002000 bytes @ 0x80000000
 
Autoboot in 8s. Press key to abort.
Aborted.
 
Available commands:
h: Help
r: Restart
u: Upload
s: Store to flash
l: Load from flash
e: Execute
CMD:>
----
 
[start=6]
. Execute the "Upload" command by typing `u`. Now the bootloader is waiting for a binary executable to be send.
 
[source,bash]
----
CMD:> u
Awaiting neorv32_exe.bin...
----
 
[start=7]
. Use the "send file" option of your terminal program to send a NEORV32 executable (`neorv32_exe.bin`).
. Again, make sure to transmit the executable in raw binary mode (no transfer protocol).
When using TeraTerm, select the "binary" option in the send file dialog.
. If everything went fine, OK will appear in your terminal:
 
[source,bash]
----
CMD:> u
Awaiting neorv32_exe.bin... OK
----
 
[start=10]
. The executable is now in the instruction memory of the processor. To execute the program right
now run the "Execute" command by typing `e`:
 
[source,bash]
----
CMD:> u
Awaiting neorv32_exe.bin... OK
CMD:> e
Booting...
Blinking LED demo program
----
 
[start=11]
. If everything went fine, you should see the LEDs blinking.
 
[NOTE]
The bootloader will print error codes if something went wrong.
See section https://stnolting.github.io/neorv32/#_bootloader[Bootloader] of the NEORV32 datasheet for more information.
 
[TIP]
See section <<_programming_an_external_spi_flash_via_the_bootloader>> to learn how to use an external SPI
flash for nonvolatile program storage.
 
[TIP]
Executables can also be uploaded via the **on-chip debugger**.
See section <<_debugging_with_gdb>> for more information.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Installing an Executable Directly Into Memory
 
If you do not want to use the bootloader (or the on-chip debugger) for executable upload or if your setup does not provide
a serial interface for that, you can also directly install an application into embedded memory.
 
This concept uses the "Direct Boot" scenario that implements the processor-internal IMEM as ROM, which is
pre-initialized with the application's executable during synthesis. Hence, it provides _non-volatile_ storage of the
executable inside the processor. This storage cannot be altered during runtime and any source code modification of
the application requires to re-program the FPGA via the bitstream.
 
[TIP]
See datasheet section https://stnolting.github.io/neorv32/#_direct_boot[Direct Boot] for more information.
 
 
 
Using the IMEM as ROM:
 
* for this boot concept the bootloader is no longer required
* this concept only works for the internal IMEM (but can be extended to work with external memories coupled via the processor's bus interface)
* make sure that the memory components (like block RAM) the IMEM is mapped to support an initialization via the bitstream
 
[start=1]
. At first, make sure your processor setup actually implements the internal IMEM: the `MEM_INT_IMEM_EN` generics has to be set to `true`:
 
.Processor top entity configuration - enable internal IMEM
[source,vhdl]
----
  -- Internal Instruction memory --
  MEM_INT_IMEM_EN => true, -- implement processor-internal instruction memory
----
 
[start=2]
. For this setup we do not want the bootloader to be implemented at all. Disable implementation of the bootloader by setting the
`INT_BOOTLOADER_EN` generic to `false`. This will also modify the processor-internal IMEM so it is initialized with the executable during synthesis.
 
.Processor top entity configuration - disable internal bootloader
[source,vhdl]
----
  -- General --
  INT_BOOTLOADER_EN => false, -- boot configuration: false = boot from int/ext (I)MEM
----
 
[start=3]
. To generate an "initialization image" for the IMEM that contains the actual application, run the `install` target when compiling your application:
 
[source,bash]
----
neorv32/sw/example/blink_led$ make clean_all install
Memory utilization:
   text    data     bss     dec     hex filename
   3176       0     120    3296     ce0 main.elf
Compiling ../../../sw/image_gen/image_gen
Installing application image to ../../../rtl/core/neorv32_application_image.vhd
----
 
[start=4]
. The `install` target has compiled all the application sources but instead of creating an executable (`neorv32_exe.bit`) that can be uploaded via the
bootloader, it has created a VHDL memory initialization image `core/neorv32_application_image.vhd`.
. This VHDL file is automatically copied to the core's rtl folder (`rtl/core`) so it will be included for the next synthesis.
. Perform a new synthesis. The IMEM will be build as pre-initialized ROM (inferring embedded memories if possible).
. Upload your bitstream. Your application code now resides unchangeable in the processor's IMEM and is directly executed after reset.
 
 
The synthesis tool / simulator will print asserts to inform about the (IMEM) memory / boot configuration:
 
[source]
----
NEORV32 PROCESSOR CONFIG NOTE: Boot configuration: Direct boot from memory (processor-internal IMEM).
NEORV32 PROCESSOR CONFIG NOTE: Implementing processor-internal IMEM as ROM (3176 bytes), pre-initialized with application.
----
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Setup of a New Application Program Project
 
[start=1]
. The easiest way of creating a _new_ software application project is to copy an _existing_ one. This will keep all
file dependencies. For example you can copy `sw/example/blink_led` to `sw/example/flux_capacitor`.
. If you want to place you application somewhere outside `sw/example` you need to adapt the application's makefile.
In the makefile you will find a variable that keeps the relative or absolute path to the NEORV32 repository home
folder. Just modify this variable according to your new project's home location:
 
[source,makefile]
----
# Relative or absolute path to the NEORV32 home folder (use default if not set by user)
NEORV32_HOME ?= ../../..
----
 
[start=3]
. If your project contains additional source files outside of the project folder, you can add them to
the `APP_SRC` variable:
 
[source,makefile]
----
# User's application sources (add additional files here)
APP_SRC = $(wildcard *.c) ../somewhere/some_file.c
----
 
[start=4]
. You also can add a folder containing your application's include files to the
`APP_INC` variable (do not forget the `-I` prefix):
 
[source,makefile]
----
# User's application include folders (don't forget the '-I' before each entry)
APP_INC = -I . -I ../somewhere/include_stuff_folder
----
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Enabling RISC-V CPU Extensions
 
Whenever you enable/disable a RISC-V CPU extensions via the according `CPU_EXTENSION_RISCV_x` generic, you need to
adapt the toolchain configuration so the compiler can actually generate according code for it.
 
To do so, open the makefile of your project (for example `sw/example/blink_led/makefile`) and scroll to the
"USER CONFIGURATION" section right at the beginning of the file. You need to modify the `MARCH` variable and eventually
the `MABI` variable according to your CPU hardware configuration.
 
[source,makefile]
----
# CPU architecture and ABI
MARCH ?= rv32i <1>
MABI  ?= ilp32 <2>
----
<1> MARCH = Machine architecture ("ISA string")
<2> MABI = Machine binary interface
 
For example, if you enable the RISC-V `C` extension (16-bit compressed instructions) via the `CPU_EXTENSION_RISCV_C`
generic (set `true`) you need to add the `c` extension also to the `MARCH` ISA string in order to make the compiler
emit compressed instructions.
 
.Privileged Architecture Extensions
[IMPORTANT]
Privileged architecture extensions like `Zicsr` or `Zifencei` are "used" _implicitly_ by the compiler. Hence, according
instruction will only be generated when "encoded" via inline assembly or when linking according libraries. In this case,
these instruction will _always_ be emitted (even if the according extension is not specified in `MARCH`). +
**I recommend to _not_ specify any privileged architecture extensions in `MARCH`.**
 
[WARNING]
ISA extension enabled in hardware can be a superset of the extensions enabled in software, but not the other way
around. For example generating compressed instructions for a CPU configuration that has the `c` extension disabled
will cause _illegal instruction exceptions_ at runtime.
 
You can also override the default `MARCH` and `MABI` configurations from the makefile when invoking the makefile:
 
[source,bash]
----
$ make MARCH=rv32ic clean_all all
----
 
[NOTE]
The RISC-V ISA string for `MARCH` follows a certain _canonical_ structure:
`rev32[i/e][m][a][f][d][g][q][c][b][v][n]...` For example `rv32imac` is valid while `rv32icma` is not.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Application-Specific Processor Configuration
 
Due to the processor's configuration options, which are mainly defined via the top entity VHDL generics, the SoC
can be tailored to the application-specific requirements. Note that this chapter does not focus on optional
_SoC features_ like IO/peripheral modules. It rather gives ideas on how to optimize for _overall goals_
like performance and area.
 
[NOTE]
Please keep in mind that optimizing the design in one direction (like performance) will also effect other potential
optimization goals (like area and energy).
 
=== Optimize for Performance
 
The following points show some concepts to optimize the processor for performance regardless of the costs
(i.e. increasing area and energy requirements):
 
* Enable all performance-related RISC-V CPU extensions that implement dedicated hardware accelerators instead
of emulating operations entirely in software:  `M`, `C`, `Zfinx`
* Enable mapping of compleX CPU operations to dedicated hardware: `FAST_MUL_EN => true` to use DSP slices for
multiplications, `FAST_SHIFT_EN => true` use a fast barrel shifter for shift operations.
* Implement the instruction cache: `ICACHE_EN => true`
* Use as many _internal_ memory as possible to reduce memory access latency: `MEM_INT_IMEM_EN => true` and
`MEM_INT_DMEM_EN => true`, maximize `MEM_INT_IMEM_SIZE` and `MEM_INT_DMEM_SIZE`
* Increase the CPU's instruction prefetch buffer size: `CPU_IPB_ENTRIES`
* _To be continued..._
 
 
=== Optimize for Size
 
The NEORV32 is a size-optimized processor system that is intended to fit into tiny niches within large SoC
designs or to be used a customized microcontroller in really tiny / low-power FPGAs (like Lattice iCE40).
Here are some ideas how to make the processor even smaller while maintaining it's _general purpose system_
concept and maximum RISC-V compatibility.
 
**SoC**
 
* This is obvious, but exclude all unused optional IO/peripheral modules from synthesis via the processor
configuration generics.
* If an IO module provides an option to configure the number of "channels", constrain this number to the
actually required value (e.g. the PWM module `IO_PWM_NUM_CH` or the external interrupt controller `XIRQ_NUM_CH`).
* Reduce the FIFO sizes of implemented modules (e.g. `SLINK_TX_FIFO`).
* Disable the instruction cache (`ICACHE_EN => false`) if the design only uses processor-internal IMEM
and DMEM memories.
* _To be continued..._
 
**CPU**
 
* Use the _embedded_ RISC-V CPU architecture extension (`CPU_EXTENSION_RISCV_E`) to reduce block RAM utilization.
* The compressed instructions extension (`CPU_EXTENSION_RISCV_C`) requires additional logic for the decoder but
also reduces program code size by approximately 30%.
* If not explicitly used/required, constrain the CPU's counter sizes: `CPU_CNT_WIDTH` for `[m]instret[h]`
(number of instruction) and `[m]cycle[h]` (number of cycles) counters. You can even remove these counters
by setting `CPU_CNT_WIDTH => 0` if they are not used at all (note, this is not RISC-V compliant).
* Reduce the CPU's prefetch buffer size (`CPU_IPB_ENTRIES`).
* Map CPU shift operations to a small and iterative shifter unit (`FAST_SHIFT_EN => false`).
* If you have unused DSP block available, you can map multiplication operations to those slices instead of
using LUTs to implement the multiplier (`FAST_MUL_EN => true`).
* If there is no need to execute division in hardware, use the `Zmmul` extension instead of the full-scale
`M` extension.
* Disable CPU extension that are not explicitly used (`A`, `U`, `Zfinx`).
* _To be continued..._
 
=== Optimize for Clock Speed
 
The NEORV32 Processor and CPU are designed to provide minimal logic between register stages to keep the
critical path as short as possible. When enabling additional extension or modules the impact on the existing
logic is also kept at a minimum to prevent timing degrading. If there is a major impact on existing
logic (example: many physical memory protection address configuration registers) the VHDL code automatically
adds additional register stages to maintain critical path length. Obviously, this increases operation latency.
 
In order to optimize for a minimal critical path (= maximum clock speed) the following points should be considered:
 
* Complex CPU extensions (in terms of hardware requirements) should be avoided (examples: floating-point unit, physical memory protection).
* Large carry chains (>32-bit) should be avoided (constrain CPU counter sizes: e.g. `CPU_CNT_WIDTH => 32` and `HPM_NUM_CNTS => 32`).
* If the target FPGA provides sufficient DSP resources, CPU multiplication operations can be mapped to DSP slices (`FAST_MUL_EN => true`)
reducing LUT usage and critical path impact while also increasing overall performance.
* Use the synchronous (registered) RX path configuration of the external memory interface (`MEM_EXT_ASYNC_RX => false`).
* _To be continued..._
 
[NOTE]
The short and fixed-length critical path allows to integrate the core into existing clock domains.
So no clock domain-crossing and no sub-clock generation is required. However, for very high clock
frequencies (this is technology / platform dependent) clock domain crossing becomes crucial for chip-internal
connections.
 
 
=== Optimize for Energy
 
There are no _dedicated_ configuration options to optimize the processor for energy (minimal consumption;
energy/instruction ratio) yet. However, a reduced processor area (<<_optimize_for_size>>) will also reduce
static energy consumption.
 
To optimize your setup for low-power applications, you can make use of the CPU sleep mode (`wfi` instruction).
Put the CPU to sleep mode whenever possible. Disable all processor modules that are not actually used (exclude them
from synthesis if the will be _never_ used; disable the module via it's control register if the module is not
_currently_ used). When is sleep mode, you can keep a timer module running (MTIME or the watch dog) to wake up
the CPU again. Since the wake up is triggered by _any_ interrupt, the external interrupt controller can also
be used to wake up the CPU again. By this, all timers (and all other modules) can be deactivated as well.
 
.Processor-internal clock generator shutdown
[TIP]
If _no_ IO/peripheral module is currently enabled, the processor's internal clock generator circuit will be
shut down reducing switching activity and thus, dynamic energy consumption.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Adding Custom Hardware Modules
 
In resemblance to the RISC-V ISA, the NEORV32 processor was designed to ease customization and _extensibility_.
The processor provides several predefined options to add application-specific custom hardware modules and accelerators.
 
 
=== Standard (_External_) Interfaces
 
The processor already provides a set of standard interfaces that are intended to connect _chip-external_ devices.
However, these interfaces can also be used chip-internally. The most suitable interfaces are
https://stnolting.github.io/neorv32/#_general_purpose_input_and_output_port_gpio[GPIO],
https://stnolting.github.io/neorv32/#_primary_universal_asynchronous_receiver_and_transmitter_uart0[UART],
https://stnolting.github.io/neorv32/#_serial_peripheral_interface_controller_spi[SPI] and
https://stnolting.github.io/neorv32/#_two_wire_serial_interface_controller_twi[TWI].
 
The SPI and (especially) the GPIO interfaces might be the most straightforward approaches since they
have a minimal  protocol overhead. Device-specific interrupt capabilities can be added using the
https://stnolting.github.io/neorv32/#_external_interrupt_controller_xirq[External Interrupt Controller (XIRQ)].
Beyond simplicity, these interface only provide a very limited bandwidth and require more sophisticated
software handling ("bit-banging" for the GPIO).
 
 
=== External Bus Interface
 
The https://stnolting.github.io/neorv32/#_processor_external_memory_interface_wishbone_axi4_lite[External Bus Interface]
provides the classic approach to connect to custom IP. By default, the bus interface implements the widely adopted
Wishbone interface standard. However, this project also includes wrappers to bridge to other protocol standards like ARM's
AXI4-Lite or Intel's Avalon. By using a full-featured bus protocol, complex SoC structures can be implemented (including
several modules and even multi-core architectures). Many FPGA EDA tools provide graphical editors to build and customize
whole SoC architectures and even include pre-defined IP libraries.
 
.Example AXI SoC using Xilinx Vivado
image::neorv32_axi_soc.png[]
 
The bus interface uses a memory-mapped approach. All data transfers are handled by simple load/store operations since the
external bus interface is mapped into the processor's https://stnolting.github.io/neorv32/#_address_space[address space].
This allows a very simple still high-bandwidth communications.
 
 
=== Stream Link Interface
 
The NEORV32 https://stnolting.github.io/neorv32/#_stream_link_interface_slink[Stream Link Interface] provides
point-to-point, unidirectional and parallel data channels that can be used to transfer streaming data. In
contrast to the external bus interface, the streaming data does not provide any kind of "direction" control,
so it can be seen as "constant address bursts". The stream link interface provides less protocol overhead
and less latency than the bus interface. Furthermore, FIFOs can be be configured to each direction (RX/TX) to
allow more CPU-independent operation.
 
 
=== Custom Functions Subsystem
 
The NEORV32 https://stnolting.github.io/neorv32/#_custom_functions_subsystem_cfs[Custom Functions Subsystem] is
an "empty" template for a processor-internal module. It provides 32 32-bit memory-mapped interface
registers that can be used to communicate with any arbitrary custom design logic. The intentions of this
subsystem is to provide a simple base, where the user can concentrate on implementing the actual design logic
rather than taking care of the communication between the CPU/software and the design logic. The interface
registers are already allocated within the processor's address space and are supported by the software framework
via low-level hardware access mechanisms. Additionally, the CFS provides a direct pre-defined interrupt channel to
the CPU, which is also supported by the NEORV32 runtime environment.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Customizing the Internal Bootloader
 
The NEORV32 bootloader provides several options to configure and customize it for a certain application setup.
This configuration is done by passing _defines_ when compiling the bootloader. Of course you can also
modify to bootloader source code to provide a setup that perfectly fits your needs.
 
[IMPORTANT]
Each time the bootloader sources are modified, the bootloader has to be re-compiled (and re-installed to the
bootloader ROM) and the processor has to be re-synthesized.
 
[NOTE]
Keep in mind that the maximum size for the bootloader is limited to 32kB and should be compiled using the
base ISA `rv32i` only to ensure it can work independently of the actual CPU configuration.
 
.Bootloader configuration parameters
[cols="<2,^1,^2,<6"]
[options="header", grid="rows"]
|=======================
| Parameter | Default | Legal values | Description
4+^| Serial console interface
| `UART_EN`   | `1` | `0`, `1` | Set to `0` to disable UART0 (no serial console at all)
| `UART_BAUD` | `19200` | _any_ | Baud rate of UART0
4+^| Status LED
| `STATUS_LED_EN`  | `1` | `0`, `1` | Enable bootloader status led ("heart beat") at `GPIO` output port pin #`STATUS_LED_PIN` when `1`
| `STATUS_LED_PIN` | `0` | `0` ... `31` | `GPIO` output pin used for the high-active status LED
4+^| Boot configuration
| `AUTO_BOOT_SPI_EN`  | `0` | `0`, `1` | Set `1` to enable immediate boot from external SPI flash
| `AUTO_BOOT_OCD_EN`  | `0` | `0`, `1` | Set `1` to enable boot via on-chip debugger (OCD)
| `AUTO_BOOT_TIMEOUT` | `8` | _any_ | Time in seconds after the auto-boot sequence starts (if there is no UART input by user); set to 0 to disabled auto-boot sequence
4+^| SPI configuration
| `SPI_EN`                | `1` | `0`, `1` | Set `1` to enable the usage of the SPI module (including load/store executables from/to SPI flash options)
| `SPI_FLASH_CS`          | `0` | `0` ... `7` | SPI chip select output (`spi_csn_o`) for selecting flash
| `SPI_FLASH_SECTOR_SIZE` | `65536` | _any_ | SPI flash sector size in bytes
| `SPI_FLASH_CLK_PRSC`    | `CLK_PRSC_8`  | `CLK_PRSC_2` `CLK_PRSC_4` `CLK_PRSC_8` `CLK_PRSC_64` `CLK_PRSC_128` `CLK_PRSC_1024` `CLK_PRSC_2024` `CLK_PRSC_4096` | SPI clock pre-scaler (dividing main processor clock)
| `SPI_BOOT_BASE_ADDR`    | `0x08000000` | _any_ 32-bit value | Defines the _base_ address of the executable in external flash
|=======================
 
Each configuration parameter is implemented as C-language `define` that can be manually overridden (_redefined_) when
invoking the bootloader's makefile. The according parameter and its new value has to be _appended_
(using `+=`) to the makefile `USER_FLAGS` variable. Make sure to use the `-D` prefix here.
 
For example, to configure a UART Baud rate of 57600 and redirecting the status LED to output pin 20
use the following command (_in_ the bootloader's source folder `sw/bootloader`):
 
.Example: customizing, re-compiling and re-installing the bootloader
[source,console]
----
$ make USER_FLAGS+=-DUART_BAUD=57600 USER_FLAGS+=-DSTATUS_LED_PIN=20 clean_all bootloader
----
 
[NOTE]
The `clean_all` target ensure that all libraries are re-compiled. The `bootloader` target will automatically
compile and install the bootloader to the HDL boot ROM (updating `rtl/core/neorv32_bootloader_image.vhd`).
 
:sectnums:
=== Bootloader Boot Configuration
 
The bootloader provides several _boot configurations_ that define where the actual application's executable
shall be fetched from. Note that the non-default boot configurations provide a smaller memory footprint
reducing boot ROM implementation costs.
 
:sectnums!:
==== Default Boot Configuration
 
The _default_ bootloader configuration provides a UART-based user interface that allows to upload new executables
at any time. Optionally, the executable can also be programmed to an external SPI flash by the bootloader (see
section <<_programming_an_external_spi_flash_via_the_bootloader>>).
 
This configuration also provides an _automatic boot sequence_ (auto-boot) which will start fetching an executable
from external SPI flash using the default SPI configuration. By this, the default bootloader configuration
provides a "non volatile program storage" mechanism that automatically boot from external SPI flash
(after `AUTO_BOOT_TIMEOUT`) while still providing the option to re-program SPI flash at any time
via the UART interface.
 
:sectnums!:
==== `AUTO_BOOT_SPI_EN`
 
The automatic boot from SPI flash (enabled when `AUTO_BOOT_SPI_EN` is `1`) will fetch an executable from an external
SPI flash (using the according _SPI configuration_) right after reset. The bootloader will start fetching
the image at SPI flash base address `SPI_BOOT_BASE_ADDR`.
 
Note that there is _no_ UART console to interact with the bootloader. However, this boot configuration will
output minimal status messages via UART (if `UART_EN` is `1`).
 
:sectnums!:
==== `AUTO_BOOT_OCD_EN`
 
If `AUTO_BOOT_OCD_EN` is `1` the bootloader is implemented as minimal "halt loop" to be used with the on-chip debugger.
After initializing the hardware, the CPU waits in this endless loop until the on-chip debugger takes control over
the core (to upload and run the actual executable). See section <<_debugging_using_the_on_chip_debugger>>
for more information on how to use the on-chip debugger to upload and run executables.
 
[NOTE]
All bootloader boot configuration support uploading new executables via the on-chip debugger.
 
[WARNING]
Note that this boot configuration does not load any executable at all! Hence,
this boot configuration is intended to be used with the on-chip debugger only.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Programming an External SPI Flash via the Bootloader
 
The default processor-internal NEORV32 bootloader supports automatic booting from an external SPI flash.
This guide shows how to write an executable to the SPI flash via the bootloader so it can be automatically
fetched and executed after processor reset. For example, you can use a section of the FPGA bitstream configuration
memory to store an application executable.
 
[NOTE]
This section assumes the _default_ configuration of the NEORV32 bootloader.
See section <<_customizing_the_internal_bootloader>> on how to customize the bootloader and its setting
(for example the SPI chip-select port, the SPI clock speed or the flash base address for storing the executable).
 
 
:sectnums:
=== SPI Flash
 
The bootloader can access an SPI compatible flash via the processor top entity's SPI port. By default, the flash
chip-select line is to `spi_csn_o(0)` and uses 1/8 of the processor's main clock as clock frequency.
The SPI flash has to support single-byte read and write, 24-bit addresses and at least the following standard commands:
 
* READ `0x03`
* READ STATUS `0x05`
* WRITE ENABLE `0x06`
* PAGE PROGRAM `0x02`
* SECTOR ERASE `0xD8`
* READ ID `0x9E`
 
Compatible (FGPA configuration) SPI flash memories are for example the "Winbond W25Q64FV2 or the "Micron N25Q032A".
 
 
:sectnums:
=== Programming an Executable
 
[start=1]
. At first, reset the NEORV32 processor and wait until the bootloader start screen appears in your terminal program.
. Abort the auto boot sequence and start the user console by pressing any key.
. Press u to upload the executable that you want to store to the external flash:
 
[source]
----
CMD:> u
Awaiting neorv32_exe.bin...
----
 
[start=4]
. Send the binary in raw binary via your terminal program. When the upload is completed and "OK"
appears, press `p` to trigger the programming of the flash (do not execute the image via the `e`
command as this might corrupt the image):
 
[source]
----
CMD:> u
Awaiting neorv32_exe.bin... OK
CMD:> p
Write 0x000013FC bytes to SPI flash @ 0x00800000? (y/n)
----
 
[start=5]
. The bootloader shows the size of the executable and the base address inside the SPI flash where the
executable is going to be stored. A prompt appears: Type `y` to start the programming or type `n` to
abort.
 
[TIP]
Section <<_customizing_the_internal_bootloader>> show the according C-language `define` that can be modified
to specify the base address of the executable inside the SPI flash.
 
[source]
----
CMD:> u
Awaiting neorv32_exe.bin... OK
CMD:> p
Write 0x000013FC bytes to SPI flash @ 0x08000000? (y/n) y
Flashing... OK
CMD:>
----
 
[start=6]
. If "OK" appears in the terminal line, the programming process was successful. Now you can use the
auto boot sequence to automatically boot your application from the flash at system start-up without
any user interaction.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Packaging the Processor as IP block for Xilinx Vivado Block Designer
 
[start=1]
. Import all the core files from `rtl/core` (including default internal memory architectures from `rtl/core/mem`)
and assign them to a _new_ design library `neorv32`.
. Instantiate the `rtl/wrappers/neorv32_top_axi4lite.vhd` module.
. Then either directly use that module in a new block-design ("Create Block Design", right-click -> "Add Module",
thats easier for a first try) or package it ("Tools", "Create and Package new IP") for the use in other projects.
. Connect your AXI-peripheral directly to the core's AXI4-Interface if you only have one, or to an AXI-Interconnect
(from the IP-catalog) if you have multiple peripherals.
. Connect ALL the `ACLK` and `ARESETN` pins of all peripherals and interconnects to the processor's clock and reset
signals to have a _unified_ clock and reset domain (easier for a first setup).
. Open the "Address Editor" tab and let Vivado assign the base-addresses for the AXI-peripherals (you can modify them
according to your needs).
. For all FPGA-external signals (like UART signals) make all the connections you need "external"
(right-click on the signal/pin -> "Make External").
. Save everything, let VIVADO create a HDL-Wrapper for the block-design and choose this as your _Top Level Design_.
. Define your constraints and generate your bitstream.
 
.TWI Tri-State Drivers
[IMPORTANT]
Set the synthesis option "global" when generating the block design to maintain the internal TWI tri-state drivers.
 
[NOTE]
Guide provided by GitHub user https://github.com/AWenzel83[`AWenzel83`] (see
https://github.com/stnolting/neorv32/discussions/52#discussioncomment-819013). ❤️
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Simulating the Processor
 
The NEORV32 project includes a core CPU, built-in peripherals in the Processor Subsystem, and additional peripherals in
the templates and examples.
Therefore, there is a wide range of possible testing and verification strategies.
 
On the one hand, a simple smoke testbench allows ensuring that functionality is correct from a software point of view.
That is used for running the RISC-V architecture tests, in order to guarantee compliance with the ISA specification(s).
 
On the other hand, http://vunit.github.io/[VUnit] and http://vunit.github.io/verification_components/user_guide.html[Verification Components] are used for verifying the functionality of the various peripherals from a hardware point of view.
 
:sectnums:
=== Testbench
 
A plain-VHDL (no third-party libraries) testbench (`sim/simple/neorv32_tb.simple.vhd`) can be used for simulating and
testing the processor.
This testbench features a 100MHz clock and enables all optional peripheral and CPU extensions except for the `E`
extension and the TRNG IO module (that CANNOT be simulated due to its combinatorial (looped) architecture).
 
The simulation setup is configured via the "User Configuration" section located right at the beginning of
the testbench's architecture. Each configuration constant provides comments to explain the functionality.
 
Besides the actual NEORV32 Processor, the testbench also simulates "external" components that are connected
to the processor's external bus/memory interface. These components are:
 
* an external instruction memory (that also allows booting from it)
* an external data memory
* an external memory to simulate "external IO devices"
* a memory-mapped registers to trigger the processor's interrupt signals
 
The following table shows the base addresses of these four components and their default configuration and
properties:
 
[NOTE]
====
Attributes:
 
* `r` = read
* `w` = write
* `e` = execute
* `a` = atomic accesses possible
* `8` = byte-accessible
* `16` = half-word-accessible
* `32` = word-accessible
====
 
.Testbench: processor-external memories
[cols="^4,>3,^5,<11"]
[options="header",grid="rows"]
|=======================
| Base address | Size          | Attributes           | Description
| `0x00000000` | `imem_size_c` | `r/w/e,  a, 8/16/32` | external IMEM (initialized with application image)
| `0x80000000` | `dmem_size_c` | `r/w/e,  a, 8/16/32` | external DMEM
| `0xf0000000` |      64 bytes | `r/w/e, !a, 8/16/32` | external "IO" memory, atomic accesses will fail
| `0xff000000` |       4 bytes | `-/w/-,  a,  -/-/32` | memory-mapped register to trigger "machine external", "machine software" and "SoC Fast Interrupt" interrupts
|=======================
 
[IMPORTANT]
The simulated NEORV32 does not use the bootloader and _directly boots_ the current application image (from
the `rtl/core/neorv32_application_image.vhd` image file).
 
.UART output during simulation
[IMPORTANT]
Data written to the NEORV32 UART0 / UART1 transmitter is send to a virtual UART receiver implemented
as part of the testbench. Received chars are send to the simulator console and are also stored to a log file
(`neorv32.testbench_uart0.out` for UART0, `neorv32.testbench_uart1.out` for UART1) inside the simulation's home folder.
**Please note that printing via the native UART receiver takes a lot of time.** For faster simulation console output
see section <<_faster_simulation_console_output>>.
 
 
:sectnums:
=== Faster Simulation Console Output
 
When printing data via the UART the communication speed will always be based on the configured BAUD
rate. For a simulation this might take some time. To have faster output you can enable the **simulation mode**
for UART0/UART1 (see section https://stnolting.github.io/neorv32/#_primary_universal_asynchronous_receiver_and_transmitter_uart0[Documentation: Primary Universal Asynchronous Receiver and Transmitter (UART0)]).
 
ASCII data sent to UART0|UART1 will be immediately printed to the simulator console and logged to files in the simulator
execution directory:
 
* `neorv32.uart?.sim_mode.text.out`: ASCII data.
* `neorv32.uart?.sim_mode.data.out`: all written 32-bit dumped as 8-char hexadecimal values.
 
You can "automatically" enable the simulation mode of UART0/UART1 when compiling an application.
In this case, the "real" UART0/UART1 transmitter unit is permanently disabled.
To enable the simulation mode just compile and install your application and add _UART?_SIM_MODE_ to the compiler's
_USER_FLAGS_ variable (do not forget the `-D` suffix flag):
 
[source, bash]
----
sw/example/blink_led$ make USER_FLAGS+=-DUART0_SIM_MODE clean_all all
----
 
The provided define will change the default UART0/UART1 setup function in order to set the simulation
mode flag in the according UART's control register.
 
[NOTE]
The UART simulation output (to file and to screen) outputs "complete lines" at once. A line is
completed with a line feed (newline, ASCII `\n` = 10).
 
 
:sectnums:
=== Simulation using a shell script (with GHDL)
 
To simulate the processor using _GHDL_ navigate to the `sim/simple/` folder and run the provided shell script.
Any arguments that are provided while executing this script are passed to GHDL.
For example the simulation time can be set to 20ms using `--stop-time=20ms` as argument.
 
[source, bash]
----
neorv32/sim/simple$ sh ghdl_sim.sh --stop-time=20ms
----
 
 
:sectnums:
=== Simulation using Application Makefiles (In-Console with GHDL)
 
To directly compile and run a program in the console (using the default testbench and GHDL
as simulator) you can use the `sim` makefile target. Make sure to use the UART simulation mode
(`USER_FLAGS+=-DUART0_SIM_MODE` and/or `USER_FLAGS+=-DUART1_SIM_MODE`) to get
faster / direct-to-console UART output.
 
[source, bash]
----
sw/example/blink_led$ make USER_FLAGS+=-DUART0_SIM_MODE clean_all sim
[...]
Blinking LED demo program
----
 
 
:sectnums:
==== Hello World!
 
To do a quick test of the NEORV32 make sure to have https://github.com/ghdl/ghdl[GHDL] and a
[RISC-V gcc toolchain](https://github.com/stnolting/riscv-gcc-prebuilt) installed.
Navigate to the project's `sw/example/hello_world` folder and run `make USER_FLAGS+=-DUART0_SIM_MODE MARCH=rv32imac clean_all sim`:
 
[TIP]
The simulator will output some _sanity check_ notes (and warnings or even errors if something is ill-configured)
right at the beginning of the simulation to give a brief overview of the actual NEORV32 SoC and CPU configurations.
 
[source, bash]
----
stnolting@Einstein:/mnt/n/Projects/neorv32/sw/example/hello_world$ make USER_FLAGS+=-DUART0_SIM_MODE MARCH=rv32imac clean_all sim
../../../sw/lib/source/neorv32_uart.c: In function 'neorv32_uart0_setup':
../../../sw/lib/source/neorv32_uart.c:301:4: warning: #warning UART0_SIM_MODE (primary UART) enabled! Sending all UART0.TX data to text.io simulation output instead of real UART0 transmitter. Use this for simulations only! [-Wcpp]
  301 |   #warning UART0_SIM_MODE (primary UART) enabled! Sending all UART0.TX data to text.io simulation output instead of real UART0 transmitter. Use this for simulations only! <1>
      |    ^~~~~~~
Memory utilization:
   text    data     bss     dec     hex filename
   4612       0     120    4732    127c main.elf <2>
Compiling ../../../sw/image_gen/image_gen
Installing application image to ../../../rtl/core/neorv32_application_image.vhd <3>
Simulating neorv32_application_image.vhd...
Tip: Compile application with USER_FLAGS+=-DUART[0/1]_SIM_MODE to auto-enable UART[0/1]'s simulation mode (redirect UART output to simulator console). <4>
Using simulation runtime args: --stop-time=10ms <5>
../rtl/core/neorv32_top.vhd:347:3:@0ms:(assertion note): NEORV32 PROCESSOR IO Configuration: GPIO MTIME UART0 UART1 SPI TWI PWM WDT CFS SLINK NEOLED XIRQ <6>
../rtl/core/neorv32_top.vhd:370:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: Boot configuration: Direct boot from memory (processor-internal IMEM).
../rtl/core/neorv32_top.vhd:394:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: Implementing on-chip debugger (OCD).
../rtl/core/neorv32_cpu.vhd:169:3:@0ms:(assertion note): NEORV32 CPU ISA Configuration (MARCH): RV32IMACU_Zbb_Zicsr_Zifencei_Zfinx_Debug
../rtl/core/neorv32_cpu.vhd:189:3:@0ms:(assertion note): NEORV32 CPU CONFIG NOTE: Implementing NO dedicated hardware reset for uncritical registers (default, might reduce area). Set package constant  = TRUE to configure a DEFINED reset value for all CPU registers.
../rtl/core/neorv32_imem.vhd:107:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: Implementing processor-internal IMEM as ROM (16384 bytes), pre-initialized with application (4612 bytes).
../rtl/core/neorv32_dmem.vhd:89:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: Implementing processor-internal DMEM (RAM, 8192 bytes).
../rtl/core/neorv32_wishbone.vhd:136:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: External Bus Interface - Implementing STANDARD Wishbone protocol.
../rtl/core/neorv32_wishbone.vhd:140:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: External Bus Interface - Implementing auto-timeout (255 cycles).
../rtl/core/neorv32_wishbone.vhd:144:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: External Bus Interface - Implementing LITTLE-endian byte order.
../rtl/core/neorv32_wishbone.vhd:148:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: External Bus Interface - Implementing registered RX path.
../rtl/core/neorv32_slink.vhd:161:3:@0ms:(assertion note): NEORV32 PROCESSOR CONFIG NOTE: Implementing 8 RX and 8 TX stream links.
<7>
                                                                                       ##
                                                                                       ##         ##   ##   ##
 ##     ##   #########   ########    ########   ##      ##   ########    ########      ##       ################
####    ##  ##          ##      ##  ##      ##  ##      ##  ##      ##  ##      ##     ##     ####            ####
## ##   ##  ##          ##      ##  ##      ##  ##      ##          ##         ##      ##       ##   ######   ##
##  ##  ##  #########   ##      ##  #########   ##      ##      #####        ##        ##     ####   ######   ####
##   ## ##  ##          ##      ##  ##    ##     ##    ##           ##     ##          ##       ##   ######   ##
##    ####  ##          ##      ##  ##     ##     ##  ##    ##      ##   ##            ##     ####            ####
##     ##    #########   ########   ##      ##      ##       ########   ##########     ##       ################
                                                                                       ##         ##   ##   ##
                                                                                       ##
Hello world! :)
----
<1> Notifier that "simulation mode" of UART0 is enabled (by the `USER_FLAGS+=-DUART0_SIM_MODE` makefile flag). All UART0 output is send to the simulator console.
<2> Final executable size (`text`) and _static_ data memory requirements (`data`, `bss`).
<3> The application code is _installed_ as pre-initialized IMEM. This is the default approach for simulation.
<4> A note regarding UART "simulation mode", but we have already enabled that.
<5> List of (default) arguments that were send to the simulator. Here: maximum simulation time (10ms).
<6> "Sanity checks" from the core's VHDL files. These reports give some brief information about the SoC/CPU configuration (-> generics). If there are problems with the current configuration, an ERROR will appear.
<7> Execution of the actual program starts.
 
 
:sectnums:
=== Advanced Simulation using VUnit
 
https://vunit.github.io/[VUnit] is an open source unit testing framework for VHDL/SystemVerilog.
It allows continuous and automated testing of HDL code by complementing traditional testing methodologies.
The motto of VUnit is _"testing early and often"_ through automation.
 
VUnit is composed by a http://vunit.github.io/py/ui.html[Python interface] and multiple optional
http://vunit.github.io/vhdl_libraries.html[VHDL libraries].
The Python interface allows declaring sources and simulation options, and it handles the compilation, execution and
gathering of the results regardless of the simulator used.
That allows having a single `run.py` script to be used with GHDL, ModelSim/QuestaSim, Riviera PRO, etc.
On the other hand, the VUnit's VHDL libraries provide utilities for assertions, logging, having virtual queues, handling CSV files, etc.
The http://vunit.github.io/verification_components/user_guide.html[Verification Component Library] uses those features
for abstracting away bit-toggling when verifying standard interfaces such as Wishbone, AXI, Avalon, UARTs, etc.
 
Testbench sources in `sim` (such as `sim/neorv32_tb.vhd` and `sim/uart_rx*.vhd`) use VUnit's VHDL libraries for testing
NEORV32 and peripherals.
The entry-point for executing the tests is `sim/run.py`.
 
[source, bash]
----
# ./sim/run.py -l
neorv32.neorv32_tb.all
Listed 1 tests
 
# ./sim/run.py -v
Compiling into neorv32:   rtl/core/neorv32_uart.vhd                                                                                            passed
Compiling into neorv32:   rtl/core/neorv32_twi.vhd                                                                                             passed
Compiling into neorv32:   rtl/core/neorv32_trng.vhd                                                                                            passed
...
----
 
See http://vunit.github.io/user_guide.html[VUnit: User Guide] and http://vunit.github.io/cli.html[VUnit: Command Line Interface] for further info about VUnit's features.
 
 
<<<
// ####################################################################################################################
:sectnums:
== Building the Documentation
 
The documentation (datasheet + user guide) is written using `asciidoc`. The according source files
can be found in `docs/...`. The documentation of the software framework is written _in-code_ using `doxygen`.
 
A makefiles in the project's `docs` directory is provided to build all of the documentation as HTML pages
or as PDF documents.
 
[TIP]
Pre-rendered PDFs are available online as _nightly pre-releases_: https://github.com/stnolting/neorv32/releases.
The HTML-based documentation is also available online at the project's https://stnolting.github.io/neorv32/[GitHub Pages].
 
The makefile provides a help target to show all available build options and their according outputs.
 
[source,bash]
----
neorv32/docs$ make help
----
 
.Example: Generate HTML documentation (data sheet) using `asciidoctor`
[source,bash]
----
neorv32/docs$ make html
----
 
[TIP]
If you don't have `asciidoctor` / `asciidoctor-pdf` installed, you can still generate all the documentation using
a _docker container_ via `make container`.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Zephyr RTOS Support 🪁
 
The NEORV32 processor is supported by upstream Zephyr RTOS: https://docs.zephyrproject.org/latest/boards/riscv/neorv32/doc/index.html
 
[IMPORTANT]
The absolute path to the NEORV32 executable image generator binary (`.../neorv32/sw/image_gen`) has to be added to the `PATH` variable
so the Zephyr build system can generate executables and memory-initialization images.
 
[NOTE]
Zephyr OS port provided by GitHub user https://github.com/henrikbrixandersen[henrikbrixandersen]
(see https://github.com/stnolting/neorv32/discussions/172). ❤️
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== FreeRTOS Support
 
A NEORV32-specific port and a simple demo for FreeRTOS (https://github.com/FreeRTOS/FreeRTOS) are
available in the `sw/example/demo_freeRTOS` folder. See the according documentation (`sw/example/demo_freeRTOS/README.md`)
for more information.
 
 
 
// ####################################################################################################################
:sectnums:
== RISC-V Architecture Test Framework
 
The NEORV32 Processor passes the according tests provided by the official RISC-V Architecture Test Suite
(V2.0+), which is available online at GitHub: https://github.com/riscv/riscv-arch-test
 
All files required for executing the test framework on a simulated instance of the processor (including port
files) are located in the `sw/isa-test` folder of the NEORV32 repository. The test framework is executed via the
`sim/run_riscv_arch_test.sh` script. Take a look at the provided `sim/README.md`
(https://github.com/stnolting/neorv32/tree/master/sim[online at GitHub])
file for more information on how to run the tests and how testing is conducted in detail.
 
 
 
<<<
// ####################################################################################################################
:sectnums:
== Debugging using the On-Chip Debugger
 
The NEORV32 on-chip debugger allows _online_ in-system debugging via an external JTAG access port from a
host machine. The general flow is independent of the host machine's operating system. However, this tutorial uses
Windows and Linux (Ubuntu on Windows) in parallel.
 
[TIP]
See datasheet section https://stnolting.github.io/neorv32/#_on_chip_debugger_ocd[On Chip Debugger (OCD)]
for more information.
 
[NOTE]
This tutorial uses `gdb` to **directly upload an executable** to the processor. If you are using the default
processor setup _with_ internal instruction memory (IMEM) make sure it is implemented as RAM
(_INT_BOOTLOADER_EN_ generic = true).
 
[IMPORTANT]
The on-chip debugger is only implemented if the _ON_CHIP_DEBUGGER_EN_ generic is set _true_. Furthermore, it requires
the `Zicsr` and `Zifencei` CPU extension to be implemented (top generics _CPU_EXTENSION_RISCV_Zicsr_
and _CPU_EXTENSION_RISCV_Zifencei_ = true).
 
 
:sectnums:
=== Hardware Requirements
 
Make sure the on-chip debugger of your NEORV32 setups is implemented (_ON_CHIP_DEBUGGER_EN_ generic = true).
Connect a JTAG adapter to the NEORV32 `jtag_*` interface signals. If you do not have a full-scale JTAG adapter, you can
also use a FTDI-based adapter like the "FT2232H-56Q Mini Module", which is a simple and inexpensive FTDI breakout board.
 
.JTAG pin mapping
[cols="^3,^2,^2"]
[options="header",grid="rows"]
|=======================
| NEORV32 top signal | JTAG signal | FTDI port
| `jtag_tck_i`       | TCK         | D0
| `jtag_tdi_i`       | TDI         | D1
| `jtag_tdo_o`       | TDO         | D2
| `jtag_tms_i`       | TMS         | D3
| `jtag_trst_i`      | TRST        | D4
|=======================
 
[TIP]
The low-active JTAG _test reset_ (TRST) signals is _optional_ as a reset can also be triggered via the TAP controller.
If TRST is not used make sure to pull the signal _high_.
 
 
:sectnums:
=== OpenOCD
 
The NEORV32 on-chip debugger can be accessed using the https://github.com/riscv/riscv-openocd[RISC-V port of OpenOCD].
Prebuilt binaries can be obtained - for example - from https://www.sifive.com/software[SiFive]. A pre-configured
OpenOCD configuration file (`sw/openocd/openocd_neorv32.cfg`) is available that allows easy access to the NEORV32 CPU.
 
[NOTE]
You might need to adapt `ftdi_vid_pid`, `ftdi_channel` and `ftdi_layout_init` in `sw/openocd/openocd_neorv32.cfg`
according to your interface chip and your operating system.
 
[TIP]
If you want to modify the JTAG clock speed (via `adapter speed` in `sw/openocd/openocd_neorv32.cfg`) make sure to meet
the clock requirements noted in https://stnolting.github.io/neorv32/#_debug_module_dm[Documentation: Debug Transport Module (DTM)].
 
To access the processor using OpenOCD, open a terminal and start OpenOCD with the pre-configured configuration file.
 
.Connecting via OpenOCD (on Windows)
[source, bash]
--------------------------
N:\Projects\neorv32\sw\openocd>openocd -f openocd_neorv32.cfg
Open On-Chip Debugger 0.11.0-rc1+dev (SiFive OpenOCD 0.10.0-2020.12.1)
Licensed under GNU GPL v2
For bug reports:
        https://github.com/sifive/freedom-tools/issues
1
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 1000 kHz
Info : JTAG tap: neorv32.cpu tap/device found: 0x0cafe001 (mfg: 0x000 (), part: 0xcafe, ver: 0x0)
Info : datacount=1 progbufsize=2
Info : Disabling abstract command reads from CSRs.
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40801105
Info : starting gdb server for neorv32.cpu.0 on 3333
Info : Listening on port 3333 for gdb connections
--------------------------
 
OpenOCD has successfully connected to the NEORV32 on-chip debugger and has examined the CPU (showing the content of
the `misa` CSRs). Now you can use `gdb` to connect via port 3333.
 
 
:sectnums:
=== Debugging with GDB
 
This guide uses the simple "blink example" from `sw/example/blink_led` as simplified test application to
show the basics of in-system debugging.
 
At first, the application needs to be compiled. We will use the minimal machine architecture configuration
(`rv32i`) here to be independent of the actual processor/CPU configuration.
Navigate to `sw/example/blink_led` and compile the application:
 
.Compile the test application
[source, bash]
--------------------------
.../neorv32/sw/example/blink_led$ make MARCH=rv32i USER_FLAGS+=-g clean_all all
--------------------------
 
.Adding debug symbols to the executable
[NOTE]
`USER_FLAGS+=-g` passes the `-g` flag to the compiler so it adds debug information/symbols
to the generated ELF file. This is optional but will provide more sophisticated information for debugging
(like source file line numbers).
 
This will generate an ELF file `main.elf` that contains all the symbols required for debugging.
Furthermore, an assembly listing file `main.asm` is generated that we will use to define breakpoints.
 
Open another terminal in `sw/example/blink_led` and start `gdb`.
The GNU debugger is part of the toolchain (see <<_software_toolchain_setup>>).
 
.Starting GDB (on Linux (Ubuntu on Windows))
[source, bash]
--------------------------
.../neorv32/sw/example/blink_led$ riscv32-unknown-elf-gdb
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "--host=x86_64-pc-linux-gnu --target=riscv32-unknown-elf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
    .
 
For help, type "help".
Type "apropos word" to search for commands related to "word".
(gdb)
--------------------------
 
Now connect to OpenOCD using the default port 3333 on your machine.
We will use the previously generated ELF file `main.elf` from the `blink_led` example.
Finally, upload the program to the processor and start debugging.
 
[NOTE]
The executable that is uploaded to the processor is **not** the default NEORV32 executable (`neorv32_exe.bin`) that
is used for uploading via the bootloader. Instead, all the required sections (like `.text`) are extracted from `mail.elf`
by GDB and uploaded via the debugger's indirect memory access.
 
.Running GDB
[source, bash]
--------------------------
(gdb) target extended-remote localhost:3333 <1>
Remote debugging using localhost:3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0xffff0c94 in ?? () <2>
(gdb) file main.elf <3>
A program is being debugged already.
Are you sure you want to change the file? (y or n) y
Reading symbols from main.elf...
(gdb) load <4>
Loading section .text, size 0xd0c lma 0x0
Loading section .rodata, size 0x39c lma 0xd0c
Start address 0x00000000, load size 4264
Transfer rate: 43 KB/sec, 2132 bytes/write.
(gdb)
--------------------------
<1> Connect to OpenOCD
<2> The CPU was still executing code from the bootloader ROM - but that does not matter here
<3> Select `mail.elf` from the `blink_led` example
<4> Upload the executable
 
After the upload, GDB will make the processor jump to the beginning of the uploaded executable
(by default, this is the beginning of the instruction memory at `0x00000000`) skipping the bootloader
and halting the CPU right before executing the `blink_led` application.
 
 
:sectnums:
==== Breakpoint Example
 
The following steps are just a small showcase that illustrate a simple debugging scheme.
 
While compiling `blink_led`, an assembly listing file `main.asm` was generated.
Open this file with a text editor to check out what the CPU is going to do when resumed.
 
The `blink_led` example implements a simple counter on the 8 lowest GPIO output ports. The program uses
"busy wait" to have a visible delay between increments. This waiting is done by calling the `neorv32_cpu_delay_ms`
function. We will add a _breakpoint_ right at the end of this wait function so we can step through the iterations
of the counter.
 
.Cut-out from `main.asm` generated from the `blink_led` example
[source, assembly]
--------------------------
00000688 <__neorv32_cpu_delay_ms_end>:
 688:   01c12083                lw      ra,28(sp)
 68c:   02010113                addi    sp,sp,32
 690:   00008067                ret
--------------------------
 
The very last instruction of the `neorv32_cpu_delay_ms` function is `ret` (= return)
at hexadecimal `690` in this example. Add this address as _breakpoint_ to GDB.
 
[NOTE]
The address might be different if you use a different version of the software framework or
if different ISA options are configured.
 
.Adding a GDB breakpoint
[source, bash]
--------------------------
(gdb) b * 0x690
Breakpoint 1 at 0x690
--------------------------
 
.How do breakpoints work?
[TIP]
The NEORV32 on-chip debugger does not provide any hardware breakpoints (RISC-V "trigger modules") that compare an address like the PC
with a predefined value. Instead, gdb will modify the actual executable in IMEM: the actual instruction at the address
of the specified breakpoint is replaced by a `break` / `c.break` instruction. Whenever execution reaches this instruction, debug mode is
re-entered and the debugger restores the original instruction at this address to maintain original program behavior.
 
Now execute `c` (= continue). The CPU will resume operation until it hits the break-point.
By this we can "step" from increment to increment.
 
.Iterating from breakpoint to breakpoint
[source, bash]
--------------------------
Breakpoint 1 at 0x690
(gdb) c
Continuing.
 
Breakpoint 1, 0x00000690 in neorv32_cpu_delay_ms ()
(gdb) c
Continuing.
 
Breakpoint 1, 0x00000690 in neorv32_cpu_delay_ms ()
(gdb) c
Continuing.
--------------------------
 
include::../legal.adoc[]

Line No.	Rev	Author	Line
1	60	zero_gravi	`Let's Get It Started!`
2
3	63	zero_gravi	This user guide uses the NEORV32 project _as is_ from the official `neorv32` repository.
4			`To make your first NEORV32 project run, follow the guides from the upcoming sections. It is recommended to`
5			`follow these guides step by step and eventually in the presented order.`
6	60	zero_gravi
7	63	zero_gravi	`[TIP]`
8			`This guide uses the minimalistic and platform/toolchain agnostic SoC test setups from`
9			`rtl/test_setups` for illustration. You can use one of the provided test setups for
10			your first FPGA tests. Alternatively, have a look at the `setups` folder,
11			`which provides more sophisticated example setups for various FPGAs/FPGA boards and toolchains.`
12
13
14	60	zero_gravi	`:sectnums:`
15	61	zero_gravi	`== Software Toolchain Setup`
16	60	zero_gravi
17	61	zero_gravi	`To compile (and debug) executables for the NEORV32 a RISC-V toolchain is required.`
18			`There are two possibilities to get this:`
19	60	zero_gravi
20	63	zero_gravi	`1. Download and _build_ the official RISC-V GNU toolchain yourself.`
21	61	zero_gravi	`2. Download and install a prebuilt version of the toolchain; this might also done via the package manager / app store of your OS`
22	60	zero_gravi
23	63	zero_gravi	`[NOTE]`
24			The default toolchain prefix (`RISCV_PREFIX` variable) for this project is `riscv32-unknown-elf-`. Of course you can use any other RISC-V
25			toolchain (like `riscv64-unknown-elf-`) that is capable to emit code for a `rv32` architecture. Just change `RISCV_PREFIX`
26			`according to your needs.`
27	60	zero_gravi
28
29			`:sectnums:`
30			`=== Building the Toolchain from Scratch`
31
32	65	zero_gravi	`To build the toolchain by yourself you can follow the guide from the official https://github.com/riscv-collab/riscv-gnu-toolchain GitHub page.`
33	61	zero_gravi	`You need to make sure the generated toolchain fits the architecture of the NEORV32 core. To get a toolchain that even supports minimal`
34			ISA extension configurations, it is recommend to compile for `rv32i` only. Please note that this minimal ISA also provides further ISA
35	65	zero_gravi	extensions like `m` or `c`. Of course you can use a _multilib_ approach to generate toolchains for several target ISAs at once.
36	60	zero_gravi
37	61	zero_gravi	.Configuring GCC build for `rv32i` (minimal ISA)
38	60	zero_gravi	`[source,bash]`
39			`----`
40	65	zero_gravi	`riscv-gnu-toolchain$ ./configure --prefix=/opt/riscv --with-arch=rv32i --with-abi=ilp32`
41	60	zero_gravi	`riscv-gnu-toolchain$ make`
42			`----`
43
44	63	zero_gravi	`[IMPORTANT]`
45	65	zero_gravi	Keep in mind that - for instance - a toolchain build with `--with-arch=rv32imc` only provides library code compiled with
46	63	zero_gravi	compressed (`C`) and `mul`/`div` instructions (`M`)! Hence, this code cannot be executed (without
47			`emulation) on an architecture without these extensions!`
48	60	zero_gravi
49	63	zero_gravi
50	60	zero_gravi	`:sectnums:`
51			`=== Downloading and Installing a Prebuilt Toolchain`
52
53			`Alternatively, you can download a prebuilt toolchain.`
54
55	61	zero_gravi	`:sectnums:`
56			`==== Use The Toolchain I have Build`
57	60	zero_gravi
58	61	zero_gravi	`I have compiled a GCC toolchain on a 64-bit x86 Ubuntu (Ubuntu on Windows, actually) and uploaded it to`
59	60	zero_gravi	`GitHub. You can directly download the according toolchain archive as single _zip-file_ within a packed`
60	61	zero_gravi	`release from https://github.com/stnolting/riscv-gcc-prebuilt.`
61	60	zero_gravi
62			`Unpack the downloaded toolchain archive and copy the content to a location in your file system (e.g.`
63			`/opt/riscv`). More information about downloading and installing my prebuilt toolchains can be found in
64			`the repository's README.`
65
66
67	61	zero_gravi	`:sectnums:`
68			`==== Use a Third Party Toolchain`
69
70	60	zero_gravi	`Of course you can also use any other prebuilt version of the toolchain. There are a lot RISC-V GCC packages out there -`
71	61	zero_gravi	`even for Windows. On Linux system you might even be able to fetch a toolchain via your distribution's package manager.`
72	60	zero_gravi
73			`[IMPORTANT]`
74			Make sure the toolchain can (also) emit code for a `rv32i` architecture, uses the `ilp32` or `ilp32e` ABI and was not build using
75			CPU extensions that are not supported by the NEORV32 (like `D`).
76
77
78			`:sectnums:`
79			`=== Installation`
80
81	61	zero_gravi	Now you have the toolchain binaries. The last step is to add them to your `PATH` environment variable (if you have not
82			already done so): make sure to add the _binaries_ folder (`bin`) of your toolchain.
83	60	zero_gravi
84			`[source,bash]`
85			`----`
86			`$ export PATH:$PATH:/opt/riscv/bin`
87			`----`
88
89			You should add this command to your `.bashrc` (if you are using bash) to automatically add the RISC-V
90			`toolchain at every console start.`
91
92			`:sectnums:`
93			`=== Testing the Installation`
94
95			`To make sure everything works fine, navigate to an example project in the NEORV32 example folder and`
96			`execute the following command:`
97
98			`[source,bash]`
99			`----`
100			`neorv32/sw/example/blink_led$ make check`
101			`----`
102
103	66	zero_gravi	`This will test all the tools required for generating NEORV32 executables.`
104	61	zero_gravi	Everything is working fine if `Toolchain check OK` appears at the end.
105	60	zero_gravi
106
107
108			`<<<`
109			`// ####################################################################################################################`
110			`:sectnums:`
111			`== General Hardware Setup`
112
113	63	zero_gravi	`This guide shows the basics of setting up a NEORV32 project for FPGA implementation (or simulation only)`
114			`_from scratch_. It uses a _simplified_ test "SoC" setup of the processor to keeps things simple at the beginning.`
115			`This simple setup is intended for evaluation or as "hello world" project to check out the NEORV32`
116			`on _your_ FPGA board.`
117	60	zero_gravi
118			`[TIP]`
119	63	zero_gravi	`If you want to use a more sophisticated pre-defined setup to start with, check out the`
120			`setups` folder, which provides example setups for various FPGA, boards and toolchains.
121	60	zero_gravi
122	63	zero_gravi	`The NEORV32 project features two minimalistic pre-configured test setups in`
123			https://github.com/stnolting/neorv32/blob/master/rtl/test_setups[`rtl/test_setups`].
124			`Both test setups only implement very basic processor and CPU features.`
125			`The main difference between the two setups is the processor boot concept - so how to get a software executable`
126			`_into_ the processor:`
127	60	zero_gravi
128	63	zero_gravi	* `rtl/test_setups/neorv32_testsetup_approm.vhd`: this setup does not require a connection via UART. The
129			`software executable is "installed" into the bitstream to initialize a read-only memory. Use this setup`
130			`if your FPGA board does _not_ provide a UART interface.`
131			* `rtl/test_setups/neorv32_testsetup_bootloader.vhd`: this setups uses the UART and the default NEORV32
132			`bootloader to upload new software executables. Use this setup if your board _does_ provide a UART interface.`
133
134			.NEORV32 "hello world" test setup (`rtl/test_setups/neorv32_testsetup_bootloader.vhd`)
135			`image::neorv32_test_setup.png[align=center]`
136
137			`.External Clock Source`
138			`[NOTE]`
139			`These test setups are intended to be directly used as design top entity. Of course you can also instantiate them`
140			`into another design unit. If your FPGA board only provides _very fast_ external clock sources (like on the FOMU board)`
141			`you might need to add clock management components (PLLs, DCMs, MMCMs, ...) to the test setup or to the according top entity`
142			`if you instantiate one of the test setups.`
143
144	61	zero_gravi	`[start=1]`
145	60	zero_gravi	`. Create a new project with your FPGA EDA tool of choice.`
146	63	zero_gravi	. Add all VHDL files from the project's `rtl/core` folder to your project.
147	64	zero_gravi
148			`.Internal Memories`
149			`[IMPORTANT]`
150	68	zero_gravi	For a _general_ first setup (technology-independent) use the `*.default.vhd` memory architectures for the internal memories
151			(IMEM and DMEM). These are located in `rtl/core/mem` so make sure to add the files to your project, too. +
152	64	zero_gravi	`+`
153			`If synthesis cannot efficiently map those default memory descriptions to the available memory resources, you can later replace the`
154			default memory architectures by optimized platform-specific memory architectures. Example: The `setups/radiant/UPduino_v3`
155			`example setup uses optimized memory primitives. Hence, it does not include the default memory architectures from`
156			`rtl/core/mem` as these are replaced by device-specific implementations. However, it still has to include the entity
157			definitions from `rtl/core`.
158
159			`[start=3]`
160	61	zero_gravi	. Make sure to add all the rtl files to a new library called `neorv32`. If your FPGA tools does not
161			`provide a field to enter the library name, check out the "properties" menu of the added rtl files.`
162	64	zero_gravi
163			`.Compile order`
164			`[NOTE]`
165			`Some tools (like Lattice Radiant) might require a _manual compile order_ of the VHDL source files to identify the dependencies.`
166			The package file `neorv32_package.vhd` should be analyzed first followed by the memory image files (`neorv32_application_imagevhd`
167			and `neorv32_bootloader_image.vhd`) and the entity-only files (`neorv32_*mem.entity.vhd`).
168
169			`[start=4]`
170	63	zero_gravi	. The `rtl/core/neorv32_top.vhd` VHDL file is the top entity of the NEORV32 processor, which can be
171			`instantiated into the "real" project. However, in this tutorial we will use one of the pre-defined`
172			test setups from `rtl/test_setups` (see above).
173	61	zero_gravi
174			`[IMPORTANT]`
175			Make sure to include the `neorv32` package into your design when instantiating the processor: add
176			`library neorv32;` and `use neorv32.neorv32_package.all;` to your design unit.
177
178			`[start=5]`
179	63	zero_gravi	`. Add the pre-defined test setup of choice to the project, too, and select it as _top entity_.`
180			`. The entity of both test setups`
181			`provide a minimal set of configuration generics, that might have to be adapted to match your FPGA and board:`
182	60	zero_gravi
183	63	zero_gravi	`.Test setup entity - configuration generics`
184	60	zero_gravi	`[source,vhdl]`
185			`----`
186	63	zero_gravi	`generic (`
187			`-- adapt these for your setup --`
188			`CLOCK_FREQUENCY : natural := 100000000; <1>`
189			`MEM_INT_IMEM_SIZE : natural := 16*1024; <2>`
190			`MEM_INT_DMEM_SIZE : natural := 8*1024 <3>`
191			`);`
192	60	zero_gravi	`----`
193	61	zero_gravi	<1> Clock frequency of `clk_i` signal in Hertz
194			`<2> Default size of internal instruction memory: 16kB`
195			`<3> Default size of internal data memory: 8kB`
196	60	zero_gravi
197	63	zero_gravi	`[start=7]`
198	65	zero_gravi	`. If you feel like it - or if your FPGA does not provide sufficient resources - you can modify the`
199			_memory sizes_ (`MEM_INT_IMEM_SIZE` and `MEM_INT_DMEM_SIZE` - marked with notes "2" and "3"). But as mentioned
200	63	zero_gravi	`above, let's keep things simple at first and use the standard configuration for now.`
201			`. There is one generic that _has to be set according to your FPGA board_ setup: the actual clock frequency`
202			of the top's clock input signal (`clk_i`). Use the `CLOCK_FREQUENCY` generic to specify your clock source's
203			`frequency in Hertz (Hz).`
204	60	zero_gravi
205			`[NOTE]`
206	63	zero_gravi	If you have changed the default memory configuration (`MEM_INT_IMEM_SIZE` and `MEM_INT_DMEM_SIZE` generics)
207	65	zero_gravi	`keep those new sizes in mind - these values are required for setting`
208	60	zero_gravi	`up the software framework in the next section <<_general_software_framework_setup>>.`
209
210	63	zero_gravi	`[start=9]`
211	60	zero_gravi	`. Depending on your FPGA tool of choice, it is time to assign the signals of the test setup top entity to`
212	63	zero_gravi	`the according pins of your FPGA board. All the signals can be found in the entity declaration of the`
213			`corresponding test setup:`
214	60	zero_gravi
215	63	zero_gravi	.Entity signals of `neorv32_testsetup_approm.vhd`
216	60	zero_gravi	`[source,vhdl]`
217			`----`
218			`port (`
219			`-- Global control --`
220	63	zero_gravi	`clk_i : in std_ulogic; -- global clock, rising edge`
221			`rstn_i : in std_ulogic; -- global reset, low-active, async`
222	60	zero_gravi	`-- GPIO --`
223	63	zero_gravi	`gpio_o : out std_ulogic_vector(7 downto 0) -- parallel output`
224			`);`
225			`----`
226
227			.Entity signals of `neorv32_testsetup_bootloader.vhd`
228			`[source,vhdl]`
229			`----`
230			`port (`
231			`-- Global control --`
232			`clk_i : in std_ulogic; -- global clock, rising edge`
233			`rstn_i : in std_ulogic; -- global reset, low-active, async`
234			`-- GPIO --`
235	60	zero_gravi	`gpio_o : out std_ulogic_vector(7 downto 0); -- parallel output`
236			`-- UART0 --`
237			`uart0_txd_o : out std_ulogic; -- UART0 send data`
238	63	zero_gravi	`uart0_rxd_i : in std_ulogic -- UART0 receive data`
239			`);`
240	60	zero_gravi	`----`
241
242	63	zero_gravi	`.Signal Polarity`
243			`[NOTE]`
244			If your FPGA board has inverse polarity for certain input/output you can add `not` gates. Example: The reset signal
245			`rstn_i` is low-active by default; the LEDs connected to `gpio_o` high-active by default.
246			`You can do this in your board top if you instantiate the test setup,`
247			or _inside_ the test setup if this is your top entity (low-active LEDs example: `gpio_o <= NOT con_gpio_o(7 downto 0);`).
248
249			`[start=10]`
250	60	zero_gravi	. Attach the clock input `clk_i` to your clock source and connect the reset line `rstn_i` to a button of
251	65	zero_gravi	`your FPGA board. Check whether it is low-active or high-active - the reset signal of the processor is`
252	60	zero_gravi	`low-active, so maybe you need to invert the input signal.`
253	63	zero_gravi	. If possible, connected _at least_ bit `0` of the GPIO output port `gpio_o` to a LED (see "Signal Polarity" note above).
254			. Finally, if your are using the UART-based test setup (`neorv32_testsetup_bootloader.vhd`)
255			connect the UART communication signals `uart0_txd_o` and `uart0_rxd_i` to the host interface (e.g. USB-UART converter).
256	60	zero_gravi	`. Perform the project HDL compilation (synthesis, mapping, bitstream generation).`
257	61	zero_gravi	`. Program the generated bitstream into your FPGA and press the button connected to the reset signal.`
258	63	zero_gravi	. Done! The LED at `gpio_o(0)` should be flashing now.
259	60	zero_gravi
260	63	zero_gravi	`[TIP]`
261			`After the GCC toolchain for compiling RISC-V source code is ready (chapter <<_general_software_framework_setup>>),`
262			`you can advance to one of these chapters to learn how to get a software executable into your processor setup:`
263			* If you are using the `neorv32_testsetup_approm.vhd` setup: See section <<_installing_an_executable_directly_into_memory>>.
264			* If you are using the `neorv32_testsetup_bootloader.vhd` setup: See section <<_uploading_and_starting_of_a_binary_executable_image_via_uart>>.
265	60	zero_gravi
266
267	63	zero_gravi
268	60	zero_gravi	`<<<`
269			`// ####################################################################################################################`
270			`:sectnums:`
271			`== General Software Framework Setup`
272
273	61	zero_gravi	`To allow executables to be _actually executed_ on the NEORV32 Processor the configuration of the software framework`
274			`has to be aware to the hardware configuration. This guide focuses on the memory configuration. To enabled`
275	66	zero_gravi	`certain CPU ISA features refer to the <<_enabling_risc_v_cpu_extensions>> section.`
276	60	zero_gravi
277	61	zero_gravi	`[TIP]`
278			`If you have not changed the _default_ memory configuration in section <<_general_hardware_setup>>`
279			`you are already done and you can skip the rest of this guide.`
280
281	60	zero_gravi	`[start=1]`
282			. Open the NEORV32 linker script `sw/common/neorv32.ld` with a text editor. Right at the
283	61	zero_gravi	beginning of this script you will find the `MEMORY` configuration listing the different memory section:
284	60	zero_gravi
285	61	zero_gravi	.Cut-out of the linker script `neorv32.ld`: `ram` memory section configuration
286	60	zero_gravi	`[source,c]`
287			`----`
288			`MEMORY`
289			`{`
290	65	zero_gravi	`ram (rwx) : ORIGIN = 0x80000000, LENGTH = DEFINED(make_bootloader) ? 512 : 8*1024 <1>`
291	61	zero_gravi	`...`
292	60	zero_gravi	`----`
293	61	zero_gravi	`<1> Size of the data memory address space (right-most value) (internal/external DMEM); here 8kB`
294	60	zero_gravi
295	61	zero_gravi	`[start=2]`
296			. We only need to change the `ram` section, which presents the available data address space.
297			If you have changed the DMEM (_MEM_INT_DMEM_SIZE_ generic) size adapt the `LENGTH` parameter of the `ram`
298			section (here: `8*1024`) so it is equal to your DMEM hardware configuration.
299	60	zero_gravi
300	61	zero_gravi	`[IMPORTANT]`
301			`Make sure you only modify the _right-most_ value (here: 8*1024)! +`
302			The "`512`" are not relevant for the application.
303
304	60	zero_gravi	`[start=3]`
305	61	zero_gravi	`. Done! Save your changes and close the linker script.`
306	60	zero_gravi
307	61	zero_gravi	`.Advanced: Section base address and size`
308	60	zero_gravi	`[IMPORTANT]`
309	61	zero_gravi	`More information can be found in the datasheet section https://stnolting.github.io/neorv32/#_address_space[Address Space].`
310	60	zero_gravi
311
312
313			`<<<`
314			`// ####################################################################################################################`
315			`:sectnums:`
316			`== Application Program Compilation`
317
318	62	zero_gravi	`This guide shows how to compile an example C-code application into a NEORV32 executable that`
319	61	zero_gravi	`can be uploaded via the bootloader or the on-chip debugger.`
320
321			`[IMPORTANT]`
322			`If your FPGA board does not provide such an interface - don't worry!`
323			`Section <<_installing_an_executable_directly_into_memory>> shows how to`
324			`run custom programs on your FPGA setup without having a UART.`
325
326	60	zero_gravi	`[start=1]`
327	61	zero_gravi	`. Open a terminal console and navigate to one of the project's example programs. For instance, navigate to the`
328			simple `sw/example_blink_led` example program. This program uses the NEORV32 GPIO module to display
329	60	zero_gravi	an 8-bit counter on the lowest eight bit of the `gpio_o` output port.
330			`. To compile the project and generate an executable simply execute:`
331
332			`[source,bash]`
333			`----`
334	61	zero_gravi	`neorv32/sw/example/blink_led$ make clean_all exe`
335	60	zero_gravi	`----`
336
337			`[start=3]`
338	66	zero_gravi	. We are using the `clean_all` target to make sure everything is re-build.
339	60	zero_gravi	`. This will compile and link the application sources together with all the included libraries. At the end,`
340	61	zero_gravi	your application is transformed into an ELF file (`main.elf`). The _NEORV32 image generator_ (in `sw/image_gen`)
341			`takes this file and creates a final executable. The makefile will show the resulting memory utilization and`
342			`the executable size:`
343	60	zero_gravi
344			`[source,bash]`
345			`----`
346	61	zero_gravi	`neorv32/sw/example/blink_led$ make clean_all exe`
347	60	zero_gravi	`Memory utilization:`
348	61	zero_gravi	`text data bss dec hex filename`
349			`3176 0 120 3296 ce0 main.elf`
350			`Compiling ../../../sw/image_gen/image_gen`
351	60	zero_gravi	`Executable (neorv32_exe.bin) size in bytes:`
352	62	zero_gravi	`3188`
353	60	zero_gravi	`----`
354
355	61	zero_gravi	`[start=5]`
356			. That's it. The `exe` target has created the actual executable `neorv32_exe.bin` in the current folder
357			`that is ready to be uploaded to the processor.`
358	60	zero_gravi
359			`[TIP]`
360	61	zero_gravi	The compilation process will also create a `main.asm` assembly listing file in the current folder, which
361			`shows the actual assembly code of the application.`
362	60	zero_gravi
363
364
365			`<<<`
366			`// ####################################################################################################################`
367			`:sectnums:`
368			`== Uploading and Starting of a Binary Executable Image via UART`
369
370	61	zero_gravi	`Follow this guide to use the bootloader to upload an executable via UART.`
371	60	zero_gravi
372	61	zero_gravi	`[NOTE]`
373			`This concept uses the default "Indirect Boot" scenario that uses the bootloader to upload new executables.`
374			`See datasheet section https://stnolting.github.io/neorv32/#_indirect_boot[Indirect Boot] for more information.`
375	60	zero_gravi
376	61	zero_gravi	`[IMPORTANT]`
377			`If your FPGA board does not provide such an interface - don't worry!`
378			`Section <<_installing_an_executable_directly_into_memory>> shows how to`
379			`run custom programs on your FPGA setup without having a UART.`
380	60	zero_gravi
381			`[start=1]`
382	61	zero_gravi	`. Connect the primary UART (UART0) interface of your FPGA board to a serial port of your host computer.`
383	68	zero_gravi	`. Start a terminal program. In this tutorial, I am using TeraTerm for Windows. You can download it for free`
384			`from https://ttssh2.osdn.jp/index.html.en . On Linux you could use GTKTerm, which you can get here`
385			`https://github.com/Jeija/gtkterm.git (or install via your package manager).`
386	60	zero_gravi
387	68	zero_gravi
388	61	zero_gravi	`[NOTE]`
389			`_Any_ terminal program that can connect to a serial port should work. However, make sure the program`
390			`can transfer data in _raw_ byte mode without any protocol overhead around it.`
391	60	zero_gravi
392			`[start=3]`
393	61	zero_gravi	`. Open a connection to the the serial port your UART is connected to. Configure the terminal setting according to the`
394	60	zero_gravi	`following parameters:`
395
396			`* 19200 Baud`
397			`* 8 data bits`
398			`* 1 stop bit`
399			`* no parity bits`
400	61	zero_gravi	`* _no_ transmission/flow control protocol`
401			* receiver (host computer) newline on `\r\n` (carriage return & newline)
402	60	zero_gravi
403			`[start=4]`
404	61	zero_gravi	`. Also make sure that single chars are send from your computer _without_ any consecutive "new line" or "carriage`
405	60	zero_gravi	`return" commands (this is highly dependent on your terminal application of choice, TeraTerm only`
406			`sends the raw chars by default).`
407			`. Press the NEORV32 reset button to restart the bootloader. The status LED starts blinking and the`
408			`bootloader intro screen appears in your console. Hurry up and press any key (hit space!) to abort the`
409			`automatic boot sequence and to start the actual bootloader user interface console.`
410
411			`.Bootloader console; aborted auto-boot sequence`
412			`[source,bash]`
413			`----`
414			`<< NEORV32 Bootloader >>`
415
416			`BLDV: Mar 23 2021`
417			`HWV: 0x01050208`
418			`CLK: 0x05F5E100`
419			`MISA: 0x40901105`
420			`ZEXT: 0x00000023`
421			`PROC: 0x0EFF0037`
422			`IMEM: 0x00004000 bytes @ 0x00000000`
423			`DMEM: 0x00002000 bytes @ 0x80000000`
424
425			`Autoboot in 8s. Press key to abort.`
426			`Aborted.`
427
428			`Available commands:`
429			`h: Help`
430			`r: Restart`
431			`u: Upload`
432			`s: Store to flash`
433			`l: Load from flash`
434			`e: Execute`
435			`CMD:>`
436			`----`
437
438			`[start=6]`
439	61	zero_gravi	. Execute the "Upload" command by typing `u`. Now the bootloader is waiting for a binary executable to be send.
440	60	zero_gravi
441			`[source,bash]`
442			`----`
443			`CMD:> u`
444			`Awaiting neorv32_exe.bin...`
445			`----`
446
447			`[start=7]`
448	61	zero_gravi	. Use the "send file" option of your terminal program to send a NEORV32 executable (`neorv32_exe.bin`).
449			`. Again, make sure to transmit the executable in raw binary mode (no transfer protocol).`
450			`When using TeraTerm, select the "binary" option in the send file dialog.`
451	60	zero_gravi	`. If everything went fine, OK will appear in your terminal:`
452
453			`[source,bash]`
454			`----`
455			`CMD:> u`
456			`Awaiting neorv32_exe.bin... OK`
457			`----`
458
459			`[start=10]`
460	61	zero_gravi	`. The executable is now in the instruction memory of the processor. To execute the program right`
461	60	zero_gravi	now run the "Execute" command by typing `e`:
462
463			`[source,bash]`
464			`----`
465			`CMD:> u`
466			`Awaiting neorv32_exe.bin... OK`
467			`CMD:> e`
468			`Booting...`
469			`Blinking LED demo program`
470			`----`
471
472			`[start=11]`
473	61	zero_gravi	`. If everything went fine, you should see the LEDs blinking.`
474	60	zero_gravi
475	61	zero_gravi	`[NOTE]`
476			`The bootloader will print error codes if something went wrong.`
477			`See section https://stnolting.github.io/neorv32/#_bootloader[Bootloader] of the NEORV32 datasheet for more information.`
478	60	zero_gravi
479	61	zero_gravi	`[TIP]`
480			`See section <<_programming_an_external_spi_flash_via_the_bootloader>> to learn how to use an external SPI`
481			`flash for nonvolatile program storage.`
482	60	zero_gravi
483	61	zero_gravi	`[TIP]`
484			`Executables can also be uploaded via the on-chip debugger.`
485			`See section <<_debugging_with_gdb>> for more information.`
486
487
488
489	60	zero_gravi	`<<<`
490			`// ####################################################################################################################`
491			`:sectnums:`
492	61	zero_gravi	`== Installing an Executable Directly Into Memory`
493	60	zero_gravi
494	61	zero_gravi	`If you do not want to use the bootloader (or the on-chip debugger) for executable upload or if your setup does not provide`
495			`a serial interface for that, you can also directly install an application into embedded memory.`
496	60	zero_gravi
497	61	zero_gravi	`This concept uses the "Direct Boot" scenario that implements the processor-internal IMEM as ROM, which is`
498			`pre-initialized with the application's executable during synthesis. Hence, it provides _non-volatile_ storage of the`
499			`executable inside the processor. This storage cannot be altered during runtime and any source code modification of`
500			`the application requires to re-program the FPGA via the bitstream.`

Browse

Tools

Subversion Repositories neorv32

[/] [neorv32/] [trunk/] [docs/] [userguide/] [content.adoc] - Blame information for rev 68