Apple M1, openocd and j-link debugger

Success on my Mac mini M1 getting VSCode to build and program and debug seed/Blink using J-Link with Cortex Debug but not without some edits to a Makefile and launch.json.

Homebrew on my M1 put openocd in /opt/homebrew/bin and libDaisy/core/Makefile expects it in /usr/local/bin. Also, PGM_DEVICE was updated with jlink.cfg.

My libDaisy/core/Makefile:

OCD_DIR ?= /opt/homebrew/bin/openocd/scripts
PGM_DEVICE ?= interface/jlink.cfg
OCDFLAGS = -f $(PGM_DEVICE) -f target/$(CHIPSET).cfg

For .vscode/launch.json on line 5 i had to change a occurrence of stlink.cfg to jlink.cfg

I’m not sure where to change how the launch.json is built so it’s a manual change for me for now.

Minor annoyance: I get the following output from VSCode when I open a example folder:
11/25/2021, 10:02:41 AM] Unable to resolve configuration with compilerPath “/usr/local/bin/arm-none-eabi-g++”. Using “/opt/homebrew/bin/arm-none-eabi-gcc” instead.

It looks like another homebrew misconfiguration but it doesn’t cause any problems.

Thanks, I’m just sharing my experience with you and not expecting any fixes. I’m enjoying my pod and it’s been fun to play with it.

1 Like