Help¶

These define the capacity of the Object Property Table, i.e., the maximum
            number of objects active at any given point, within each object class (e.g.,
            task, queue, semaphore, ...).

            If tasks or other objects are deleted in your system, this
            setting does not limit the total amount of objects created, only the number
            of objects that have been successfully created but not yet deleted.

            Using too small values will cause vTraceError to be called, which stores an
            error message in the trace that is shown when opening the trace file. The
            error message can also be retrieved using xTraceGetLastError.

            It can be wise to start with large values for these constants,
            unless you are very confident on these numbers. Then do a recording and
            check the actual usage by selecting View menu -> Trace Details ->
            Resource Usage -> Object Table.

Direct dependencies¶

PERCEPIO_TRC_RECORDER_MODE_SNAPSHOT && PERCEPIO_TRC_RECORDER_MODE_SNAPSHOT && PERCEPIO_TRACERECORDER

(Includes any dependencies from ifs and menus.)

Default¶

10

Kconfig definition¶

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

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:23 → <Zephyr>/modules/Kconfig:6 → <BuildDir>/kconfig/Kconfig.modules:56

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

config PERCEPIO_RECORDER_TRC_CFG_NQUEUE
    int "Number of Queues"
    range 1 2048
    default 10
    depends on PERCEPIO_TRC_RECORDER_MODE_SNAPSHOT && PERCEPIO_TRC_RECORDER_MODE_SNAPSHOT && PERCEPIO_TRACERECORDER
    help
      These define the capacity of the Object Property Table, i.e., the maximum
                  number of objects active at any given point, within each object class (e.g.,
                  task, queue, semaphore, ...).

                  If tasks or other objects are deleted in your system, this
                  setting does not limit the total amount of objects created, only the number
                  of objects that have been successfully created but not yet deleted.

                  Using too small values will cause vTraceError to be called, which stores an
                  error message in the trace that is shown when opening the trace file. The
                  error message can also be retrieved using xTraceGetLastError.

                  It can be wise to start with large values for these constants,
                  unless you are very confident on these numbers. Then do a recording and
                  check the actual usage by selecting View menu -> Trace Details ->
                  Resource Usage -> Object Table.

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