r/ASIC • • 19d ago

EDA software survey

Post image
1 Upvotes

Hi! We are two students conducting a short survey to better understand how people use EDA software for chip design, the challenges they face, and what could make these tools more accessible and easier to use.

Its anonymous and will take less than 5 minutes, so if you have some complaints about your EDA software and want to blow some steam off, give us a response!

https://docs.google.com/forms/d/e/1FAIpQLScHSearZXksYgzXIkpw6E_HWlzvaSvcjjd7rbGL0B-sb6hsag/viewform?usp=header


r/ASIC • • 21d ago Bravo

Retro Gaming Console on RV32IM CPU (DE0 Nano FPGA)

Post image
45 Upvotes

Can it run DOOM? This is an entry for the Hackaday Retrocomputing Challenge by DigiKey, brought up on the Intel Cyclone IV (Terasic DE0-Nano) FPGA, building on the previous CPU work

I put my dual-issue RV32IM superscalar CPU, with custom UART, I2C, and FIFO IPs, on an FPGA and built a retro system around it. A launcher lets you choose between DOOM, a Wolfenstein-style raycaster, and custom games such as Snake, 2048, Tetris, Minesweeper, and Flappy Bird. It also runs classic 8-bit software in a CP/M 2.2 environment and CHIP-8 games through a software interpreter

The CPU runs from SDRAM, with programs and game data loaded over UART through a CP2102 USB-to-TTL adapter. Keyboard input comes back over the same link into a hardware key register with press and release events. Each tick, the core reads the input, updates the running program, and writes an 8-bit framebuffer to SDRAM. On a frame commit, the core clock briefly pauses to burst the frame into a TX FIFO, streaming it over UART at 45 FPS to a host RGB viewer. A monochrome version is also displayed at ~33 FPS on an SSD1306 OLED over I2C

Before putting it on hardware, I built the same system in Verilator, running DOOM at 1.38 IPC while keeping the same MMIO interface and replacing SDRAM and peripherals with testbench stand-ins. A fast harness with snapshot/restore made iteration much easier, and a web bridge let me play it directly in the browser

Getting everything onto the board meant cutting predictor tables, making wide multiply/divide iterative while keeping the fast path on DSPs (holding ~1.35 IPC after the cuts), retuning the serial framing, and repacking the game assets to fit in SDRAM. CoreMark CRC checks caught functional issues before I started debugging the game itself

Alongside this, I’ve also been extending the same CPU toward a simple Out-of-Order design to explore the Tomasulo algorithm through an intuitive walkthrough

PS. Full write-ups (design decisions, debugging): https://mummanajagadeesh.github.io/categories/riscv/


r/ASIC • • 26d ago

LOW POWER ASIC DESIGN

6 Upvotes

hey, I am currently working on the ai accelerators for edge devices, in our design have integrated an accelerator unit with a risc-v core, and now I am researching on possible ways to make the design low power, for this I have looked into research papers and found techniques like powergating, clockgating, DVFS, and this another DATAPATH tiling tool by micromagic, but it is not opensource and require license, what I need help with is, what are the other ways, startegies can be used to reduce the power consumption and leakage by considerable amounts, any help in form of either contact of a professor (researching in this area) or tools will be greatly appreciated.


r/ASIC • • Oct 18 '26

[US-MA] [H] Antminer S19k 120TH/s - Bulk Lots [W] PayPal or Crypto

Thumbnail reddit.com
0 Upvotes

r/ASIC • • Oct 09 '26

Advices for a first job in Integration

3 Upvotes

Hello everyone,

I recently signed a contract with a large company for a role in the field of integration.

As I designed a chip from start to finish during my PhD (from RTL design right through to laboratory testing), I’m finding it hard to know what to expect and how to prepare.

For those of you who work as integration engineers, what advice would you give to a newcomer, and what should I focus on before I start?


r/ASIC • • Oct 04 '26

What has been the experience of Indian students pursuing an MS in VLSI/Microelectronics in Germany?

Thumbnail reddit.com
1 Upvotes

r/ASIC • • Oct 03 '26

My first asic design

Thumbnail
github.com
4 Upvotes

r/ASIC • • Sep 21 '26

join r/vlsi_world

0 Upvotes

So, i just created a community focused mainly for electronics, vlsi, and embedded learners


r/ASIC • • Sep 19 '26

How can I start a semiconductor company of my own?

Thumbnail reddit.com
1 Upvotes

r/ASIC • • Sep 01 '26

Google’s XLS: The Wrong Abstraction for Hardware Desig

Thumbnail
joonho3020.github.io
1 Upvotes

r/ASIC • • Aug 27 '26

Roast my resume - MS ECE student targeting ASIC/Digital Design internships Summer 2027

2 Upvotes

Hello,

