Modem trace on Thingy:91X

RE: Modem trace on Thingy:91X

Elfving — Mon, 26 Jan 2026 09:06:49 GMT

Hi Emanuel. Understood. Good thing that you've made a seperate ticket for this though. I agree that some documentation could be better but I hope DevZone is able to fill that gap :)

RE: Modem trace on Thingy:91X

EAB — Mon, 26 Jan 2026 01:14:29 GMT

I have a similar problem, and really wish Nordic could do a better job documenting the diag ports on their products.
Including how to set the trace bitmaps to customize what's coming out.

What is the trace protocol used on the trace DIAG interface for LTE-M?

RE: Modem trace on Thingy:91X

Elfving — Mon, 19 Jan 2026 13:36:35 GMT

Hi Matteo,

You've already gotten some great comments here from Achim Kraus . I also just tried this myself with NCS 3.0, and that seems to have gone fine. I used the build target thingy91x/nrf9151/ns, what are you using? That, as well as the NCS version would be great.

Regards,

Elfving

RE: Modem trace on Thingy:91X

Achim Kraus — Sat, 17 Jan 2026 15:42:07 GMT

A build error using the target board "thingy91x/nrf9151/ns" should not be related to the nRF53 of the Thingy:91X.

From the log I guess you use NCS 3.2.0. It may help, if you provide the "command line" (e.g. "west build -b thingy91x/nrf9151/ns ... ") used to build.

My suspicion is, that your a victim of the complexity of an "multi image sysbuild" and "snippets", see sysbuild and snippets . (Using the snippet for rtt and uart isn't that different, in both cases you will need to apply the snippet only to the application image.)

Once it builds, you may need to replace the "communication bridge" on the nRF53 (see Thingy:91X - nrf53_connectivity_bridge_v2.0.1 - wrong characters), but I would just try without and see, if that works already.

Let me also add, that using DKs comes in my experience with less struggle.