I recently picked up a Segger jLink Edu, wanting to upgrade my debugging game from print statements to something a bit less pedestrian. I installed the software from Segger, which went easy enough. Soldered some leads from the jLink to the Feather M0 that I'm using, again, super easy. Plugged the jLink and the feather into two conveniently available front ports on my development box, and well, nothing seems to work.

I'm lost, very lost, and was hopeful someone here might be able to answer a couple questions:

1. I read about using the zadig app to update my drivers, but I'm not sure exactly "what" to update. Is it the jLink device that's listed, and if so, which driver do you update it to? I tried all of them and nothing seemed to have any effect other than making the Segger applications angry.

2. I'm pretty confident that my jLink is connected to my Feather properly (wiring wise), but how do you confirm that you didn't connect something incorrectly?

3. Trying to upload and debug a simple blink sketch via VS 2019 and Visual Micro yields the following error. Note that I have the following configured via Visual Micro: Adafruit Feather M0 board, COM9 Port (J-Link), J-Link over OpenOCD, Enable Programmer, Debug: Hardware, Segger JLink (SWD), No Project or Library Optimizations.

Debugger: Segger JLink (SWD)
Compiling 'Blink' for 'Adafruit Feather M0'
Build Folder: her_m0/Debug"
Program size: 10,840 bytes (used 4% of a 262,144 byte maximum) (0.27 secs)

Uploading 'Blink' to 'Adafruit Feather M0' using 'J-Link over OpenOCD'
Uploader started for board Adafruit Feather M0
Uploader will use programmer name: adafruit_jlink
ino\bin\openocd.exe -d2 -s uino/share/openocd/scripts/" -f riants/feather_m0/openocd_scripts/feather_m0.cfg" -c "telnet_port disabled; program Debug/Blink.ino.elf}} verify reset; shutdown"
Open On-Chip Debugger 0.9.0-gd4b7679 (2015-06-10-22:24)
	The upload process has finished.
Licensed under GNU GPL v2

# MI Debugger Properties
{
  "serverLaunchTimeout": 5000,
  "filterStdout": false,
  "filterStderr": true,
  "targetArchitecture": "arm",
  "stopAtEntry": false,
  "externalConsole": false,
  "MIMode": "gdb",
  "MIDebuggerServerAddress": "localhost:3333",
  "cwd": her_m0\\Debug",
  "MIDebuggerPath": -eabi-gcc\\4.8.3-2014q1/bin\\arm-none-eabi-gdb.exe",
  "MIDebuggerArgs": "",
  "debugServerPath": "C:\\ProgramData\\vmicro\\tools\\openocd-0.10.0.1\\bin/openocd.exe",
  "debugServerArgs": "-d2 -l ather_m0\\Debug/Blink.ino_DebugOpenOCD.log}\" -s\"C:\\ProgramData\\vmicro\\tools\\openocd-0.10.0.1/scripts/\" -f  -c \"transport select swd\" -f d\\1.5.5/variants/feather_m0/openocd_scripts/feather_m0.cfg\" -c \"init\"",
  "program": ebug/Blink.ino.elf",
  "logging": {
    "moduleLoad": false,
    "trace": false,
    "engineLogging": false,
    "programOutput": false,
    "exceptions": false,
    "traceResponse": false
  },
  "visualizerFile": her_m0\\Debug\\debugger_tmp.natvis",
  "showDisplayString": true
}
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
Error: Debug adapter does not support any transports? Check config file order.
Error: unable to select a session transport. Can't continue.
shutdown command invoked
 

After this error message outputs, I get a visual studio modal error window stating "Unable to start debugging. Unable to establish a connection to GDB. Debug output may contain more information".

Also, pasting this in results in syntax errors regarding an unexpected token '-d' in expression or statement

"C:\ProgramData\vmicro\tools\openocd-0.10.0.1\bin/openocd.exe" -d2 -l Debug/Blink.ino_DebugOpenOCD.log}" -s"C:\ProgramData\vmicro\tools\openocd-0.10.0.1/scripts/" -f "C:\ProgramData\vmicro\tools\openocd-0.10.0.1/scripts/interface/jlink.cfg" -c "transport select swd" -f riants/feather_m0/openocd_scripts/feather_m0.cfg" -c "init" 

So looking at my list of things, I'm assuming there are several issues.

1. I've not updated or added any drivers, mostly cuz I don't know which device to update to what driver.
2. There seems to be a syntax error of some kind when trying to execute openocd.
3. I tried to debug with both the JLink over OpenOCD and JLink over OpenOCD (vMicro). Neither worked, both OpenOCD command line statements resulting in the same syntax error statement with the only exception being the path to different versions of OpenOCD.

