vscode-assembly
cortex-debug
| vscode-assembly | cortex-debug | |
|---|---|---|
| 3 | 8 | |
| 110 | 927 | |
| - | - | |
| 0.0 | 7.0 | |
| over 1 year ago | 27 days ago | |
| TypeScript | ||
| GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-assembly
cortex-debug
- Help OpenOCD not recognizing SWD parameter for J-Link probe config
-
Help debugging RP2040 using J-Link and OpenOCD
Cortex-Debug: VSCode debugger extension version 1.10.0 git(cf1c296). Usage info: https://github.com/Marus/cortex-debug#usage Reading symbols from arm-none-eabi-objdump --syms -C -h -w /home/smith/Documents/gpio_int_test/build/zephyr/zephyr.elf Reading symbols from arm-none-eabi-nm --defined-only -S -l -C -p /home/smith/Documents/gpio_int_test/build/zephyr/zephyr.elf Launching GDB: arm-none-eabi-gdb -q --interpreter=mi2 IMPORTANT: Set "showDevDebugOutput": "raw" in "launch.json" to see verbose GDB transactions here. Very helpful to debug issues or report problems Error: arm-none-eabi-nm failed! statics/global/functions may not be properly classified: Error: spawn arm-none-eabi-nm ENOENT Expecting `nm` next to `objdump`. If that is not the problem please report this. Error: objdump failed! statics/globals/functions may not be properly classified: Error: spawn arm-none-eabi-objdump ENOENT ENOENT means program not found. If that is not the issue, please report this problem.Launching gdb-server: /home/smith/openocd/src/openocd -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s /home/smith/openocd/tcl -f /home/smith/.vscode/extensions/marus25.cortex-debug-1.10.0/support/openocd-helpers.tcl -f /interface/jlink.cfg -f /target/rp2040.cfg Please check TERMINAL tab (gdb-server) for output from /home/smith/openocd/src/openocd Finished reading symbols from objdump: Time: 11 ms Finished reading symbols from nm: Time: 9 ms Failed to launch OpenOCD GDB Server: Error: spawn /home/smith/openocd/src/openocd ENOENT
- Seer – a GUI front end to GDB for Linux
-
Why so many of you hate Eclipse IDE?
This guy: https://github.com/Marus/cortex-debug. Can grab it from the VSCode extensions window.
- Configuring VS Code with remote OpenOCD running on Raspberry Pi zero. How?
-
Configuring VS Code with remote openocd.
https://github.com/Marus/cortex-debug/issues/603 More info here.
-
Tutorial to set up VSCode for assembly
There's also https://marketplace.visualstudio.com/items?itemName=maziac.asm-code-lens and https://github.com/Marus/cortex-debug
-
Rust for web development: 2 years later
Thank you!
OK. I was thinking to assemble a "Press F5 to debug" solution to speed up my learning process. I'm used to command line tools and hacking stuff together too, so I should be fine if that is the state of the art for debugging (but it would be difficult to convince my coworkers in the future). I wonder if a combination of Eclipse for Rust and OpenOCD plugin is doable. Or perhaps cortex-debug[1] for VS:Code. I have some research to do, to explore the different solutions.
And I'm stuck on Windows too, since many of the tools I use require Windows.
Thanks again.
[1]: https://github.com/marus/cortex-debug
What are some alternatives?
edb-debugger - edb is a cross-platform AArch32/x86/x86-64 debugger.
debug-adapter-protocol - Defines a common protocol for debug adapters.
gf - A GDB frontend for Linux.
debugprobe
vscode-neovim - Vim mode for VSCode, powered by Neovim
seer - Seer - a gui frontend to gdb
yew - Rust / Wasm framework for creating reliable and efficient web applications
picoemp-fw
dbmate - :rocket: A lightweight, framework-agnostic database migration tool.