Searches titles, sections and text. ↑ ↓ to move, Enter to open, Esc to close. Opens with / or Ctrl+K.

    Contact

    Is this target traceable?

    The processor name is only the first input. Seven feasibility layers from core capability to metric, and the information a review actually needs.

    Published 2026-08-28Last technically reviewed 2026-08-28Evidence basis: Engineering analysis

    A usable configuration requires an implemented trace source, a way to enable it, a route with sufficient bandwidth, a matching program image, attribution of observed execution to the right OS process or task where the analysis needs it, and support for the required metric.

    Feasibility layers

    1. Core capability: which trace architecture and options can the implemented core support?
    2. SoC integration and security: which source, funnel, buffer, formatter and security controls are present, and can they be enabled?
    3. Package, board and sink: which trace pins, serial links or on-chip sinks are exposed and routed?
    4. Transport and bandwidth: can the complete path sustain the workload and protocol configuration?
    5. Executable and mapping: are the executable and compiler mapping available and compatible?
    6. OS, process and task context: can observed execution be attributed to the process or task that ran it? On Linux®, process and task identity may require context-ID configuration, kernel integration or an Accemic patch depending on architecture, kernel version and required analysis - verified per configuration.
    7. Requested metric and product support: is the requested object, source, condition, timing or CFI evidence observable in this configuration, and supported by the product?
    1 · Core trace capability
    1 · Core trace capability
    2 · SoC implementation · security enablement
    2 · SoC implementation · security enablement
    3 · Package and board routing
    3 · Package and board routing
    4 · Trace transport and bandwidth
    4 · Trace transport and bandwidth
    5 · Program image · compiler mapping
    5 · Program image · compiler mapping
    7 · Required metric · product support
    7 · Required metric · product support
    Example failure points
    Example failure points
    core has no trace unit - ask us
    core has no trace unit - ask us
    trace access locked by security state
    trace access locked by security state
    no trace pins routed on the board
    no trace pins routed on the board
    sustained rate above transport budget
    sustained rate above transport budget
    image or mapping does not match the build
    image or mapping does not match the build
    metric not supported for this configuration
    metric not supported for this configurat...
    Ask our experts.
    Ask our experts.
    6 · OS context and process mapping
    6 · OS context and process mapping
    Linux®/ process and task identity: may require context-ID configuration, kernel integration or an Accemic patch depending on architecture, kernel version and required analysis.
    Verified per configuration.
    Linux® / process and task identity: may require context-ID...
    A core name alone does not establish support: every layer of the stack needs a documented answer before a configuration counts as verified.

    Information to send Accemic

    Exact device and package; board and revision; schematic pages or connector details; core and security state; compiler and version; executable/debug format; operating system or RTOS and kernel version where process or task attribution is required; expected clock and workload; required metric; and any restrictions on target configuration or external hardware.

    The feasibility review returns the trace-source assumption, physical path, bandwidth estimate, required hardware and remaining verification steps. Start the review.

    In this context, the following expressions refer to closely related aspects of the same question: target trace feasibility; trace feasibility check; target traceability (in the observation sense, not requirements traceability); trace-port feasibility; “can my target be traced”. This page uses target trace feasibility as the canonical term.

    Related: supported targets · the trace port