RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V mnscratch CSR Register

Address 0x740Privilege MachineAccess RW / MXLEN/XLENReserved, custom, or uncategorized CSRs

RNMI scratch register used by resumable non-maskable interrupt handlers to save and restore context.

Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
VALUE63:0RW
Field Map

Understand mnscratch By Bit Fields

1 key fields
XLEN-1:0

VALUE

RW

MXLEN-bit scratch value held in mnscratch.

VALUE (bits XLEN-1:0) — MXLEN-bit scratch value held in mnscratch.

What This Field Controls

  • - MXLEN-bit scratch value held in mnscratch.

Common Values

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

What To Check First When Reading This CSR

  • - First confirm that the current hart implements mnscratch; unimplemented or insufficiently privileged accesses raise an illegal-instruction exception.
  • - Use address 0x740 and the lowest access privilege (Machine) 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

  • - Preserve bits that are not being changed so reserved or implementation-defined fields are not written with invalid values.
  • - Prefer CSRRS/CSRRC for local set/clear operations to avoid CSRRW overwriting concurrently updated status bits.

Put It Back Into A Real Flow

1

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

2

Modify only the target fields while preserving all other bits.

3

Read back the CSR or validate through later trap, interrupt, or context-switch behavior that the setting took effect.