Please see examples for a description of this example.
fusesoc
and its dependenciesThe easiest way to build and execute this example is to call the following make goals from the root directory.
Use the following for the Arty A7-35
make build-arty-35 program-arty
and for the Arty A7-100
make build-arty-100 program-arty
First the software must be built. Go into examples/sw/led
and call:
make CC=/path/to/RISC-V-compiler
The setting of CC
is only required if riscv32-unknown-elf-gcc
is not available through the PATH
environment variable. The path to the RV32 compiler /path/to/RISC-V-compiler
depends on the environment. For example, it can be for example /opt/riscv/bin/riscv-none-embed-gcc
if the whole path is required or simply the name of the executable if it is available through the PATH
environment variable.
This should produce a led.vmem
file which is used in the synthesis to update the SRAM storage.
Run either of the following commands at the top level to build the respective hardware. Both variants of the Arty A7 are supported and can be selected via the --parts
parameter.
fusesoc --cores-root=. run --target=synth --setup --build lowrisc:ibex:top_artya7 --part xc7a35ticsg324-1L
fusesoc --cores-root=. run --target=synth --setup --build lowrisc:ibex:top_artya7 --part xc7a100tcsg324-1
This will create a directory build
which contains the output files, including the bitstream.
After the board is connected to the computer it can be programmed with:
fusesoc --cores-root=. run --target=synth --run lowrisc:ibex:top_artya7
LED1/LED3 and LED0/LED2 should alternately be on after the FPGA programming is finished.