It can be seen that DW3 QM33 SDK v1.1.1 supported targets don’t include nRF52840-DK, so when will nRF52840-DK be supported?
Thanks.
Hi @paopaohepan ,
QM33120WDK1 has nRF52840, so you can use the FW in QM33120WDK1 folder.
Kind regards,
Emre
Thanks. Here is my test.
In the directory in SDK as figure1, I use segger jflash to download 52840 qani hex file to my board.
My board is nRF52840-DK as figure2.
Then I use QorvoNI APP on iphone14 pro max to test QANI. After connect to nRF52840DK in the APP, the problem is as figure 3.
The right side of nRF52840(325B514A) keeps spinning in circles, the prompt above the arrow remains “Sent shareable configuration data”, the distance and azimuth remain 0.
I have test another hex file figure 4 on dwm3001CDK board. I download this DWM3001CDK QANI hex file to my DWM3001CDK board, and then use the same iphone and everything is normal, ble can connect, distance can measure.
So it seems that nRF52840-QANI-FreeRTOS.hex file cannot work on nRF52840DK, so could you please test this firmware and how to solve this problem. I need use QANI on nRF52840.
Thank you very much.
Did you move the USB cable to the other port (J3) on the nRF52840DK?
The nRF52840 DK is equipped with two micro-USB ports:
• J2: used for flashing/debugging via J-Link OB.
• J3: used for UART/USB communications with MCU.
Yes, I have moved the USB cable to J3, and switch the power source from “VDD” to “USB”, and the phenomenon is exactly the same as before.
I think the QANI 1.1.1 phone app doesn’t support using the camera AR which is required on iPhone 14 and up. you won’t get direction unless you enable and USE AR sessions.
iPhone 11-13 work ok, 14 and up need Augmented Reality (AR) to work.
Thanks. I change the shield of my nRF52840-DK from DWM3000 (the white board in the picture above) to QM33110WEVB (the red board), as shown in the picture below, and then it works. BLE can be connected, distances can be measured. And then I test QM33120WEVB and also works.
So it seems that SDK v1.1.1’s support for nRF52840-DK is limited to the QM series (QM33110 and QM33120) and does not include the DW series (DW3110 and DW3120).
The following code snippet seems to validate my guess.
In the src/Boards/src of the SDK, it can be seen from platform_11_config. c in the DWM3001CDK directory that PLATFORM_ID_DW3000 and PLATFORM_ID_DW3000C are defined, without including QM series tranceiver. This is reasonable because the transceiver of DWM3001CDK is dw3110.
However, only two QM series transceivers are defined in platform_11_config. c in the nRF52840-DK directory, and no DW series transceivers are defined. So this should explain why it starts working after I change the shield of the nRF52840-DK from DWM3000 (the white board) to QM3110WEB (the red board).
Please confirm whether my guess is correct. If so, does Qorvo have any plans to add support for the DW series transceivers for nRF52840-DK in the future versions of the sdk?
In addition, I would also like to further understand the differences between the DW series and the QM series transceivers, that is, what are the specific differences between DW3110 and QM33110, as well as between DW3120 and QM31120?
Thank you very much.
Regarding this issue, I have made some new discoveries and I will continue to discuss them in another post.