Flash operations support#172
Conversation
|
Very cool, thanks for sending this in! From my quick skim - this looks like a straightforward, simple, non-API-breaking One thing to note: I'm currently out travelling, so even once this PR lands, I likely won't be able to cut a new release of |
daniel5151
left a comment
There was a problem hiding this comment.
A bit of feedback wrt. docs, but code-wise, everything is looking great.
|
Apologies for the delay. I will push out a new |
This PR adds support for the flash commands as described in (https://sourceware.org/gdb/current/onlinedocs/gdb.html/Packets.html#Packets). I had to change the memory map in the armv4t example providing a real memory map, otherwise GDB would not load a real .elf file. It doesn't have to be a real memory map, but you need at least a region marked a flash containing the address of the elf sections to be loaded. (eg: .vector_table, .text etc..)
|
gdbstub 0.7.6 has been published to crates.io, and includes this feature. Thank you for your contribution! |
Description
This PR adds support for the flash commands as described in (https://sourceware.org/gdb/current/onlinedocs/gdb.html/Packets.html#Packets).
I had to change the memory map in the armv4t example providing a real memory map, otherwise GDB would not load a real .elf file. It doesn't have to be a real memory map, but you need at least a region marked a flash containing the address of the elf sections to be loaded. (eg: .vector_table, .text etc..)
Tell me if I have to revert that, but in that case the flash commands cannot be tested.
API Stability
Checklist
rustdocformatting looks good (viacargo doc)examples/armv4twithRUST_LOG=trace+ any relevant GDB output under the "Validation" section below./example_no_std/check_size.shbefore/after changes under the "Validation" section belowexamples/armv4t./example_no_std/check_size.sh)Validation
GDB output
armv4t output
Before/After `./example_no_std/check_size.sh` output
Before
After