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.
"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.