-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easy firmware flashing #311
Comments
@therealprof and I have started working on this some time ago: https://github.com/Yatekii/probe-rs |
@Yatekii sure, it will be helpful. However, it seems like we still need a gdb layer for debugging. Do you have any ideas about using gdb with |
@Disasm If someone wants to write a gdbserver protocol adapter, that'd be one option. Better ideas (IMHO, of course) would be:
|
Hey totally agreed it'd be excellent to make this easy! A couple of thoughts:
|
Definitely cool projects you have here! The problem at least for myself is, that I'd like to eliminate unnecessary layers like GDB, which all of those tools don't. They basically encapsulate the bazzillion tools there is. Each and every of them has it's own quirks and implementations of the GDB protocol. Flashing might or might not work, etc. I will definitely have a look at those projects, especially the Cortex Debug one, but on the long run, I would love to have a standalone tool without the layer cake. |
@ryankurte Can you flash with Cortex Debug? I am currently using a pre-launch task to do this in C/C++, it would be neat to avoid this. |
@Yatekii interesting! i can see the benefit of not having the layers and quirks (though personally might be a little attached to GDB). @ejpcmac i've been doing the same. there is however an option to pre-run gdb commands on connect in the launch configuration, in which case something like |
probe-rs has made tremendous progress and provides |
We need some tool to make firmware upload process as easy as running "cargo flash".
Possible functions:
Original comments:
#256 (comment)
rust-embedded/book#12 (comment)
The text was updated successfully, but these errors were encountered: