Skip to content

fusesoc/fusesoc-cores

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4493946 · Jan 28, 2025
Apr 21, 2020
Feb 5, 2021
Mar 3, 2020
Feb 11, 2021
Aug 18, 2018
Feb 5, 2021
Aug 20, 2020
Sep 30, 2019
Aug 27, 2022
Dec 20, 2021
Jun 2, 2022
Mar 3, 2020
Aug 18, 2020
Jan 11, 2022
Feb 11, 2021
Feb 11, 2021
Jan 28, 2025
Feb 11, 2021
Apr 11, 2023
Jul 24, 2022
Mar 3, 2020
Feb 5, 2021
Feb 11, 2021
Mar 3, 2020
Feb 11, 2021
May 25, 2020
May 29, 2020
Jan 18, 2021
Mar 24, 2018
Jan 18, 2021
Nov 17, 2023
Jul 31, 2024
Feb 5, 2021
Mar 3, 2020
Mar 3, 2020
Aug 17, 2020
Oct 19, 2018
Oct 9, 2017

Repository files navigation

FuseSoC standard core library

This is the standard core library to be used with FuseSoC

Installation

This library will be automatically cloned to ~/.local/share/fusesoc/fusesoc-cores and added to fusesoc.conf when you run fusesoc init.

If you have a existing FuseSoC setup and the above does not work for you, please consider this alternative installation method. Use git to clone this repository and add it to your fusesoc.conf. For example in ~/.config/fusesoc/fusesoc.conf:

[main]
cores_root =
 /home/joe/work/fusesoc-cores
cache_root = /home/joe/work/fuse-cache
build_root = /home/joe/work/fuse-builds

Contributing

Cores for FuseSoC should follow the following guidelines.

  • No Code Please do not store code in fusesoc-cores. Please store your code in a separate repo or somewhere it can be fetched with the url provider.
  • If your core is really small please consider storing in the tiny-cores repo.
  • Stay Modern Use the modern sections in your core file like fileset and parameter, please no obsolete verilog sections. For details on migrating old cores to the current standard please refer to the FuseSoC migration guide.
  • Versioning Each core should be versioned with either
    • Versioned For cores where the upstream provider provides a release version, in git using tags is ideal, please use the corresponding release version.
    • Pseudo-versioned When an core's upstream provider is out of your control and does not use versions please use version 0 and point to a location which is unique for that revision (e.g. the sha for git repos or revision for svn repos instead of pointing to master, which might change over time). If you need to refer to a newer version of the upstream repo, still without a proper version, step the revision number (0-r1, 0-r2..etc).

About

FuseSoC standard core library

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published