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

[Øyvind]

Understood! I will update you if there are any changes from the internal ticket. Let me know when you have been able to test!

Are you able to provide logs from the connectivity bridge? 

[Achim Kraus]

Øyvind said:

Are you able to provide logs from the connectivity bridge? 

Until now, I didn't need to get logs from the connectivity bridge. Not sure, if that works well, though the issue occurs, when writing via that connectivity bridge. Let's see, if the next update of the connectivity bridge solves that issue.  

[Achim Kraus]

Øyvind said:

I will update you if there are any changes from the internal ticket.

Any updates?

I migrated to NCS 2.9.0, but that doesn't fix it. Though I focus recently on developing apps for the Thingy:91X (and recommend that as PoC platform), it's irritating that the UART log doesn't work reliable as the one for the Thingy:91.

If there is something to test (even without "release"), let me know.

[Øyvind]

Unfortunately, no updates yet. 

[Achim Kraus]

Thanks for the information.

I tested the connectivity bridge of NCS 2.9.1, but it doesn't fix it ;-).

[Øyvind]

What application are you running on the nRF9151 itself of Thingy:91 X? Do you get the same issue with e.g. Asset Tracker v2?

What terminal are you using? I.e. any difference if you use other? Just to go through the list of potential questions that will arise. Even though this is a known issue, I can't find other customer reporting this. 

[Achim Kraus]

I run my own CoAP/DTLS 1.2 CID client .

That runs with other nRF9151 based board (DK and Conexio Stratus Pro) well and without any issue in the logging. As well as with nRF9160 and nRF9161 boards.

If I remember it well, even running the app the Thingy:91X is shipped with, shows sometimes this strange characters.

> Just to go through the list of potential questions that will arise.

Once Nordic fixes the known issue and my issue doesn't disappear, I would add a test with configuring the QWIIC into a UART (cutting the solder jumpers and use an overlay) and use a common USB-2-serial adapter. I guess, this will then give some insights, we will see ...

> Even though this is a known issue, I can't find other customer reporting this.

I guess, this is caused by my usage of it. Especially for the Thingy:91 the UART over BLE is brilliant for applying updates in the field with a SmartPhone or Tablet. I've implemented for that FOTA also over XMODEM (additional to cellular) and that's the reason, why this channel should be reliable for me.

To be frank:

As you see, if someone report something, she/he will be asked to do that or that test. Sometimes that's relevant, and sometimes I understand, that this is only way (I remember some issues with SIM card rate limit, where the nasty point was, that the Nordic developer had no such SIM card at hand and it would have take some days to get one.). But sometimes I belief, it will be only a waste of time ;-).

[Øyvind]

Øyvind said:

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

The answer I get from our developers, is that they are aware of if and working on it.