In windows with WSL (1 not 2) I am using openocd build for windows to attach to the device via any of stlink/cmsis-dap/jlink usb dongles and then use gdb from linux command line e.g. arm-none-eabi-gdb espruino_2v10.83_E104BT5032A.elf -ex "target remote :3333" when run like this it will stop the code and I can investigate the state (backtrace, frame info, print, ...)
I can also open another connection to openocd from another command window (telnet localhost 4444) and use mix of openocd and gdb commands concurrently - openocd can read/write memory while the program is running and can restart the running program reset run without gdb noticing.
I guess VSCode with wsl integration could possibly debug the source via arm-none-eabi-gdb too but never tried this.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
In windows with WSL (1 not 2) I am using openocd build for windows to attach to the device via any of stlink/cmsis-dap/jlink usb dongles and then use gdb from linux command line e.g.
arm-none-eabi-gdb espruino_2v10.83_E104BT5032A.elf -ex "target remote :3333"
when run like this it will stop the code and I can investigate the state (backtrace, frame info, print, ...)I can also open another connection to openocd from another command window (
telnet localhost 4444
) and use mix of openocd and gdb commands concurrently - openocd can read/write memory while the program is running and can restart the running programreset run
without gdb noticing.I guess VSCode with wsl integration could possibly debug the source via
arm-none-eabi-gdb
too but never tried this.