I appreciate the length of this post, and any thoughts you might have on things I can try. I'm eager to learn more, and up my debugging game.

Ok, a bit of progress here!

I ran the command line with the log portion removed and it still threw an error. Then I realized that powershell and cmd are different animals, switched to cmd and things ran properly but it did not find the JLink. I used Zadig to update the JLink driver to the libusbK driver, which I'm assuming is the correct one of the several we have to choose from, and re-ran the cmd with a successful result:

Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
swd
none separate
adapter speed: 400 kHz
cortex_m reset_config sysresetreq
Info : No device selected, using first device.
Info : J-Link V10 compiled Jan  7 2020 16:51:47
Info : Hardware version: 10.10
Info : VTarget = 3.283 V
Info : clock speed 400 kHz
Info : SWD DPIDR 0x0bc11477
Info : at91samd21g18.cpu: hardware has 4 breakpoints, 2 watchpoints
 

So, switching back to VS2019, I'm using Visual Micro version 1912.28.2.

Here's the interesting thing...

I can successfully start the debugger (Via F5 Start Debugging) if I select the programmer to be JLink over OpenOCD. The green light on the JLink blinks/flickers (rapidly), the debugger starts, but none of my breakpoints actually hit/break. Being a software engineer in my professional life, I'm pretty good with the Visual Studio debugger, so I'm fairly confident they work the same way as they do in any other VS based application. In this scenario, Visual Studio gives me this in the output window (debug):

openocd: Open On-Chip Debugger 0.10.0
openocd: Licensed under GNU GPL v2
openocd: For bug reports, read
openocd: 	http://openocd.org/doc/doxygen/bugs.html
openocd: debug_level: 2
=thread-group-added,id="i1"
GNU gdb (GNU Tools for ARM Embedded Processors) 7.6.0.20140228-cvs
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
=cmd-param-changed,param="pagination",value="off"
Note: automatically using hardware breakpoints for read-only addresses.
 

So, progress most certainly, but still not working as we'd hope.

Next I ran the exact scenario above but this time using the JLink over OpenOCD (vMicro) programmer, and get this in the output:

Debugger: Segger JLink (SWD)
Compiling 'Blink' for 'Adafruit Feather M0'
Build Folder: her_m0/Debug"
Program size: 10,856 bytes (used 4% of a 262,144 byte maximum) (0.29 secs)

Uploading 'Blink' to 'Adafruit Feather M0' using 'J-Link over OpenOCD (vMicro)'
Uploader started for board Adafruit Feather M0
Uploader will use programmer name: vmjlink
C:\ProgramData\vmicro\tools\openocd-0.10.0.1\bin\openocd.exe -d2 -l Debug/Blink.ino_DebugOpenOCD.log}" -s "C:\ProgramData\vmicro\tools\openocd-0.10.0.1/share/openocd/scripts/" -f "interface/jlink.cfg" -c "transport select swd" -f riants/feather_m0/openocd_scripts/feather_m0.cfg" -c "echo -n {****[vMicro]**** Uploading ELF :}" -c "reset_config; telnet_port disabled; program Debug/Blink.ino.elf}} reset;reset_config; shutdown"
Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
Error during upload using programmer
The uploader process failed

The uploader process failed
The uploader returned an error
 

To recap:

1. I updated the JLink USB driver with Zadig to what I "think" is the right driver: libusbK
2. I can debug with the programmer set to JLink over OpenOCD, but my breakpoints aren't being hit (NOTE: I added a breakpoint to a simple incremented counter variable, and another to a method invocation)
3. I cannot debug with the programmer set to JLink over OpenOCD (vMicro) at all, it results in error.
4. For the young players out there: cmd and powershell aren't the same thing. I use powershell every day so its kind of habit to use it...

Hopefully this provides a bit more insight into what's going on and the progress here.

Apologies for missing the previous post.

Zadig Driver - We have tested using the WinUSB Driver

Upload Error - In that command there was the -l logging command to the OpenOCD Log in the build directory.  If you remove the -l "{logfile}" part and re-run it you should be able to see more in the console, hopefully showing more information about the error.

Could you try updating the driver to the Win USB one, and then try just the debug attach (with code uploaded via USB or known good upload method).  Once the debugger is stable we can move onto the programmer more easily, and with less risk.

just giving this a quick bump. Any thoughts on where to go next for this issue?