nRF Profiler scripts can't seem to handle different RTT backend channel from default.

[mattheis]

Development Setup:

- nRF Connect SDK v2.6.0
- Custom nRF9160 board
- OS: Debian Bookworm (running scripts in python virtual enviroment)

Currently application uses Shell and Logging both with RTT backend.  SHELL_BACKEND_RTT_BUFFER=0 and LOG_BACKEND_RTT_BUFFER=1
Shell logging backend is enabled or disabled based on debugging needs. Normal logging is used for long term capture of logs during test runs.

Scripts under the nRF Profiling will give following log when error occurs:

[INFO] Profiler Rtt to stream: Recognized device family: NRF91
[ERROR] Profiler Rtt to stream: Cannot find properly configured RTT channels
[INFO] Profiler model creator: Module closed before receiving event descriptions.
[INFO] Plot Nordic: Module closed before receiving event descriptions.

This error occurs if Shell logging backend is enabled or disabled.

When Shell is disabled and Logging and LOG_BACKEND_RTT_BUFFER=0 scripts run fine.

Any chance this is a bug? Or is this just not an implemented feature? Otherwise I can take this up at GitHub issues and have a go at the problem myself.

[Simonr]

Hi Matthijs

Okay, I understand. I have reached out to the devs behind the nRF Profiler now, and will get back to you when I hear from them. I agree that this sounds like either a bug or a feature that hasn't been added to the Profiler yet.

Best regards,

Simon