Efabless corporation is an open innovation, hardware creation platform for “smart” products. Our community delivers the customized integrated electronics required for semiconductor and hardware system innovators to turn their product visions into a marketable reality.
Today, Efabless focuses on on-demand and custom IP. Efabless gives chip companies two ways to obtain analog & mixed-signal IP: you can search for existing IP in our growing library of verified designs, but more importantly you can also request the Efabless community to design new IP and derivatives.
To register for an Efabless account, you must sign in using an existing account from a third-party social login provider or using a Corporate Account. The third party social options are LinkedIn®, Google or Github.
Each time you log in, it is best to choose the service you selected when you registered. If you select a different service provider, you may end up with a new account if the primary email for that service does not match the service you chose for initial registration.
Registration via a LinkedIn® account is the preferred method and has benefits. If you (eventually) do request verification of your account, the primary path is through a LinkedIn® account anyway. If you registered via LinkedIn®, the verification process is typically simpler, has less steps and communications, and is completed sooner with less effort on your part.
After you have registered for an account, you will see a drop-down menu under your name in the upper right corner of the web browser. From this menu you will see the status of your account, ‘verified’ or ‘unverified’. If ‘unverified’, you have the option to request account verification. You will be presented with Terms and Conditions for using protected content on the site. After accepting these terms, your account will be submitted to a review process by Efabless staff.
The primary means to verify your account is through your LinkedIn® profile. Efabless will review the content of your LinkedIn® profile as part of the verification process and may request additional information if needed. You may also receive an email from Efabless to initiate a connection request from your LinkedIn® account.
If you do not have a LinkedIn® account, please submit a help ticket requesting account verification and someone from Efabless will contact you.
You should note that you do not need to have a verified account in order to participate in the Open MPW or chipIgnite shuttle programs. In the shuttle review process, US export-controls are still enforced: not all non-verified accounts are shuttle eligible.
Third-party social-network accounts (i.e. not Corporate-Users) that are impersonal or represent a group or organization, cannot be verified.
At Efabless we provide a full path from open IP to silicon products. Lowering the barrier for designer community to reach prototypes that can enable effective showcasing of the design work to the customers. The platform has three main pillars:
First point, the shuttles: Efabless offers community members and customers access to shuttles. Shuttles can be accessed on demand for premium pricing or on a Leave-When-Full basis that is very affordable. In the latter case, the shuttle cost per mm2 is within the low to high $100’s depending on the process technology. Keep in mind we focus on technologies like 180/130nm BCD and more mature 250/350nm with higher voltage support.
Second, characterization & testing: We designed an open source HW platform board, including a reference ASIC designed to enable characterization of community IP. The design has been silicon-proven on our platform and will be announced to the world in early 2017. The designers will then be able to fork the reference ASIC and replace the template design with their own IP. After fabrication, the designer will utilize the platform board and wakeup SW to validate their specific design. In the future, we intend to forge partnerships with companies offering labs and test facilities that support low volume production in different geographical regions. Through such partnerships, the Efabless design community will access the capabilities as a part of an Efabless ecosystem. Stay tuned as we publish our progress on this front.
The project must be licensed under open-source license and contain a LICENSE file with the license agreement language.
All third_party material should be under a third_party directory and have a license identifier.
All text files should have a copyright header and appropriate SPDX identifier.
Repository should have a README file
All documentation should use inclusive language
Projects must have a complete info.yaml containing project meta-data per the example in the Caravel User Project repo. The metadata will be used by the Efabless platform for creating entries into a public project showcase page for the shuttle program.
The precheck tool performs a series of checks to confirm the project meets the requirements for participating in the Open MPW Shuttle Program. The precheck tool addresses the following items:
The tool runs as a Linux container. It can be cloned and run offline prior to uploading the project to the Efabless platform. Further details can be found on the README file located in the git repository for the tool ( https://github.com/efabless/mpw_precheck )
Efabless will confirm the deliverables provided by the submitter using both automated tools and manual review. This includes the following items:
The git repo for the project should include the following items.
The Open MPW Shuttle Program is sponsored by Google. All costs associated with fabrication, packaging, assembly into evaluation boards as well as shipping to world-wide locations are covered and the user bears no cost for these items.
The only item that a user may be responsible for is any import duty or taxes for shipping parts and boards to a location outside of the United States. The shipping cost will be included, but any additional costs for duty or tax are the responsibility of the recipient.
The Open MPW Shuttle Program supports a global community and will ship parts and boards to project owners worldwide.
The shipping cost will be included, but any additional costs for duty or tax are the responsibility of the recipient.
There are several options to get support.
The list of steps is provided on the 'Instructions' tab when viewing your request. They include:
Once you have completed these steps, please select ‘change’ next to the ‘Submitted’ status indicator to update your request status to ‘CONFIRMED’.
Efabless will then review each of your deliverables and send any questions back to you using the message thread located on the Activity tab for the request.
Once everything has been confirmed, Efabless will update the status for ‘Provider’ to ‘CONFIRMED’.
Efabless will update the status of your request for ‘Provider’ to ‘CONFIRMED’ to indicate you have met all of the requirements for your project to be included on the shuttle.
If more than 40 projects are submitted, projects will be selected randomly to be included on the current shuttle. Project owners will be notified either way on the status of their project.
The program has been extended to include a range of permissible open source licenses. The precheck tool recognizes a subset of these, but may flag a warning for other permitted licenses it does not recognize. Recognized licenses include the following list:
['0BSD', 'Apache-2.0', 'BSD-2-Clause', 'BSD-3-Clause', 'CC-BY-1.0', 'CC-BY-2.0',
'CC-BY-2.5', 'CC-BY-3.0', 'CC-BY-4.0', 'CC-BY-NC-SA-1.0', 'CC-BY-NC-SA-2.0',
'CC-BY-NC-SA-2.5', 'CC-BY-NC-SA-3.0', 'CC-BY-SA-4.0', 'CC0-1.0', 'GPL-2.0', 'GPL-3.0',
'ISC', 'LGPL-2.1', 'LGPL-3.0', 'MIT', 'Unlicense']
Licenses that are recognized by the precheck tool and explicitly prohibited include:
['AGPL-1.0', 'AGPL-3.0', 'CC-BY-NC-1.0', 'CC-BY-NC-2.0', 'CC-BY-NC-2.5', 'CC-BY-NC-3.0',
'CC-BY-NC-4.0', 'CC-BY-NC-ND-1.0', 'CC-BY-NC-ND-2.0', 'CC-BY-NC-ND-2.5',
'CC-BY-NC-ND-3.0', 'CC-BY-NC-ND-4.0', 'CC-BY-NC-SA-1.0', 'CC-BY-NC-SA-2.0',
'CC-BY-NC-SA-2.5', 'CC-BY-NC-SA-3.0', 'CC-BY-NC-SA-4.0', 'CC-BY-ND-1.0',
'CC-BY-ND-2.0', 'CC-BY-ND-2.5', 'CC-BY-ND-3.0', 'CC-BY-ND-4.0', 'CPAL-1.0',
'CPOL-1.02', 'EUPL-1.0', 'EUPL-1.1', 'EUPL-1.2', 'SISSL-1.2', 'SISSL', 'SSPL-1.0',