Thingy:91X - nrf53_connectivity_bridge_v2.0.1 - wrong characters

[Achim Kraus]

Thingy:91X V1.0.0 (multiple devices)

NCS 2.6.2, nrf53_connectivity_bridge_v2.0.1

Using the logging of the nRF9151 via the nrf53_connectivity_bridge_v2.0.1 shows on longer outputs "broken characters".

"b 23::Ʌѕb&::Ʌѕ͕ͭɕb 23.055 :   get         : get settings.(?)"

With both, using USB as well as using BLE.

Using the same app (only difference configuration for the board) on a

nRF9151-DK

Conexio Stratus Pro nRF9151

or on a

Thingy:91 (nRF9160/nRF52840)

doesn't show that defect.

Also, if I slow down the UART logging with some additional short "k_sleep" instructions, then it works on the Thingy:91X as well.

This slow down is not needed for the other boards.

For me this looks pretty much like an issue with the "double buffering" in the nrf53_connectivity_bridge_v2.0.1.

[Øyvind]

Hello, 

NCS 2.6.2, nrf53_connectivity_bridge_v2.0.1

Could you please test with the version from e.g. NCS v2.9.0? As this was when official support for the Thingy:91 X was added? Do you see the same issues there?

Kind regards,
Øyvind

[Øyvind]

Hello again, this seems to be a know issue I have been informed by the developers. I will push for more answers internally.

Kind regards,
Øyvind

[Achim Kraus]

> this seems to be a know issue

Great!

Though I considered it to be an issue of the "nrf53_connectivity_bridge_v2.0.1.", I don't think, an update of the nRF9151 app to NCS 2.9.0 will not change the issue. But I know, I need to update ;-) ...

[Øyvind]

No, it is not certain it will change anything, but as there are several improvements done in regards to the launch of Thingy:91X - it's worth a shot

[Achim Kraus]

I assume, it will take quite a lot of time to migrate successful from 2.6.2 to 2.9.0 therefore my plan is to finish other stuff first (mainly in Eclipse/Californium), before I start that migration.