Fortior's FU75xx is not a faster DSP for motor control. It is a RISC-V core next to a purpose-built Motor Engine (ME2) that offloads field-oriented control, leaving the RISC-V free for parameter management, state machines, and communication stacks. FOC cycle time is 5 microseconds. Target applications are robotic joints, servo drives, BLDC fans, and EV auxiliary motors, the class of designs where real-time torque control and software configurability used to be in conflict.
The shift matters because traditional motor controller ICs are fixed-function: you tune the hardware parameters, flash firmware, and live with the algorithm baked into silicon. When the control strategy changes (different motor constants, new tuning, updated FOC algorithm), you typically need a board respin or a new chip. RISC-V on the FU75xx makes the general-purpose logic version-controlled and flashable; the ME2 handles the microsecond-scale timing that a general-purpose core cannot hit in software alone. The result is motor control firmware that behaves more like embedded software than a hardware design artifact.
Robotics is the immediate target, and that is the right place to start. Robotic joint controllers need to tune gains, change motion profiles, and adapt to mechanical wear in the field. A fixed-function DSP makes that process expensive and opaque. A RISC-V core with hardware-assisted FOC makes it a software update. Fortior is not alone in this direction; Renesas, STMicro, and Texas Instruments are all experimenting with programmable-core motor controllers. But the FU75xx's explicit ME2 hardware block is a cleaner split between the real-time constraint and the software layer than competing approaches that try to do FOC purely in firmware on a fast general-purpose core.