Hi all, my first post here.
I'm in Australia, trying to connect to a Flasher-ARM in the US via our company's global Intranet, to debug firmware in a device over there. I can ping the Flasher's IP address and access its webserver without any problems. The ping time averages about 205ms. However, when I start J-Link Configurator, it initially doesn't find the Flasher.
If I then start J-Flash and specify the Flasher's IP address I can download config & data to the Flasher, and it then usually shows up in the Configurator, but with a red dot beside it followed by something like "0 (21*n/a)" with the 21 slowly incrementing, I presume as the Configurator tries to communicate with the Flasher.
When I try to use Rowley Crossworks for ARM 3.3 to connect to the Flasher as a J-Link at the specified IP address, I usually get an error box: "J-Link V4.92 Error --- IP communication error. Connection closed!". Sometimes I also get an error when downloading data to the Flasher using J-Flash: "J-Flash V4.92 Error --- Communication timed out: Requested 4 bytes, received 0 bytes! --- Failed to download to emulator".
I had no problems using the Flasher as a J-Link via TCP/IP when it was plugged into the same network as my computer here in Australia - it behaved pretty much as if it were connected by USB.
It feels like the connection is just a little too slow to work reliably. Is there an upper limit on the allowable connection ping time? Are there any options to increase the timeout delay or something similar I can do to get this working? Is there some other problem I'm not aware of that could be a factor? Any other ideas?
Thanks,
Kevin.
I'm in Australia, trying to connect to a Flasher-ARM in the US via our company's global Intranet, to debug firmware in a device over there. I can ping the Flasher's IP address and access its webserver without any problems. The ping time averages about 205ms. However, when I start J-Link Configurator, it initially doesn't find the Flasher.
If I then start J-Flash and specify the Flasher's IP address I can download config & data to the Flasher, and it then usually shows up in the Configurator, but with a red dot beside it followed by something like "0 (21*n/a)" with the 21 slowly incrementing, I presume as the Configurator tries to communicate with the Flasher.
When I try to use Rowley Crossworks for ARM 3.3 to connect to the Flasher as a J-Link at the specified IP address, I usually get an error box: "J-Link V4.92 Error --- IP communication error. Connection closed!". Sometimes I also get an error when downloading data to the Flasher using J-Flash: "J-Flash V4.92 Error --- Communication timed out: Requested 4 bytes, received 0 bytes! --- Failed to download to emulator".
I had no problems using the Flasher as a J-Link via TCP/IP when it was plugged into the same network as my computer here in Australia - it behaved pretty much as if it were connected by USB.
It feels like the connection is just a little too slow to work reliably. Is there an upper limit on the allowable connection ping time? Are there any options to increase the timeout delay or something similar I can do to get this working? Is there some other problem I'm not aware of that could be a factor? Any other ideas?
Thanks,
Kevin.