Skip to main content

faebryk

[fˈɛbɹɪk]


Open-source software-defined EDA tool

Version License: MIT Pull requests open Issues open Discord PyPI - Downloads GitHub commit activity

Code style: black

In short faebryk is a python library that allows you to design ready-to-order electronics (PCBs, schematics, etc) in code. It aims to reduce the entry-barrier for hardware design by bridging the gap between software and hardware design.


Using faebryk

> pip install faebryk
import faebryk.library._F as F
from faebryk.core.module import Module
from faebryk.libs.brightness import TypicalLuminousIntensity
from faebryk.libs.examples.buildutil import apply_design_to_pcb

class App(Module):
    led : F.PoweredLED
    battery : F.Battery

    def __preinit__(self) -> None:
        self.led.power.connect(self.battery.power)

        # Parametrize
        self.led.led.color.merge(F.LED.Color.YELLOW)
        self.led.led.brightness.merge(
            TypicalLuminousIntensity.APPLICATION_LED_INDICATOR_INSIDE.value.value
        )


apply_design_to_pcb(App())

Get stared with your own project

> pip install faebryk
> faebryk project <name> local

# if that doesn't work because faebryk is not in your PATH
> python -m faebryk project <name> local

For more details checkout the project template.


About

What [is faebryk]

faebryk is an open-source software-defined electronic design automation (EDA) tool. Think of it like the evolution from EDA tools like KiCAD, Altium, Eagle... in the way those were the next step from designing electronic circuits on paper. The main idea of faebryk is to describe your product on the highest level possible and then iteratively refining the description to arrive on a complete and detailed implementation. In comparison to classic EDA and design tools which use GUIs, faebryk uses code (Python) to create designs. While the main focus is on the EDA part currently, faebryk aims to become a holistic system design tool.

How [does designing with faebryk work]

faebryk itself is just a python library that you include in your project. It is providing you with all the tools to describe and design your system and to export that design into something useful like for example a netlist, a devicetree, gerbers etc, which you then can use in the next steps of your project. Key concepts of faebryk are the graph, importers, exporters, the library and the user application. To understand how to use faebryk in your project see using faebryk.

Who [is faebryk]

faebryk is a community driven project. That means faebryk does not only consist out of core developers but also users, external contributors, moderators and you! It is founded by a group of embedded, electrical, product design and software engineers with a love for making.

Why [do we make faebryk]

We noticed that the innovations of software engineering that make fast, scalable, robust solutions possible have not found their way into hardware design. Furthermore there is a lot of duplicate work done. Think of determining the pinout of a SoC and then having to translate that exact pinout into software again or having to constantly adapt designs for supply chain issues. Additionally, hardware design has quite a big barrier of entry for makers, but we don't think it has to. Currently hardware design is also quite labor intensive with very little automation. faebryk aims to tackle all those issues and also opens up some exciting possibilities, such as benefiting from the version management and collaboration tools that are used in modern software development.

When [is faebryk being developed]

faebryk is being continuously developed. The core team focuses on core functionality and features of faebryk, as well as the general direction of the project. The strength of the community can really shine with the development of importers, exporters, libraries, and projects, but everyone is welcome to help out where they can.

Where [do we develop faebryk]

faebryk is being developed completely in the open on Github. All the information you need to start using and contributing to faebryk will be in or linked to from this repository. If you have any questions you can ask them on our Discord. For pull requests and bug-reports, see our contributing guidelines.


Development

Installing from source

Setup

> git clone https://github.com/atopile/faebryk.git
> cd faebryk
>
> poetry install

Running examples

> poetry shell
> python ./examples/<sample_name>.py

Versioning

faebryk uses semantic versioning in the releases.

As feabryk is still in the early stages of development new releases will have a lot of (breaking) changes in them. Our roadmap(TODO) will show you where the project is going to and what you can expect in future releases.

Contributing

See CONTRIBUTING.md

To get inspiration on things to work on check out the issues.

Running your own examples/Making samples

First follow the steps in get running from source. Then add a file in examples/ (you can use one of the examples as template). Call your file with python3 examples/<yourfile>.py.

Running tests

Run

> pytest test

Community Support

Community support is provided via Discord; see the Resources below for details.

Resources

Metadata

Release files for faebryk 4.1.2

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

Source distribution (sdist)

Source distribution for faebryk 4.1.2
File Size Uploaded
faebryk-4.1.2.tar.gz 2.6 MB Details

