Hi there,
I recently got a new Laptop for work, a Microsoft Surface Book 3. Segger RTT for me is a crucial tool for my development work and I often have multiple targets connected at the same time. Unfortunately it looks like there is something with how RTT transfers data via USB that brings out an issue on the Microsoft Surface Book 3 that makes other USB devices not perform as expected.
In detail it looks like this: As soon as a target device is connected via RTT, my external USB-keyboard and mouse stop working intermittently. I.e. a lot of keyboard events and mouse events are entirely lost. I estimate that this happens around once every 10s for a couple 100 milliseconds. Sometimes more often, sometimes less, I think. The issue disappears as soon as the RTT session is closed. The issue exists with both RTT client and RTT viewer, but it seems to not be triggered when simply debugging - i.e. running the debugger in Keil uVision or J-Link Commander by itself does not seem to trigger the issue. It does not seem to matter whether the target device is "quiet" or outputting a lot of data via RTT.
For the record, I do think that this is actually some issue with either the Surface Book 3 hardware, firmware or drivers - as I found other users having reported the same / similar issues on the device, but unrelated to RTT. Nonetheless I'm curious as to why this behaviour is specifically triggered by RTT and if there is a possible workaround on the RTT side as well. I did open a thread in the Surface Book 3 support forum on this topic, so far with no useful responses.
For these tests I was using J-Link version 6.88 and 6.92 and the Nordic nRF52 Development Kits which have J-Links on-board.
I'd be grateful for any help!
I recently got a new Laptop for work, a Microsoft Surface Book 3. Segger RTT for me is a crucial tool for my development work and I often have multiple targets connected at the same time. Unfortunately it looks like there is something with how RTT transfers data via USB that brings out an issue on the Microsoft Surface Book 3 that makes other USB devices not perform as expected.
In detail it looks like this: As soon as a target device is connected via RTT, my external USB-keyboard and mouse stop working intermittently. I.e. a lot of keyboard events and mouse events are entirely lost. I estimate that this happens around once every 10s for a couple 100 milliseconds. Sometimes more often, sometimes less, I think. The issue disappears as soon as the RTT session is closed. The issue exists with both RTT client and RTT viewer, but it seems to not be triggered when simply debugging - i.e. running the debugger in Keil uVision or J-Link Commander by itself does not seem to trigger the issue. It does not seem to matter whether the target device is "quiet" or outputting a lot of data via RTT.
For the record, I do think that this is actually some issue with either the Surface Book 3 hardware, firmware or drivers - as I found other users having reported the same / similar issues on the device, but unrelated to RTT. Nonetheless I'm curious as to why this behaviour is specifically triggered by RTT and if there is a possible workaround on the RTT side as well. I did open a thread in the Surface Book 3 support forum on this topic, so far with no useful responses.
For these tests I was using J-Link version 6.88 and 6.92 and the Nordic nRF52 Development Kits which have J-Links on-board.
I'd be grateful for any help!