GDB Monitor commands for debugging AVR microcontrollers on GNU/Linux
Bloom's GDB server supports a number of custom GDB commands, which can be invoked via the
monitor command in avr-gdb.
(gdb) monitor [COMMAND_NAME]
reset command can be used to reset the connected target.
(gdb) monitor reset Target reset complete - use the 'continue' command to begin execution. (gdb)
Upon issuing the command, Bloom will reset the connected target to its reset vector, and hold it in a stopped state. Execution can then be restarted via GDB.
Generate SVD file
This command was introduced in version 0.11.0.
svd command can be used to generate a System View Description (SVD) XML
file, for the connected target.
(gdb) monitor svd SVD output saved to /path/to/project/ATxmega16C4.svd (gdb)
Upon issuing the command, Bloom will generate the SVD XML and save it to a file in the current project
directory. Or, if the
--out option was passed, Bloom will send the XML to
GDB, to present as command output.
If the output file already exists, it will be overwritten.
For AVR targets, the peripheral base addresses in the generated SVD will be offset by 0x0800000. This offset is required by GDB, for accessing the SRAM address space on AVR targets via GDB.
The generated SVD will not include register fields. This is due to a limitation in Bloom. Report an issue to express demand for this.
Display help text
help command can be used to display the server's help text, which
describes the supported
(gdb) monitor help
Display version number
version command can be used to display Bloom's current version number.
(gdb) monitor version
version machine command can be used to display Bloom's current version
number, in machine-friendly (JSON) format.
(gdb) monitor version machine