18. Advanced Guidelines

18.1. Setup environment and debug multicore CA55 with CR52 using renesas-amalgamator

18.1.1. Overview

Support debug multicore with CA55 and CR52 for R-Car S4 device on VS code.

This item describes how to connect the S4 board to the PC host, install an extension, import the project, configure file launch.json, run and debug.

18.1.2. Connecting S4 board to PC host

We need to connect between board and PC to debug multicore ARM on VSCode as shown in the picture below:

_images/connecting-s4-board-to-pc-host.gif

Select the mode for S4 Spider Configuration tool -Renesas as shown below:

_images/s4-spider-config-tool.png

18.1.3. Setup debugger options

  1. Install the Renesas Debug extension to VSCode (please refer to Section 1: Installation).

  2. Import the built CA55 and CR52 projects into VS Code.

  3. In order to debug a project using VS Code and the Renesas Debug extension, a configuration file called launch.json needs to be created.

    1. Select [Run and Debug] view.

      _images/cacr-run-and-debug.png

    2. Select [Create a launch.json file] link.

      _images/creating-launch-json-config.png

    3. Select [Renesas Amalgamator].

      _images/renesas-amalgamator-debug-config-selection.png

    4. A launch.json file will be created inside .vscode folder with some default settings.

    5. For debugging multicore with multiple architectures on a single device, the configuration can be combined into a single launch entry.

    6. In the launch.json file, fill in the following fields.

      launch.json
       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      "type": "renesas-amalgamator",
 9      "request": "launch",
10      "name": "<display name of the configuration>",
11      "children": [
12        {
13          "name": "<display name of core>",
14          "debugAdapterRuntime": "node",
15          "interfaceType": "GDB",
16          "cortexArmList": [
17            "CortexA55", //The first Cortex is launched as the primary session
18            "CortexR52"  //All remaining Cortex-s are attached as secondary sessions
19          ],
20          "arguments": {
21            "type": "renesas-hardware",
22            "request": "launch",
23            "hardwareBreakpoint": true,
24            "isHeterogeneous": true, //Enables multi-architecture debugging
25            "program": "<absolute path to project's executable file (.x, .elf,...)>",
26            "target": {
27              "deviceFamily": "RCAR",
28              "device": "<CPU of the device>",
29              "debuggerType": "<type of the debugger>"
30            }
31          }
32        }
33      ]
34    }
35  ]
36}

      Example configuration file launch.json:

      Example: launch.json
       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      "type": "renesas-amalgamator",
 9      "request": "launch",
10      "name": "Debug Multiple",
11      "children": [
12        {
13          "name": "proc1",
14          "debugAdapterRuntime": "node",
15          "interfaceType": "GDB",
16          "cortexArmList": [
17            "CortexA55",
18            "CortexR52"
19          ],
20          "arguments": {
21            "type": "renesas-hardware",
22            "request": "launch",
23            "hardwareBreakpoint": true,
24            "isHeterogeneous": true,
25            "program": "${cwd}/CACore_Project/build/release/ca55_loader.elf",
26            "images": [
27                {
28                    "file": "${cwd}/CACore_Project/build/release/ca55_loader.elf",
29                    "type": "image-and-symbols",
30                    "program": true, //Specify the program for the first Cortex
31                    "coreName": "CA55CPU0"
32                },
33                {
34                    "file": "${cwd}/CRCore_Project/build/release/cr52_loader.elf",
35                    "type": "image-and-symbols",
36                    "program": true, //Specify the program for the second Cortex
37                    "coreName": "CR52CPU0"
38                },
39            ],
40            "target": {
41              "deviceFamily": "RCAR",
42              "device": "R8A779F0",
43              "debuggerType": "E2ARM",
44              "serverParameters": ["-uInteface=", "JTAG", "-w", "0", "-uConnectMode=", "RESET", "-uWorkRamAddress=", "0x0", "-uSyncMode=", "async", "--gdbVersion=", "7.2"]
45            },
46          }
47        }
48      ]
49    }
50  ]
51}

18.1.4. Start debugging

  1. After setting up debugger options, a debug session can be started by selecting the created configuration and click [Start Debugging] button in [Run and Debug] view, or press [F5].

    _images/multiple-debug-config-button.png

  2. Waiting for the program to launch and debug successfully.

    _images/hitting-breakpoint-successfully.png

  3. Displaying variables, watch expression, call stack… are supported in VS Code:

    1. Select [View] -> [Open View…]

      _images/open-var-view.png

    2. Select the Views to be displayed on the window.

      _images/select-display-views.png

