Skip to main content

YoWASP nextpnr packages

The YoWASP nextpnr suite of packages provides nextpnr and related tools for several FPGA families built for WebAssembly. See the overview of the YoWASP project for details.

The supported FPGA families are:

Notes

For technical reasons, the ecppack, ecpunpack, ecpbram, ecppll, and ecpmulti tools from the MachXO2 toolchain shipped in the yowasp-nextpnr-machxo2 PyPI package are installed under the names yowasp-xo2pack, yowasp-xo2unpack, yowasp-xo2bram, yowasp-xo2pll, and yowasp-xo2multi respectively. These commands run bit-for-bit identical code as their yowasp-ecp* prefixed brethren from the yowasp-nextpnr-ecp5 PyPI package of the same version.

Versioning

The version of this package is derived from the upstream nextpnr package version in the X.Y[.Z] format, and is comprised of five or six parts in a X.Y.Z.N.postM[.dev] format:

  1. X: nextpnr major version
  2. Y: nextpnr minor version
  3. Z: nextpnr patch version; reserved as nextpnr currently does not do patch releases
  4. N: zero for packages built from nextpnr releases, N for packages built from unreleased nextpnr snapshots; N is the amount of commits since the latest release
  5. postM: package build version; disambiguates different builds produced from the same nextpnr source tree
  6. dev: present only for packages built from unreleased nextpnr snapshots; marks these packages as pre-releases

With this scheme, there is a direct correspondence between upstream versions and PEP 440 Python package versions. Packages built from unreleased snapshots are ignored by pip by default, but can be still installed explicitly. (These packages are uploaded daily to TestPyPI, but only occasionally to PyPI.)

A different versioning scheme was used earlier, where the package build version was denoted by a .devM suffix. This scheme did not work well with PEP 440 version specifiers and was retired.

Configuration

See the documentation for yowasp-runtime.

License

This package is covered by the ISC license, which is the same as the nextpnr license.

Metadata

Release files for yowasp-nextpnr-machxo2 0.9.0.0.post685

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Built distribution (wheel)

Table of built distributions (wheels) for yowasp-nextpnr-machxo2 0.9.0.0.post685
File Interpreter ABI Platform
yowasp_nextpnr_machxo2-0.9.0.0.post685-py3-none-any.whl Python 3 none any Details

Release files / yowasp_nextpnr_machxo2-0.9.0.0.post685-py3-none-any.whl

Download URL yowasp_nextpnr_machxo2-0.9.0.0.post685-py3-none-any.whl
Size 36.1 MB
Tags Python 3
SHA-256 checksum
How to use checksums
b9578549b4fcd445e7d0899332731e46e90d58898b316e03eaf4990098ea2b31
BLAKE2b-256 checksum
How to use checksums
3eb5eb95413bd2b32f41ff7fde09ca2f2f587728fa36551de819af69dc361edd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 11, 2025.

Transparency log
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page