An Automotive Intelligence SoC Designed Around Svashasan OS
Purpose: How Svashasan Labs proposes to develop its own automotive compute chip, Svashasan S1, by designing it around the measured workloads of Svashasan OS, and how that chip anchors a wider ecosystem of software, silicon, intelligence and developer tools.
Status note. Svashasan S1 is a proposed SoC described in an internal product requirements document (v1.0). Every hardware figure on this page is a preliminary target pending workload profiling, IP selection, architecture validation and OEM requirements. No silicon has been designed or fabricated, and the chip alone does not determine an SAE autonomy level.
Measure
Workloads first
Profile Svashasan OS on existing chips before drawing a single block.
Design
A chip shaped by the OS
NPU, memory bandwidth and safety island sized to measured demand.
Gate
No premature silicon
Seven conditions must hold before any tapeout spend.
Grow
An ecosystem, not a part
OS, HAL, silicon, intelligence and SDKs reinforcing each other.
1. Why Our Own Silicon
Software-defined vehicles are consolidating dozens of separate controllers into a few central computers. The company that defines both the operating system and the compute it runs on can tune them to each other, reduce OEM integration effort and execute perception, decisions and vehicle services locally, without depending on the cloud.
Figure 1. The long-term platform. Svashasan OS stays the product; the hardware abstraction layer lets it run on existing automotive chips today, and Svashasan silicon is the proposed layer that makes it run best.
2. Designed Around Svashasan OS
S1 starts from the workloads, not the transistor count. The PRD defines five computational domains Svashasan OS must run, and each block on the chip exists to serve one or more of them.
Figure 2. Designed around Svashasan OS. The five workload domains in the S1 requirements map onto specific compute units; the dark blocks carry the heaviest load. The safety island watches everything and runs none of it.
How the fit is achieved
Figure 3. How “built for Svashasan OS” actually happens. The chip is sized from measured workloads, then the OS runs on a virtual and FPGA model of the chip, and the loop repeats until silicon would match real demand.
3. Inside S1
Figure 4. Svashasan S1, block by block. The NPU gets the most silicon because perception dominates the workload; the safety island is fenced off with its own cores, memory and reset so it survives when the main domains do not. All figures are preliminary targets from the S1 PRD.
Block
Proposed specification
Why Svashasan OS needs it
NPU
300–400 INT8 TOPS · INT4/FP16/BF16
Perception, BEV and fusion networks dominate compute
Application CPU
8 × 64-bit Arm-compatible · 2.0–2.5 GHz
Runs the Svashasan OS kernel, planning and orchestration
Real-time CPU
8 × Cortex-R52 class · lockstep capable
Deterministic ECU communication and control coordination
ISP / DSP
4–6 Gpx/s · radar and audio processing
Clean, synchronised sensor data before the NPU sees it
Safety island
dual lockstep MCU · ECC · independent reset
Monitors everything and survives when the main domains fail
Memory
64–128 GB LPDDR5X · 250–300 GB/s · 48–64 MB SRAM
Keeps the NPU fed; bandwidth is a top-three priority
One frame through the chip
Figure 5. One frame through the chip. Each stage hands data to the next through shared memory rather than copying it, which is where much of the latency budget is won or lost.
4. Feeding the NPU: Bandwidth and Memory
The PRD names three subsystems that will decide whether S1 is useful: NPU performance, memory bandwidth and the functional-safety architecture. The second is the one most often underestimated.
Figure 6. The arithmetic that sizes the chip. Raw camera payload alone is 23 Gbps for the baseline configuration in the S1 PRD.
Figure 7. The memory hierarchy. On-chip SRAM is the deliberate middle layer: big enough to hold sensor frames and active model tensors so the NPU is not waiting on external memory.
Figure 8. Why bandwidth matters as much as TOPS. A qualitative roofline: workloads that move a lot of data per operation hit the memory limit long before the compute ceiling. Placement of workloads is illustrative; Phase 1 profiling will measure where Svashasan OS actually sits.
5. Safe and Secure by Design
Figure 9. Isolation by design. The S1 requirements call for secure separation of seven domains; non-critical workloads must never be able to starve autonomous-driving pipelines of compute or memory.
When something fails
Figure 10. What happens when the NPU fails. The independent safety island detects, isolates and reports; the vehicle's safety architecture, not the chip alone, decides the degraded-driving response.
Hardware security
Figure 11. Security starts in silicon. A hardware root of trust anchors a verified chain up to Svashasan OS and its applications, protecting both vehicle data and Svashasan's proprietary software. Built to align with ISO/SAE 21434 and support OEM UN R155/R156 obligations.
Power and thermal
Figure 12. The power budget. Sustained NPU performance under thermal load is one of the PRD's mandatory validation tests, because peak numbers mean little inside a hot vehicle.
6. The Software Stack
S1 must ship with a full software ecosystem: secure bootloader, Linux and QNX compatibility, AUTOSAR integration, ROS 2, DDS and SOME/IP middleware, a hypervisor, ONNX-compatible inference, a dedicated NPU compiler and runtime, drivers and profiling tools.
Figure 13. The hardware abstraction layer is the strategy. Svashasan OS ships on existing chips now; S1 becomes the best place to run it, never the only one.
7. Development Roadmap
Figure 14. The development roadmap. Profiling, architecture and pre-silicon prototyping come first; the PRD's “avoid premature fabrication” rule puts a hard gate in front of tapeout.
Acceptance benchmarks
Figure 15. What S1 must achieve. Dark bars are the minimum, the dashed outline the preferred target; for latency, lower is better, so the bar shows how far minimum is from preferred.
Qualification
Figure 16. Qualification. Fifteen mandatory validation tests from the PRD, under the standards an automotive chip is judged against. Qualifying the chip does not by itself establish compliance of the vehicle.
8. Competitive Position
Figure 17. Where S1 aims to sit. The PRD benchmarks against NVIDIA DRIVE Thor for AI compute and NXP's S32N family for deterministic, safety-oriented central compute; S1's thesis is to combine both around its own OS. Dots show only what the PRD records — check current vendor datasheets before any external comparison.
9. Building the Ecosystem
Figure 18. Own the system, license the commodity. The value is in the architecture and how tightly it fits Svashasan OS, not in re-inventing a CPU core or a DDR controller.
Partners
Figure 19. Nobody builds an automotive SoC alone. Named organisations are potential partners listed in the PRD, not agreements; each relationship must be scoped as licensing, co-development, services or manufacturing.
Product generations
Figure 20. Three generations. S1 earns the right to build S2; chiplets in S3 let one design scale across vehicle classes. Generation targets are aspirations, each gated on the one before.
The ecosystem flywheel
Figure 21. The wider ecosystem. The loop starts with the OS shipping on other people's chips; real deployment data is what makes custom silicon worth building and what makes it fit.
10. Key Engineering Decisions
Decision
What it means
Build around Svashasan OS
The OS stays the primary product; silicon accelerates it through the HAL
Prioritise three subsystems
NPU performance, memory bandwidth and functional safety decide usefulness
License proven IP
Own the architecture and integration; license CPUs, memory, security and interface IP
Avoid premature fabrication
No tapeout before profiling, OEM validation, IP, cost, simulation, software and funding checks pass
Svashasan S1 is the chip Svashasan OS would design for itself: sized by measured workloads, fenced by an independent safety island, and optional by design, so the software never waits for the silicon.