18.2. Setup environment and debug project ARM & G4MH using renesas-amalgamator

18.2.1. Overview

Support multiple different (ARM/G4MH) cores for R-Car S4 device on VS code.

This item describes how to debug (Project ARM+G4MH).

18.2.2. Connecting S4 board to PC host

We need to connect between board and PC to debug ARM and G4MH on VSCode as shown in the picture below:

_images/connecting-arm-and-g4mh-to-pc.gif

Select the mode for S4 Spider Configuration tool -Renesas as shown below:

_images/gm4h-spider-config-tool.png

18.2.3. Setup debugger options

  1. Install the Renesas Debug extension to VSCode (please refer to Section 1: Installation).

  2. Import the built G4MH and CR52 projects into VS Code.

  3. In order to debug a project using VS Code and the Renesas Debug extension, a configuration file called launch.json needs to be created.

    1. Select [Run and Debug] view.

      _images/cacr-run-and-debug.png

    2. Select [Create a launch.json file] link.

      _images/creating-launch-json-config.png

    3. Select [Renesas Amalgamator].

      _images/renesas-amalgamator-debug-config-selection.png

    4. A launch.json file will be created inside .vscode folder with some default settings.

    5. In the launch.json file, fill in the following fields

      launch.json
       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      "type": "renesas-amalgamator",
 9      "request": "launch",
10      "name": "<display name of the configuration>",
11      "children": [
12        {
13          //RH850 Core G4MH
14          "name": "<display name of core>",
15          "debugAdapterRuntime": "node",
16          "arguments": {
17            "type": "renesas-hardware",
18            "request": "launch",
19            "program": "<absolute path to project's executable file (.x, .elf,...)>",
20            "target": {
21              "deviceFamily": "RCAR",
22              "device": "<CPU of the device>",
23              "debuggerType": "<type of the debugger>"
24            }
25          }
26        },
27        {
28          //Core Arm (CA/CR)
29          "name": "<display name of core>",
30          "debugAdapterRuntime": "node",
31          "arguments": {
32            "type": "renesas-hardware",
33            "request": "launch",
34            "program": "<absolute path to project's executable file (.x, .elf,...)>",
35            "target": {
36              "deviceFamily": "RCAR",
37              "device": "<CPU of the device>",
38              "debuggerType": "<type of the debugger>"
39            }
40          }
41        }
42      ]
43    }
44  ]
45}

      Example configuration file launch.json:

      Example: launch.json
       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      "type": "renesas-amalgamator",
 9      "request": "launch",
10      "name": "Debug Multiple",
11      "children": [
12        {
13          //RH850 Core G4MH
14          "name": "G4MH",
15          "debugAdapterRuntime": "node",
16          "arguments": {
17            "type": "renesas-hardware",
18            "request": "launch",
19            "program": "${cwd}/G4MH/HardwareDebug/G4MH_Debug.x",
20            "target": {
21              "deviceFamily": "RCAR",
22              "device": "R8A779F0",
23              "debuggerType": "E2RH850",
24              "serverParameters": ["-ulpdType=","15","-uJTagClockFreq=","Default","-setOptJtagLpd=","-uocdID=","0000000000000000000000000000000000000000000000000000000000000000","-ucustomerID=","0000000000000000000000000000000000000000000000000000000000000000","-uneedAuthentication=","0","-uWorkRamAddress=","0x0","-uTraceEnable=","PE0|PE1","-uTraceClock=","PE0|400|PE1|400","-uUseSyncTrace=","1","-uSyncTraceStandard=","0","-uTraceCore=","PE0","--gdbVersion=","7.2"]
25            },
26          }
27        },
28        {
29          //Core Arm (CA/CR)
30          "name": "ARM",
31          "debugAdapterRuntime": "node",
32          "arguments": {
33            "type": "renesas-hardware",
34            "request": "launch",
35            "program": "${cwd}/BAREMETAL_CR52/Debug/MR_BAREMETAL_CR52.axf",
36            "target": {
37                "deviceFamily": "RCAR",
38                "debuggerType": "E2ARM",
39                "device": "R8A779F0_CR52",
40                "serverParameters": ["-uInteface=", "JTAG", "-w", "0", "-uWorkRamAddress=", "0x0", "--gdbVersion=", "7.2"]
41            },
42          }
43        }
44      ]
45    }
46  ]
47}

