Bureaucrats, dave_user, Administrators
4,650
edits
Changes
no edit summary
</syntaxhighlight>
*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]] The source file will be open into in VSC, which will jump on the selected line.[[File:TBDBoraLite-VSC4.png|thumb|center|600px|Using VSC as the default editor for PVT32]]===Catching cross-tool chain toolchain output===