@carlos.silva@wassim I’m hoping you can help provide some clarity and guidance on getting started with the DWM3001C. After spending a couple of days researching and experimenting, I have a couple of questions.
Can the DWM3001C be used as a standalone device (with just a battery), or does it need a host controller? It incorporates the nRF52833, which has a Cortex-M4, so I would think that it can run on its own once it’s programmed? For example, if I took a DWM3001CDK, programmed it, then desoldered the DWM3001C module from the dev board and provided it with power, would it run the programmed code the same as if it was still soldered to the dev board?
Transmit all of this data (range to each anchor, GPIO value) to a computer via BLE
Repeat on an interval
Once the SDK/firmware is built and downloaded to the module (per section 9 of the User Guide), where/how do we actually develop an application to utilize that SDK/firmware? Are there any examples available for this?
DWM3001C is actually a module produced by Qorvo that you can acquire. DK is just Dev Kit for that module, which includes the power connection, LEDs, buttons, and a built-in J-Link. https://www.qorvo.com/products/p/DWM3001C
All software listed for DWM3001CDK will work as is with the module, also examples for Nordic nRF528XX (maybe a pin reallocation will be needed in this case).
You can start with the Developer Guide and understand how the UWB tasks are set, how UWB is configured, and where the results are reported. The example software implements a command line interface, you can configure and start UWB using that or even create a Python script to test what you want. When you’re happy with the sequence, then you can check how the application handles each command and bring it to your own app. About GPIO and BLE, you can check Nordic examples folder inside their SDK folder, keep in mind that you’re developing for an nRF52833 after all.
You can always come here with more specific questions, like “How to start the app as an initiator?”
Hope it helps and good luck!
Thanks for the very quick and thorough response. I managed to sort through the SDK and understand now how the pins would be reallocated if I mounted the DWM3001C on a custom board, instead of using it on the DWM3001CDK.
To confirm, the J-link debugger isn’t actually needed for the DWM3001C to run, correct? It’s only used for programming and debugging?
Based on your response, a couple more questions then, if I may:
Could you describe the difference between the CLI and UCI example projects in the DWM3001C SDK? It looks like they use exactly the same code, but the Project/Solution files themselves are different.
I may have a fundamental misunderstanding about how this is intended to function. It seems that the two SDK projects (CLI and UCI) are intended to run continuously and accept commands over serial (CLI) or UART/USB (UCI). This implies that there’s some external host that is sending those commands. But, what if I don’t have an external host, and I want the DWM3001C to be entirely self-contained with a pre-programmed loop of operations/commands to run (those described in question 4 above)? This might be what you mean by “bring it to your own app”, but it’s unclear how to create a new continuous task that runs these commands.
You mention using the Nordic examples, which makes sense, but how does one integrate the Nordic example code (BLE, GPIO) into the example DWM3001CDK projects (e.g. DWM3001CDK-DW3_QM33_SDK_UCI-FreeRTOS.emProject)? The main.c file for the Qorvo projects appears to start several tasks and a scheduler (which never returns); how would I start an ongoing task that, on an interval, uses the UWB module and transmits certain data from that over BLE?
This may not be related, but do you know how to have .h files appear in the SES file explorer? I’m not sure if it’s an SES thing or a configuration settin in the Qorvo SDK projects, but it’s only showing the .c files.
I am working on a standalone solution (just battery, no USB/UART) for ToF ranging. I am using the “DWM3001CDK DK Software, Sources, Tools and Developer Guide” with DWM30001CDK, but there are similar issues so I decided to reply to this thread.
As far as I understand it the provided firmware DWM3001CDK-DW3_QM33_SDK_CLI-FreeRTOS_0_1_1.hex is built for the NRF52833, and Segger J-Flash Lite flashes it directly to the DWM30001C. However, the FW still relies on inputs from the UART to configure and start the applications (initf, respf). I am looking into the DWM3001CDK-DW3_QM33_SDK_CLI-FreeRTOS.emProject, and try to make it running in a standalone fashion, but I don’t yet understand how all the bits and pieces work together.
The CLI is the Command Line Interface that I mentioned in 4, UCI (UWB Command Interface) is a standard for software applications to communicate with UWB devices, the scripts folder has an example using UCI over uart.
I suggest you try the CLI first, connect a flashed DWM3001CDK to a PC using the User USB (J20), the PC will find a new COM Port, then you can use your preferred serial terminal to connect to it, then try the command “help”.
You got it right, but it doesn’t require to have an external host. After starting a board with a specific configuration you can use the CLI command “save” to write to flash your UWB configuration and function.
This is something you can try right now, open two terminals for two boards, set one as responder and the other as initiator they should start TWR, then save the initiator, keep the responder connected for monitoring and unplug the initiator, plug the initiator into a power supply or powerbank. It may take a few seconds but TWR between them will start again.
To set your application you need to change the default_config values or decide on how to set it (e.g.: via BLE), and then rewrite main() to start a specific role instead of loading the saved state from flash or waiting for a command, but then I recommend you to get familiar to the application first.
@christian.i, look for the “app_definition_t” type in /Src/Apps/Src/common/app/common/app.c, there you can set a variable (let’s say, “fira_initiator_app”) and configure it as the DEFAULT_APP. Also, take a look at how the “default_app” is loaded.
You can start following how it is implemented for other components, like USB CDC in the CLI example. The Nearby Interaction project uses the same structure and implements BLE: https://www.qorvo.com/products/d/da008212
I don’t know, I almost always use “right click->Go To Declaration” and few times I expand a .c file and look at its dependencies.