Hi, I just got a DWM3001CDKE1.0 development module for evaluating UWB RTLS. However, I don’t know exactly how to get started. I connected the board to the PC using USB and tried running the DecaRanging_5p02.exe software, I get an error “Cannot open a Cheetah/FTDI device or connect to EVK3000 over COM port…” Also, I see that the D20 LED is blinking indicating that the J-Link is not enumerated. Can you please provide any documents/help what tools are needed and/or how to get started? Thanks.
You can find here https://www.qorvo.com/products/p/DWM3000EVB#documents API software revision 1.4 and in this link
https://www.decawave.com/wp-content/uploads/2022/03/DW3xxx_XR6.0C_24Feb2022.zip you can find API software revision 2.2 with uwb driver in library format.
These 2 releases supports STM32F429 Nucleo and nrF52840 DK targets.
DWM3001CDK is based on nRF52833, so you need to port the code of the release to that target.
Qorvo provides a ready software for DWM3001CDK for Nearby Interaction where you can interact with iPhone and get distance and direction relative to a U1-equipped iPhone.
Hope it helps,
“…driver in library format…DWM3001CDK is based on nRF52833, so you need to port the code of the release to that target.”
It would be far easier to port code with actual source code.
What needs done to port this library?
You don’t need to port the library as it’s already generated for Cortex-M33.
Maye you can start from this Nordic Q&A
Really at this point I’ve decided to look at alternative vendors such as NXP and Spark, because Qurvo is not forthcoming with documentation and source files.
The DWM3001CDK is delivered with zero documentation and code, not sure how anyone thinks that is useful. There is at least Apple Demo.
I have just purchased DWM3001CDK, NRF52’s have nothing on them. There is also nothing in the SDK that is on the DK product page. I just want to evaluate it, I don’t want to port code, I have enough to do.
You have cutting edge technology but prehistoric customer support! Please can you provide us with precompiled firmware for DWM3001CDK to work with your software.
I just got two DWM3001CDKE kits and I am willing to give a try to your porting suggestion. I did as you said and changed every reference to the
dw3000_api.emProject to the corresponding
NRF52833 value. I tried to add screenshots of the differences but apparently new users cannot embed media in posts.
I managed to compile successfully like this, however when I try to run even the first example (
ex_00a_reading_dev_id) I get an error in
platform/port.c, line 92. I gather this probably has to do with the definition of the pins, which do not match between the
DWM3001CDKE and the original project.
I am hoping @wassim or someone else here can offer some guidance on how to proceed further.
Thanks in advance!
Please use these definition instead for DWM30001CDK:
#define ARDUINO_13_PIN NRF_GPIO_PIN_MAP(0, 3) // used as DW3000_CLK_Pin
#define ARDUINO_12_PIN NRF_GPIO_PIN_MAP(0, 29) // used as DW3000_MISO_Pin
#define ARDUINO_11_PIN NRF_GPIO_PIN_MAP(0, 8) // used as DW3000_MOSI_Pin
#define ARDUINO_10_PIN NRF_GPIO_PIN_MAP(1, 6) // used as DW3000_CS_Pin
#define ARDUINO_9_PIN NRF_GPIO_PIN_MAP(1, 19) // used as DW3000_WKUP_Pin
#define ARDUINO_8_PIN NRF_GPIO_PIN_MAP(1, 2) // used as DW3000_IRQ_Pin
#define ARDUINO_7_PIN NRF_GPIO_PIN_MAP(0, 25) // used as DW3000_RST_Pin
Also keep in mind, you need to update FLASH and RAM ranges according to nRF52833 target.
Hope it helps,
Thanks @wassim. That does help!
well, I have just received my CDK boards. and I ‘hope’ I have started right…
to flash the board, connect the computer USB cable to the J9 connector (flash/debug) (I guess, nothing says that )
red light on solid
flash the nrf52833, CLI .hex binary (the jlink doc says 52840… )
connect serial terminal, no response
switch to USB J20 (I guess, none of the instructions says to move the cable)
red light flash (good)
D9 on solid, green
no response on serial terminal.
no flash of the LEDs when typing either …
all this on a mac mini.
ok, the no response was the terminal app needed to set DTR.
I want the CDK to be a responder… so I start the RESPF app,
but my IOS app can’t find it… using BLE for the service UUID
and I don’t see it in my android scanner either
according to the R2 NI accessory spec, the service UUID is 48fe3e40-0817-4bb2-8633-3073689c2dba
the sample code from Apple uses the 6E400001/6E400002/6E400003 uuids
download from here, have to logon
upgraded to the V3 sdk… now it works as expected… no serial port interaction required