Thingy:53 disconnects console during reboot

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

Parents
  • 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.

Reply
  • 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.

Children
No Data
Related