GitPlanet

Cheap and reliable Node.js hosting starts at $3/month, and $1/month static HTML hosting

Created with love in Canada, visit hostnodejs.com today

Feel like to post an Ad? Learn Details
All Projects → plex1 → SpinalDev

plex1 / SpinalDev

Licence: Unlicense license
Docker Development Environment for SpinalHDL

Programming Languages

Dockerfile
14818 projects
shell
77523 projects

Labels

dockerfilefpgavhdlrtlverilogspinalhdl

Projects that are alternatives of or similar to SpinalDev

SpinalCrypto
SpinalHDL - Cryptography libraries
Stars: ✭ 36 (+111.76%)
Mutual labels:  fpga, vhdl, rtl, verilog, spinalhdl
Spinalhdl
Scala based HDL
Stars: ✭ 696 (+3994.12%)
Mutual labels:  fpga, vhdl, rtl, verilog
hwt
VHDL/Verilog/SystemC code generator, simulator API written in python/c++
Stars: ✭ 145 (+752.94%)
Mutual labels:  fpga, vhdl, rtl, verilog
Verilog
Repository for basic (and not so basic) Verilog blocks with high re-use potential
Stars: ✭ 296 (+1641.18%)
Mutual labels:  fpga, rtl, verilog
Edalize
An abstraction library for interfacing EDA tools
Stars: ✭ 270 (+1488.24%)
Mutual labels:  fpga, vhdl, verilog
Cores
Various HDL (Verilog) IP Cores
Stars: ✭ 271 (+1494.12%)
Mutual labels:  fpga, rtl, verilog
Clash Compiler
Haskell to VHDL/Verilog/SystemVerilog compiler
Stars: ✭ 958 (+5535.29%)
Mutual labels:  fpga, vhdl, verilog
Image Processing
Image Processing Toolbox in Verilog using Basys3 FPGA
Stars: ✭ 31 (+82.35%)
Mutual labels:  fpga, vhdl, verilog
Tinytpu
Implementation of a Tensor Processing Unit for embedded systems and the IoT.
Stars: ✭ 153 (+800%)
Mutual labels:  fpga, vhdl, verilog
Rggen
Code generation tool for configuration and status registers
Stars: ✭ 54 (+217.65%)
Mutual labels:  fpga, rtl, verilog
Darkriscv
opensouce RISC-V cpu core implemented in Verilog from scratch in one night!
Stars: ✭ 1,062 (+6147.06%)
Mutual labels:  fpga, rtl, verilog
J1sc
A reimplementation of a tiny stack CPU
Stars: ✭ 64 (+276.47%)
Mutual labels:  fpga, vhdl, verilog
Fake-SDcard
Imitate SDcard using FPGAs.
Stars: ✭ 26 (+52.94%)
Mutual labels:  fpga, rtl, verilog
blarney
Haskell library for hardware description
Stars: ✭ 81 (+376.47%)
Mutual labels:  fpga, rtl, verilog
Logic
CMake, SystemVerilog and SystemC utilities for creating, building and testing RTL projects for FPGAs and ASICs.
Stars: ✭ 149 (+776.47%)
Mutual labels:  fpga, rtl, verilog
intfftk
Fully pipelined Integer Scaled / Unscaled Radix-2 Forward/Inverse Fast Fourier Transform (FFT) IP-core for newest Xilinx FPGAs (Source language - VHDL / Verilog). GNU GPL 3.0.
Stars: ✭ 43 (+152.94%)
Mutual labels:  fpga, vhdl, verilog
FPGA-USB-Device
FPGA-based USB-device controller to implement USB-CDC, USB-HID, etc.
Stars: ✭ 29 (+70.59%)
Mutual labels:  fpga, rtl, verilog
getting-started
List of ideas for getting started with TimVideos projects
Stars: ✭ 50 (+194.12%)
Mutual labels:  fpga, vhdl, verilog
Fpga readings
Recipe for FPGA cooking
Stars: ✭ 164 (+864.71%)
Mutual labels:  fpga, rtl, verilog
Vexriscv
A FPGA friendly 32 bit RISC-V CPU implementation
Stars: ✭ 1,041 (+6023.53%)
Mutual labels:  fpga, vhdl, verilog
View All Similar Projects ➔

SpinalDev - Development Environment for SpinalHDL

SpinalHDL is a hardware description language (HDL). SpinalHDL written on top of Scala and allows for high level constructs. This repository contains a Dockerfile for FPGA/ASIC development with SpinalHDL. The Dockerfile and content of this README is mostly based on the instructions found at https://spinalhdl.github.io/SpinalDoc. The container includes a number of tools, libraries and dependencies related to SpinalHDL.

Container Content

The following tools and libraries are installed:

Getting Started

