[DWM3000] Nearby Interaction QSG demo issue

Hi Qorvo teams,

I am setting up the Nearby Interaction demo with DW3000 + nRF52840 currently. I have downloaded the .hex file( located in Qorvo_Apple_Nearby_Interaction_Beta_release_1.0.0-1\Binaries\nRF52840DK) to nRF dev board and configured JLink RTT Viewer V7.54b to check any log from the nRF dev board (application, target board, os, version,…). I did not get any information from terminal and have seen that LED1-LED4 were blinking sometimes (each 1 minute ). I have some questions to clarify about hardware/software setup:

  1. Do we need to launch the Nearby Interaction Demo app and start session to see if any log from RTT Viewer ?
  2. Qorvo have an application in App Store( Qorvo Nearby Interaction). Can we use this app for testing with our hardware setup or have to build the source code from Apple developer page by XCode?

I attached some images of hardware/software setup below, please review and feedback if we have any incorrect setup.

Regards,
Phuoc

Just want to add more images of our setup:

Hi Qorvo teams,
Addition information that we use the DWM3000 with device id = 0xDECA0302( without PDoA support). Do we need the DWM3000 with PDoA support to run this demo ?

Hi @Phuoc ,

  1. Do we need to launch the Nearby Interaction Demo app and start session to see if any log from RTT Viewer ?
    If you don’t start a session you’ll see only some information about the application in RTT viewer as below

  2. Qorvo have an application in App Store( Qorvo Nearby Interaction). Can we use this app for testing with our hardware setup or have to build the source code from Apple developer page by XCode?
    Yes you can download the application directly from App Store to test your hardware.

  3. Do we need the DWM3000 with PDoA support to run this demo ?
    No, a part without PdoA support should be fine for Nearby Interaction.

Hope it helps,
Wassim

Hi @wassim ,
Thank you for your information.
As I mentioned above, I did not see any log from RTT Viewer. Could you please review the hardware setup in the attached images to see if any problem ?

Regards,
Phuoc

Hi @wassim ,
I have one more information on this issue. I got the Qorvo NI source code for nRF52840 and built with SEGGER Embedded Studio for ARM v6.30. I downloaded the output file (.hex) and got the log which showed error on BT/BLE in SEGGER RTT Viewer and the LED1-LED4 didn’t blink. I have tried to build the .hex file with and without merge SoftDevice to the compiled target (by the mergehex version 10.17.3) and got the same error as mentioned.
How do you think about this issue ? We expect the output file (Qorvo_Apple_Nearby_Interaction_1.0.0/Binaries/nRF52840DK/NRF52840DK_full.hex) are same as the output which was built from Qorvo source code. I attached the RTT Viewer log below, please let me know if any issue on this.

Regards,
Phuoc

Hi @Phuoc ,

Sorry for the late response.
I’m not sure how did you succeed to build the app with SEGGER Embedded Studio for ARM v6.30.
Because with that v6.30, I’m expecting a known issue in segger starting SES 6.20a and a build error “__vfprintf.h: No such file or directory”.

Can you please confirm the version of Segger you have?

Hi @wassim ,

Firstly, I have an update with the output file (.hex) for nRF52840 from Qorvo. We have changed the new nRF52840 board and the demo has worked properly.

Secondly, we are still having issue with the .hex file which was built by the SEGGER Embedded Studio V6.30 as I mentioned in the previous thread. I got the build error “__vfprintf.h: No such file or directory” and workaround by exclude the SEGGER_RTT_Syscalls_SES.c from build.

Regards,
Phuoc

Hi @Phuoc ,

The problem is coming from SEGGER Embedded Studio V6.30.
Please use SEGGER Embedded Studio V5.60a and then you don’t have to exclude the SEGGER_RTT_Syscalls_SES.c from build.
It should work in that case.

Hope it helps,
Wassim

Hi @wassim,
Many thanks for your support! I have installed SEGGER Embedded Studio V5.60a and build project successfully without exclude SEGGER_RTT_Syscalls_SES.c file. The output hex has worked properly.
Regards,
Phuoc

1 Like