Deepgrid Semi
DG32 · LOCKSTEP RISC-V MOTOR-CONTROL SILICONFIRST SILICON · SEP 2026
Discuss your application

Where DG32 leads, and where it does not yet

Measured against the STM32G0, the incumbent entry-level motor-control MCU. DG32 wins on safety hardware and control acceleration; the G0 wins on analog, memory and maturity.

DG32-LITE compared with the STM32G0 series
DimensionDG32-LITESTM32G0 seriesWhat it means
CPU2 × RV32IM in hardware lockstep, 50 MHz1 × Arm Cortex-M0+, up to 64 MHzComparable single-thread class. DG32 spends its second core on error detection.
Safety hardwareLockstep comparator, fault latch and FAULT pin, windowed watchdog, supply monitoring, bus-error responsesIndependent and window watchdogs, brown-out reset, clock security system; software self-test librariesHardware lockstep is otherwise found in automotive MCUs such as Infineon AURIX, NXP S32K and TI Hercules.
Program memory64 KB mask ROM + external QSPI flash; application runs from SRAM16–512 KB embedded flashG0 executes in place. Embedded flash is on the DG32 roadmap.
RAM32 KB dual-port SRAM8–144 KB SRAMEnough for control loops; G0B1 has more for communication stacks.
Motor PWM3-phase with dead-time, centre-aligned ADC trigger, hardware brake; 4 × DShot in hardwareTIM1 advanced timer with dead-time and break; DShot in softwareEquivalent 3-phase capability. DShot is native on DG32.
Position sensingQuadrature encoder with index and 3 Hall inputs, decoded in hardware with edge timestampsTimer encoder mode and Hall sensor interfaceEquivalent.
Analog8-bit differential SAR, ~200 kSa/s, 2 pins12-bit, 2.5 MSa/s, up to 16 channelsG0 leads clearly. A 12-bit multi-channel ADC is the first roadmap item.
MathHardware CORDICNone (CORDIC appears on STM32G4)FOC transforms run in hardware on DG32.
On-chip AIDG32-2DOM: INT8 attention engineNone; NanoEdge AI runs in softwareCondition monitoring inside the drive itself.
Communications2 × UART, SPI, I²C, QSPI, 3 × GPIOUp to 6 × USART, 3 × SPI, 3 × I²C, USB FS, 2 × FDCANG0 has the broader catalogue. CAN-FD is on the DG32 roadmap.
Test & debugJTAG test access and scan chains; UART boot monitorSWD debug; boundary scan on larger packagesProduction test is covered. Interactive CPU debug over JTAG is a roadmap item.
Process & status130 nm; first silicon September 202690 nm; in volume production since 2018DG32-LITE proves the architecture; it is not yet a production part.

STM32G0 column: public datasheet values for the STM32G0x1 / G0B1 family (Arm Cortex-M0+). DG32-LITE column: first-silicon design values, verified in simulation and static timing, not yet measured on silicon.

WHERE DG32 LEADS

  • Hardware lockstep at the entry-level tier
  • Native DShot
  • CORDIC in hardware
  • On-chip AI variant for condition monitoring
  • Open RISC-V instruction set, no core licence

WHERE THE G0 LEADS TODAY

  • 12-bit, 2.5 MSa/s multi-channel ADC
  • Embedded flash
  • USB and CAN-FD
  • Package range
  • Production maturity and ecosystem

WHY THE DIFFERENCE

Every gap is a deliberate sequencing choice,
and each one closes in the order that first silicon makes possible.

Why the second core is the point

Against the G0, DG32-LITE is a comparable single-thread part that spends its second core on error detection.

WHYHardware lockstep is otherwise found in automotive microcontrollers such as Infineon AURIX, NXP S32K and TI Hercules. DG32 brings the mechanism to the entry-level motor-control tier.

Why the ADC is small on first silicon

An 8-bit, two-input converter against the G0’s 12-bit, 2.5 MSa/s, many-channel ADC.

WHYFirst silicon carries a small converter to prove the analog integration path. The G0 is clearly ahead here, which is why a 12-bit multi-channel ADC is the first roadmap item.

Why the application loads at boot

The G0 executes in place from embedded flash; DG32-LITE copies its application from external flash into SRAM.

WHYA flash-less die keeps the 130 nm process simple for a first spin. Embedded flash comes with the second spin.

Why the roadmap runs in this order

Analog and program memory first, then CAN-FD and interactive CPU debug.

WHYThe analog front end and program memory are where the incumbent leads most clearly, so they close first. Connectivity and debug follow, while DG32-2DOM proceeds in parallel.

THE MULTI-SPIN ROADMAP

Closing the gaps
in deliberate order.

Each step has a job: first silicon proves the architecture, the second spin closes the largest gaps, and connectivity follows.

  1. NOW

    DG32-LITE first silicon

    On the September 2026 multi-project shuttle.

    WHAT IT DELIVERSBring-up measures what simulation and static timing predicted: loop costs, fault latency, fmax and power.

  2. NEXT

    Second spin

    12-bit multi-channel ADC and embedded flash.

    WHAT IT DELIVERSCloses the two largest gaps against the incumbent.

  3. THEN

    Connectivity and debug

    CAN-FD and interactive CPU debug over JTAG.

    WHAT IT DELIVERSThe vehicle bus a traction or steering drive expects, and the debug path a production team needs.

  4. PARALLEL

    DG32-2DOM

    The two-clock-domain variant with the INT8 attention engine.

    WHAT IT DELIVERSDesign complete and in physical trials; bring-up will measure the engine’s cycles per query row.

WHAT THIS SITE DOES NOT CLAIM

  • No measured silicon results: first silicon is on the September 2026 multi-project shuttle and bring-up has not started.
  • No functional-safety certification. Hardware lockstep is a mechanism, not a certificate.
  • No sign-off result for the tape-in die: the four gates it must pass are listed, not reported as passed.
  • No price or cost claims against any competitor.
  • No silicon result for the other nine chips: none is on a shuttle, and they rest on architecture sheets and logic validated on an FPGA. The one DeepGrid chip returned so far is a 130 nm test chip made on its own flow (whitepaper v3, §3).
  • No market size or price for the wider portfolio: the annex market tiles are rough internal estimates and are not shown. The only revenue figures on this site are the plan targets on the company page, which are not results.

WHAT TO DO NOW

Evaluate DG32-LITE now if the drive needs lockstep;
wait for the second spin if it needs a 12-bit ADC or embedded flash.

Evaluate now

A drive where hardware lockstep, native DShot or hardware CORDIC decides the part, and an 8-bit converter and boot-from-QSPI are acceptable.

WHYThose are the rows DG32-LITE leads on, and the pinout, package and supplies are fixed enough to lay out a board today.

Plan for the second spin

A drive that needs a 12-bit multi-channel ADC, execute-in-place flash, USB or CAN-FD.

WHYThose are the G0 rows, and the roadmap closes the ADC and flash first, then CAN-FD and interactive debug.