The best way to get started is to download the image for this container directly from Doc Hub and then run the container and play inside it. Here are the steps for Ubuntu.

  1. Install docker client (e.g. see docker docks)
  2. Get the image, either
    • get image from docker hub
      • sudo docker pull plex1/spinaldev
    • OR build image yourself
      • git clone https://github.com/plex1/SpinalDev.git
      • cd SpinalDev/docker/main/
      • sudo docker build -t plex1/spinaldev .
  3. Add X access for root
    • xhost local:root
  4. Run the docker container
    • sudo docker run -it --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -p 3389:3389 plex1/spinaldev:latest
  5. You are now logged into the development environment as the user spinaldev

As a first step you can run the following commands. They build and test an example design.

# Go to a SpinalHDL example project
cd projects/spinal/SpinalTemplateSbt

# Generate the Verilog of the design
sbt "runMain mylib.MyTopLevelVerilog"

# Inspect generated files
ls
cat MyTopLevel.v

# Run the scala testbench
sbt "runMain mylib.MyTopLevelSim"

# Inspect the waveform of the simulation
gtkwave simWorkspace/MyTopLevel/test.vcd&

Have fun!

Remote Desktop

There is a remote desktop server running in the container. To connect from linux you may execute the following command.

rdesktop -z -P -x l -g 1024x768 127.0.0.1:3389

Then login as user spinaldev with password spinaldev. To connect from windows you may use the native remote desktop client.

Tour of the environment

Build the CPU

The VexRiscv risc-v processor can be build with the following set of commands.

# Go to a risc-v cpu
cd /home/spinaldev/projects/spinal/VexRiscv

# Generate the verilog of the cpu
sbt "runMain vexriscv.demo.GenFull"

# Inspect generated files
ls
head VexRiscv.v

Run a simulation of the CPU

The cpu including software can be simulated and debugged in the container. First, we start a simulation using verilator.

# Run a simulation of the cpu with a port for OpenOCD to connect to
cd src/test/cpp/regression
make run DEBUG_PLUGIN_EXTERNAL=yes

The last message shows BOOT which means that the simulation is running in a process. We open a second terminal. E.g. via docker from your host:

docker exec -u spinaldev -it container_id bash

In this second terminal we run the following commands to start the OpenOCD server. The server is connected to the simulation which we started above.

# Start the OpenOCD server
cd /opt/openocd_riscv/
src/openocd -c "set VEXRISCV_YAML /home/spinaldev/projects/spinal/VexRiscv/cpu0.yaml" -f tcl/target/vexriscv_sim.cfg

We should now have two terminals open and we will open a third one (e.g. as describe above). Here we run the actual debugger and connect it to the OpenOCD server via tcp port 3333.

# Run the debugger with prebuild uart example sw
riscv64-unknown-elf-gdb ~/projects/spinal/VexRiscv/src/test/resources/elf/uart.elf
target remote localhost:3333
monitor reset halt
load
continue

Now, the simulation of the cpu is running and messages shoud be printed in the first terminal. Specifically, we can see the uart output of the program.

Build the software

Software for the VexRiscv can be compiled as follows. In this example the uart program for the briey soc is built.

# Build the elf file
cd ~/projects/spinal/VexRiscvSocSoftware/projects/briey/uart
make all

# Inspect the generated files
ls build/

Create programming file

This container contains all the tools to generate the programming files for a lattice iCE40 FPGAs. A script to generate the Murax System-on-chip for the iCE40HX8K-EVB open source hardware board is provided in the VexRiscv repository. The following command is necssary to build the bin file.

# Compilation / synthesis / place and route / bitstream generation
cd ~/projects/spinal/VexRiscv/scripts/Murax/iCE40HX8K-EVB
make compile

# Inspect the generated files
ls bin/

Docker Volumes

When working with projects in SpinalDev it is recommended to use docker volumes. The data in containers is not persistent. Therfore the data needs to be stored on the host and mounted in the container (volumes). Docker has build in methods to deal with volumes. It is recommeded to mount the complete home directory (/home/spinaldev). This is because in home some application data is stored. E.g the for the intellij editor this data is under ~/.idea. Without keeping this data upd to date, the idea application and projects become unsynchronized and projects cannot be opened anymore. The following procedure to generate the docker volumes is recommended. The first time when the docker run command is executed the content of the docker home directory is copied onto the host (in this example under /home/username/spinalvol).

mkdir /home/username/spinalvol
sudo docker volume create --driver local --opt type=none --opt device=/home/username/spinalvol --opt o=bind spinalvol
sudo docker volume inspect spinalvol

sudo docker run -it --rm -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -v spinalvol:/home/spinaldev -p 3389:3389 plex1/spinaldev:latest

See also on the docker website.

Create your own projects

To create your own projects run the project.bash script and follow the instructions.

cd /home/spinaldev/projects/user
./project.bash -h
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].