<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="https://media.rss.com/style.xsl"?>
<rss xmlns:podcast="https://podcastindex.org/namespace/1.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:psc="http://podlove.org/simple-chapters" xmlns:atom="http://www.w3.org/2005/Atom" xml:lang="en" version="2.0">
  <channel>
    <title><![CDATA[Athos Silicon]]></title>
    <link>https://rss.com/podcasts/athos-silicon-why</link>
    <atom:link href="https://media.rss.com/athos-silicon-why/feed.xml" rel="self" type="application/rss+xml"/>
    <atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
    <description><![CDATA[<p>Athos Silicon is a semiconductor company focused on building the compute foundation for safety critical autonomy and physical AI. The core idea is to move beyond the traditional model of a single monolithic system on chip that must never fail, and instead build a scalable platform that assumes faults will happen, detects them quickly, contains them, and keeps operating in a controlled way. The company’s work combines chiplet based design, structured redundancy, fast consensus checking, deterministic scheduling, and fault tolerant power and control so autonomy systems can be engineered for real world deployment at scale.</p><p>In this podcast, the conversation will explore why autonomy is not only an AI performance problem but a reliability problem that becomes unavoidable when products ship in large volumes and operate for billions of miles. It will unpack how a multi domain compute architecture can cross check results and reach agreement before committing critical decisions, and how disagreements can trigger recovery paths such as retry, reset, isolation, or safe degradation. The episode will also cover how repeating a verified chiplet building block enables scaling without multiplying validation risk, and how role based execution can distribute workload and wear over time while keeping timing predictable. Finally, it will discuss why power integrity, fault containment, and redundant control are essential to prevent cascading failures, and how this architecture supports safety arguments for certification and long term trust in the field.</p>]]></description>
    <generator>RSS.com 2026.401.141116</generator>
    <lastBuildDate>Fri, 17 Apr 2026 15:24:22 GMT</lastBuildDate>
    <language>en</language>
    <copyright><![CDATA[Athos Silicon]]></copyright>
    <itunes:image href="https://media.rss.com/athos-silicon-why/20260227_100228_4ab146adad63cbc7cd664d6d16551cde.png"/>
    <podcast:guid>72363cc0-60e8-5c39-892a-52891abcaa54</podcast:guid>
    <image>
      <url>https://media.rss.com/athos-silicon-why/20260227_100228_4ab146adad63cbc7cd664d6d16551cde.png</url>
      <title>Athos Silicon</title>
      <link>https://rss.com/podcasts/athos-silicon-why</link>
    </image>
    <podcast:locked>yes</podcast:locked>
    <podcast:license>Athos Silicon</podcast:license>
    <itunes:author>Francois Piednoel</itunes:author>
    <itunes:owner>
      <itunes:name>Francois Piednoel</itunes:name>
    </itunes:owner>
    <itunes:explicit>false</itunes:explicit>
    <itunes:type>episodic</itunes:type>
    <itunes:category text="Business"/>
    <itunes:category text="Leisure">
      <itunes:category text="Automotive"/>
    </itunes:category>
    <podcast:medium>podcast</podcast:medium>
    <podcast:txt purpose="ai-content">true</podcast:txt>
    <item>
      <title><![CDATA[Why Athos Silicon]]></title>
      <itunes:title><![CDATA[Why Athos Silicon]]></itunes:title>
      <description><![CDATA[<p>In this podcast, Athos Silicon is introduced as a company building the computing foundation for physical AI, including autonomous cars, commercial drones, industrial robots, and humanoid robots. The discussion starts with a simple reality: autonomy is not just about better AI models or more compute. At scale, reliability becomes the real problem, because rare faults become inevitable when millions of systems operate for billions of miles. The podcast then explains Athos Silicon’s core platform, mSoC, meaning Multiple Systems on Chip. Instead of relying on one monolithic system that must never fail, mSoC uses multiple cooperating compute domains that cross check each other to prevent a single point of failure from becoming a catastrophe. The physical strategy behind this is Chiptile: design one chiplet, verify it deeply, then tile it into a scalable fabric that can isolate a failing tile without losing the whole system. A key theme is voting as a first class architectural feature, using triple redundant mailboxes so disagreements are detected quickly and outliers can be reset, isolated, or safely degraded. The episode also touches on deterministic scheduling, role based execution, and power monitoring to prevent cascading failures. The takeaway is clear: the next era of autonomy will be built on architectures designed to fail safely and remain trustworthy in real deployments.</p>]]></description>
      <link>https://rss.com/podcasts/athos-silicon-why/2588027</link>
      <enclosure url="https://content.rss.com/episodes/375382/2588027/athos-silicon-why/2026_02_27_22_23_52_36deb6f1-f64c-4a57-8d80-b8717350bd4a.mp3" length="12034580" type="audio/mpeg"/>
      <guid isPermaLink="false">a7c08e65-4258-4755-8418-bf2fb410e334</guid>
      <itunes:duration>752</itunes:duration>
      <itunes:episodeType>full</itunes:episodeType>
      <itunes:season>1</itunes:season>
      <podcast:season>1</podcast:season>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:explicit>false</itunes:explicit>
      <pubDate>Fri, 27 Feb 2026 22:25:22 GMT</pubDate>
      <podcast:txt purpose="ai-content">true</podcast:txt>
      <itunes:image href="https://media.rss.com/athos-silicon-why/ep_cover_20260227_100237_2c911673a2955ec56b4f07a866703050.png"/>
      <podcast:location rel="creator" geo="geo:37.3541132,-121.955174" osm="R2221647" country="us">Santa Clara, Santa Clara, Santa Clara County, California, 95050, USA</podcast:location>
    </item>
  </channel>
</rss>