Clarifying naming of interrupt vectors on new AVR MCUs about atdf2svd HOT 5 CLOSED

Additional informations in #15

from atdf2svd.

What about naming the fields "module-instance_name", iff module-instance is available? As far as I've seen now (attiny412.atdf and AVR128DA28.atdf), the module-instance only shows up in the interrupt map.

from atdf2svd.

Yeah, this is what I was thinking as well. Though we need to check whether this regresses any of the "old" ATDF files. It might also be worth it to look at the C headers, how they name interrupts on the newer MCUs.

from atdf2svd.

iotn412.h - Header of attiny412:

/* ========== Interrupt Vector Definitions ========== */
/* Vector 0 is the reset vector */

/* CRCSCAN interrupt vectors */
#define CRCSCAN_NMI_vect_num  1
#define CRCSCAN_NMI_vect      _VECTOR(1)  /*  */

/* BOD interrupt vectors */
#define BOD_VLM_vect_num  2
#define BOD_VLM_vect      _VECTOR(2)  /*  */

/* PORTA interrupt vectors */
#define PORTA_PORT_vect_num  3
#define PORTA_PORT_vect      _VECTOR(3)  /*  */

/* RTC interrupt vectors */
#define RTC_CNT_vect_num  6
#define RTC_CNT_vect      _VECTOR(6)  /*  */
#define RTC_PIT_vect_num  7
#define RTC_PIT_vect      _VECTOR(7)  /*  */
...

This are all AVR targets containing the module-instance keyword:

• ATmega1608
• ATmega1609
• ATmega3208
• ATmega3209
• ATmega4808
• ATmega4809
• ATmega808
• ATmega809
• ATtiny827
• ATtiny826
• ATtiny824
• ATtiny817
• ATtiny816
• ATtiny814
• ATtiny807
• ATtiny806
• ATtiny804
• ATtiny427
• ATtiny426
• ATtiny424
• ATtiny417
• ATtiny416
• ATtiny414
• ATtiny412
• ATtiny406
• ATtiny404
• ATtiny402
• ATtiny3217
• ATtiny3216
• ATtiny214
• ATtiny212
• ATtiny204
• ATtiny202
• ATtiny1627
• ATtiny1626
• ATtiny1624
• ATtiny1617
• ATtiny1616
• ATtiny1614
• ATtiny1607
• ATtiny1606
• ATtiny1604
• ATtiny416auto
• AVR32DA28
• AVR32DA32
• AVR32DA48
• AVR32DB28
• AVR32DB32
• AVR32DB48
• AVR64DA28
• AVR64DA32
• AVR64DA48
• AVR64DA64
• AVR64DB28
• AVR64DB32
• AVR64DB48
• AVR64DB64
• AVR128DA28
• AVR128DA32
• AVR128DA48
• AVR128DA64
• AVR128DB28
• AVR128DB32
• AVR128DB48
• AVR128DB64

(From the atdf's in Microchip ATautomotive Series Device Support (2.1.39), Microchip ATmega Series Device Support (2.2.108),
Microchip ATtiny Series Device Support (2.5.116), Microchip AVR-Dx Series Device Support (1.6.88))

from atdf2svd.

Okay, that does not seem to include any of the "old" chips which I was worried about ... And the C header does look like it is doing the same thing you proposed so I think this is the way to go!

from atdf2svd.