Memory map comparison

Thanks for this PR! I'll need a bit of time to review it properly but I can give you some pointers first:

• you might find the svd interrupts tool useful (part of svdtools), it outputs a sorted list of interrupts for a specific svd file (original or patched), and shows which are are missing in sequence order too. It also shows which peripheral an interrupt is associated with.

# TODO: The blocks that are commented-out below should either go into an existing
#       block, or have a new block made for them. It's probably better that I 
#       don't improvise...

By "block" do you mean in the YAML file or an SVD peripheral? The peripherals probably already exist in the SVD so long as you use the right name.

Thank you for the tips and positive response. Working on these few definitions in the PR really drove home just how important this crate really is to get anything to work right with these processors, and the amount of work that has already been done to enable this.

Unfortunately, I seem to have used the word "block" to mean multiple things, depending on the context.

What I meant is that some of the peripheral modifications I included in the PR YAML file, I could not assign to a particular, pre-existing peripheral, and they were thus left commented-out. This is either because:

• I couldn't find the correct, pre-existing name. Or was too unsure about it.
• There was no pre-existing name, but it seemed closely related to existing peripheral family (eg: USART10, I2C5) and probably needs to be included under their umbrella somehow.

Memory map comparison

Build succeeded:

• CI

Thank you! Happy to see that it was useful.