Difficulties directing shell to both RTT and UART backend

RE: Difficulties directing shell to both RTT and UART backend

Sigurd Hellesvik — Thu, 28 Jul 2022 14:17:44 GMT

Hi Alyssa,

It looks like some timing issue, where deactivation of the RTT shell deactivates the UART shell at the same times.

I tried to increase the loop sleep time to 1 second, and the issue did not appear as often as before.

In addition to this, I were able to decrease the apparance of the issue by tuning the Shell backend configurations using the VS Code Kconfig extension:

I try to change the configurations a bit yourself, and see if you are able to solve the issue.

Another thing which is weird:

When I try to reproduce the issue while debugging using VS Code (without Kconfig changes), both RTT and UART works all the time, even if I repeatedly reconnect RTT.

Regards,
Sigurd Hellesvik

RE: Difficulties directing shell to both RTT and UART backend

Sigurd Hellesvik — Tue, 26 Jul 2022 14:37:22 GMT

Hi Alyssa,

Due to lower staffing in the summer vacation, it takes longer than normal to answer cases.

I am sorry that it takes some time. But I will have a closer look at your case and give you an answer by end of Thursday.

Regards,
Sigurd Hellesvik

RE: Difficulties directing shell to both RTT and UART backend

ahoward — Fri, 22 Jul 2022 16:34:08 GMT

Hi,

I would like shell functionality and logging on both RTT and UART. It's able to this as long as RTT is connected, but once the viewer is disconnected, both logging and shell functionality stop on UART.

Alyssa

RE: Difficulties directing shell to both RTT and UART backend

Sigurd Hellesvik — Fri, 22 Jul 2022 10:56:11 GMT

Hi Alussa,

So you need to have shell functionality (input+output) on the RTT, but only log on UART(output)?

Regards,
Sigurd Hellesvik