Built distributions (wheels)

Table of built distributions (wheels) for faebryk 4.1.2
File
faebryk-4.1.2-cp312-cp312-musllinux_1_2_x86_64.whl CPython 3.12 CPython 3.12 Linux musl 1.2+ x86-64 Details
faebryk-4.1.2-cp312-cp312-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl CPython 3.12 CPython 3.12 Linux glibc 2.28+ x86-64, Linux glibc 2.24+ x86-64 Details
faebryk-4.1.2-cp312-cp312-macosx_11_0_arm64.whl CPython 3.12 CPython 3.12 macOS 11.0+ ARM64 Details
faebryk-4.1.2-cp312-cp312-macosx_10_13_x86_64.whl CPython 3.12 CPython 3.12 macOS 10.13+ x86-64 Details

Total release size: 5.3 MB

Release files / faebryk-4.1.2.tar.gz

Download URL faebryk-4.1.2.tar.gz
Size 2.6 MB
Tags Source
SHA-256 checksum
How to use checksums
4ca1742af42dbf2a6e4af330e633d6b11569c0bc7145ff74f8d10ccfad2b62e0
BLAKE2b-256 checksum
How to use checksums
995aeff6aef29a536fd069cbc70d509b7d27a7895ef46c94371ff2b39e5fdb1b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/5.1.1 CPython/3.12.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 Oct 28, 2024.

Transparency log

Release files / faebryk-4.1.2-cp312-cp312-musllinux_1_2_x86_64.whl

Download URL faebryk-4.1.2-cp312-cp312-musllinux_1_2_x86_64.whl
Size 1.4 MB
Tags CPython 3.12 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
c729ea60eaae4b55de8cec9bd387a98f9259d2892a06962b96b780982e4114bb
BLAKE2b-256 checksum
How to use checksums
fe4176bb3c2c67ecd66cd14a3145ace9d83d7a777012a061b9de874c47816ea1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/5.1.1 CPython/3.12.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 Oct 28, 2024.

Transparency log

Release files / faebryk-4.1.2-cp312-cp312-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl

Download URL faebryk-4.1.2-cp312-cp312-manylinux_2_24_x86_64.manylinux_2_28_x86_64.whl
Size 426.3 kB
Tags CPython 3.12 Linux glibc 2.24+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
1b2a01a5aa782fb9fb2455edf5fe4e3cdb6d39e62e42f1ce954a2fcee3a522ef
BLAKE2b-256 checksum
How to use checksums
b0399f202dd5b45bca3113af5a2e1b5cc9e86abf6f1c6fe69f1ac72e0e51b122
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/5.1.1 CPython/3.12.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 Oct 28, 2024.

Transparency log

Release files / faebryk-4.1.2-cp312-cp312-macosx_11_0_arm64.whl

Download URL faebryk-4.1.2-cp312-cp312-macosx_11_0_arm64.whl
Size 414.6 kB
Tags CPython 3.12 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
b99b2ec635d9d9d55cf9be8f403ffc262809410a745ef71254cc01a05329d6fe
BLAKE2b-256 checksum
How to use checksums
ad4cfaade28e986107202eaf0f24c42479b704ca39982f1f75094455b6a3c98d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/5.1.1 CPython/3.12.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 Oct 28, 2024.

Transparency log

Release files / faebryk-4.1.2-cp312-cp312-macosx_10_13_x86_64.whl

Download URL faebryk-4.1.2-cp312-cp312-macosx_10_13_x86_64.whl
Size 416.1 kB
Tags CPython 3.12 macOS 10.13+ x86-64
SHA-256 checksum
How to use checksums
0c67e41cff07b5d14e8b189075cbc2060ff57936e70c9c01f172954a75354738
BLAKE2b-256 checksum
How to use checksums
d0829817c1905409105ef30523d9d401f576bce4dc61d1a0de8b3f5e17a41a30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/5.1.1 CPython/3.12.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 Oct 28, 2024.

Transparency log

Release history Release notifications | RSS feed

This release

4.1.2 This release

5 release files

4.1.1

2 release files

4.1.0

2 release files

4.0.1

2 release files

4.0.0

2 release files

3.0.4

2 release files

3.0.3

2 release files

3.0.2

2 release files

3.0.1

2 release files

3.0.0

2 release files

2.0.0

2 release files

1.0.0

2 release files

0.0.1

2 release files

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