Wearing Flip-Flops

Wearing Flip-Flops

In the world of semiconductor engineering, the path from architecture to silicon is rarely a straight line. Wearing Flip-Flops is a podcast dedicated to the people that love hardware, engineers, architects, and leaders navigating the challenges of modern SOC (System-on-Chip) verification. Hosted by industry veteran Ronen Laviv, the show strips away the corporate jargon to have honest, high-level technical conversations about EDA tools, simulation platforms, and the verification bottlenecks that keep R&D teams up at night. Whether we’re discussing the latest in hardware-assisted verification or the unique culture of lean startup teams, we keep it grounded, insightful, and true to our name completely informal. Enjoyed a specific episode? A rating takes 10 seconds and helps more chip designers find the show. Spotify: on the show page, tap the stars under the description (or ... then “Rate show”). Apple Podcasts: scroll to the bottom of the show page, tap the stars, then “Write a Review” and share one takeaway that stuck with you. If you’re looking for a technical deep dive without the stiff suit-and-tie atmosphere, grab your flip-flops and join us.

  1. 6h ago ·  Video

    Hope Is Not a Strategy

    Only 5% of IC/ASIC projects hit first-silicon success in 2026. Two years ago it was 14%. Dr. Ashish Darbari, CEO of Axiomise, buys the number 100%, and he has a pamphlet on his desk that explains why: hope is not a strategy. In episode 15 of Wearing Flip-Flops, the hardware podcast for chip designers and verification engineers, host Ronen Laviv talks formal verification with one of the field's most outspoken practitioners. Ashish has spent 25+ years in formal, from a DPhil at Oxford through ARM, Imagination Technologies and OneSpin, before founding Axiomise in London in 2017. We cover: Why first-silicon success collapsed and why AI silicon makes it worse: system-of-systems coherency, coherent NoCs on top of coherent NoCs, and software that changes with every modelHow many teams really use formal for sign-off (Ashish's estimate: about a dozen companies worldwide)A real bug: a GPU test chip that would not boot because of an X read from an uninitialized FIFOThe 512-deep FIFO that only ever used one slot, and why reachability analysis missed itWhy clock-gating verification is a nightmare in practiceScenario coverage and mutation: how to measure formal so a VP can sign offAre formal engineers treated as second-class citizens in DV?Finding bugs in taped-out RISC-V cores and vector FPUs within hoursLLM-written SystemVerilog assertions: who audits them?Chapters 00:58 Welcome: Ashish Darbari, CEO of Axiomise 01:17 From Oxford to ARM, Imagination, OneSpin and Axiomise 04:16 First-silicon success drops from 14% to 5%: do you buy it? 07:42 System of systems: why AI chips break verification 09:41 How many designs actually use formal in 2026? 11:28 Is formal growing? Nvidia, DVCon and the big accounts 12:58 Power, security, clocking: what formal can catch 15:22 The 512-deep FIFO that only used one slot 17:12 Clock gating: easy to define, a nightmare to verify 19:24 Without measurement, formal is just a promise 23:56 Scenario coverage and mutation, explained 27:03 Are formal engineers second-class citizens? 29:15 Merging formal and simulation coverage, and hope is not a strategy 31:12 What the big three do well, and the gap Axiomise fills 34:13 Apps for NoCs, floating point and RISC-V 35:02 Bugs found in already-verified designs 38:43 Vector FPU bugs found within 90 minutes of git clone 39:50 LLM-generated assertions: can you trust them? 43:41 Redundant logic found at Akeana before tape-out 47:00 Wrap-up Mentioned in this episode 2026 Siemens EDA and Wilson Research Group Functional Verification Study: https://blogs.sw.siemens.com/verificationhorizons/2026/09/08/the-2026-functional-verification-study/ Akeana partners with Axiomise: https://www.newswire.com/news/akeana-partners-with-axiomise-for-formal-verification-of-its-cores Verified. Until It Isn't (Axiomise, Semiconductor Engineering): https://semiengineering.com/verified-until-it-isnt-why-datapath-verification-needs-a-new-playbook/ Part two with Ashish is episode 16, Nobody Sues an AI Agent (Yet). Enjoying Wearing Flip-Flops? Rate us on Spotify or Apple Podcasts and subscribe on YouTube. Ratings are how other chip designers find the show. Bugs have feelings, too. Got a hardware story, a bug you'll never forget, or a guest we should invite? Tell us: https://wearing-flip-flops.com/contact Full episode page, takeaways and FAQ: https://wearing-flip-flops.com #FormalVerification #ChipDesign #Semiconductors #RISCV #DesignVerification #EDA #AIchips

  2. Nov 2 ·  Video

    Probably Proven

    Formal verification gives you a mathematical yes or no. A large language model gives you its best guess. What happens when the LLM writes the properties and drives the proof? Prof. Ziyad Hanna, Corporate Vice President of R&D and Strategic Head of AI at Cadence Design Systems, returns to Wearing Flip-Flops with host Ronen Laviv. Ziyad worked on formal verification at Intel and led R&D for the Jasper formal verification platform, so this one goes deep on the discipline he grew up in. In this episode: - When formal verification moved from research into everyday engineering - LLMs in front of formal engines: a category error, or what makes AI safe to use? - AI-generated assertions, and weak properties that prove trivially and still show green - Bounded proofs: does AI make them more trustworthy, or just more comfortable? - State space explosion and the formal skills barrier: what AI solves, and what it might hide - Formal apps vs AI agents, and how many engineers can now drive Jasper on their own - Where the line between formal and simulation sits in 2026 - Agents launching hundreds of simulation and formal jobs: who schedules them, and where they run - Verification in the cloud: cloud-native or lift and shift, burst capacity, spot instances and checkpointing long proofs - Who watches the compute farm at 2am when agents run unattended Part 1 with Ziyad, Who Signs the Tapeout?, covers agentic AI in chip design and who owns a silicon failure. Enjoyed the episode? Rate and review Wearing Flip-Flops on Apple Podcasts or Spotify, or subscribe on YouTube. It takes a minute and helps other chip designers find the show. Want to be a guest? If you work on formal verification, chip design or the silicon behind AI and have a story worth telling, reach out: https://wearing-flip-flops.com/contact Follow the show on LinkedIn: https://www.linkedin.com/company/wearing-flip-flops Wearing Flip-Flops is a hardware podcast for chip designers, with deep dives into verification, emulation and the silicon powering AI.

  3. Oct 19 ·  Video

    Who Signs The Tapeout ?

    When an AI agent designs and verifies the chip, and a human signs the tapeout, who owns the bug that reaches silicon? Prof. Ziyad Hanna, Corporate Vice President of R&D and Strategic Head of AI at Cadence Design Systems, joins Ronen Laviv to talk about generative AI and agentic AI in chip design. Ziyad spent decades in formal verification at Intel and Cadence before taking on AI strategy across Cadence's EDA platforms. In this episode: - The role of EDA companies in generative AI: model provider, orchestration layer or ground truth? - Level-5 autonomy for the Cadence ChipStack AI Super Agent, and why AI in front-end design and verification is still early - What sits inside the claim of 40x faster RTL validation - Why Cadence bought ChipStack instead of building it - How a head agent coordinates design and verification agents, and where it hands back to the engineer - Accountability when an AI agent's work fails in silicon - Multi-vendor EDA flows: does agentic AI make them harder? - When chip companies should build their own AI agents, and when to buy - Which EDA products generative AI could replace, and how chip designers can prepare This is part 1 of 2 with Ziyad Hanna. Part 2, "Probably Proven", covers formal verification, AI and cloud. Episode article, key takeaways and transcript: https://wearing-flip-flops.com/who-signs-the-tapeout Wearing Flip-Flops is a hardware podcast for chip designers, with deep dives into verification, emulation and the silicon powering AI. https://wearing-flip-flops.com

  4. Oct 5 ·  Video

    The Tools, The Bill, and the jobs

    An AI agent built a complete RISC-V core in 12 hours. So why can't it tape out your SoC yet? Tzviel Lemberger from Google is back to separate the breakthrough from the hype. Description Tzviel Lemberger leads AI activities in Google's Silicon Hardware group, and he's back for round two. Last time we ran out of time with questions still on the table. This time we went straight at them. Tzviel compares today's AI chip design demos to the first four-minute mile. Once one runner broke the barrier, everyone believed it was possible. A RISC-V core in 12 hours does the same thing for chip design. Then reality shows up: a full SoC with dozens of IPs, legacy layout, PPA tradeoffs, and a spec that changes every week is a different race altogether. We talk about what chip designers should expect from EDA vendors now that agents, not humans, run the tools. An agent can generate a million versions of an RTL block. If every evaluation needs an overnight run, the flow never converges, either on time or on budget. We also cover why multi-vendor AI flows are stuck on data formats, and how agents move work from engineers to compute. Tzviel explains what owning the entire stack, from models to cloud to silicon, means for co-design at Google. Then we get practical. Is RTL the new assembly language? Will lint and log-crawling be handed to agents? Will waveform viewers and formal engines survive as independent checks? And the question everyone keeps asking: if AI does the junior-level work, how do juniors become senior architects? If you work in RTL design, verification, physical design, or EDA, and you want a grounded view of where AI chip design really stands, this one is for you. In this episode The four-minute mile of chip design: what AI demos prove, and what they don'tAgent-friendly EDA: faster, lighter feedback loops for AI-driven flowsMulti-vendor AI flows and the data format problemFrom human work to compute workIs RTL the new assembly? Higher-level hardware languagesThe junior-to-senior gap in the AI eraHow engineers can prepare to what's comingEnjoyed it? Rate and review Wearing Flip-Flops. It's the single biggest thing that helps other chip designers find the show. Have a topic worth an episode, or want to be a guest? drop us a note.

  5. Sep 9 ·  Video

    The Death Of The Waveform Viewer

    Nobody enjoys opening a waveform viewer at 11pm. So here's the question this episode starts with: if AI reads the simulation database directly and does the root cause analysis for you, how much time are you actually spending in waves a year from now? Predrag Nikolic, AI Tech Lead at Veriest, thinks a lot less, and he is careful to say he hopes so rather than knows so. The logic is worth following. A waveform viewer is a human debug interface. It exists because a person has to eyeball signals to work out why a test failed. AI does not need pictures, it works against the database, and root cause analysis on failing regressions is already one of the few places generative AI genuinely earns its keep in verification today. Extend that and manual waveform browsing becomes the fallback rather than the first move. The obvious counterargument is that you open waves precisely when you do not trust what the tool just told you. That is exactly where the rest of the conversation goes. Veriest works hands-on inside customer verification teams across many companies, so this is the pattern Predrag sees across a lot of SoC verification flows rather than one company's experience. Yours probably looks different in places, and that is the interesting part. Also in this episode: Closed-loop verification, where AI debugs a failure, proposes a fix and re-runs the regression, exists at most serious shops now. Almost nobody runs it day to day. Predrag's read is that the gap is adoption and efficiency, not capability. Why design verification stays in SystemVerilog and UVM even though LLMs write better Python. There is far more Python in the training data, so the models are better at it, but a human reviews every line and that human is a verification engineer who knows SV. The reviewer is the constraint, not the model. Why the next wave of AI lands on the passive side of the testbench, monitors, checkers, coverage inspection and documentation, before it touches sequence and test generation. Build vs buy for AI verification infrastructure, from someone sitting inside customer teams while they make the decision. What EDA vendors have to deliver before any of this is trusted in a signoff flow. And the bottleneck waiting on the other side of all of it: simulation runtime. Disagree? Good. Tell us where your verification flow looks different. Wearing Flip-Flops is a podcast about hardware and chip design, hosted by Ronen Laviv. Deep dives into verification, EDA, silicon architecture and the engineering behind the AI hardware buildout, for the people who actually design the chips. All episodes: https://wearing-flip-flops.com #chipdesign #verification #systemverilog #uvm #eda #semiconductors #asic #functionalverification #waveformviewer #rtl

About

In the world of semiconductor engineering, the path from architecture to silicon is rarely a straight line. Wearing Flip-Flops is a podcast dedicated to the people that love hardware, engineers, architects, and leaders navigating the challenges of modern SOC (System-on-Chip) verification. Hosted by industry veteran Ronen Laviv, the show strips away the corporate jargon to have honest, high-level technical conversations about EDA tools, simulation platforms, and the verification bottlenecks that keep R&D teams up at night. Whether we’re discussing the latest in hardware-assisted verification or the unique culture of lean startup teams, we keep it grounded, insightful, and true to our name completely informal. Enjoyed a specific episode? A rating takes 10 seconds and helps more chip designers find the show. Spotify: on the show page, tap the stars under the description (or ... then “Rate show”). Apple Podcasts: scroll to the bottom of the show page, tap the stars, then “Write a Review” and share one takeaway that stuck with you. If you’re looking for a technical deep dive without the stiff suit-and-tie atmosphere, grab your flip-flops and join us.

You Might Also Like