Open-Source Chip Design in Academic Education

Syed Anas Alam, Jakob Furbo Enevoldsen, Andreas Alkjaer Eriksen, Niels William Hartmann, Ulrik Helk, Jorgen Kragh Jakobsen, Christa Skytte Jensen, Nicolai Dyre Bulow Jespersen, Karl Herman Krause, Mads Rumle Nordstrom, Tjark Petersen, Luca Pezzarossa*, Simon Winther Rasmussen, Martin Schoeberl, Jonas Ingerslev Sorensen

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review

Abstract

Chip design is usually a high-effort, high-cost, and high- risk process. However, Google has recently taken the lead to bring chip design to a level where many engineers, researchers, and even students can actively participate. In this paper, we report on a course at the Technical University of Denmark (DTU) where a group of BSc students were able to design and produce a chip using open-source tools and the SkyWater process. We present the toolchain, explain the implemented hardware architecture, and discuss the challenges encountered in the process as well as the learning values of the course. The project was finalized within one semester and has recently achieved tape-out for the next multi-project wafer manufacturing.

Original languageEnglish
Title of host publicationProceedings of the 2022 IEEE Nordic Circuits and Systems Conference, NorCAS
Number of pages6
PublisherIEEE
Publication date2022
ISBN (Print)979-8-3503-4551-3
ISBN (Electronic)979-8-3503-4550-6
DOIs
Publication statusPublished - 2022
Event8th IEEE Nordic Circuits and Systems Conference: NorCAS 2022 - Oslo, Norway
Duration: 25 Oct 202226 Oct 2022

Conference

Conference8th IEEE Nordic Circuits and Systems Conference
Country/TerritoryNorway
CityOslo
Period25/10/202226/10/2022
SponsorIEEE, IEEE, Tampere University, University of Oslo

Keywords

  • Chip design
  • Chisel
  • Education
  • Open-source
  • Patmos processor

Fingerprint

Dive into the research topics of 'Open-Source Chip Design in Academic Education'. Together they form a unique fingerprint.

Cite this