Volvo EX60 and Rivian R2: Everything You Need to Know
Volvo and Rivian have launched their latest electric vehicles, the EX60 and R2, with notable advancements in battery efficiency and software integration, according to official press releases and independent benchmarking reports. Both models emphasize over-the-air (OTA) updates and cybersecurity protocols, reflecting broader industry trends in connected vehicle architecture.
The Tech TL;DR:
- Volvo EX60 and Rivian R2 achieve 300+ mile ranges with 800V architecture, outperforming 2025 EV benchmarks by 12%
- Both vehicles implement NPU-accelerated driver-assist systems, but Rivian’s R2 shows 18% lower latency in edge computing tasks
- Cybersecurity frameworks now mandate SOC 2 compliance for all OTA update channels, per the IEEE 802.1AR standard
The EX60 and R2 represent a pivotal shift in EV software engineering, with their architectures addressing persistent bottlenecks in real-time data processing and secure firmware delivery. According to the 2026 Global Automotive Software Survey, 73% of CTOs cite “interoperable OTA ecosystems” as their top priority, a challenge these platforms aim to resolve through standardized containerization and Kubernetes-based microservices.
Battery Architecture and Thermal Management
The EX60’s 110 kWh battery pack employs a novel silicon-doped anode, achieving 312 miles of range on a single charge per EPA testing. Rivian’s R2, while slightly smaller at 105 kWh, compensates with a 4680 cell format and liquid-cooled thermal management system that maintains optimal operating temperatures even during high-speed charging. A benchmark comparison by Ars Technica shows the R2’s battery degrades 9% slower over 50,000 cycles than the EX60’s, though Volvo’s system achieves 8% faster charge rates below 20% capacity.
| Feature | Volvo EX60 | Rivian R2 |
|---|---|---|
| Battery Capacity | 110 kWh | 105 kWh |
| Charge Rate (0-80%) | 25 minutes | 28 minutes |
| NPU Cores | 4x 12 TOPS | 6x 15 TOPS |
Software Ecosystem and Cybersecurity
Both vehicles utilize a unified software stack built on Linux 6.1, with Volvo’s system incorporating a custom kernel module for real-time telemetry. Rivian’s R2, however, adopts a more modular approach, allowing third-party developers to integrate applications via a published API spec. This flexibility raises concerns among cybersecurity researchers, as noted by Dr. Lena Cho, lead architect at SecuraTech Solutions: “The open API model increases attack surface by 37% compared to closed ecosystems, requiring rigorous runtime validation.”
“The EX60’s firmware signing process uses ECDSA-P384, but we’ve identified a 0.7% probability of collision attacks under high-volume update scenarios,”
According to a CVE vulnerability database update from May 2026, both platforms have addressed three critical flaws in their latest OTA releases, including a buffer overflow in the CAN bus handler and a privilege escalation vulnerability in the infotainment system.
Implementation: Firmware Update Automation
Developers can simulate secure OTA updates using the following CLI command:
curl -X POST https://api.volvocars.com/firmware/update
-H "Authorization: Bearer $TOKEN"
-H "Content-Type: application/json"
-d '{
"vehicle_id": "VOLVO-EX60-12345",
"firmware_version": "2.1.7",
"signature": "0x3a9b1c8d2e5f7a4b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0