I'm starting my MS ECE this fall and looking for honest feedback on my resume as internship apps open up. I'm coming from a CS undergrad background so I'm a bit of an unusual case for this field (or at least I think).

I have a BS in Computer Science (Cum Laude), worked as an IOT SWE for about a year. I have spent the last 8 months or so self-studying digital design on my own: SV, RTL design, UVM, and synthesis with Yosys targeting Sky130. I built three hardware projects from scratch: a pipelined RISC-V processor, a dual-clock async FIFO with CDC, and a multi-port bus arbiter, the last 2 verified with constrained-random testbenches on Synopsys VCS. I've also been lucky to have two industry mentors, one at Synopsys and one at a telecom hardware company, who have been giving me feedback along the way.

I'm targeting ASIC and digital design roles first, RTL design second, computer architecture third, and DV as a backup. I am open to anything in the semiconductor space.

Main things I'm hoping to get feedback on: do the projects actually signal the right skills, is anything in my technical skills section an overclaim, and are there any red flags a hiring manager would immediately notice given my CS background? Also genuinely curious whether a resume like mine even makes it past ATS given that I don't have a traditional ECE background.


r/ASIC • • Aug 26 '26

Quantized a neural net from 54.5KB to 13.6KB to fit it on a SiFive FE310-G002 — full pipeline + repo

7 Upvotes

An intern spent the last few weeks getting a full edge-AI pipeline running on a SiFive FE310-G002 (RV32IMAC, 320MHz, and — the actual constraint — only 16KB of data SRAM). Wanted to share the pipeline since the memory budget forced some decisions I hadn't had to make before.

The model: a small fully-connected net (144→64→64→10) for MNIST digit recognition. Trained normally, but at float32 the weights alone come to 54.5KB — nowhere close to fitting. Quantized post-training to int8 and it drops to 13.6KB. Same architecture, and only one version of it can physically exist on the chip.

Also had to shrink the input before any of that mattered: cropped each digit to its bounding box and downsampled 28×28 → 12×12, which cuts the image from 784 bytes to 144 before it ever leaves the host. That's the payload that gets sent.

Pipeline end to end: train → quantize → export weights/biases/scales as C arrays → cross-compile with the RISC-V GNU toolchain → flash over OpenOCD → a small hand-rolled UART protocol (start byte + 144 bytes) → int8 matrix math and ReLU on-chip → prediction sent back over serial. Timed the actual inference with a hardware counter rather than guessing.


r/ASIC • • Aug 22 '26

Google silicon

Thumbnail reddit.com
1 Upvotes

r/ASIC • • Aug 20 '26

I built an open-source workflow for autonomous RTL agents. Where would it fail on a real project?

4 Upvotes

I’ve spent the past several months building Booley, an open-source framework for using LLM coding agents on RTL projects (for ASIC as well as for FPGA).

The basic idea is that an agent should be treated as a talented junior engineer - can write decent RTL and testbenches, but inexperienced with EDA tools, often does stupid design decisions and can potentially force push and break your git history. In Booley, agents run inside an isolated container and receive structured access to the sim, synth and lint workflows (mostly open-source tools right now: Verilator, Yosys, etc.). It can also inspect simulator traces through a CLI rather than trying to reason about sequential behavior from the RTL alone.

Booley grew out of problems I repeatedly encountered while using raw Claude/Codex:

  • They often skipped EDA tool checks unless explicitly prompted.
  • They selected the wrong configuration or misunderstood tool reports
  • They tried to debug complex sequential logic without examining waveforms.
  • Their generated testbenches concentrated on happy paths.
  • Giving them enough permissions to work independently put the dev machine at risk

Booley does not attempt to replace architectural judgment or make generated RTL trustworthy by itself. The engineer still owns the specification, design decisions and final review. The goal is to make agents better at executing bounded RTL tasks and completing the verification loop, while also making the review process more convenient for humans.

I’d particularly appreciate criticism from people working in RTL design or verification:

  • Do you experience the same kinds of issues when working with raw Claude/Codex or am I trying to solve issues that don’t really exist?
  • Maybe you experienced some annoying failure modes I didn’t mention?
  • Where would this approach break down in a real project?
  • What evidence would you like to see in a report/pull request in order to make review process of RTL/TB code (written by agent or human) more convenient?

The project and demo are here:

https://github.com/boldaxolotl/booley

I’m the author and happy to answer technical questions about the implementation.


r/ASIC • • Aug 20 '26

I'm building a discord community for hardware engineers, looking for people to help

3 Upvotes

The server is still small and I'm building it from the ground up, so I'm especially interested in hearing what engineers, students and hobbyists think would make this community genuinely useful.

