CSR Bit Fields

RISC-V stimecmph CSR Register

Address 0x15DPrivilege SupervisorAccess RW / RV32 only / 32Supervisor AIA, timer, and indirect interrupt CSRs

stimecmph (0x15D) is the RV32 CSR for the upper 32 bits of the 64-bit stimecmp value.

Field Map

Understand stimecmph By Bit Fields

1 key fields
31:0

STIMECMP_63_32

RW

RV32 access window for stimecmp[63:32].

STIMECMP_63_32 (bits 31:0) — RV32 access window for stimecmp[63:32].

What This Field Controls

  • - RV32 access window for stimecmp[63:32].

Common Values

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

Open Official Manual
Official Basis & Search Notes

stimecmph is used only on RV32 to access stimecmp[63:32]; RV64 accesses the full 64-bit timer-compare state through stimecmp.

Sstc defines stimecmp as a 64-bit register on all RV32 and RV64 systems.
On RV32, stimecmp is the low half and stimecmph is the high half.
Do not treat stimecmph as an independent timer.

What To Check First When Reading This CSR

  • - First confirm that the hart implements the extension containing stimecmph; unimplemented or insufficiently privileged CSR accesses raise an illegal-instruction exception.
  • - Use address 0x15D, the lowest access privilege, and the official access class to decide whether software may access it directly.
  • - Do not assume fixed values for reserved, WPRI, WARL, or WLRL fields; interpret them according to the specification and implementation.

Risk Checks Before Writing

  • - When writing stimecmph, modify only the officially defined target fields and preserve unchanged bits.
  • - Handle WARL, WLRL, WPRI, and reserved fields according to the official specification; do not overwrite the whole CSR as an ordinary integer.

Put It Back Into A Real Flow

1

On RV32, read/write the upper 32 bits of stimecmp.

2

Maintain the full 64-bit compare value together with the low 32 bits in stimecmp.

3

Follow Sstc STIP-update and spurious-interrupt guidance.

FAQ

Is stimecmph used on RV64?

No. It is an RV32-only high-half CSR.