Hi,
I have a concrete example, where I have no clue, as to why a given configuration is not working. In general, I wonder, how one is supposed to debug / investigate such, quite time consuming issues.
I want to add RTT logging to a MCUBoot bootloader. Here is the configuration, that according to the available documentation (https://docs.nordicsemi.com/bundle/ncs-2.7.99-cs2/page/nrf/test_and_optimize/logging.html) should work:
This results in this warning:
I think, I understand that warning and applying it to my configuration yields this:
But still, this results in a warning, that `LOG_BACKEND_RTT` got the value `n`, even though, `LOG_MODE_MINIMAL` is set to y.
Beside the question, whether this should work or not, how should we debug such issues to find working configurations? Obvious starting point, is probably the mentioned definition of `LOG_BACKEND_RTT`:
I don't even see a dependency on `LOG_MODE_MINIMAL` in that code. Is it possible to somehow capture the call to the configuration parser and add some switches for more verbosity here? Are there other strategies to debug such issues?
(Version, nrf-connect v2.7.99-cs2, Target: nRF5340)