Hi there,
I have been using a J-Link running v6.50b. My development environment is inside a linux Docker container, and the Host OS is Windows 10. I run the J-Link remote server on the host with the J-Link connected via USB and connect from inside the container using
My docker container still resolves the address using ping
And can connect using the hard coded address
But does not connect using the host.docker.internal name anymore
What I notice is that the error is
But if I type a wrong IP it gives
Almost like it is treating the host.docker.internal as the name of a J-Link even though it is passed in with the -ip.
Can anyone shed some light on this and how I can fix?
Thanks
Travis
I have been using a J-Link running v6.50b. My development environment is inside a linux Docker container, and the Host OS is Windows 10. I run the J-Link remote server on the host with the J-Link connected via USB and connect from inside the container using
JLinkeExe -ip host.docker.internal
which has been working fine. Recently I upgraded the segger tools to version 6.98c and it has stopped working.My docker container still resolves the address using ping
Source Code
- ping host.docker.internal
- PING host.docker.internal (192.168.65.2) 56(84) bytes of data.
- 64 bytes from 192.168.65.2 (192.168.65.2): icmp_seq=1 ttl=37 time=1.15 ms
- 64 bytes from 192.168.65.2 (192.168.65.2): icmp_seq=2 ttl=37 time=1.48 ms
- 64 bytes from 192.168.65.2 (192.168.65.2): icmp_seq=3 ttl=37 time=1.19 ms
And can connect using the hard coded address
Source Code
- JLinkExe -NoGui 1 -ip host.docker.internal:19020
- SEGGER J-Link Commander V6.98c (Compiled Mar 16 2021 12:23:05)
- DLL version V6.98c, compiled Mar 16 2021 12:22:49
- Connecting to J-Link via IP...FAILED: Cannot connect to J-Link name host.docker.internal via TCP/IP. No emulators found.
- Cannot connect to J-Link.
But if I type a wrong IP it gives
Can anyone shed some light on this and how I can fix?
Thanks
Travis