18.2.4. Start debugging

In the select box RUN AND DEBUG (ctrl+shift+D) select “Debug Multiple” option then click [Start Debugging] (F5) button.

_images/debug-multiple-arm-gm4h.png

Waiting for program to launch and debug successfully.

_images/arm-gm4h-successful-debug.png

18.3. Setup environment and debug multi-core ARM device R-Car S4 (CA55: CPU0 to CPU7)

18.3.1. Overview

Support debug multicore with CA55 (CPU0 -> CPU7) for R-Car S4 device on VS code.

This item describes how to connect the S4 board to the PC host, install an extension, import the project, configure file launch.json, run and debug.

18.3.2. Connecting S4 board to PC host

We need to connect between board and PC to debug multicore ARM on VSCode as shown in the picture below:

_images/connecting-s4-board-to-pc-host.gif

Select the mode for S4 Spider Configuration tool -Renesas as shown below:

_images/s4-spider-config-tool.png

18.3.3. Setup debugger options

  1. Install the Renesas Debug extension to VSCode. (please refer to Section 1: Installation).

  2. Import the built CA55 projects into VS Code.

  3. In order to debug a project using VS Code and the Renesas Debug extension, a configuration file called launch.json needs to be created.

    1. Select [Run and Debug] view.

    2. Select [Create a launch.json file] link.

    3. Select [Renesas GDB Hardware Target].

    4. A launch.json file will be created inside .vscode folder with some default settings.

    5. In the launch.json file, fill in the following fields.

      launch.json
       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      "type": "renesas-hardware",
 9      "request": "launch",
10      "name": "<display name of the configuration>",
11      "program": "<absolute path to project's executable file (.x, .elf,...)>",
12      "target": {
13        "debuggerType": "<type of the debugger>",
14        "device": "<CPU of the device>",
15        "deviceFamily": "RCAR",
16      }
17    }
18  ]
19}

      Example configuration file launch.json:

      Example: launch.json
       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        "type": "renesas-hardware",
 9        "request": "launch",
10        "name": "RCAR Multicore CA55",
11        "program": "${cwd}/Debug/MR_BAREMETAL_CA55.axf",
12        "target": {
13          "deviceFamily": "RCAR",
14          "device": "R8A779F0_CA55",
15          "debuggerType": "E2ARM",
16          "serverParameters": ["-uInteface=", "JTAG", "-w", "0", "--gdbVersion=", "7.2"]
17        },
18      },
19    ]
20}

18.3.4. Start debugging

After setting up debugger options, a debug session can be started by selecting the created configuration and click [Start Debugging] button in [Run and Debug] view, or press [F5].

_images/multicore-ca55-debug-config.png

Waiting for the program to launch and debug successfully.

_images/waiting-for-ca55-to-debug-successfully.png

18.4. Setup environment and debug multi-core G4MH device R-Car S4 or device RH850

18.4.1. Overview

Support debug multicore with multi-core G4MH for R-Car S4 device (PE0, PE1) or device RH850 (PE0,PE1,PE2,PE3) on VS code.

This item describes how to connect the S4 board or RH850 board to the PC host, install an extension, import the project, configure file launch.json, run and debug.

18.4.2. Connecting S4 board to PC host

We need to connect between board and PC to debug multicore ARM on VSCode.

Select the mode for S4 Spider Configuration tool -Renesas if debug with R-Car S4 device.

18.4.3. Setup debugger options

  1. Install the Renesas Debug extension to VSCode. (please refer to Section 1: Installation).

  2. Import the built G4MH/RH850 projects into VS Code.

  3. In order to debug a project using VS Code and the Renesas Debug extension, a configuration file called launch.json needs to be created.

    1. Select [Run and Debug] view.

    2. Select [Create a launch.json file] link.

    3. Select [Renesas GDB Hardware Target].

    4. A launch.json file will be created inside .vscode folder with some default settings.

    5. In the launch.json file, fill in the following fields.

      Format of launch.json:

       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      "type": "<type>",
 9      "request": "launch",
