Monday, February 26th 2018, 2:26am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.



Date of registration: Jan 15th 2014

Posts: 43


Saturday, January 16th 2016, 2:42pm

[SOLVED] V5.10g - Type "connect" to establish a target connection - new

In previous versions of JLink(Exe) it was enough to specify device and interface and you would automatically connect to the device, eg

"JLinkExe -if swd -device nrf51"

and you could start typing commands and doing things.

However starting around 5.10g you now get the following line output after the information about the connected Segger.

Type "connect" to establish a target connection, '?' for help

If you type connect, then it connects. It seems that if you don't but type a command which requires connection, it complains there's no connection and connects for you.

However, if you're running JLink(Exe) from a tool, like make, which is pretty common, the terminal stops after the 'Type "connect" .. ' line and the rest of the script doesn't execute as it used to because it's waiting for keyboard input.

Is this an intentional change? I would have expected if you specify the interface and device on the command line, it would auto connect. Is there another argument you can add to the command line to tell it to actually connect and keep processing? You can't add the 'connect' to the makefile script because it stops for keyboard input before it gets there. You can put the script in a file on the command line, but that's not really how most of those makefile build-and-upload scripts work.

Date of registration: Jun 25th 2015

Posts: 21


Saturday, January 16th 2016, 10:20pm


Source code

JLinkExe -if swd -device nrf51 -AutoConnect 1 -CommanderScript (your_file_name.jlink)

I think the change was to know what special handling is needed befor probing for connection.
The config option/command should not apply to SWD?



Date of registration: Jan 15th 2014

Posts: 43


Sunday, January 17th 2016, 2:01am

I'll try Autoconnect .. can't find that in the manual or the list of commands which' ? gives you'.

I did find a note in the release notes back to 5.02 that JLink no-longer performs an auto-connect with searches on all interfaces by default. However this isn't a search on all interfaces so that shouldn't seem to apply.

As I said at the end of the question - putting the commands into a file to be run isn't really how these makefile build-and-loads work. It needs to work if you were typing from the keyboard or there are a lot of makefiles going to need to be rewritten.

SEGGER - Niklas

Super Moderator

Date of registration: Oct 6th 2014

Posts: 1,691


Monday, January 18th 2016, 6:19pm



I'll try Autoconnect .. can't find that in the manual or the list of commands which' ? gives you'.

thanks for pointing that out, we will update the manual and the command list provided by "?" regarding "autoconnect".

Are you facing any other issues, or does "autoconnect" solve all problems caused by the switch from 5.02 to 5.10?

Best regards,
Would you like to be added to the J-Link software update notification list, so you get informed automatically when a new version becomes available?
Just write me a PM or in case you want to subscribe to it yourself, please use this link: Link
Notification for J-Link, J-Link Debugger, SystemView & J-Scope: Link
Notification for Embedded Studio: Link



Date of registration: Jan 15th 2014

Posts: 43


Tuesday, January 19th 2016, 3:08am

Thanks for the reply, sorry I missed it for a day.

Yes Autoconnect seems to return it to doing almost what it did before, close enough at least. One person on the Nordic forums claims it still hung at the end of his script and never returned, but I can't make that happen myself.

Date of registration: Jun 8th 2016

Posts: 20


Monday, August 8th 2016, 5:52pm

I am wondering the same thing. How can I connect it automatically. The bat that I've made, doe snot seem to work.

JLink.exe ....