NOTE: If a chip vendor ships it's own OpenOCD version, for sure use NOTHING but that.OpenOCD - provides a GDB Server that can be used with a number of debuggers ( ).J-Link Software Tools - provides the J-Link GDB Server for J-Link based debuggers ( ).ARM GCC Toolchain ( ) - provides arm-none-eabi-gdb and related tools.With MS convention, if the minor version is odd, then it is a pre-release. To summarize, extensions use semantic versioning (SemVer) system which in simple terms is. They allow you participate during the formation of a feature of how an issue gets addressed. We use pre-releases as allow testing of bug fixes and new features. You can enable (or disable) pre-releases within VSCode for this extension and you will automatically get new pre-releases. We will consider make an Extension Pack in the futureĬortex-Debug uses a versioning system specified by Microsoft that allows distribution of pre-releases via the marketplace. These extensions are considered as dependency of this extension and VSCode should help you install all of them.Highlights are a Memory Viewer, Peripheral (SVD) Viewer, RTOS viewer.These services are under the mcu-debug organization and lot of that content was re-factored from this extension to make them work with other debuggers and with browsers.We have a set of extensions that this extension relies on for various frontend services (since V1.6).Live Watch with supported GDB servers (tested with OpenOCD, J-Link, STLink so far - since V1.6).As a general rule do not try to use stepping instructions before the scheduler of your RTOS has started - in many cases this tends to crash the GDB servers or leave it in an inconsistent state.RTOS Thread Support in CALL STACK window (J-Link, OpenOCD, pyOCD - RTOS supported depend on GDB server).Initial support for Rust code (most functionality is working report any issues.Globals and Static scopes in the variables view.See image above for console style output. All the features supported for SWO (text, binary, graphing) are also supported with RTT. Support for SEGGER Real Time Trace (RTT) using OpenOCD and J-Link gdb-servers.This applies to those gdb-servers that do their semi-hosting on their stdio. That terminal is bidirectional and is intended for semi-hosting. In the TERMINAL tab, there will be a sub-window called gdb-server. If you are using TCP/IP instead, you can use a variety of tools to connect to the that port. Data can be printed to a output window, or sent to the graphing system. Ability to define JavaScript modules to decode complex data formats streamed over one or more ITM ports.Decoding ETM data over the SWO pin is not currently supported.Firmware may still need to enable the SWO output pin - as this part of the setup is microcontroller dependant.The registers that are part of the DWT, TPIU, and ITM debug components will automatically be configured and do not need to be set in firmware.SWO Decoding - "console" text output and binary data (signed and unsigned 32-bit integers, Q16.16 fixed point integers, single precision floating point values).In some cases the st-util GDB server can report incomplete/incorrect registers, so there may be some issues here.Cortex Core Register Viewer (integrated into Variables window since V1.2).The actual disassembly window is provided and managed by VSCode. Disassembly of source code available along with instruction level breakpoints and stepping.Multi-core and multi-session debugging.Partial support textane/stlink (st-util) GDB Servers (SWO can only be captured via a serial port).Initial support for the Black Magic Probe (This has not been as heavily tested SWO can only be captured via a serial port).Support J-Link, OpenOCD GDB Server, STMicroelectronic's ST-LINK GDB server (no SWO support yet), pyOCD.Debugging support for ARM Cortex-M Microcontrollers with the following features:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |