RVOPcode
Back To CSR WorkbenchView In Register Browser
CSR Bit Fields

RISC-V mscratchcswl CSR Register

Address 0x349Privilege MachineAccess Historical CLIC v0.10 draft only (not current standard) / Not defined by the current standardLegacy CLIC draft CSRs

mscratchcswl was the Conditional Scratch Swap on Interrupt-Level Change CSR in the CLIC v0.10 draft at historical address 0x349; current ACLIC v0.19 and the privileged CSR table no longer define that name.

Related Search Terms
mscratchcswl CSRmscratchcswl 0x349mscratchcswl CLIC v0.10mscratchcswl draftACLIC v0.19
Bit Overview
bit 3 = only bit 3; bits 12..11 = bits 12 down to 11
MSBLSB
Field Map

Understand mscratchcswl By Bit Fields

0 key fields
Official Basis & Search Notes

mscratchcswl belongs only to the historical official CLIC v0.10 draft. ACLIC v0.19 no longer defines the name, so this page provides no current-standard fields or access semantics.

CLIC v0.10 lists mscratchcswl at 0x349.
ACLIC v0.19 removes mscratchcswl and assigns 0x349 to the Smcsps mspcs CSR; current software must not interpret that address using the old draft.
The current privileged CSR table does not allocate the name; this page does not present old draft behavior as a current standard.
RISC-V Core-Local Interrupt Controller (CLIC) draft v0.10RISC-V Advanced Core-Local Interrupt Controller (ACLIC) draft v0.19RISC-V Privileged Architecture Manual: CSR Listing (2026-07-09 release)

What To Check First When Reading This CSR

  • - ACLIC v0.19 removes mscratchcswl and assigns 0x349 to the Smcsps mspcs CSR; current software must not interpret that address using the old draft.
  • - 0x349 is only the historical draft address of mscratchcswl in CLIC v0.10.
  • - Check the published extension version implemented by the target; do not infer a current CSR from this old name.

Risk Checks Before Writing

  • - Do not access this old draft CSR in portable code targeting current standards.
  • - The same historical address may have a different meaning in a newer A-CLIC draft; verify the implemented version before access.

Put It Back Into A Real Flow

1

Confirm that the reference explicitly targets CLIC v0.10.

2

Check the historical address and the newer A-CLIC definition of that address.

3

For a current target, use only the extension and CSR set that the implementation declares.

FAQ

Is mscratchcswl a current standard CSR?

No. It appears in the CLIC v0.10 draft, but ACLIC v0.19 and the current privileged CSR table no longer define the name.