How to Hardcode Application Startup (INITF, LISTENER, RESPF) in DWM3001CDK Firmware?

Wireless Connectivity Ultra-Wideband
1

Hello,

Pardon in advance if I’m missing something obvious as im very much new to C and embedded programming.

I have a DWK3001CDK and the provided firmware. How can I hardcode in the firmware, each given application (LISTENER, INITF, RESPF) to boot from start? Such that when I plug in power to the DWM3001CDK development board, and it boots up, the application is immediately started.

Just like how you would if you connected to the device with a serial terminal, and ran ‘SETAPP INITF’ and then ‘SAVE’ afterwards, and then unplugged it and replugged it back in and it starts automatically.

I want to accomplish the same concept but by hardcoding it into the firmware, ideally in the main_cli.c file, or as close to it as possible (as that seems to be the entry point to the firmware). How would I do this for each application?

For context, Ive been able to build, flash, and run the debugger in VSCode but so far as I know, I have no way to issue commands while running the debugger and watch them live in the debugger, so the debugger is kinda useless since I can’t actually see how a command works in real time. That is my goal. I want to hardcode each application to boot from start, so I can use the debugger to step through the entire function call chain, as deep down as it can go, so I can understand how the actual DW3010 transceiver works.

@carlos.silva any chance you could help with this? I’ve been stuck on this for 2 weeks now, any insight would be greatly appreciated!

2

@carlos.silva Hey Carlos I saw your comment on the other thread, I appreciate the reply. I created this thread with a more specific question. Would you have any insight on this question? I am using SDK version 1.0.2

3

Hi @harrysonhall !

Just like how you would if you connected to the device with a serial terminal, and ran ‘SETAPP INITF’ and then ‘SAVE’ afterwards, and then unplugged it and replugged it back in and it starts automatically.

Right, I was going to suggest that, but I see what you need.

The CLI implementation is open in the code, so you can search for the “initf” command and reproduce what is done there. The implementation has changed a lot since the release of the other topic, this is why what was described doesn’t apply.
I’ll try to give this a try still this week.

Please share your progress!
Kind regards!