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 → SpinalHDL → SaxonSoc

SpinalHDL / SaxonSoc

Licence: MIT license
SoC based on VexRiscv and ICE40 UP5K

Programming Languages

scala
5932 projects
c
50402 projects - #5 most used programming language
tcl
693 projects
Verilog
626 projects
Makefile
30231 projects
shell
77523 projects

Labels

riscvrtlsoc

Projects that are alternatives of or similar to SaxonSoc

Scr1
SCR1 is a high-quality open-source RISC-V MCU core in Verilog
Stars: ✭ 393 (+250.89%)
Mutual labels:  riscv, rtl
Cores Swerv
SweRV EH1 core
Stars: ✭ 406 (+262.5%)
Mutual labels:  riscv, rtl
Quasar
Quasar 2.0: Chisel equivalent of SweRV-EL2
Stars: ✭ 19 (-83.04%)
Mutual labels:  riscv, rtl
tree-core-cpu
A series of RISC-V soft core processor written from scratch. Now, we're using all open-source toolchain( chisel, mill, verilator, NEMU, AM and difftest framework, etc) to design and verify.
Stars: ✭ 22 (-80.36%)
Mutual labels:  riscv, rtl
Ustc Rvsoc
FPGA-based RISC-V CPU+SoC.
Stars: ✭ 77 (-31.25%)
Mutual labels:  riscv, rtl
Chipyard
An Agile RISC-V SoC Design Framework with in-order cores, out-of-order cores, accelerators, and more
Stars: ✭ 436 (+289.29%)
Mutual labels:  riscv, rtl
Riscv Mini
Simple RISC-V 3-stage Pipeline in Chisel
Stars: ✭ 221 (+97.32%)
Mutual labels:  riscv, rtl
Rocket Chip
Rocket Chip Generator
Stars: ✭ 2,079 (+1756.25%)
Mutual labels:  riscv, rtl
Darkriscv
opensouce RISC-V cpu core implemented in Verilog from scratch in one night!
Stars: ✭ 1,062 (+848.21%)
Mutual labels:  riscv, rtl
Riscv Boom
SonicBOOM: The Berkeley Out-of-Order Machine
Stars: ✭ 852 (+660.71%)
Mutual labels:  riscv, rtl
Cores Swerv El2
SweRV EL2 Core
Stars: ✭ 79 (-29.46%)
Mutual labels:  riscv, rtl
Dana
Dynamically Allocated Neural Network Accelerator for the RISC-V Rocket Microprocessor in Chisel
Stars: ✭ 160 (+42.86%)
Mutual labels:  riscv, rtl
tree-core-ide
The next generation integrated development environment for processor design and verification. It has multi-hardware language support, open source IP management and easy-to-use rtl simulation toolset.
Stars: ✭ 79 (-29.46%)
Mutual labels:  riscv
FPGA Ultrasound
CMU 18545 FPGA project -- Multi-channel ultrasound data acquisition and beamforming system.
Stars: ✭ 39 (-65.18%)
Mutual labels:  soc
kianRiscV
KianRISC-V! No RISC-V, no fun! RISC-V CPU with strong design rules and unittested! CPU you can trust! kianv rv32im risc-v a hdmi soc with harris computer architecture in verilog: multicycle, singlecycle and 5-stage pipelining Processor. Multicycle Soc with firmware that runs raytracer, mandelbrot, 3d hdmi gfx, dma controller, etc.....
Stars: ✭ 167 (+49.11%)
Mutual labels:  riscv
PyChip-py-hcl
A Hardware Construct Language
Stars: ✭ 36 (-67.86%)
Mutual labels:  rtl
platform-shakti
Shakti: development platform for PlatformIO
Stars: ✭ 26 (-76.79%)
Mutual labels:  riscv
SpinalDev
Docker Development Environment for SpinalHDL
Stars: ✭ 17 (-84.82%)
Mutual labels:  rtl
Ckb Vm
CKB's vm, based on open source RISC-V ISA
Stars: ✭ 211 (+88.39%)
Mutual labels:  riscv
rtl-md
📝 A simple markdown to html converter which knows the direction!
Stars: ✭ 27 (-75.89%)
Mutual labels:  rtl
View All Similar Projects ➔

Description

This repo experiment multiple things at once :

  • The BMB (Banana Memory Bus) which can cover both cached and cacheless SoC without compromises
  • A hardware description paradigm made of generators and depedancies which should be able to solve SoC toplevel hell
  • Linux and U-Boot on VexRiscv

A few kits are supported :

  • ulx3s (ECP5) , documented in bsp/radiona/ulx3s/smp/README.md

  • Arty-A7 (Artix 7), documented in bsp/digilent/ArtyA7SmpLinux/README.md

  • Efinix Xyloni xyloni_1

  • ...

Repository structure

- hardware
  - scala      : SpinalHDL hardware description
  - netlist    : Folder used by SpinalHDL to generate the netlist
  - synthesis  : Contains synthesis scripts for various boards
- bsp          : Contains multiple Board Support Package used to build the software
- software
  - standalone : Contains multiple demo software to run in the CPU
- ext
  - SpinalHDL  : Hardware description language compiler
  - VexRiscv   : CPU hardware description

Dependencies

On Ubuntu 14 :

# JAVA JDK >= 8
sudo add-apt-repository -y ppa:openjdk-r/ppa
sudo apt-get update
sudo apt-get install openjdk-8-jdk -y
sudo update-alternatives --config java
sudo update-alternatives --config javac

