This section describes the interrupt-related information that flows within NAVSS and how this information is configured or generated.
- Ring Number (R#)
- Data is read from and written to a specific Ring Accelerator ring using direct ring-mode, proxy, or secure proxy accesses
- The Ring Accelerator has specific ring number ranges for specific purposes. The
R# must match the intended purpose of the ring (see RINGACC Ring
Mapping)
- Global Event and Event Numbers (GE# and E#)
- GE# = EO + E#
- EO determines the destination module for the event. The PSILSS will route the
GE# to the destination module per the NAVSS event mapping, removing EO
in the process. The destination module sees only E#. See Global event
Map for details. Examples:
- GE# in the range 0x0000 – 0x1FFF (EO = 0x0000,
E# = 0x0000 – 0x1FFF) would go to NAVSS0_UDMASS_INTR_AGGR0. The
INTR_AGGR sees E#.
- GE# in the range 0x4000 – 0x47FF (EO = 0x4000,
E# = 0x0000 – 0x07FF) would go to MCU_NAVSS0_UDMASS_INTR_AGGR0. The INTR_AGGR sees
E#.
- For the INTR_AGGR module, E# ranges from 0 to (IA_SEVI - 1)
- Virtual Interrupt (VI#)
- The INTR_AGGR maps E# (via software configuration) to any SB#
- SB# ranges from 0 to (IA_SEVI - 1)
- Each VI# (0 – (IA_VINTR-1)) is driven by a group of 64 contiguous SB# numbers (VI# driven by SB#'s VI#×64 – (VI#×64)+63)
- Output Interrupt (OI#)
- The Interrupt Router has a hardwired set of interrupt inputs from various
modules (see NAVSS Interrupt Router Input Mapping). Examples:
- In the NAVSS, 256 interrupt inputs from the
NAVSS0_UDMASS_INTR_AGGR0 are hardwired to interrupt inputs 0 –
255. The VI# is zero-relative to this range.
- In the MCU_NAVSS, 4 event interrupt inputs from
the MCRC0 are hardwired to interrupt inputs 256 – 259. The VI#
is zero-relative to this range.
- Software configures an interrupt input (based on VI# + IR_IBASE ) to an OI#