A set of GDB/Python-based utilities to make life debugging ARM Cortex-M processors a bit easier
It will consist of several modules which will hopefully become integrated as they evolve. Presently, there is only one:
ARM defines an SVD (System View Description) file format in its CMSIS standard as a means for Cortex-M-based chip manufacturers to provide a common description of peripherals, registers, and register fields. You can download SVD files for different manufacturers here.
I originally tested primarily with ST parts, then Freescale for a while. Now many vendor parts have been tested, each with their own quirks. If you run into a file that doesn't parse right, either make an issue and ask for help or fix it and push a patch.
The implementation consists of two components -- An lxml-based parser module (svd.py) and a GDB file (svd_gdb). I haven't yet worked out a perfect workflow for this, though it's quite easy to use when you already tend to have a GDB initialization file for starting up OpenOCD and the like. However your workflow works, just make sure to, in GDB:
source /path/to/gdb.py svd_load [your_svd_file].svd
These files can be huge so it might take a second or two. Anyways, after that, you can do
to list available peripherals with descriptions. Or you can do
to see all of the registers (with their values) for a given peripheral. For more details, run
svd [some_peripheral_name] [some_register_name]
to see all of the field values with descriptions.
You can add format modifiers like:
svd/xwill display values in hex
svd/owill display values in octal
svd/bwill display values in binary
svd/awill display values in hex and try to resolve symbols from the values
All field values are displayed at the correct lengths as provided by the SVD files.
Also, tab completion exists for nearly everything! When in doubt, run
Update this with instructions that match what it can actually do now...
The ARM Data Watchpoint and Trace Unit (DWT) offers data watchpoints and a series of gated cycle counters. For now, I only support the raw cycle counter but facilities are in place to make use of others. As this is independent of the specific device under test, commands are simple and you can configure a clock speed to get real time values from counters.
dwt configclk 48000000
will set the current core clock speed. Then
dwt cyccnt reset dwt cyccnt enable
will reset and start the cycle counter. At any point
will then indicate the number of cycles and amount of time that has passed.
This is not implemented yet. I want to have more complete support for some of the nicer debug and trace features on Cortex-M processors. Parts of this will probably be dependent on OpenOCD and possibly on specific interfaces. I'll try to avoid this where possible but can't make any promises.