CONFIG_PERCEPIO_RECORDER_CFG_STACK_MONITOR_MAX_REPORTS

Stack Monitor Max Reports

Type: int

Help

This defines how many tasks that will be subject to stack usage analysis for
each execution of the Tracealyzer Control task (TzCtrl). Note that the stack
monitoring cycles between the tasks, so this does not affect WHICH tasks that
are monitored, but HOW OFTEN each task stack is analyzed.

This setting can be combined with TRC_CFG_CTRL_TASK_DELAY_MS to tune the
frequency of the stack monitoring. This is motivated since the stack analysis
can take some time to execute.
However, note that the stack analysis runs in a separate task (TzCtrl) that
can be executed on low priority. This way, you can avoid that the stack
analysis disturbs any time-sensitive tasks.

Direct dependencies

TRACING_STACK && PERCEPIO_RECORDER_CFG_STACK_MONITOR && PERCEPIO_TRACERECORDER

(Includes any dependencies from ifs and menus.)

Default

• 1

Kconfig definition

At /home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/debug/TraceRecorder/kernelports/Zephyr/Kconfig:105

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:31 → <Zephyr>/modules/Kconfig:6 → <nRF>/doc/_build/kconfig/Kconfig.modules:80

Menu path: (Top) → Modules → TraceRecorder (/home/runner/work/sdk-nrf/sdk-nrf/ncs/modules/debug/TraceRecorder) → Percepio Trace Recorder → Stack Monitor

config PERCEPIO_RECORDER_CFG_STACK_MONITOR_MAX_REPORTS
    int "Stack Monitor Max Reports"
    range 1 64
    default 1
    depends on TRACING_STACK && PERCEPIO_RECORDER_CFG_STACK_MONITOR && PERCEPIO_TRACERECORDER
    help
      This defines how many tasks that will be subject to stack usage analysis for
      each execution of the Tracealyzer Control task (TzCtrl). Note that the stack
      monitoring cycles between the tasks, so this does not affect WHICH tasks that
      are monitored, but HOW OFTEN each task stack is analyzed.

      This setting can be combined with TRC_CFG_CTRL_TASK_DELAY_MS to tune the
      frequency of the stack monitoring. This is motivated since the stack analysis
      can take some time to execute.
      However, note that the stack analysis runs in a separate task (TzCtrl) that
      can be executed on low priority. This way, you can avoid that the stack
      analysis disturbs any time-sensitive tasks.

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