Help¶

The Image Vector Table (IVT) provides the boot ROM with pointers to the application entry point and device configuration data. The boot ROM requires a fixed IVT offset for each type of boot device.

Help¶

The Image Vector Table (IVT) provides the boot ROM with pointers to the application entry point and device configuration data. The boot ROM requires a fixed IVT offset for each type of boot device.

Direct dependencies¶

(NXP_IMX_RT_BOOT_HEADER && SOC_SERIES_IMX_RT && SOC_FAMILY_IMX) || (NXP_IMX_RT6XX_BOOT_HEADER && SOC_SERIES_IMX_RT6XX && SOC_FAMILY_IMX)

(Includes any dependencies from ifs and menus.)

Defaults¶

0x1000 if BOOT_FLEXSPI_NOR || BOOT_SEMC_NOR
0x400 if BOOT_FLEXSPI_NAND || BOOT_SEMC_NAND
0x1000

Kconfig definitions¶

At <Zephyr>/soc/arm/nxp_imx/rt/Kconfig.soc:378

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:28 → <Zephyr>/soc/Kconfig:11 → <BuildDir>/Kconfig/Kconfig.soc.arch:2 → <Zephyr>/soc/arm/nxp_imx/Kconfig:14

Menu path: (Top) → Hardware Configuration → Enable the boot header

config IMAGE_VECTOR_TABLE_OFFSET
    hex "Image vector table offset"
    default 0x1000 if BOOT_FLEXSPI_NOR || BOOT_SEMC_NOR
    default 0x400 if BOOT_FLEXSPI_NAND || BOOT_SEMC_NAND
    depends on NXP_IMX_RT_BOOT_HEADER && SOC_SERIES_IMX_RT && SOC_FAMILY_IMX
    help
      The Image Vector Table (IVT) provides the boot ROM with pointers to
      the application entry point and device configuration data. The boot
      ROM requires a fixed IVT offset for each type of boot device.

At <Zephyr>/soc/arm/nxp_imx/rt6xx/Kconfig.soc:92

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:28 → <Zephyr>/soc/Kconfig:11 → <BuildDir>/Kconfig/Kconfig.soc.arch:2 → <Zephyr>/soc/arm/nxp_imx/Kconfig:14

Menu path: (Top) → Hardware Configuration → Enable the boot header

config IMAGE_VECTOR_TABLE_OFFSET
    hex "Image vector table offset"
    default 0x1000
    depends on NXP_IMX_RT6XX_BOOT_HEADER && SOC_SERIES_IMX_RT6XX && SOC_FAMILY_IMX
    help
      The Image Vector Table (IVT) provides the boot ROM with pointers to
      the application entry point and device configuration data. The boot
      ROM requires a fixed IVT offset for each type of boot device.

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