The “svdFile” entry in the launch.json file is optional, but crucial to embedded system debugging because it describes the device peripheral registers. “ svdFile“: Optional, this is a CMSIS-SVD file for register detail debugging.“ runToMain“: if debugger shall set a temporary breakpoint on main() und run until there.“ device“: Device ID used for J-Link, see SEGGER J-Link website.“ armToolchainPath“: path to the arm-none-eabi-gdb executable.“ serverpath“: Path and file name of J-Link GDB Server executable.“ executable“: the binary to load and debug.
vscode folder, create a new file named launch.json, with the following content: /device/MK22F51212.svd", The J-Link can be used with GDB, LLDB, OpenOCD or CMSI-DAP. NXP FRDM-K22F BoardĪdditionally many silicon vendor boards ( LPC4322 or FRDM OpenSDA) and debug probes can load the J-Link firmware, including the NXP LPC-Link2 or STLink. The J-Link is widely available and the EDU only costs $20 or €20, is very small and universally works for many, many devices out of the box. Technically it should be possible to use other probes too. In this article I’m using a SEGGER J-Link EDU Mini debug probe.
I’m using SWD here because the FRDM-K22F only has SWD available on the debug header, but JTAG could be used too. Debugging is through a debug probe (J-Link), either external (standalone debug probe) or on-board (available with many development boards e.g. For this I need the tools and extensions installed in Part 1 of this tutorial series. In this article I show how to debug an ARM Cortex (M4F, NXP K22FN512) microcontroller with the Microsoft Visual Studio Code. This one is about debugging an ARM Cortex-M Microcontroller with Visual Studio Code: Cortex-M4 (NXP K22FN512) Debugging with Visual Studio Code Outline The previous parts were about installation, project setup and building.
0 kommentar(er)
