Replies: 2 comments 13 replies
-
|
I don't know if it requires any custom extensions, if it doesn't it should at least in theory work. You could get the built version or compile it from source as described in their README. And try with an adapter configuration like this: dap.adapters.cortex = {
type = 'executable',
command = 'node',
args = '/path/to/cortex-debug/dist/debugadapter.js'
}As for the |
Beta Was this translation helpful? Give feedback.
-
The type refers to the debug adapter it should use. You can use dashes in lua as well: dap.adapters['cortex-debug'] = {...}The value is also sent to the debug adapter as part of the launch or attach request, but it usually is not used by the debug adapter (though there are some exceptions) I'm not sure I can help you further here - the communication looks in general okay. Maybe you could create an issue in the cortex-debug repository? If you post those logs I think they should be able to tell you if some configuration is missing, or if cortex-debug requires some off-spec extensions. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, didn't know about that one. I was suspecting about the adapter name, but not sure if it was possible in LUA. Thanks a lot, I will try it later |
Beta Was this translation helpful? Give feedback.
-
|
Hi @zul00 I'm trying to do the same thing as you are. Did you have any luck so far? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @gueldenstone, I have not succeeded in using the plugin. So right now I am still relying on Termdebug. But, once I have time, I will test it again. How far did you get? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @zul00 I'm using openocd so slightly different setup. This is what I get from logs: If I set the the I also tried to tweak the regex for parsing the GDB Port, as you can see in the config. Nothing helped. I give up for now. Still it would be awesome if this worked! |
Beta Was this translation helpful? Give feedback.
-
|
Are there any news on this or has anybody achieved this? I'm currently trying to set up a similar setup using the ST-Link GDB server and have a launch.json file with which i can launch a debug session in vscode through the cortex-debug extension and am now trying to port it to neovim. I also have an adapter configuration that launches the st-link GDB server like this: dap.adapters.cortex = {
type = 'executable';
command = '/home/rick/dev/st/stm32cubeide_1.10.1/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.linux64_2.0.300.202203231527/tools/bin/ST-LINK_gdbserver';
args = {'-p 50000', '-cp /usr/bin/', '--shared', '--swd', '--halt'};
}With this configuration i'm able to start the GDB server from nvim-dap with {
"version": "0.2.0",
"configurations": [
{
"name": "Cortex Debug",
"cwd": "${workspaceFolder}",
"executable": "./build/display_eval.elf",
"request": "launch",
"type": "cortex",
"runToEntryPoint": "main",
"servertype": "stlink",
"stlinkPath": "/home/rick/dev/st/stm32cubeide_1.10.1/plugins/com.st.stm32cube.ide.mcu.externaltools.stlink-gdb-server.linux64_2.0.300.202203231527/tools/bin/ST-LINK_gdbserver",
"stm32cubeprogrammer": "/usr/bin/",
"gdbPath": "/usr/bin/arm-none-eabi-gdb",
"runToMain": true,
"device": "STM32L486VGTX",
"armToolchainPath": "/usr/bin/",
"v1": false
}
]
}I can confirm that this starts the server since i'm able to connect to it with So i guess my problem is the config about how i try to connect to the adapter and i don't really know how to go about this atm. |
Beta Was this translation helpful? Give feedback.
-
To use I'm fairly sure that the adapter definition would have to look something like this: dap.adapters['cortex-debug'] = {
type = 'executable',
command = 'node',
args = '/path/to/cortex-debug/dist/debugadapter.js'
}Or with dap.adapters.cortex = {
type = 'executable',
command = 'node',
args = '/path/to/cortex-debug/dist/debugadapter.js'
} |
Beta Was this translation helpful? Give feedback.
-
|
Yes on further inspection I noticed that as well, however same result, the GDB server is starting, but I'm unable to connect to it in nvim. However I just found this and it looks promising. Will take a look tomorrow once I've got some time again |
Beta Was this translation helpful? Give feedback.
-
|
does anyone get any luck with this? I still can't get jlink to work stm32 even with this adapter jedrzejboczar/nvim-dap-cortex-debug. |
Beta Was this translation helpful? Give feedback.
-
I like this plugin, the integration is quite intuitive when I test it on a cpp debugger. However, currently I am looking to implement it for an embedded application. From what I know I have two alternatives, either use
vscode-cpptoolsadapter with some limitation or usecortex-debug(https://github.com/Marus/cortex-debug) adapter which is specific for what I am using.Looking into 'cortex-debug' adapter it seems that it is not listed in the https://microsoft.github.io/debug-adapter-protocol/implementors/adapters/
I wonder if using
cortex-debugadapter is possible with nvim-dap, and if it is, do you have hints on where to start?Side note, I already tried the
cortex-debugadapter on vscode, and it is working in my PC, I wonder how to integrate that with nvim-dapBeta Was this translation helpful? Give feedback.
All reactions