Help¶

From: https://developer.arm.com/products/architecture/instruction-sets/a32-and-t32-instruction-sets

A32 instructions, known as Arm instructions in pre-Armv8 architectures, are 32 bits wide, and are aligned on 4-byte boundaries. A32 instructions are supported by both A-profile and R-profile architectures.

A32 was traditionally used in applications requiring the highest performance, or for handling hardware exceptions such as interrupts and processor start-up. Much of its functionality was subsumed into T32 with the introduction of Thumb-2 technology.

Direct dependencies¶

!ARM64 && ARM

(Includes any dependencies from ifs and menus.)

Defaults¶

No defaults. Implicitly defaults to n.

Symbols that select this symbol¶

ARMV7_R

Kconfig definition¶

At <Zephyr>/arch/arm/core/aarch32/Kconfig:62

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:29 → <Zephyr>/arch/Kconfig:12 → <Zephyr>/arch/arm/Kconfig:42

Menu path: (Top) → ARM Options

config ISA_ARM
    bool
    depends on !ARM64 && ARM
    help
      From: https://developer.arm.com/products/architecture/instruction-sets/a32-and-t32-instruction-sets

      A32 instructions, known as Arm instructions in pre-Armv8 architectures,
      are 32 bits wide, and are aligned on 4-byte boundaries. A32 instructions
      are supported by both A-profile and R-profile architectures.

      A32 was traditionally used in applications requiring the highest
      performance, or for handling hardware exceptions such as interrupts and
      processor start-up. Much of its functionality was subsumed into T32 with
      the introduction of Thumb-2 technology.

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