JLinkExe hangs in Makefile but not in terminal on Mac OS

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Tue, 19 Jan 2016 00:59:21 GMT

Well I don't know what your makefile looks like but after some more testing I pretty much can't make this hang whether I pipe the commands into JLinkExe, or put them in a file and put that on the end, or use Autoconnect or don't use Autoconnect (although Autoconnect is cleaner). This makefile for instance works with make test or make test2. Doesn't hang, exits with a clean 0 exit.

test: 
	echo "r\nh\nloadbin test.bin 0x00\nexit\n" |\
	JLinkExe -if swd -device nrf51 -speed 4000

xx: makefile
	echo r\\nh\\nloadbin test.bin 0x00\\nexit\\n >> xx

test2: xx
	JLinkExe -if swd -device nrf51 -speed 4000 xx

clean:
	rm -f xx

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Sun, 17 Jan 2016 22:50:15 GMT

works for me - also working for me is using 'q' at the end instead of 'exit', or 'qc` which explicitly disconnects or putting the commands into a file and placing that filename on the end of the line instead of emitting them from the makefile. Still annoying they changed it however.

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

LukaszM — Sun, 17 Jan 2016 20:16:20 GMT

Seems like it is connecting now but it still hangs (waits or a n input) unfortunately. The only difference is that it hangs on the last console log line: "Cortex-M0 identified." instead of "Type "connect" to establish a target connection, '?' for help"

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Sun, 17 Jan 2016 02:03:01 GMT

Yes that works - just change the run line to

JLinkExe -if swd -device nrf51 -speed 4000 -Autoconnect 1

and it will work just as it did before - no need to muck around with Applescript.

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Sun, 17 Jan 2016 01:04:04 GMT

Suggestion on the segger forums just to add

-AutoConnect 1

to the command line - try that - I don't have a board to hand right now.

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

LukaszM — Sat, 16 Jan 2016 21:57:48 GMT

I managed to work around this by appliyin Apple script. I created upload.sh script file (had to have executable permissions, use chmod +x if needed). Then Makefile invokes this script instead of JLinkExe commands directly. Content of upload.sh:

#!/bin/sh 
osascript <<END 
tell application "Terminal"
    do script "JLinkExe  -device nrf51422_xxac -if swd -speed 4000\nloadbin filepath.bin 0x18000\nr\nexit\n$1"
end tell
END

Replace filepath.bin with full path where bin file is expected to be after compilation (_build subdirectory) or use environmental variables to set it for you (did not have time for this yet and will update my answer when I perfect it).

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Sat, 16 Jan 2016 13:27:30 GMT

oh yes all my JLinks are doing it now - fortunately it doesn't affect RKNRFGO or I would be annoyed. Seems that it no-longer automatically connects, you have to connect it yourself. Typing any command which requires a connection outputs a message about needing a connection but not being connected, and then it connects. That's probably why it works from the terminal.

You might be able to append a command onto the end of the command line, one which does nothing useful but forces the connect.

Definitely should ask Segger about this one.

RE: JLinkExe hangs in Makefile but not in terminal on Mac OS

RK — Sat, 16 Jan 2016 11:31:28 GMT

well it doesn't hang - it's just waiting for input. It wants someone to type 'connect'. I don't know why however I did notice my JLink-Edu was doing that yesterday when I was running it from the command line which is rather annoying.

I'm assuming it's something Segger put in the latest version of JLinkExe, possibly by mistake, but perhaps not. I'd head over to their forums and ask why JLink(Exe) is now asking for a connect command to be typed in even when switches are put on the original command.

I don't know why it's not doing it when you type it by hand. I suspect they broke something. You could try a downgrade to 5.10