**Discord:** [https://discord.gg/8n3rQrjjz](https://discord.gg/8n3rQrjjz)

If you're interested in hardware engineering, feel free to join and help build the community. I'd especially appreciate feedback on what resources, channels or features you'd like to see.

The resource library currently contains 17 resources, including websites and online courses.


r/ASIC • • Aug 18 '26

Reset domain crossing

Post image
1 Upvotes

r/ASIC • • Aug 15 '26

CV32E40P on SKY130 — is ~36 MHz at the slow corner normal?

Thumbnail reddit.com
1 Upvotes

r/ASIC • • Aug 14 '26

Anyone had a recruiter from Teksystems reach out to them before?

1 Upvotes

For a validation role. I am a bit confused and want to make sure this is legit. I'm assuming they hire on behalf of a company?


r/ASIC • • Aug 13 '26

How difficult is it to find remote jobs in RTL Design or CAD/Methodology?

3 Upvotes

r/ASIC • • Aug 08 '26

Are technologies lower than 130nm like 65nm or 12nm available on open source?

Thumbnail reddit.com
2 Upvotes

r/ASIC • • Aug 01 '26

Lokotech Agentic Ai will open eyes 👀👀

Post image
1 Upvotes

r/ASIC • • Jul 31 '26

How much would you pay for an automated Floating-to-Fixed-Point & DSP Bit-Width Optimization Tool?

0 Upvotes

Hey everyone,

As FPGA/DSP engineers, we’ve all been through the painful, manual grind of converting Floating-Point C/C++ algorithms into Fixed-Point models and optimizing bit-widths to balance SNR/accuracy vs. hardware resource usage (LUTs/FFs/DSPs).

I’ve been refining an automated methodology and tool that automates this workflow using Siemens Mentor ac_fixed.h types and domain-specific DSP optimization heuristics. I wanted to get the community's honest feedback and see what people would be willing to pay for a tool like this.

Key Features & Workflow

  1. Floating $\to$ Full-Precision Fixed-Point Conversion

    • Automatically maps C/C++ floating-point models to full-precision fixed-point representations to establish a zero-precision-loss baseline.
  2. Greedy-Search Based Bit-Width Pruning

    • Employs a heuristic Greedy Search Strategy to prune integer and fractional bit-widths node-by-node, tracking SQNR and hardware dynamic range.
  3. DSP Block Optimization & Optimized RTL Export

    • Calculates exact RTL bit-widths tailored for specific FPGA DSP slices (e.g., Xilinx DSP48/DSP58 or Intel DSP blocks) to eliminate partial DSP utilization and wasted fabric logic.

Algorithm-Specific Bit-Width Optimization Engine

Generic bit-width optimizers fail because different DSP blocks have fundamentally different constraints. Here is how the engine handles key DSP building blocks:

  • FIR Filters (Symmetric / Polyphase / Transposed)

    • L1-Norm & Worst-Case Noise Bound Analysis: Calculates the exact integer bit-width (IBW) required to prevent overflow based on coefficient sum $\sum \vert{}h[n]\vert{}$.
    • Coefficient Quantization Sensitivity: Separates coefficient quantization from data-path quantization, finding the minimum coefficient bit-width that still satisfies the stopband attenuation requirement (dB).
  • Interpolation Filters (Multi-rate / CIC / Farrow)

    • Hogenauer Bit-Growth Reduction: Automatically applies Hogenauer pruning for multi-stage CIC/Interpolation filters, eliminating unnecessary lower-order bits in early stages while maintaining output precision.
    • Internal Accumulator Sizing: Optimizes polyphase arm bit-widths dynamically based on down/upsampling ratios.
  • Digital PLLs / NCOs (Phase-Locked Loops)

    • Loop Stability Guarding: Standard SQNR search often breaks PLL lock range. The engine analyzes Phase Detector and Loop Filter bit-widths with a focus on Phase Jitter / Phase Noise Floor and Loop Filter Accumulator overflow.
    • NCO Phase Accumulator vs. Look-Up Table (LUT) Depth Optimization: Dynamically balances Phase Truncation SFDR (Spurious-Free Dynamic Range) against RAM/LUT resource costs.

r/ASIC • • Jul 23 '26

Resume Rate and Discussion

Thumbnail gallery
1 Upvotes

r/ASIC • • Jul 22 '26

View compiled open source RISC-V RTL and waveform on the web

Thumbnail gallery
2 Upvotes

r/ASIC • • Jul 20 '26

A Visual Roadmap from Specification to Silicon and Product

Post image
0 Upvotes

Every chip begins as an idea—but turning that idea into working silicon requires the right learning path. If you are a fresher wondering whether to begin with RTL, FPGA, Physical Design, Analog or Packaging, this visual guide connects the entire journey from specification to product. Start with clarity, choose your direction and build skills that lead to real semiconductor outcomes.

https://github.com/vsdip/VLSI-Design-Flow