CSR Bit Fields

RISC-V tinfo CSR Register

Address 0x7A4Privilege Machine/DebugAccess RW (writes have no effect) / XLENDebug, trace, and trigger CSRs

tinfo at 0x7A4 reports the trigger types supported by the trigger selected by tselect and the Sdtrig version; it may be absent when no triggers exist, or when type is not writable and version is 0.

Field Map

Understand tinfo By Bit Fields

3 key fields
XLEN-1:24

Reserved

RO zero

Reserved bits that read as zero.

Reserved (bits XLEN-1:24) — Reserved bits that read as zero.

What This Field Controls

  • - Reserved bits that read as zero.

Common Values

This field is better understood together with surrounding context than as a fixed memorized enumeration.

Open Official Manual
23:16

version

RO

Implemented Sdtrig version: 0 denotes the older 2023-02-02 version and 1 denotes the ratified 1.0 version.

version (bits 23:16) — Implemented Sdtrig version: 0 denotes the older 2023-02-02 version and 1 denotes the ratified 1.0 version.

What This Field Controls

  • - Implemented Sdtrig version: 0 denotes the older 2023-02-02 version and 1 denotes the ratified 1.0 version.

Common Values

This field is better understood together with surrounding context than as a fixed memorized enumeration.

Open Official Manual
15:0

info

RO

One bit per tdata1 type number; a set bit means the selected trigger supports that type. It contains 1 when the selected trigger does not exist.

info (bits 15:0) — One bit per tdata1 type number; a set bit means the selected trigger supports that type. It contains 1 when the selected trigger does not exist.

What This Field Controls

  • - One bit per tdata1 type number; a set bit means the selected trigger supports that type. It contains 1 when the selected trigger does not exist.

Common Values

This field is better understood together with surrounding context than as a fixed memorized enumeration.

Open Official Manual

What To Check First When Reading This CSR

  • - First confirm that the current hart implements tinfo; unimplemented or insufficiently privileged accesses raise an illegal-instruction exception.
  • - Use address 0x7A4 and the lowest access privilege (Machine/Debug) to decide whether software may read it directly.
  • - Do not assume fixed values for reserved, WARL, or WLRL bits; interpret the value according to the specification and implementation.

Risk Checks Before Writing

  • - Writes to tinfo have no effect; use its read value to enumerate the capability of the trigger selected by tselect.

Put It Back Into A Real Flow

1

During initialization or the relevant privileged flow, software reads tinfo to observe the current state.

2

Read version and info; if accessing tinfo raises an exception, discover the trigger type through tdata1.type as specified.