Files
rt-thread/libcpu/arm/cortex-m4
hanzhijian e2e6245aac [arm][cortex-m4] Add hardware stack guard support
Enable RT_USING_HW_STACK_GUARD on Cortex-M4, which was previously only
available on Cortex-M7 and Cortex-M33.

Core porting (libcpu/arm/cortex-m4/):
- Add mpu.c/mpu.h/mputype.h aligned with the Cortex-M7 MPU layer. The only
  difference is the default memory type attribute: Cortex-M4 has no L1 cache,
  so the cacheability bits are reduced to three cases.
- Add rt_hw_stack_guard_init() to cpuport.c.
- Add missing #include <rtconfig.h> to context_gcc.S and invoke
  rt_hw_mpu_table_switch() in the PendSV context switch path.
- Update SConscript to exclude mpu.c when memory protection is disabled.

BSP reference (bsp/stm32/stm32f407-fk407m2-zgt6/):
- board.h: include rtthread.h and define NUM_STATIC_REGIONS.
- board.c: define static_regions[] marking the Flash region read-only,
  guarded by RT_USING_MEM_PROTECTION so it is not enabled by default.
2026-08-26 10:37:02 +08:00
..
…

Independent Interrupts Management

Introduction

Calling rt_hw_interrupt_disable in multiple places on rt-thread may cause interruption delays when the application requires accurate interrupt responses. This is because the system cannot generate any interrupts except abnormal interrupts after disabling interrupts. This is a common problem in the interrupt management of the operating system. The independent interrupt management module is designed to solve this problem.

The independent interrupt management module is designed to solve the problem of interrupt delays caused by calling rt_hw_interrupt_disable in multiple places on rt-thread. The module is implemented by rewrite the rt_hw_interrupt_disable and rt_hw_interrupt_enable functions in the libcpu library.

Usage

  • Add the following code to the project's board.c file.
#ifdef RT_USING_INDEPENDENT_INTERRUPT_MANAGEMENT
#define RT_NVIC_PRO_BITS    __NVIC_PRIO_BITS

rt_base_t rt_hw_interrupt_disable(void)
{
    rt_base_t level = __get_BASEPRI();
    __set_BASEPRI(RT_MAX_SYSCALL_INTERRUPT_PRIORITY << (8 - RT_NVIC_PRO_BITS));

    __ISB();
    __DSB();

    return level;
}

void rt_hw_interrupt_enable(rt_base_t level)
{
    __set_BASEPRI(level);
}

#endif /* RT_USING_INDEPENDENT_INTERRUPT_MANAGEMENT */
  • Add the following configuration to the Kconfig file in the board directory.
    menuconfig RT_USING_INDEPENDENT_INTERRUPT_MANAGEMENT
        bool "Enable independent interrupt management"
        default n

        if RT_USING_INDEPENDENT_INTERRUPT_MANAGEMENT
            config RT_MAX_SYSCALL_INTERRUPT_PRIORITY
                int "Set max syscall interrupt priority"
                range 0 7
                default 2
        endif
  • Select RT_USING_INDEPENDENT_INTERRUPT_MANAGEMENT to enable this feature.
  • Select RT_MAX_SYSCALL_INTERRUPT_PRIORITY to set the maximum priority of the interrupt that can be called by the system call. The default value is 2.

Description

  • The basepri register is used in the functions to complete the interrupt management.
  • For example, if RT_MAX_SYSCALL_INTERRUPT_PRIORITY is set to 0x01, the system masking only interrupts with a priority of 0x01-0xFF.
  • Interrupts with a priority of 0 are not managed by the system and can continue to respond to interrupts after rt_hw_interrupt_disable is called.
  • When using the basepri register for independent interrupt management, note that interrupts with a priority value lower than RT_MAX_SYSCALL_INTERRUPT_PRIORITY cannot call any system API.