how do I start the svd viewer? about vscode-peripheral-inspector HOT 10 CLOSED

Hi @soundart

There's a few things to check here....

I have not used cortex-debug before

Your launch.json config outlines you are using the cppdbg debugger which is from the cpptools extension, not cortex-debug extension.

Which device are you trying to debug and which debugger do you want to use?

svdPath": "${workspaceFolder}/vscode/svd/arm_uart_pl011.svd",

svdPath has recently been renamed to definitionPath, can you also check the path, as the .vscode folder has a dot in it.

This extension is standalone and should appear when the following conditions are met:

• A debug session is started
• Valid data is loaded from the svd file

You can check the latter by loading any valid svd file, e.g.:

{
           "name": "Qemu Attach with GDB",
           "type": "cppdbg",
           "request": "launch",
...
           "definitionPath": "https://pack-content.cmsis.io/NXP/K32L3A60_DFP/18.0.0/devices/K32L3A60/K32L3A60_cm4.xml",
...
  }

Please let us know if you still fail to see the peripheral window after trying this.

from vscode-peripheral-inspector.

from vscode-peripheral-inspector.

OK, I can see your confusion, which is my fault, sorry!

I assume you are using cortex-debug.svd-viewer? This is being deprecated in favour of clipse-cdt.peripheral-inspector (this repository).

Could you use the new extension, then try the definitionPath test above (pointing at the svd file url) to see if anything appears for you at all?

from vscode-peripheral-inspector.

from vscode-peripheral-inspector.

Visual studio still complains wrt definitionPath property.

Ah yes it would, because we cant control the parameters listed for the debugger you are using.

all register values are currently 0xeeeeeee

I can see the debugger is returning unreadableBytes so the debugger isnt happy with your request

No handler implemented for request type 'WriteMemoryRequest'

Your debugger doesn't support writing memory, perhaps we should handle that case in the extension?

from vscode-peripheral-inspector.

from vscode-peripheral-inspector.

And no "WriteMemoryRequest"

Oh dear, that means the adapter wont be able to write to memory. Its a bit drastic, but you may need to switch to using a different adapter.

Ones I know of which wrap gdb:

• https://github.com/eclipse-cdt-cloud/cdt-gdb-vscode (recommended as its a sister project to this one)
• cortex-debug

from vscode-peripheral-inspector.

Hi thank you very much for the help.

I am a bit surprised that memory writes are not supported. This sounds like a basic
functionality.

I think all extensions (except the svd viewer) which I am using are provided by microsoft itself.

I have seen this eclipse-cdt-cloud/cdt-gdb-vscode#119 and suspect it wont be easy to install that extension, or?

from vscode-peripheral-inspector.

I have seen this eclipse-cdt-cloud/cdt-gdb-vscode#119 and suspect it wont be easy to install that extension, or?

This is a debug adapter which wraps gdb and is maintained by the eclipse foundation (along with the svd viewer here). It isn't currently published on the vscode marketplace, but I believe there are plans to do this very soon (@jonahgraham ?).

In the meantime, you can clone the repo and build it locally to get a vsix package to install.

As of yesterday, you also have another option. We have just promoted the Arm Debugger extension to version 1 here:

https://marketplace.visualstudio.com/items?itemName=Arm.arm-debugger

It doesn't use gdb, but is a full-featured debugger and could be a good alternative for you.

from vscode-peripheral-inspector.

Thank you very much for your help!

from vscode-peripheral-inspector.