Duplicate RTT output from Thingy:91 X

[Scott Grubb]

I'm developing code to run on the nRF5340 SoC in a Thingy:91 X and I am seeing duplicate RTT output.  For example, if I look at the RTT output from the default 'Connectivity Bridge' application, I see the following in VSCode and the same in RTT Viewer.  What is causing this, and how do I prevent it?

Thanks.

PS.  It's also a bit concerning to see that the only sample app that is listed as compatible with the nRF5340 SoC in a Thingy:91 X generates run-time errors out of the box.  I believe the error indicates that the USB subsystem is being enabled twice.  Should this just be a warning?

[Øyvind]

Hello, 

That is a very odd outcome. Are you able to share what exactly your code does i.e. what steps do I need to replicate the issue? 

It's also a bit concerning to see that the only sample app that is listed as compatible with the nRF5340 SoC in a Thingy:91 X generates run-time errors out of the box

What sample are you referring to? Do you mean the Connectivity Bridge? The Connectivity Bridge acts as a USB composite device allowing users to connect to the nRF9151 using USB only, instead of RTT, exposing two UART interfaces to a USB host as two CDC ACM devices

I believe the error indicates that the USB subsystem is being enabled twice.  Should this just be a warning?

#define NRF_EALREADY 120        /**< Connection already in progress */

From the looks of the provided logs it seems that you have logging activated twice in some way. 

Kind regards,
Øyvind

[Scott Grubb]

Hi Øyvind,

The code is indeed the Connectivity Bridge application.  It is unmodified.  I created a new application in nRF Connect for VSCode extension based on the sample in ncs 3.0.0 and built it for the thingy91x/nrf5340/cpuapp target.  I have not modified the sample in any way.

As I understand it, the Connectivity Bridge allows you to log from the nRF9151 SiP using USB but you still need to use RTT to log from the nRF5340 SoC.

The error originates from this block of code, which enables the USB subsystem when the filesystem and the bulk module are ready.  However, it seems that this block of code is being triggered twice.

I'm not too concerned about the error.  My main problem is with the duplicate RTT output.

[Scott Grubb]

I think I've found the source of the duplicate RTT messages.  Disabling the console in the prj.conf file (CONFIG_CONSOLE=n) stops them.