Difference between revisions of "BELK-TN-008: Integrating Visual Studio Code and Lauterbach PowerView TRACE32"
(Created page with "{{InfoBoxTop}} {{Applies To Bora}} {{Applies To BoraX}} {{Applies To BoraLite}} {{InfoBoxBottom}} __FORCETOC__ {{WarningMessage|text=This technical note was validated against...") |
|||
| Line 20: | Line 20: | ||
== Introduction == | == Introduction == | ||
| + | This Technical Note (TN) shows how to integrate Visual Studio Code (VSC) and Lauterbach PowerView TRACE32 (PVT32). The integration aims to: | ||
| + | *Debugging the program in VSC by using PVT32 to run it on the target | ||
| + | *To jump from PVT32 to VSC (in editing mode) to edit the source file where the bug was found. | ||
| + | |||
| + | This article also shows how to configure VSC in order to cross-build a Makefile-based application. This configuration supports cross-toolchain error messages to jump on erroneous lines with a simple click. | ||
Revision as of 16:26, 12 February 2020
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
|
This technical note was validated against specific versions of hardware and software. What is described here may not work with other versions. |
|
Contents
History[edit | edit source]
| Version | Date | Notes |
|---|---|---|
| 1.0.0 | February 2020 | First public release |
Introduction[edit | edit source]
This Technical Note (TN) shows how to integrate Visual Studio Code (VSC) and Lauterbach PowerView TRACE32 (PVT32). The integration aims to:
- Debugging the program in VSC by using PVT32 to run it on the target
- To jump from PVT32 to VSC (in editing mode) to edit the source file where the bug was found.
This article also shows how to configure VSC in order to cross-build a Makefile-based application. This configuration supports cross-toolchain error messages to jump on erroneous lines with a simple click.
