Hello,
I saw this thread about using RTTLogger in background mode, and I have the same issue with JLinkExe: forum.segger.com/index.php/Thr…gger-in-background-mode/?
My question is: will this change be only for RTTLogger, or does it share a common backend with other tools and thus allow other Segger Tools, such as JLinkExe, to run in the background?
How we found this: My team updated our version of Segger Tools to version v7.82, but this broke one of our scripts that ran JLinkExe in the background and then accessed the device connected to the JLink over netcat (nc). When we downgraded back to v6.98 we were able to run JLinkExe in the background and connect over netcat.
We are using JLink BASE Compact's that are connected to raspberry pi's.
Thank you,
Grant
I saw this thread about using RTTLogger in background mode, and I have the same issue with JLinkExe: forum.segger.com/index.php/Thr…gger-in-background-mode/?
My question is: will this change be only for RTTLogger, or does it share a common backend with other tools and thus allow other Segger Tools, such as JLinkExe, to run in the background?
How we found this: My team updated our version of Segger Tools to version v7.82, but this broke one of our scripts that ran JLinkExe in the background and then accessed the device connected to the JLink over netcat (nc). When we downgraded back to v6.98 we were able to run JLinkExe in the background and connect over netcat.
We are using JLink BASE Compact's that are connected to raspberry pi's.
Thank you,
Grant