:orphan:

.. title:: CONFIG_RUNTIME_NMI

.. kconfig:: CONFIG_RUNTIME_NMI

CONFIG_RUNTIME_NMI
##################

*Attach an NMI handler at runtime*

Type: ``bool``

Help
====

.. code-block:: none

    The kernel provides a simple NMI handler that simply hangs in a tight
    loop if triggered. This fills the requirement that there must be an
    NMI handler installed when the CPU boots. If a custom handler is
    needed, enable this option and attach it via _NmiHandlerSet().

Direct dependencies
===================

\ :kconfig:`ARM <CONFIG_ARM>` || (\ :kconfig:`CPU_CORTEX_R <CONFIG_CPU_CORTEX_R>` && \ :kconfig:`ARM <CONFIG_ARM>`)

*(Includes any dependencies from ifs and menus.)*

Default
=======

- y

Symbols selected by this symbol
===============================

- \ :kconfig:`REBOOT <CONFIG_REBOOT>`

Kconfig definitions
===================



At ``<Zephyr Architecture>/arm/core/aarch32/Kconfig:125``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39`` → ``<Zephyr Architecture>/Kconfig:12`` → ``<Zephyr Architecture>/arm/Kconfig:57``

Menu path: (Top) → ARM Options

.. code-block:: kconfig

    config RUNTIME_NMI
    	bool "Attach an NMI handler at runtime"
    	select REBOOT
    	depends on ARM
    	help
    	  The kernel provides a simple NMI handler that simply hangs in a tight
    	  loop if triggered. This fills the requirement that there must be an
    	  NMI handler installed when the CPU boots. If a custom handler is
    	  needed, enable this option and attach it via _NmiHandlerSet().

----

At ``<Zephyr Architecture>/arm/core/aarch32/cortex_a_r/Kconfig:87``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:39`` → ``<Zephyr Architecture>/Kconfig:12`` → ``<Zephyr Architecture>/arm/Kconfig:57`` → ``<Zephyr Architecture>/arm/core/aarch32/Kconfig:295``

Menu path: (Top) → ARM Options

.. code-block:: kconfig

    config RUNTIME_NMI
    	bool
    	default y
    	depends on CPU_CORTEX_R && ARM

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*