a6d67f7477
Using `sys.excepthook` to silence the must-use warning has some false negatives: applications may catch the exception and then quit normally, e.g. becaue the error is well known and does not require a traceback to be shown (which would be noisy). The current implementation prints even more noise in that case. In addition to the existing heuristic, silence the warning if *nothing* has been elaborated, which is almost always a reliable sign. It doesn't work if multiple designs are independently created in the application and some of them are dropped without being used, but this is unavoidable as it is not distinguishable from the mistake this warning is attempting to prevent. Fixes #848. |
||
|---|---|---|
| .github/workflows | ||
| amaranth | ||
| docs | ||
| examples | ||
| tests | ||
| .codecov.yml | ||
| .coveragerc | ||
| .git_archival.txt | ||
| .gitattributes | ||
| .gitignore | ||
| CONTRIBUTING.txt | ||
| LICENSE.txt | ||
| pyproject.toml | ||
| README.md | ||
| setup.py | ||
Amaranth HDL (previously nMigen)
The Amaranth project provides an open-source toolchain for developing hardware based on synchronous digital logic using the Python programming language, as well as evaluation board definitions, a System on Chip toolkit, and more. It aims to be easy to learn and use, reduce or eliminate common coding mistakes, and simplify the design of complex hardware with reusable components.
The Amaranth toolchain consists of the Amaranth hardware definition language, the standard library, the simulator, and the build system, covering all steps of a typical FPGA development workflow. At the same time, it does not restrict the designer’s choice of tools: existing industry-standard (System)Verilog or VHDL code can be integrated into an Amaranth-based design flow, or, conversely, Amaranth code can be integrated into an existing Verilog-based design flow.
The development of Amaranth has been supported by LambdaConcept, ChipEleven, and Chipflow.
Introduction
See the Introduction section of the documentation.
Installation
See the Installation section of the documentation.
Supported devices
Amaranth can be used to target any FPGA or ASIC process that accepts behavioral Verilog-2001 as input. It also offers extended support for many FPGA families, providing toolchain integration, abstractions for device-specific primitives, and more. Specifically:
- Lattice iCE40 (toolchains: Yosys+nextpnr, LSE-iCECube2, Synplify-iCECube2);
- Lattice MachXO2 (toolchains: Diamond);
- Lattice MachXO3L (toolchains: Diamond);
- Lattice ECP5 (toolchains: Yosys+nextpnr, Diamond);
- Xilinx Spartan 3A (toolchains: ISE);
- Xilinx Spartan 6 (toolchains: ISE);
- Xilinx 7-series (toolchains: Vivado);
- Xilinx UltraScale (toolchains: Vivado);
- Intel (toolchains: Quartus);
- Quicklogic EOS S3 (toolchains: Yosys+VPR).
FOSS toolchains are listed in bold.
Community
Amaranth has a dedicated IRC channel, #amaranth-lang at libera.chat, which is bridged1 to Matrix at #amaranth-lang:matrix.org. Feel free to join to ask questions about using Amaranth or discuss ongoing development of Amaranth and its related projects.
License
Amaranth is released under the very permissive two-clause BSD license. Under the terms of this license, you are authorized to use Amaranth for closed-source proprietary designs.
-
The same messages appear on IRC and on Matrix, and one can participate in the discussion equally using either communication system. ↩︎