---
title: "SPI Flash"
---

`spiflash` is a tool used to update the firmware stored in OpenTitan's embedded flash.
The tool resets OpenTitan and signals the boot ROM to enter bootstrap mode before sending the update payload.

Currently, the tool supports both Verilator and FPGA targets.

## Build instructions for spiflash tool

`spiflash` is written in C++14.

Required packages:

```console
$ sudo apt-get install libssl-dev libftdi1-dev
```

Build command for tool:

```console
$ cd ${REPO_TOP}
$ ./meson_init.sh
$ ninja -C build-out sw/host/spiflash/spiflash_export
```

## Setup instructions for Verilator and FPGA
Please refer to [Verilator]({{< relref "doc/getting_started/setup_verilator" >}}) and [FPGA]({{< relref "doc/getting_started/setup_fpga" >}}) docs for more information.

## Build target program

In this example, we build the `hello_world` as the target program.
Set `${FLASH_BIN}` to the path to the generated binary.

```console
$ cd ${REPO_TOP}
$ ninja -C build-out sw/device/examples/hello_world/hello_world_export_${DEVICE}
```

Where ${DEVICE} is one of 'sim_verilator' or 'fpga_nexysvideo'

## Run the tool with the Verilator Simulation

Run Verilator with test ROM as described in the [verilator]({{< relref "doc/getting_started/setup_verilator" >}}) getting started guide.

Run spiflash.
In this example we use SPI device `/dev/pts/3` as an example.
After the transmission is complete, you should be able to see the hello_world output in the UART console.

```console
$ cd ${REPO_TOP}
$ build-bin/sw/host/spiflash/spiflash --input ${FLASH_BIN} \
   --verilator /dev/pts/3
```

## Run the tool in FPGA

To run spiflash for an FPGA, the instructions are similar.
There is no requirement to enable the FPGA with ROM.
Note, for FPGA, the tool simply searches for a valid interface to attach.
If there are two FPGAs or multiple valid targets attached at the same time, it is possible for the tool to connect to the incorrect device.

```console
$ cd ${REPO_TOP}
$ build-bin/sw/host/spiflash/spiflash --input ${FLASH_BIN}
```

The tool supports overriding the FTDI USB device ID and serial number as follows:

```console
$ cd ${REPO_TOP}
# --dev-id: "vendor_id:product_id" in hex string format.
# --dev-sn: Serial number in string format as returned by lsusb command.
$ build-bin/sw/host/spiflash/spiflash  --dev-id=0403:6014 --dev-sn=FT2U2SK1 \
   --input=${FLASH_BIN}
```