The most recent IAR Build and IAR C-SPY Debug Extensions v1.20 for Visual Studio (VS) Code are compatible with all the latest versions of IAR Embedded Workbench and include symmetric multicore debugging, support for more advanced breakpoint types, and a customisable build toolbar.
These new features mean that the VS Code extensions will further help software engineers optimise workflows, improve performance, and reduce development costs. The IAR Build and IAR C-SPY Debug Extensions v1.20 for VS Code are available for free download on Visual Studio Code Marketplace.
Visual Studio Code is a code editor that’s used by embedded developers to build and debug complex projects, task running, version control, and many other tasks. With IAR’s Visual Studio Code Extensions, developers can work in VS Code and take full advantage of the features of IAR Embedded Workbench including the IAR C-SPY and IAR Build tools.
The IAR tools are automatically detected and support a wide range of versions for Arm, RISC-V, Renesas RH850 and RL78, AVR, 8051, and many more.
IAR C-SPY is a high-level-language debugger for embedded applications which is fully integrated into IAR Embedded Workbench and provides development and debugging capabilities within the same IDE. The IAR C-SPY Debug Extension for VS Code automatically provides debug configuration from the tool suite and project. The extension supports Arm and RISC-V, and with v1.20 also Microchip AVR and Renesas RL78 devices.
In addition, the latest version of the extension offers symmetric multicore debugging and the use of advanced Visual Studio breakpoint types like conditional breakpoints, data breakpoints, and log breakpoints (log messages).
The latest version of the IAR Build Extension for VS Code includes a new toolbar window with buttons for building the application and performing C-STAT static analysis. A new dropdown menu in the “Extension Configuration” view allows developers to select the “Custom Argument Variables” featured in IAR Embedded Workbench.
To exclude unwanted project files in the workspace from the project list, a setting for “Projects to Exclude” has been added and, to avoid errors, the file paths in the settings file are now workspace-relative rather than absolute.
