Silicon To Software

Imran Valiani

Welcome to Silicon to Software, the podcast covering PCB manufacturing, AI infrastructure, hardware, and cybersecurity. Hosted by Imran Valiani, an industry insider with 20+ years of experience in PCB electronics manufacturing and technical sales serving major Bay Area and global tech clients. This show explores the deep hardware layer that makes AI, autonomous systems, and modern technology actually work—the circuit boards, chips, and supply chains that most tech writers never see up close. Subscribe for expert technical teardowns on everything from autonomous vehicle vulnerabilities to the future of silicon compute. 🌐 Read our latest articles and get in touch at https://silicontosoftware.com

  1. 3d ago

    NVIDIA 800V DC: The Power Problem It Doesn't Solve

    A one-megawatt AI rack fed at 54 volts has to pull about 18,500 amps. At 800 volts, the same rack draws about 1,250. NVIDIA estimates a 54-volt megawatt rack would need up to 200 kilograms of copper busbar, and its power shelves alone would eat up to 64 rack units. In this episode: - Why rack power is climbing toward a megawatt: more GPUs packed into one rack so they can talk over short copper NVLink links - The 54-volt comparison: roughly 15 times less current at 800 volts, far less heat in the copper - The comparison most coverage misses: against 480-volt AC already in many data halls, each wire carries almost the same current — the gain is two conductors instead of three - The transitional rack: the first 800-volt hardware converts back down to 54 volts inside the compute rack, adding a conversion step rather than removing one; NVIDIA projects up to 5% better efficiency, and as of late October no independent measurements from an operating 800-volt AI data hall were found - Where the hard engineering moves: converters close to the GPU (silicon carbide, gallium nitride, stacked topologies — vendor numbers, not field data), and the circuit board, where 800-volt spacing, laminate choice, manufacturing tolerances, and cleanliness become safety issues - Protection and certification: DC arcs are harder to extinguish than AC arcs, grounding is still undecided, solid-state breakers are only mature at lower currents, and key standards were written around lower voltages or AC The verdict: against a 54-volt bus the physics is decisive, but 800-volt DC does not make the power problem disappear — it moves it into converters, boards, connectors, breakers, and certification. Full analysis: https://www.silicontosoftware.com/nvidia-800v-dc-architecture/

    NVIDIA 800V DC: The Power Problem It Doesn't Solve
  2. Oct 23

    Tesla AI5 Chip: Why Samsung and TSMC Make It So Complicated

    Tesla AI5 could be manufactured by Samsung and TSMC. But how can two different chip implementations run the same AI software? We break down Tesla AI5 chip manufacturing, semiconductor design, PCB power delivery, thermal management, and the hidden engineering costs of dual-foundry production. Tesla's AI5 strategy raises a difficult semiconductor engineering question: How do you maintain consistent software-visible behavior when two different foundries manufacture separate physical implementations of a processor? In this episode of Silicon to Software, host Imran Valiani examines the engineering challenges behind Tesla's proposed Samsung and TSMC manufacturing approach. With more than 20 years of experience in PCB manufacturing and technical sales, Imran explains why the problems don't stop at the silicon die. WHAT YOU'LL LEARN - Why Tesla is pursuing Samsung and TSMC for AI5 manufacturing - What changes when a semiconductor design moves between foundries - Why RTL and architecture can transfer while standard cells and physical layouts cannot simply be reused - How chip performance, power consumption, and operating limits may differ - Why BGA pin assignments, package compatibility, power sequencing, and PCB power delivery require validation - How two chips with similar total power can produce different thermal hotspots - Why formal equivalence, numerical equivalence, and real-time system correctness are separate verification objectives - What Tesla has publicly confirmed versus what remains unverified THE ENGINEERING PROBLEM A common logical architecture does not guarantee identical physical implementations. Samsung and TSMC use different manufacturing technologies, design rules, standard-cell libraries, and process-specific IP. Those differences can affect timing closure, power distribution, semiconductor packaging, thermal behavior, and system qualification. And even if both processors execute the same AI software, the complete system still has to meet its performance and timing requirements. For robotics and autonomous systems, producing the correct result is not enough. The result must also arrive when the system needs it. TESLA AI5 PRODUCTION OUTLOOK Tesla has discussed AI5 production plans for 2027, while Elon Musk has expressed hopes for volume production around mid-2027. Specific foundry process nodes, memory configurations, manufacturing allocations, and package-level compatibility details remain incompletely confirmed. This episode distinguishes reported manufacturing information from Tesla's public statements. READ THE FULL ENGINEERING ANALYSIS Read the complete article, including technical diagrams and supporting sources: https://www.silicontosoftware.com/ ABOUT THE HOST Imran Valiani is the founder of Silicon to Software and has more than 20 years of experience in PCB electronics manufacturing and technical sales. Silicon to Software explores the physical engineering behind semiconductors, AI infrastructure, PCB manufacturing, embedded systems, and modern electronics. SUBSCRIBE Subscribe to Silicon to Software for technical discussions about the manufacturing constraints, hardware trade-offs, and reliability challenges behind today's technology. #TeslaAI5 #SemiconductorManufacturing #AIHardware

    Tesla AI5 Chip: Why Samsung and TSMC Make It So Complicated
  3. Oct 19

    Face ID vs Fingerprint Sensors: How They Really Work

    How does Face ID recognize your face, and how do fingerprint sensors actually work? Discover the infrared, ultrasonic, optical, and capacitive technology behind smartphone biometric authentication. From Apple's Face ID and Touch ID to Google's Pixel 8, we examine the engineering behind biometric security—and why these systems sometimes fail. In this episode of Silicon to Software, host Imran Valiani, with more than 20 years of experience in PCB electronics manufacturing, breaks down the hardware and physics behind the smartphone technologies we use every day. WHAT YOU'LL LEARN 1. How Fingerprint Sensors Work Discover the differences between capacitive, optical, and ultrasonic fingerprint sensors. Learn how capacitive sensors detect changes caused by fingerprint ridges and valleys, how optical sensors use display illumination and reflected light, and how ultrasonic sensors measure acoustic echoes through the display stack. 2. Why Samsung's Fingerprint Sensor Failed In 2019, Samsung acknowledged an unlocking issue affecting certain Galaxy smartphones using ultrasonic fingerprint recognition. We examine how textured silicone screen protectors created an unexpected security problem—and what the incident teaches engineers about sensor integration and accessory compatibility. 3. How Apple's Face ID Works Apple's TrueDepth camera system projects invisible infrared dots to capture facial depth information. Learn how facial data is converted into mathematical representations and protected through the iPhone's Secure Enclave. We also explain why Face ID can operate in complete darkness. 4. Apple Face ID vs. Google Pixel 8 Google's Pixel 4 used dedicated infrared facial recognition hardware. The Pixel 8 took a different approach, using its conventional front camera and machine learning to achieve Android Class 3 biometric security. What does that mean for security, low-light performance, and hardware design? 5. Can Biometric Authentication Be Fooled? Apple reports a random-person Face ID false-match probability of less than one in a million under its stated conditions. But random false matches and deliberate spoofing attacks are different security measurements. We explain why that distinction matters, how physical presentation attacks are evaluated, and why your passcode remains the ultimate fallback. VIDEO CHAPTERS [Insert Timestamps here] READ THE FULL ENGINEERING ANALYSIS For detailed technical explanations, engineering diagrams, and supporting research, visit: https://www.silicontosoftware.com ABOUT SILICON TO SOFTWARE Silicon to Software explores the engineering behind modern technology—from semiconductor devices and PCB manufacturing to embedded systems, automotive electronics, and AI hardware. Hosted by Imran Valiani, a technology professional with more than 20 years of experience in PCB electronics manufacturing and technical sales. CONNECT WITH SILICON TO SOFTWARE Website: https://www.silicontosoftware.com X: https://x.com/SiToSoftware Subscribe to the channel for engineering-focused technology explanations, hardware analysis, and semiconductor insights. #FaceID #FingerprintSensor #BiometricSecurity

    Face ID vs Fingerprint Sensors: How They Really Work
  4. Oct 12

    SSD Lifespan Explained: Why Every Write Wears Out Your Drive

    Your SSD wears out every time you save a file. But how long do SSDs actually last, and what happens when they reach their write endurance limit? In this episode of Silicon to Software, Imran Valiani explains the engineering behind SSD lifespan, NAND flash wear, write amplification, and the controller technology that keeps modern solid-state drives working for years. WHAT YOU'LL LEARN • Why NAND flash cells wear out during program/erase cycles • How SLC, MLC, TLC, and QLC differ in endurance • Why SSDs write more data internally than your computer requests • How wear leveling, spare blocks, and LDPC error correction protect your data • What TBW (Terabytes Written) and DWPD actually mean • Why a 600 TBW rating is not an automatic SSD failure point • The difference between SSD write endurance and data retention • What Tesla's eMMC recall teaches engineers about flash endurance THE ENGINEERING BEHIND SSD LIFESPAN Every NAND flash cell has a finite program/erase endurance budget. As cells wear, their threshold-voltage distributions shift and widen, increasing the risk of errors. Modern SSD controllers compensate through wear leveling, garbage collection, over-provisioning, and error correction. But the controller introduces another critical variable: write amplification. A host write does not necessarily equal one NAND write. Internal data movement can multiply the amount of data written to flash. We also examine Samsung's 990 PRO 1TB SSD, rated for 600 TBW over five years, and explain why reaching that endurance threshold does not automatically mean the drive stops working. Finally, we examine the Tesla Model S and Model X eMMC recall as a real-world example of what happens when flash endurance is insufficient for the system's write workload. READ THE FULL TECHNICAL ANALYSIS https://www.silicontosoftware.com/ssd-lifespan-nand-flash-wear/ ABOUT SILICON TO SOFTWARE Silicon to Software explores the hardware engineering behind modern technology, from PCB manufacturing and semiconductors to embedded systems, AI infrastructure, and electronics reliability. Hosted by Imran Valiani, with more than 20 years of experience in PCB electronics manufacturing and technology sales. CONNECT WITH SILICON TO SOFTWARE Website: https://www.silicontosoftware.com/ X: https://x.com/SiToSoftware Instagram: https://www.instagram.com/silicon_to_software/ Subscribe to Silicon to Software for engineering-focused discussions about the physical hardware behind the technology we use every day. #SSDLifespan #NANDFlash #HardwareEngineering

    SSD Lifespan Explained: Why Every Write Wears Out Your Drive
  5. Oct 9

    Smartwatch Heart Rate Accuracy: Why Your Watch Gets It Wrong

    Your smartwatch measures heart rate using light — but the number on your wrist is not a direct measurement of your heartbeat. In this episode of Silicon to Software, I break down how optical PPG heart-rate sensing actually works, from green LEDs and photodiodes to analog front-end electronics, motion artifacts, and the algorithms that ultimately produce the BPM number you see on your watch. We look inside the complete measurement chain: • Why smartwatches commonly use green light for heart-rate sensing • How reflected light changes with pulsatile blood volume • Why optical crosstalk can contaminate the signal before it reaches the skin • How watch fit and skin contact affect the optical path • How the photodiode, transimpedance amplifier, ambient-light cancellation, and ADC recover a tiny pulsatile signal • Why increasing gain can create saturation risk • Why higher LED drive and faster sampling come with a power penalty • How wrist movement creates motion artifacts • Why running cadence can sometimes resemble a heart-rate signal • What research actually says about skin pigmentation and PPG accuracy • Why hardware, mechanics, optics, and algorithms all contribute to the final measurement The important engineering point is this: A smartwatch does not directly detect your heartbeat. It estimates heart rate from a small pulsatile change buried inside a much larger optical signal. And by the time software sees that signal, the quality of the measurement has already been shaped by the LEDs, photodiode, mechanical geometry, wrist contact, analog electronics, ambient light, and motion. That is what makes smartwatch heart-rate monitoring such an interesting engineering problem. ABOUT SILICON TO SOFTWARE Silicon to Software explores the engineering behind the technology we use every day — from PCBs and semiconductors to embedded systems, AI hardware, electronics manufacturing, and consumer technology. Hosted by Imran Valiani, with 20+ years of experience in PCB manufacturing and technology sales. 🌐 WEBSITE https://www.silicontosoftware.com 📱 FOLLOW SILICON TO SOFTWARE X: https://x.com/SiToSoftware Instagram: https://www.instagram.com/silicon_to_software/ If you enjoy engineering breakdowns that go beyond the marketing specifications, subscribe to Silicon to Software and turn on notifications for future episodes. #Smartwatch #HeartRate #Engineering

    Smartwatch Heart Rate Accuracy: Why Your Watch Gets It Wrong
  6. Oct 5

    USB-C Explained: Why Every Port Is Different

    USB-C ports look identical—but charging speed, data bandwidth, video support, and cable capability can be completely different. Here’s the engineering behind USB-C, USB Power Delivery, USB4, Thunderbolt, e-marker chips, and the PCB itself. USB-C was supposed to make connectivity simpler. The connector became universal. The capability behind it didn't. In this episode of Silicon to Software, Imran Valiani breaks down what actually happens when you plug in a USB-C cable—and why two identical-looking ports can deliver radically different results. We start with the 24-pin USB Type-C connector and the CC1/CC2 configuration channels responsible for orientation, power roles, and USB Power Delivery negotiation. Then we go inside the cable itself. Higher-power USB-C cables can contain an e-marker chip that identifies the cable's capabilities to the connected hardware. That becomes critical as USB Power Delivery moves beyond standard 3A operation and into 5A cables capable of supporting up to 240W under Extended Power Range. But power is only part of the story. USB-C can carry everything from USB 2.0 to USB4 40Gbps and the newer USB 80Gbps tier. DisplayPort Alt Mode and Thunderbolt add another layer of capability—all behind a connector that can look exactly the same from the outside. And at those speeds, the PCB becomes part of the channel. We examine: • USB-C CC1 and CC2 negotiation • USB Power Delivery (USB PD) • E-marker chips and 60W vs. 240W cables • USB 2.0 vs. USB4 40Gbps vs. USB 80Gbps • Thunderbolt 4 and Thunderbolt 5 • DisplayPort Alt Mode • Controlled-impedance differential pairs • PCB vias and via-stub reflections • Retimers, redrivers, and muxes • Signal-integrity and insertion-loss constraints • Why identical USB-C ports can have different capabilities The connector isn't the promise. The silicon, cable, and PCB behind it are. READ THE FULL ENGINEERING BREAKDOWN Silicon to Software: https://www.silicontosoftware.com/ FOLLOW SILICON TO SOFTWARE X: @SiToSoftware Instagram: @silicon_to_software LinkedIn: Imran Valiani ABOUT SILICON TO SOFTWARE Silicon to Software examines the hardware layer behind modern technology—from PCB manufacturing and semiconductor packaging to embedded electronics, AI infrastructure, automotive systems, and high-speed hardware. Hosted by Imran Valiani, with 20+ years of experience in PCB electronics manufacturing and technology sales. SUBSCRIBE Subscribe for engineering-focused breakdowns of the technologies behind the headlines. #USBC #USB4 #HardwareEngineering

    USB-C Explained: Why Every Port Is Different

About

Welcome to Silicon to Software, the podcast covering PCB manufacturing, AI infrastructure, hardware, and cybersecurity. Hosted by Imran Valiani, an industry insider with 20+ years of experience in PCB electronics manufacturing and technical sales serving major Bay Area and global tech clients. This show explores the deep hardware layer that makes AI, autonomous systems, and modern technology actually work—the circuit boards, chips, and supply chains that most tech writers never see up close. Subscribe for expert technical teardowns on everything from autonomous vehicle vulnerabilities to the future of silicon compute. 🌐 Read our latest articles and get in touch at https://silicontosoftware.com