QM33 SDK CLI skipping ranging sessions when connected to USB power only

Wireless Connectivity Ultra-Wideband
1

I’ve been testing the QM33120 dev. kit with the CLI firmware with SDK version 1.0.0

I’m using the save feature to get my settings pre-configured and using setapp to pick the starter application after power up.

When I have the boards connected to a computer USB where power+data is available, the responder sends a range response all the time.

When I have a USB power only device, I’m using a standard USB charger. The range only works every 5 packets, (1 Success + 4 Timeouts).

see screenshots below:

image
image2079×1141 227 KB

2

@cewlsosyk I was able to replicate the issue and looks like you have found a bug. I will investigate how we can remedy this issue.

1 Like
3

@cewlsosyk , this issue is related to DWM30001CDK standalone operation without connection to USB UART - #16 by carlos.silva

The workaround here is to rebuild the application after removing the #if !defined(USB_ENABLE) as part of /DW3_QM33_SDK_1.0.1/SDK/Firmware/DW3_QM33_SDK_1.0.1/release/Src/Boards/Src/nRF52840DK/FreeRTOS/nRF52840DK.c

This workaround should allow for battery/power supply operation but will result in USB enumeration to take 14s at bootup.

I built the binary for you attached (please change the file extension from txt to hex as hex is not allowed to be uploaded here).
nRF52840DK-DW3_QM33_SDK_CLI-FreeRTOS.txt (1.3 MB)

4

Hi @akash , we tested this binary you provided but we are still seeing the same issue of skipping ranging sessions when powered by a USB power brick (do data lines connected).

image
image757×891 16.8 KB

5

Hi @akash. I was able to get it to work by not defining the USB_ENABLE in the project_common.cmake file and then configuring the system over the UART port.

6

Thanks for the update. Are you using the battery powered device as the initiator or responder or do you see the same behavior in both cases?

7

As of now I have the Responder as the battery powered one, my initiator is talking to 4 responders.

8

Hello @cewlsosyk, I have tried the same trick with the DWM30001CDK to no avail. Let me know if this solution works for the QM33120 dev. kit only or whether you have tried it on the DWM3001CDK board as well.

Thanks in advance.

9

Hi @gini , I only tested with the QM33120 dev. kit that runs on the Nordic nRF52840DK. This issue is related to the nRF micro, I would assume that just changing the shield from the QM33 to DWM3000 should work fine (as long as you keep using the nRF board). But I never tested with the DWM3000.