I came across this a while ago, however it gives no indication as what releases, of Segger J-Link suite, each nordic J-Link OB download has been tested with.
Is there page giving Nordics recommendations? would save developers time.
I came across this a while ago, however it gives no indication as what releases, of Segger J-Link suite, each nordic J-Link OB download has been tested with.
Is there page giving Nordics recommendations? would save developers time.
Hi Steve,
J-Link OB-SAM3U128-V2-NordicSemi 170724 based on pretty old Segger Jlink driver. We don't keep track of newer Jlink release. One JLink version that had been used for testing was v6.16.c you can update the JLink OB to this version.
Do you have any issue with the Jlink firmware ?
No issue currently have had multiple issues and wasted loads of time in the past.
currently using:
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20 which seems to work ok with JLink_V622g &V6.10m but not JLink_V630h.
So would be a customer for the compatibility information if it was available.
Could you let me know what was the issue with v630h ?
Sorry Hung only just seen your reply. Have just rerun with 630h and unfortunately the message is not helpful:
Error in services launch sequence
Launching command [/Applications/SEGGER/JLink_V630h/JLinkGDBServer -if swd -device nRF52832_xxAA -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -select usb=682336494 -singlerun -strict -timeout 0] failed.
Launching command [/Applications/SEGGER/JLink_V630h/JLinkGDBServer -if swd -device nRF52832_xxAA -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -select usb=682336494 -singlerun -strict -timeout 0] failed.
Cannot run program "/Applications/SEGGER/JLink_V630h/JLinkGDBServer": Unknown reason
Have you updated the OB firmware with the firmware comes with JLink_V630h ? (replace our OB-SAM3U128-V2-NordicSemi)
To my knowledge still using the most recent release of OB-SAM3U128-V2-NordicSemi, which is working fine with V6.22g:
SEGGER J-Link GDB Server V6.22g Command Line Version
JLinkARM.dll V6.22g (DLL compiled Jan 17 2018 16:44:56)
Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
Hardware: V1.00
S/N: 682336494
To my knowledge still using the most recent release of OB-SAM3U128-V2-NordicSemi, which is working fine with V6.22g:
SEGGER J-Link GDB Server V6.22g Command Line Version
JLinkARM.dll V6.22g (DLL compiled Jan 17 2018 16:44:56)
Connecting to J-Link...
J-Link is connected.
Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 12 2018 16:05:20
Hardware: V1.00
S/N: 682336494
Yes, but if you can try using Jlink Configurator and update the firmware, it would most likely make the board more compatible with the new Jlink driver. (when segger issue new Jlink driver, they usually also update the firmware on the OB chip)