Hello,
I can use `JLinkExe` and the `JLinkRTTClient` in a `Jenkins Pipeline` based on a `Docker` container (wiki.segger.com/J-Link_Docker_Container) without Problems,
![](https://forum.segger.com/index.php/Attachment/5314-JLinkRTTClient-png/?s=6c2058eec049e0995237a08d5e201107c59ea641)
but when I want to use the `JLinkRTTLogger` the `RTT Control Block` is not found.
![](https://forum.segger.com/index.php/Attachment/5317-JLinkRTTLogger-png/?s=6c2058eec049e0995237a08d5e201107c59ea641)
I also tested the `JLinkRTTLogger` outside of `Jenkins` and just directly in the container and here the `RTT Control Block` will be found.
![](https://forum.segger.com/index.php/Attachment/5316-Container-png/?s=6c2058eec049e0995237a08d5e201107c59ea641)
So,
1) what is difference between the client and the logger?
2) how I can debug and solve this problem (e.g., via verbose logging)
3) any experience with the logger in `Jenkins`?
Best regards
toba
I can use `JLinkExe` and the `JLinkRTTClient` in a `Jenkins Pipeline` based on a `Docker` container (wiki.segger.com/J-Link_Docker_Container) without Problems,
but when I want to use the `JLinkRTTLogger` the `RTT Control Block` is not found.
I also tested the `JLinkRTTLogger` outside of `Jenkins` and just directly in the container and here the `RTT Control Block` will be found.
So,
1) what is difference between the client and the logger?
2) how I can debug and solve this problem (e.g., via verbose logging)
3) any experience with the logger in `Jenkins`?
Best regards
toba
The post was edited 2 times, last by toba ().