VSC Debugging with SVD

[cmag]

When I start the debugger (both internal and Ozone) the registers view only shows the CPU internal registers; peripherals are not shown.

If I start Ozone manually I can load NCS\v2.6.1\modules\hal\nordic\nrfx\mdk\nrf52840.svd and all registers are displayed.

How does the debugger search the SVD file?

Is it possible to force the debugger to load a specific SVD file?

[Sigurd Hellesvik]

Hi,

Do you mean to launch them in VS Code?

Regards,
Sigurd Hellesvik

[cmag]

Yes: I am trying to start the debugger from VSC: both the internal debugger and Ozone do not display the registers for the peripherals: they display sytem registers.

[Sigurd Hellesvik]

Is this what you need?

[cmag]

I have modified the launch file; this works correctly with the internal debugger; it does not work with Ozone, but this is not a problem: I can launch Ozone double clicking an external jdebug file in explorer.

{

    // Use IntelliSense to learn about possible attributes.

    // Hover to view descriptions of existing attributes.

    // For more information, visit: go.microsoft.com/.../

    "version": "0.2.0",

    "configurations": [

        {

            "type": "nrf-connect",

            "request": "launch",

            "name": "Launch the active build configuration",

            "config": "${activeConfig}",

            "runToEntryPoint": "main",

            "svdPath": "C:/Projects/NCS/v2.6.1/modules/hal/nordic/nrfx/mdk/nrf52840.svd"

        },

        {

            "type": "nrf-connect",

            "request": "launch",

            "name": "Launch build",

            "config": "${workspaceFolder}/application/build",

            "runToEntryPoint": "main",

            "svdPath": "C:/Projects/NCS/v2.6.1/modules/hal/nordic/nrfx/mdk/nrf52840.svd"

        }

    ]

}