Designing a next generation ARM Developer Platform
summary
A proposal for an ARM developer desktop called ADUC aims to sit between Raspberry Pi and servers by using a 96Boards compute module on a Mini‑ITX carrier with PCIe breakout, optional SATA via a switch, and an RGB header. Target is native builds and UEFI/EBBR compatibility to avoid Windows‑only bootlock; current obstacles are closed SoC documentation and boot firmware. Packet funds initial engineering and engagement with Qualcomm and SolidRun for LX2160A and Snapdragon parts.
AI-written summary · about
chapters (10)
- 0:00Start
- 0:20Let's Rewind a Few Months...
- 1:58Fast Forward to January...
- 3:47We Have Identified a Problem
- 6:01Gathering Blue-Sky Specifications
- 6:29Coming back down closer to reality
- 7:36The problem is software
- 8:05What would this look like?
- 9:24Potential Current Gen. SoCs Options
- 11:51Reach out to us!
related talks
47mIntroducing the Next Generation of Windows on Arm
43mAccelerated Porting of Linux, U-Boot and Yocto for Production Ready Emb...
14mAOSP Devboards
10mRISC-V Virtual Platforms for Early RISC-V Embedded Software Development
43mSponsored Session: Why Don't You Love Me Back, Open-source Software?
11mDemo: Catapult Studio for Imagination RISC-V CPUs
10mIntroducing the Highest Performance RISC-V Development B...
27mInsights on the Re-Architecting to a Single Codebase, Running on Different Hardware...