QM35825 modules (with / without host MCU), Apple Nearby Interaction and DL-TDoA support?

[hsinyu]

We have a working product prototype on DWM3001C (nRF52833 + DW3110) using Apple Nearby Interaction, and we are evaluating QM35825 for the next hardware generation. A few questions:

1. Modules. For the QM33 generation there were two module types - DWM3000 (UWB only) and DWM3001C (nRF + UWB, pre-certified). Is there, or will there be, anything similar for QM35825?

• a UWB-only QM35825 module (antenna + RF, to be used with our own host MCU)
• a combined module with a Nordic host (for example nRF54L + QM35825)

If yes: certification status (FCC / CE) and rough availability? If no: is a custom RF design the only path today? For a small team the module is what makes the difference (RF layout, antenna, per-unit antenna delay calibration, certification).

2. Apple Nearby Interaction. Does the QM35 SDK support the NI accessory protocol (like QANI + libniq on QM33), including iOS background sessions? Is there an example?

3. DL-TDoA for iOS. Apple supports DL-TDoA from iOS 26. Is QM35825 the recommended anchor platform for it? Is there an anchor example in the QM35 SDK, and has it been verified with iPhones?

4. Multiple phones. How many concurrent FiRa sessions (one per phone) does the QM35825 stack support?

5. Interoperability. Can a QM35825 device range with DW3000 / DWM3001C devices using FiRa, so both generations can be mixed in one system?

6. BLE coexistence. I read in another thread that the UWB stack runs on the QM35825 internal core and the host controls it through UCI. Does that mean BLE activity on the host (advertising, connection events) cannot disturb UWB round scheduling? We have that problem on nRF52833 + DW3110 (see topic 25999), so this point matters a lot for us.

Thanks!

[akash]

@hsinyu

1. Modules. For the QM33 generation there were two module types - DWM3000 (UWB only) and DWM3001C (nRF + UWB, pre-certified). Is there, or will there be, anything similar for QM35825?

• a UWB-only QM35825 module (antenna + RF, to be used with our own host MCU)
• a combined module with a Nordic host (for example nRF54L + QM35825)

If yes: certification status (FCC / CE) and rough availability? If no: is a custom RF design the only path today? For a small team the module is what makes the difference (RF layout, antenna, per-unit antenna delay calibration, certification

There is not a module offering for the QM35825.

@hsinyu

2. Apple Nearby Interaction. Does the QM35 SDK support the NI accessory protocol (like QANI + libniq on QM33), including iOS background sessions? Is there an example?

There is not an example, but the NI would be implemented on the host processor and then control the QM35825 over UCI.

@hsinyu

3. DL-TDoA for iOS. Apple supports DL-TDoA from iOS 26. Is QM35825 the recommended anchor platform for it? Is there an anchor example in the QM35 SDK, and has it been verified with iPhones?

Yes, the QM35825 is the recommendation for developing a FiRa DT-Anchor or DT-Tag. An example of it can be found in the SDK: Samples/Python/UWB-Qorvo-Tools/scripts/fira/run_fira_dt · main · QORVO_SDK / Public / DevKits / qm35-sdk · GitLab. It has been verified with iPhones though Qorvo is not providing an app for this.

@hsinyu

4. Multiple phones. How many concurrent FiRa sessions (one per phone) does the QM35825 stack support?

We don’t necessarily have a limit. The limit would mostly be a limitation of the available radio time.

@hsinyu

5. Interoperability. Can a QM35825 device range with DW3000 / DWM3001C devices using FiRa, so both generations can be mixed in one system?

Yes.

@hsinyu

6. BLE coexistence. I read in another thread that the UWB stack runs on the QM35825 internal core and the host controls it through UCI. Does that mean BLE activity on the host (advertising, connection events) cannot disturb UWB round scheduling? We have that problem on nRF52833 + DW3110 (see topic 25999), so this point matters a lot for us.

Yes, this is correct.