-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Working gdb-server #1
Conversation
hi, I will have a look at the code tonight (France time). Even if the Thanks for your help, f. |
So this is an update which fixes all the bugs and adds an ability to write to flash. Now it is a complete replacement to ST's utility and a full-featured in-circuit debugger. The two things that still need fixing are ELF section writing (try to compile a file with a constant or two and then flash it), and hardware breakpoint support which is required to be able to debug code running inside flash. |
Here are a few minor fixes and hardware breakpoints. The stlink interface was not working: while it has initialized the FP_CTRL register, it did not set comparators to right values. In fact, there was completely no changes in corresponding memory cells after set_hw_break requests. So I've implemented that via plain write_mem32, and it works. |
With the last contribution, everything is implemented and ready for merge. |
Add stlink-tools link for Debian and Ubuntu
Merge most recent version of STLink into the fork.
I've just wrote a gdb remote debugging server, and it works. You can even load the code directly to SRAM (yay! now my flash won't be destroyed in two weeks).
You may say that the code is too crappy to be merged, but at least I want to notify you.
Can you also take a look at stlink_run? Looks like it runs a few hundred instructions and then hangs again somehow.