Support arrays of peripherals

[daym]

It would be nice if svd2rust also supported peripheral arrays of SVD 1.3.

See https://arm-software.github.io/CMSIS_5/SVD/html/elem_peripherals.html#elem_peripheral .

Starting version 1.3 of the SVD specification, arrays of peripherals can be specified. The single peripheral description gets duplicated automatically into an array. The number of array elements is specified by the <dim> element. To define arrays, the needs the format myPeripheral[%s]. The tag <dimIncrement> specifies the address offset between two peripherals. To create copies of a peripheral using different names, you must use the derivedFrom attribute.

[robamu]

This is possibly related to rust-embedded/svd#41 ?

What is the state of this? I am trying to generate a PAC for the VA108xx0 devices and I have issues with blocks like this

        <register derivedFrom="INT_RAM_SBE">
          <dim>32</dim>
          <dimIncrement>4</dimIncrement>
          <name>TIM[%s]</name>
          <description>TIM Interrupt Redirect Selection</description>
          <addressOffset>0x100</addressOffset>
        </register>

        <register derivedFrom="NMI">
          <dim>32</dim>
          <dimIncrement>4</dimIncrement>
          <name>IRQS[%s]</name>
          <description>Interrupt Status Register</description>
          <addressOffset>0x800</addressOffset>
        </register>

also crashes with a quite useless error message: [ERROR svd2rust] expected ,``

How easy/difficult would it be to implement handling for these array blocks?

[robamu]

Okay, I now see that the blocks I am trying to parse are actually register block arrays. I think svd2rust can parse those, but maybe its problematic that they are derived.. This would then be related to #361 . You can find a repository with my attempts here: https://github.com/robamu/va108xx-rs

[duskmoon314]

@daym This feature has been implemented and merged. 😄

[Emilgardis]

Fixed in #592

[Emilgardis]

For your information @duskmoon314 you can auto-close issues with the following syntax: https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

Very useful :D