Search Results

Thanks ! I'll Pm you

I have tried using Segger's remote server with tunneling, that fails too. Please see the screenshot attached. This is from running both - tunneling server, and client - on same PC, within the Co's network.. (Note: I still think fixing the IP errors / timeout issues without Segger's tunneling mode should be preferred ... why have a tunneling proxy server in-between? It's already going to be slow ) ;(

Is it possible to claim my old nick / user name back, with email I no longer have access to? Basically I've changed employers, and my previous profile was linked with previous work email.When I changed the company I obviously lost my email access, and I also don't remember old password (duh ...) But if a Segger admin has access to the profiles info, he /she will basically see it's same person ... ;(

Hi NinoQuote from SEGGER - Nino: “.... Make sure that the J-Link is reachable from your computer and that you are in the same subnet. ....” Quote from SEGGER - Nino: “You can easily find out by running our JLinkConfig application ” Please see also my thread here: Fail to connect to Segger J-Link Pro with Ethernet connection, using TCP/IP Segger JLink , GDBServer still refuse to work, even though I can access the J-Link over network by test tools. Does JLinkExe, JLinkGDBServer need any other port…

Quote from SEGGER - Niklas: “Hi, let me summarize: The J-Link is connected via Ethernet to a network (and via USB for power). The PC is connected to the same network, with some switches in between, but no routers. This setup should work. We have many customers using J-Link PRO via Ethernet, some are using a 3-digit amount of J-Links. Therefore we should be able to get you up and running :). Quote: “I can connect to it using my browser - port 80 - and I can check it settings, network status, etc.…

This is another issue I'm having with it, but I think a separate issue: Seems, if more that one client connected to port 80 (webservice), it starts throwing this: 503 Connection limit reached The max. number of simultaneous connections to this server reached.Please try again later. Does it only allow one webservice session, or is this configurable? Also, it may seem that, it does not like a port scan: after we've ran it some port scan client it _seems_ started replying 'max connections reached' …

Hi Niklas, Quote: “ The PC is connected to the same network, with some switches in between, but no routers.” No, PC is actually far away, connected to the network with that J-Link using VPN. I will get you the other info just now ..

Hi, I've originally asked on connecting to the Segger J-Link Pro over TCP/IP on this thread -timeout parameter to JLinkGDBServer seems not working but the subject just dealt with my misunderstanding on GDBServer -timeout parameter. Now may be I have bigger misunderstanding on remote debugging with Segger J-Link Pro. So we got this Segger J-Link Pro, with Ethernet connection. It is connected to target, and it is connected to network, and configured with IP 10.69.4.251. It's up and running, as see…

Hi Nino, Thanks for replying, so seems I have it confused on how to connect to the network'ed Segger's J-Link Pro (with Eth connection). So that unit is on network, and is connected and serves. I can ping that IP fine (as I'm connected through VPN), and I can access the Segger J-Link Pro web interface on port 80 just fine. I can see network status, and power on,off the unit through the web control. I also can access the Pro's unit port 19020, which, to be, is the remote server inside it. When I …

Hello Nino, Shouldn't the timeout parameter still work independent of what you quoted? Is it not the connection timeout one is setting? Note that I'm using the IP interface. For testing, I'm connecting to a (very) remote Segger J-Link Pro, and I do need to adjust the default timeout, as it seems GDBServer exists way too fast.

Hi, I've tried specifying a timeout on connection to GDBServer, but it seems to be ignoring it, always exists with after 1-3 secs no matter what timeout I'm giving it: /opt/SEGGER/JLink/JLinkGDBServer -device VF6xx_M4 -IF JTAG -select ip=10.69.4.251 -timeout 20000 Am I using it wrong?

may be "monitor halt" ?

Hi Niklas, Quote: “ However, specifying the JLinkScript is not necessary at all with current versions of the J-Link software in order to connect to an i.MX7D device series target” Yes but I'm connecting to and using script for the M4 core. Per your wiki you need this to connect to M4 core. And yes I need to script to connect to A7 core. Quote: “ Does the connect work when specifying Cortex-A7 as the target device and not using any script file at all?” I've repeated your steps for iMX7D on iMX7S,…

Hi Niklas, I cannot reproduce this anymore, after I have ran first Segger command successfully with root's privileges. I've noticed that the Firmware in my J-Link got upgraded, after I have installed & ran the new Segger package - Firmware: J-Link V10 compiled Jul 28 2017 08:59:01. That must have happened with the new Segger tools install, as my J-Link is older than that. It could be that after running as root segger command, the firmware got updated, and the issue went away.

Hi Niklas, That seems to work as far as I tested (connection to M4 ), but a few things: Per that wiki you referred to (JLink commander on Linux JLinkExe) /opt/SEGGER/JLink/JLinkExe -JLinkScriptFile /opt/SEGGER/JLink/Devices/NXP/iMX7D/NXP_iMX7D_Connect_CortexM4.JLinkScript does not seems to work, the script file is ignored, as far I see because no connection is established, and not even correct target core is selected. For me it was still on A7 from previous steps. Substituting this with /opt/SEG…

Ah ok,, figured that out: you have to start JLinkExe, and inside it's shell do ExpDevList command. Thanks

Hello Niklas, Quote: “ Well, what device / eval board are you using currently?” I'm using Toradex's Colibri iMX7D and/or iMX7S (Dual or Solo), https://www.toradex.com/computer-on-modules/colibri-arm-family/nxp-freescale-imx7, ( it's the 512MB Dual and 256MB Solo versions ) Eval board: https://www.toradex.com/products/carrier-board/colibri-evaluation-carrier-board ( Vybrid VF61x version works fine with Segger )

Quote from SEGGER - Niklas: “Hi, you can use the command "expdevlist " in J-Link Commander (JLinkEXE on Linux) in order to create a text file of supported devices. Quote: “I'm not necessarily using latest Segger tools ” May I ask why? If there is any regression, we would be happy to know about it in order to be able to fix it. Best regards, Niklas” Thanks Niklas, I tried now: /opt/SEGGER/JLink/JLinkExe expdevlist /tmp/devlist.txt OR /opt/SEGGER/JLink/JLinkExe -expdevlist /tmp/devlist.txt Both gi…

Hello, First question which of the -device flags to use for my device? Here are flags I got from Segger's list : MCIMX7D3_M4 MCIMX7D5_M4 MCIMX7D7_M4 MCIMX7U3_M4 MCIMX7U5_M4 The xDx's must be for iMX7 Dual? But whats the difference between D3 , D5, D7? I have tried all these flags on my iMX7Dual SoM, and Segger's GDBServer fails to connect with same error for all 3 of D flags. opt/SEGGER/JLink/JLinkGDBServer -device MCIMX7D3_M4 SEGGER J-Link GDB Server V6.18 Command Line Version JLinkARM.dll V6.1…

Is there a flag for this app (running on Linux) to dump the list of all known devices to it? The manual refers to the page : segger.com/downloads/supported-devices.php but this doesn't mention which versions support which devices. I'm not necessarily using latest Segger tools