4.8 KiB
PicoSoC - A simple example SoC using PicoRV32
This is a simple PicoRV32 example design that can run code directly from an SPI flash chip. This example design uses the Lattice iCE40-HX8K Breakout Board.
The flash is mapped to the memory region starting at 0x01000000. The reset vector is set to 0x01100000, i.e. at the 1MB offset inside the flash memory.
A small scratchpad memory (default 256 words, i.e. 1 kB) is mapped to address 0x00000000.
Run make test to run the test bench (and create testbench.vcd).
Run make prog to build the configuration bit-stream and firmware images
and upload them to a connected iCE40-HX8K Breakout Board.
| File | Description |
|---|---|
| picosoc.v | Top-level PicoSoC Verilog module |
| spimemio.v | Memory controller that interfaces to external SPI flash |
| simpleuart.v | Simple UART core connected directly to SoC TX/RX lines |
| start.s | Assembler source for firmware.hex/firmware.bin |
| firmware.c | C source for firmware.hex/firmware.bin |
| sections.lds | Linker script for firmware.hex/firmware.bin |
| hx8kdemo.v | FPGA-based example implementation on iCE40-HX8K Breakout Board |
| hx8kdemo.pcf | Pin constraints for implementation on iCE40-HX8K Breakout Board |
Memory map:
| Address Range | Description |
|---|---|
| 0x00000000 .. 0x00FFFFFF | Internal SRAM |
| 0x01000000 .. 0x01FFFFFF | External Serial Flash |
| 0x02000000 .. 0x02000003 | SPI Flash Controller Config Register |
| 0x02000004 .. 0x02000007 | UART Clock Divider Register |
| 0x02000008 .. 0x0200000B | UART Send/Recv Data Register |
| 0x03000000 .. 0xFFFFFFFF | Memory mapped user peripherals |
Reading from the addresses in the internal SRAM region beyond the end of the physical SRAM will read from the corresponding addresses in serial flash.
Reading from the UART Send/Recv Data Register will return the last received byte, or -1 (all 32 bits set) when the receive buffer is empty.
The example design (hx8kdemo.v) and generic test bench (testbench.v) have 32 GPIO pins mapped to the 32 bit word at address 0x03000000.
SPI Flash Controller Config Register:
| Bit(s) | Description |
|---|---|
| 31 | MEMIO Enable (reset=1, set to 0 to bit bang SPI commands) |
| 30:23 | Reserved (read 0) |
| 22 | DDR Enable bit (reset=0) |
| 21 | QSPI Enable bit (reset=0) |
| 20 | CRM Enable bit (reset=0) |
| 19:16 | Read latency (dummy) cycles (reset=0) |
| 15:12 | Reserved (read 0) |
| 11:8 | IO Output enable bits in bit bang mode |
| 7:6 | Reserved (read 0) |
| 5 | Chip select (CS) line in bit bang mode |
| 4 | Serial clock line in bit bang mode |
| 3:0 | IO data bits in bit bang mode |
The following settings for CRM/DDR/QSPI modes are valid:
| CRM | QSPI | DDR | Read Command Byte | Mode Byte |
|---|---|---|---|---|
| 0 | 0 | 0 | 03h Read | N/A |
| 0 | 0 | 1 | BBh Dual I/O Read | FFh |
| 1 | 0 | 1 | BBh Dual I/O Read | A5h |
| 0 | 1 | 0 | EBh Quad I/O Read | FFh |
| 1 | 1 | 0 | EBh Quad I/O Read | A5h |
| 0 | 1 | 1 | EDh DDR Quad I/O Read | FFh |
| 1 | 1 | 1 | EDh DDR Quad I/O Read | A5h |
The following plot visualizes the relative performance of the different configurations:
Consult the datasheet for your SPI flash to learn which configurations are supported by the chip and what the maximum clock frequencies are for each configuration.
For Quad I/O mode the QUAD flag in CR1V must be set before enabling Quad I/O in the
SPI master. Either set it by writing the corresponding bit in CR1NV once, or by writing
it from your device firmware at every bootup. (See set_flash_qspi_flag() in
firmware.c for an example for the latter.)