Bureaucrats, dave_user, Administrators
8,226
edits
Changes
no edit summary
{{Applies To BoraX}}
{{Applies To BoraLite}}
{{AppliesToBORA_TN}}
{{AppliesToBORA_Xpress_TN}}
{{AppliesToBORA Lite TN}}
{{AppliesToVisualStudioCode}}
{{AppliesTo VisualStudioCode TN}}
{{InfoBoxBottom}}
__FORCETOC__
|-
|1.0.0
|February June 2020
|First public release
|}
== Introduction ==
This Technical Note (TN) shows how to integrate [https://code.visualstudio.com/ Visual Studio Code (VSC) ] and [https://www.lauterbach.com/ Lauterbach PowerView TRACE32 (PVT32)]. The integration aims to:
*Debug the program in VSC by using PVT32 as a communication bridge with the target
*Jump from PVT32 to VSC (in editing mode) to edit the source file where the a an issue/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.
==Testbed==
</pre>
==Integrating VSC e PVRT32PVT32==
===Debugging in VSC by using PVT32 as a communication bridge===
*After opening VSC from the root directory of the <code>freertos_hello_world</code> project, install the ''Native Debug'' extension.
*Then, create a <code>launch.json</code> file by selecting ''Debug->Add Configuration->GDB''. The file should look like this:
<presyntaxhighlight lang="text">
{
// Use IntelliSense to learn about possible attributes.
]
}
</presyntaxhighlight>*Edit the PVT32's configuration file (ususally usually named <code>config.t32</code>) and add the following lines:<presyntaxhighlight lang="text">
; Remote Control Access
GDB=NETASSIST
PORT=30000
PROTOCOL=TCP
</presyntaxhighlight>*Run PVT32 and start a debugging session (see for instance [[BELK-TN-007:_FreeRTOS_on_single-core_Bora_Lite_SoM#Running_the_application|this section]]).[[File:TBDBoraLite-VSC1.png|thumb|center|600px|Debugging session started on PVT32 side]]
*On VSC side, start a debugging session by pressing F5. VSC will start a debug session that is synchronized with PVT32 as shown in the following image. So you can set breakpoints, steb-by-step execute the code, etc. on VSC side, but the actual operations will be done on the target by PVT32.
[[File:TBDBoraLite-VSC2.png|thumb|center|600px|Visual Studio Code and PowerView TRACE32 synchornization during a debugging session]]
===Jumping from PVT32 to VSC to edit source files===
</syntaxhighlight>
While debugging, right-click on the line you want to edit and select ''Edit Source''.[[File:BoraLite-VSC3.png|thumb|center|600px|Using VSC as the default editor for PVT32]]===Catching cross The source file will be open in VSC, which will jump on the selected line.[[File:BoraLite-tool chain output===VSC4.png|thumb|center|600px|Using VSC as the default editor for PVT32]]