Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→Integrating VSC e PVRT32
"type": "gdb",
"request": "launch",
"gdbpath": "e:/Xilinx/SDK/2019.1/gnu/aarch32/nt/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe",
"cwd": "${workspaceRoot}",
PROTOCOL=TCP
</pre>
*Run PVT32 and start a debuggin debugging session (see for instance [[BELK-TN-007:_FreeRTOS_on_single-core_Bora_Lite_SoM#Running_the_application|this section]].[[File:TBD.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:TBD.png|thumb|center|600px|captionVisual Studio Code and PowerView TRACE32 synchornization during a debugging session]]
===Jumping from PVT32 to VSC to edit source files===
To enable this functionality, add the following lines to the PRACTICE script used to initialize the debugging session:
<syntaxhighlight lang="text">
&VSCODE="E:\program_files\MicrosoftVSCode\Code.exe"
setup.editext on "&VSCODE -g ""*:#"""
</syntaxhighlight>
While debugging, select the
===Catching cross-tool chain output===