10      "name": "<display name of the configuration>",
11      "program": "<absolute path to project's executable file (.x, .elf,...)>",
12      "target": {
13        "deviceFamily": "<the device family name Eg.RCAR>",
14        "device": "<CPU of the device>",
15        "debuggerType": "<debugger type (type of the simulator or emulator)>"
16      }
17    }
18  ]
19}

      Sample configurations for launch.json file:

      Sample: launch.json for multi-core G4MH for R-Car S4 device (PE0, PE1)
      {
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "configurations": [
    {
      "name": "G4MH",
      "type": "renesas-hardware",
      "request": "launch",
      "hardwareBreakpoint": true,
      "program": "${cwd}/HardwareDebug/G4MH_Debug.x",
      "target": {
        "deviceFamily": "RCAR",
        "device": "R8A779F0",
        "debuggerType": "E2RH850",
        "serverParameters": ["-ulpdType=","15","-uJTagClockFreq=","Default","-setOptJtagLpd=","-uocdID=","0000000000000000000000000000000000000000000000000000000000000000","-ucustomerID=","0000000000000000000000000000000000000000000000000000000000000000","-uneedAuthentication=","0","-uWorkRamAddress=","0x0","-uTraceEnable=","PE0|PE1","-uTraceClock=","PE0|400|PE1|400","-uUseSyncTrace=","1","-uSyncTraceStandard=","0","-uTraceCore=","PE0","--gdbVersion=","7.2"]
      }
    }
  ]
}
      Sample: launch.json for multi-core device RH850 (PE0, PE1, PE2, PE3)
      {
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "configurations": [
    {
      "name": "RH850",
      "type": "renesas-hardware",
      "request": "launch",
      "hardwareBreakpoint": true,
      "program": "${cwd}/HardwareDebug/Project_RH850.x",
      "target": {
        "deviceFamily": "RCAR",
        "device": "R7F702Z19A",
        "debuggerType": "E2RH850",
        "serverParameters": ["-ulpdType=", "15","-setOptJtagLpd=", "0", "-w", "1", "-usupplyVoltage=", "0", "-uocdID=", "0000000000000000000000000000000000000000000000000000000000000000"]
      }
    }
  ]
}

18.5. Create and build G4MH project on R-Car SDK

18.5.1. Create G4MH Project

  1. From the menu bar select [File] > [New] > [Renesas C/C++ Project] > [Renesas R-Car]

    _images/creating-gm4h-project.png

  2. Select R-Car project template [Renesas CC-RH C Executable Project], then click [Next] button

    _images/selecting-rcar-project-template.png

  3. Input the project name then click [Next] button.

    _images/creating-ccrh-executable-project.png

  4. In New Renesas CC-RH Executable Project select Create Hardware Debug Configuration [E2 (RH850)], then click [Finish] button

    _images/create-ccrh-executable-set-target-and-debug-config.png

  5. Projects will be created.

    _images/gm4h-project-creation.png

18.5.2. Build Project G4MH

  1. Right-click on the project and select [Build Project]

    _images/gm4h-build-sample-project.png

  2. Or can click on the [Build ]icon on the toolbar.

    _images/gm4h-build-sample-project-button.png

  3. Project after built.

    _images/gm4h-build-sample-project-project-explorer.png

18.6. Build CVEngine project on R-Car SDK

18.6.1. Create Project

  1. From the menu bar select File > Import…

    _images/e2-studio-import-project.png

  2. Select Dialog Import “Existing Projects into Workspace”, then click Next button

    _images/import-existing-projects-into-workspace.png

  3. Select Dialog Import “Select archive file” > Select Browse… > Select the project you want to build in your directory, then click Finish button.

    _images/import-project-setting-archive-file.png

  4. Project after imported

    _images/imported-project-explorer.png

18.6.2. Build Project

  1. Right-click on the project and select “Clean Project”

    _images/imported-project-clean-process.png

  2. Check Toolchain Configuration: From the menu bar select File > Window > Preferences

    _images/edit-default-toolchain-location.png

  3. Select Launch Configuration (the name of the project is imported), and Launch Target “V4H DevBoard” on the toolbar.

    _images/imported-project-debug-start.png

  4. Select “Edit” icon of Launch Target “V4H DevBoard” on the toolbar, then select Target Device “Development board / SoC” and IMP Debug Level “CVe (Shader debugging)”, then click Finish button.

    _images/edit-settings-imported-project.png

  5. Right-click on the project and select “Build Project”

    _images/imported-project-build-step.png

  6. Project after built

    _images/imported-build-ensure-success.png