Finding module dependencies

[rconaway]

I'm digging into OpenThread, using the NRF52840 DK.  I find myself spending most of my time trying to figure out module dependencies.  Is there any way to quickly get all the configuration options in sdk_config.h, all the source files in Makefile, and anything else I need to use a module in my project.

For example, I started with examples/thread/cli.  I want to change the logging to use the debugging port (UART) instead of RTT.  I see that examples/ble_central/ble_app_blinky_c logs to the debug port, so I want to copy whatever it does into my app.  It looks like I need to turn on some UART flags and turn off RTT flags.  However, there are various flags that might apply.  If I take an educated guess, NRFX_UARTE_ENABLED seems to be needed.  So I copy that section from the blinky app. 

This introduces many errors that require a sisyphean effort to track down.  Fixes lead to more errors until I give up.  I've written utilities to compare projects and to expand #includes.  Grep and find are my friends.  It still feels like slogging through concrete.

Although I'm open to any suggestions about this specific problem, I'm really more interested in learning to decipher module dependencies.  My approach does not seem like a practical way to use an SDK.

I see there is another post about "Module dependencies" from jev.  The response was to request more documentation from the SDK team - certainly a good idea.  But the fact is that other people are using the SDK successfully, now.  Are they just requesting specific answers here every time they need to use a module?

What am I missing?

[haakonsh]

You're missing Segger Embedded Studios and the CMSIS configuration wizard. SES takes care of your makefiles, the configuration wizard presents the sdk_config file in a GUI with tick boxes and drop-downs. 

Nordic Semiconductor pays Segger a license fee in order to offer SES to our customers for free, as long as you're using our products ofc.  

See http://www.nordicsemi.com/eng/Products/SEGGER-Embedded-Studio-IDE and the SES video tutorial.

[rconaway]

Thanks for the reply.  I've used SES and the configuration wizard.  Recently, though, I've been just using make, since it's easier to research and compare projects.

I double checked the wizard.  It seems to just display the contents of sdk_config.h in a GUI.  Which might be useful if you know what configurations are needed.  It doesn't do anything to add source files to the project.

My problem is knowing what needs to be added to a project to use a module.  

BTW, I'm familiar with the reference sdk_config.h in config/nrf52840/config.  Again, the problem is knowing what needs to be turned on.

[haakonsh]

I guess you'll have to go into the modules and see which header files are included. If an included header file contains a function prototype you'll know that there's a corresponding source file, usually with the same name, that have to be included in the build. 

[rconaway]

That's a good suggestion.  I can write a tool to extract headers from a module, compare it to the ones I've already got in my include path and .c files and adjust accordingly.  

Any suggestions about how to fix sdk_config.h?  Configuration settings are more than just "turn this module on".  It looks like there are interdependencies and possibly even conflicts.  I.e. when I turn on UART logging, I may have to turn off RTT logging.

[haakonsh]

Yeah, that's a bit more tricky, I think there's possibly a runtime error if multiple backends is not supported in the logger module, but what we want is to catch it with the preprocessor. 

Interdependencies, are way harder to catch. I usually use snippets from the sdk_config's from whatever example uses the relevant module. It's manual cut n paste :/