RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V utvec CSR Register

Address N/A (not defined by current standard)Privilege Not defined by the current standardAccess Not applicable / Not defined by the current standardLegacy or draft-compatibility CSRs

The current RISC-V Privileged Architecture Manual removed the user-level-interrupts N extension and defines no CSR interface for this historical name; this page is retained only as a compatibility record.

Related Search Terms
utvec CSRutvec not defined by current standardRISC-V CSR listing
Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
NOT_CURRENTLY_DEFINED63:0Not applicable
Field Map

Understand utvec By Bit Fields

1 key fields
XLEN-1:0

NOT_CURRENTLY_DEFINED

Not applicable

The current privileged-architecture manual defines no field layout for this historical name.

NOT_CURRENTLY_DEFINED (bits XLEN-1:0) — The current privileged-architecture manual defines no field layout for this historical name.

What This Field Controls

  • - The current privileged-architecture manual defines no field layout for this historical name.

Common Values

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

↗Open Official Manual
Official Basis & Search Notes

The current RISC-V Privileged Architecture Manual removed the user-level-interrupts N extension and defines no CSR interface for this historical name; this page is retained only as a compatibility record.

The current manual removed the N extension and defines no CSR interface for this historical name.
The manual describes user-level interrupts as a possibility to be revised if an extension is adopted.
RISC-V Privileged Architecture Manual

What To Check First When Reading This CSR

  • - The current RISC-V Privileged Architecture Manual removed the user-level-interrupts N extension and defines no CSR interface for this historical name; this page is retained only as a compatibility record.

Risk Checks Before Writing

  • - Do not issue a CSR access based on this compatibility record; access to a nonexistent or insufficiently privileged CSR raises an illegal-instruction exception, or a virtual-instruction exception where specified.

Put It Back Into A Real Flow

1

Consult the current CSR allocation tables.

2

Use an interface only after confirming that the target extension specifies it formally.