CONFIG_GEN_IRQ_VECTOR_TABLE

Generate an interrupt vector table

Type: bool

Help

This option controls whether a platform using gen_isr_tables
needs an interrupt vector table created. Only disable this if the
platform does not use a vector table at all, or requires the vector
table to be in a format that is not an array of function pointers
indexed by IRQ line. In the latter case, the vector table must be
supplied by the application or architecture code.

Direct dependencies

SOC_ESP32C3 || SOC_ESP32S2 || SOC_ESP32C3 || SOC_ESP32S2 || (CPU_AARCH32_CORTEX_A && ARM) || (CPU_CORTEX_R && ARM) || ((CPU_CORTEX_A || CPU_AARCH64_CORTEX_R) && ARM64) || NIOS2 || RISCV || SPARC || GEN_ISR_TABLES

(Includes any dependencies from ifs and menus.)

Defaults

  • n

  • n

  • n

  • n

  • n

  • n

  • n

  • n

  • n

  • n

  • y

Kconfig definitions

At <Zephyr>/soc/riscv/esp32c3/Kconfig.defconfig:20

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:25<nRF>/doc/_build/kconfig/Kconfig.soc.defconfig:1

Menu path: (Top)

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on SOC_ESP32C3

At <Zephyr>/soc/xtensa/esp32s2/Kconfig.defconfig:14

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:25<nRF>/doc/_build/kconfig/Kconfig.soc.defconfig:1

Menu path: (Top)

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on SOC_ESP32S2

At <Zephyr>/soc/riscv/esp32c3/Kconfig.defconfig:20

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:27

Menu path: (Top)

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on SOC_ESP32C3

At <Zephyr>/soc/xtensa/esp32s2/Kconfig.defconfig:14

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:27

Menu path: (Top)

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on SOC_ESP32S2

At <Zephyr>/arch/arm/core/aarch32/cortex_a_r/Kconfig:61

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12<Zephyr>/arch/arm/Kconfig:65<Zephyr>/arch/arm/core/aarch32/Kconfig:306

Menu path: (Top) → ARM Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on CPU_AARCH32_CORTEX_A && ARM

At <Zephyr>/arch/arm/core/aarch32/cortex_a_r/Kconfig:145

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12<Zephyr>/arch/arm/Kconfig:65<Zephyr>/arch/arm/core/aarch32/Kconfig:306

Menu path: (Top) → ARM Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on CPU_CORTEX_R && ARM

At <Zephyr>/arch/arm64/core/Kconfig:151

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12<Zephyr>/arch/arm64/Kconfig:32

Menu path: (Top) → ARM64 Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on (CPU_CORTEX_A || CPU_AARCH64_CORTEX_R) && ARM64

At <Zephyr>/arch/nios2/Kconfig:28

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12

Menu path: (Top) → Nios II Options → Nios II Family Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on NIOS2

At <Zephyr>/arch/riscv/Kconfig:128

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12

Menu path: (Top) → RISCV Options → RISCV Processor Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on RISCV

At <Zephyr>/arch/sparc/Kconfig:19

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39<Zephyr>/arch/Kconfig:12

Menu path: (Top) → SPARC Options

config GEN_IRQ_VECTOR_TABLE
    bool
    default n
    depends on SPARC

At <Zephyr>/arch/Kconfig:381

Included via <Zephyr>/Kconfig:8<Zephyr>/Kconfig.zephyr:39

Menu path: (Top) → General Architecture Options → Interrupt Configuration → Use generated IRQ tables

config GEN_IRQ_VECTOR_TABLE
    bool "Generate an interrupt vector table"
    default y
    depends on GEN_ISR_TABLES
    help
      This option controls whether a platform using gen_isr_tables
      needs an interrupt vector table created. Only disable this if the
      platform does not use a vector table at all, or requires the vector
      table to be in a format that is not an array of function pointers
      indexed by IRQ line. In the latter case, the vector table must be
      supplied by the application or architecture code.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)