Thingy:53 disconnects console during reboot

[asprenger]

Hi,

I'm using a Thingy:53 for some prototyping work. The device is configured with the standard USB CDC ACM as logging backend and I use pyserial-miniterm to access the logging output. 

What is really annoying is that pyserial-miniterm disconnects every time the device reboots. I'm using the same setup for example for nrf9160 and nrf52840 where this does not happen.

Any idea how to fix this?

Best regards

Andre

[Sigurd]

I'm using the same setup for example for nrf9160 and nrf52840 where this does not happen.

On the DK's, there is another MCU, the "programmer" chip, that provides the USB CDC ACM interface(UART to USB CDC ACM bridge). So even if the nRF52/nRF91 is reset, the programmer chip is not.

On the Thingy:53, it's the on-chip USB peripheral that provides the USB CDC ACM interface. When the chip is reset, then the USB communication will also be reset/disconnected.

Any idea how to fix this?

No, I don't see how that is possible.

[asprenger]

Thanks for your quick reply. That makes a lot of sense for the dev kits.

What about the thingy:91? That does not have a programmer on board but also does not disconnect during a reboot. Can we emulate this on the thingy:53? 

[asprenger]

Now when I think about it the thingy:91 has a nrf52840 on board with some kind of bridge application. That might be the reason that it keeps the connection!?

Than again I'm also working with an Actinius board (with the nrf9160) that has no other MCU and not programmer on board and also does not disconnect!?

I might just start to look at the terminal side to find another client or patch the behavior of the miniterm.

[Sigurd]

asprenger said:

Now when I think about it the thingy:91 has a nrf52840 on board with some kind of bridge application. That might be the reason that it keeps the connection!?

Correct. The nRF52840 is used as the USB CDC ACM interface on the Thingy:91. So only if the nRF52840 is reset, the terminal will disconnect.

asprenger said:

Than again I'm also working with an Actinius board (with the nrf9160) that has no other MCU and not programmer on board and also does not disconnect!?

Looks like this board has a dedicated chip for the USB CDC ACM interface(UART to USB CDC ACM bridge)

[asprenger]

Makes sense! Thanks again for the quick reply.

I'll look for a terminal program that supports automatic reconnect or patch the python code to do that!