The QM35825 integrates a UWB transceiver together with an embedded MCU. However, Qorvo currently does not provide full low-level access to that MCU for independent firmware development.
At present, development requires flashing Qorvo-supplied precompiled firmware binaries. The internal MCU is therefore not openly programmable in the way developers might expect from a typical SoC. This limits the ability to implement custom MAC/PHY behavior, timing optimizations, or fully proprietary stacks.
In addition, detailed technical information and development access are typically routed through sales channels rather than being openly documented. For many engineers and smaller teams, this makes evaluation and independent product development more difficult than it needs to be.
From a system architecture perspective, this often means:
- You remain dependent on Qorvo’s firmware stack.
- Deep customization is not possible. See: QM35825 Application development
- An additional external application processor may still be required for full system control.
Frankly, this is frustrating, because the closed firmware model prevents developers from fully leveraging what is otherwise a very capable SoC.
Broader firmware access and clearer public documentation would greatly improve its attractiveness for advanced developers.