# Install SBT - https://www.scala-sbt.org/
echo "deb https://repo.scala-sbt.org/scalasbt/debian all main" | sudo tee /etc/apt/sources.list.d/sbt.list
echo "deb https://repo.scala-sbt.org/scalasbt/debian /" | sudo tee /etc/apt/sources.list.d/sbt_old.list
curl -sL "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x2EE0EA64E40A89B84B2DF73499E82A75642AC823" | sudo apt-key add
sudo apt-get update
sudo apt-get install sbt

# Verilator (for simulation only, v3.9+, in general apt-get will give you 3.8)
sudo apt-get install git make autoconf g++ flex bison -y  # First time prerequisites
git clone http://git.veripool.org/git/verilator   # Only first time
unsetenv VERILATOR_ROOT  # For csh; ignore error if on bash
unset VERILATOR_ROOT  # For bash
cd verilator
git pull        # Make sure we're up-to-date
git checkout v4.040
autoconf        # Create ./configure script
./configure
make -j$(nproc)
sudo make install
echo "DONE"

# A fiew dependencies ?
sudo apt install pkg-config shtool libtool cpio bc unzip rsync mercurial
sudo apt install libusb-1.0-0-dev libyaml-dev

Jar package

To package the project into a dependence free jar :

sbt clean assembly

The produced jar will be in target/scala-2.11/SaxonSoc-assembly-1.0.0.jar

To run that jar :

java -cp target/scala-2.11/SaxonSoc-assembly-1.0.0.jar YOUR_SCALA_PACKAGE.YOUR_MAIN

BMB spec (WIP)

Why BMB

The needs I had :

  • A memory bus which could be used from for cacheless + low latency to cachefull SoC design without overhead
  • Interconnect/Adapters which fit well in FPGA (without asyncronus ram reads)

Why not adopting a existing memory bus :

  • AXI4 and Tilelink memory ordering has overhead for cacheless CPU designs
  • AXI4 do not fit cacheless design as the AW W channels split add overhead to the interconnect
  • TileLink isn't FPGA friendly, as its rely on tracking each transaction (unique source identifier)
  • Nor AXI4, Tilelink, Wishbone, Avalon provide the features required for state-less adapters
  • With the SaxonSoc out of order elaboration, there was a quite some room for experimentation and automation

Key features

Feature which target the interconnect and adapters :

  • Context signals which allow a master to retrieve information from the bus responses, and consequently allow state-less adapters
  • State-less adapters allow unlimited number of pending transactions and avoid the usage of RAM/FIFO in adapters
  • Address and write data are part of the same link, which allow to have low latency interconnect (in comparison to AXI)
  • Allow out of oder completion via the 'source' signals

Feature to make slave implementation easier :

  • Address alignment parameter (BYTE, WORD, POW2) to allow simple slave implementations
  • Length width parameter, which combined with the alignement parameter, allow a slave to not support bursts (the interconnect will add the required adapters)

Other features :

  • WriteOnly, readOnly support

Signal

BMB is composed of streams to carry transaction between a source and a sink. A stream is composed of :

Name Direction Description
valid Source => Sink transaction present on the interface
payload Source => Sink transaction content
ready Source <= Sink consume the transaction on the bus, don't care if there is no transaction

More details on https://spinalhdl.github.io/SpinalDoc-RTD/SpinalHDL/Libraries/stream.html

BMB is composed of two mandatory streams :

  • cmd : M->S, to carry requests, (read, write + data)
  • rsp : M<-S, to carry responses (read + data, write)

and three optional streams to handle memory coherency :

  • inv : M<-S, for the interconnect to ask a master to invalidate a portion of memory
  • ack : M->S, for the master to notify the interconnect that an invalidation is now effective
  • sync : M<-S, for the interconnect to notify a master which issued a write that the given write is now observable by all other masters

The cmd stream is consquantly composed of the following signals

Name Bitcount Description
valid 1 Stream valid
ready 1 Stream ready
source sourceWidth Transaction source ID, allow out of order completion between different sources, similar to AXI ID
opcode 1 0 => READ, 1 => WRITE
address addressWidth Address of the first byte of the transaction, stay the same during a burst
length lengthWidth Burst bytes count - 1
data dataWidth Data used for writes
mask dataWidth/8 Data mask used for writes
context contextWidth Can be used by a master/adapter to link some informations to a burst (returned on rsp transactions)

During a write burst the source, opcode, address, length and context signal should remain stable.

The rsp stream is :

Name Bitcount Description
valid 1 Stream valid
ready 1 Stream ready
source sourceWidth Identical to the corresponding cmd source
opcode 1 0 => SUCCESS, 1 => ERROR
data dataWidth Data used for reads
context contextWidth Identical to the corresponding cmd context

During a read burst the source and context signal should remain stable.

The inv stream is :

Name Bitcount Description
valid 1 Stream valid
ready 1 Stream ready
all 1 0 => all masters, 1 => all masters but the source one should be invalidated.
address addressWidth Address of the first byte to invalidate
length lengthWidth How many bytes should be invalidated - 1
source sourceWidth See the all signal

The ack stream has no payload attached :

Name Bitcount Description
valid 1 Stream valid
ready 1 Stream ready

The sync stream is :

Name Bitcount Description
valid 1 Stream valid
ready 1 Stream ready
source sourceWidth Identify which master should be notified
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].