Difference between revisions of "BELK-TN-008: Integrating Visual Studio Code and Lauterbach PowerView TRACE32"
(→Introduction) |
|||
| (30 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
{{Applies To BoraX}} | {{Applies To BoraX}} | ||
{{Applies To BoraLite}} | {{Applies To BoraLite}} | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
{{InfoBoxBottom}} | {{InfoBoxBottom}} | ||
__FORCETOC__ | __FORCETOC__ | ||
| Line 20: | Line 15: | ||
|- | |- | ||
|1.0.0 | |1.0.0 | ||
| − | | | + | |February 2020 |
|First public release | |First public release | ||
|} | |} | ||
== Introduction == | == Introduction == | ||
| − | This Technical Note (TN) shows how to integrate | + | 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. | ||
==Testbed== | ==Testbed== | ||
To test the procedure, the same testbed described [[BELK-TN-007:_FreeRTOS_on_single-core_Bora_Lite_SoM|here]] was used. Therefore, the application used to validate the procedure is <code>freertos_hello_world</code>. | To test the procedure, the same testbed described [[BELK-TN-007:_FreeRTOS_on_single-core_Bora_Lite_SoM|here]] was used. Therefore, the application used to validate the procedure is <code>freertos_hello_world</code>. | ||
| − | + | ==Integrating VSC e PVRT32== | |
| − | < | + | ===Debugging in VSC=== |
| − | + | 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: | |
| − | + | <syntaxhighlight lang="text" line="line"> | |
| − | |||
| − | |||
| − | <syntaxhighlight lang="text"> | ||
{ | { | ||
// Use IntelliSense to learn about possible attributes. | // Use IntelliSense to learn about possible attributes. | ||
| Line 59: | Line 45: | ||
"type": "gdb", | "type": "gdb", | ||
"request": "launch", | "request": "launch", | ||
| − | "target": "${workspaceRoot}/Debug/freertos_hello_world.elf", | + | //"target": "${workspaceRoot}/Debug/freertos_hello_world.elf", |
| + | "target": "r:/home/llandre/devel/formulasae/ecu/boralite/workspace-2019.1/freertos_hello_world/Debug/freertos_hello_world.elf", | ||
"gdbpath": "e:/Xilinx/SDK/2019.1/gnu/aarch32/nt/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe", | "gdbpath": "e:/Xilinx/SDK/2019.1/gnu/aarch32/nt/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe", | ||
"cwd": "${workspaceRoot}", | "cwd": "${workspaceRoot}", | ||
| Line 71: | Line 58: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 16:37, 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. |
|
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.
Testbed[edit | edit source]
To test the procedure, the same testbed described here was used. Therefore, the application used to validate the procedure is freertos_hello_world.
Integrating VSC e PVRT32[edit | edit source]
Debugging in VSC[edit | edit source]
After opening VSC from the root directory of the freertos_hello_world project, install the Native Debug extension.
Then, create a launch.json file by selecting Debug->Add Configuration->GDB. The file should look like this:
1 {
2 // Use IntelliSense to learn about possible attributes.
3 // Hover to view descriptions of existing attributes.
4 // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
5 "version": "0.2.0",
6 "configurations": [
7 {
8 "name": "Debug (PowerView TRACE32)",
9 "type": "gdb",
10 "request": "launch",
11 //"target": "${workspaceRoot}/Debug/freertos_hello_world.elf",
12 "target": "r:/home/llandre/devel/formulasae/ecu/boralite/workspace-2019.1/freertos_hello_world/Debug/freertos_hello_world.elf",
13 "gdbpath": "e:/Xilinx/SDK/2019.1/gnu/aarch32/nt/gcc-arm-none-eabi/bin/arm-none-eabi-gdb.exe",
14 "cwd": "${workspaceRoot}",
15 "valuesFormatting": "parseText",
16 "autorun": [
17 "target remote localhost:30000",
18 "symbol-file ${workspaceRoot}/Debug/freertos_hello_world.elf",
19 ]
20 }
21 ]
22 }
