Visible to Intel only — GUID: pbp1734315260803
Ixiasoft
3.3.6.1.1. Machine Status Register (mstatus)
3.3.6.1.2. Machine Trap-Vector Base-Address Register (mtvec)
3.3.6.1.3. Machine Interrupt Register (mip and mie)
3.3.6.1.4. Machine Exception Program Counter Register (mepc)
3.3.6.1.5. Machine Cause Register (mcause)
3.3.6.1.6. Machine Trap Value Register (mtval)
4.3.1. General-Purpose Register File
4.3.2. Shadow Register
4.3.3. Arithmetic Logic Unit
4.3.4. Multipy and Divide Units
4.3.5. Floating-Point Unit
4.3.6. Custom Instruction
4.3.7. Instruction Cycles
4.3.8. Reset and Debug Signals
4.3.9. Control and Status Registers
4.3.10. Trap Controller (CLINT)
4.3.11. Trap Controller (CLIC)
4.3.12. Memory and I/O Organization
4.3.13. RISC-V based Debug Module
4.3.14. Error Correction Code (ECC)
4.3.15. Branch Prediction
4.3.16. Lockstep Module
4.3.10.1.1. Machine Status Register (mstatus)
4.3.10.1.2. Machine Trap-Vector Base-Address Register (mtvec)
4.3.10.1.3. Machine Interrupt Register (mip and mie)
4.3.10.1.4. Machine Exception Program Counter Register (mepc)
4.3.10.1.5. Machine Cause Register (mcause)
4.3.10.1.6. Machine Trap Value Register (mtval)
4.3.10.1.7. Machine Second Trap Value Register (mtval2)
4.3.11.1.3.1. Machine Trap-handler Vector Table base address Register (mtvt)
4.3.11.1.3.2. Machine Next Interrupt Handler Address and Interrupt Enable Register (mnxti)
4.3.11.1.3.3. Machine Interrupt Status Register (mintstatus)
4.3.11.1.3.4. Machine Interrupt-Level Threshold Register (mintthresh)
4.3.11.1.3.5. Machine Scratch Swap for Interrupt-Level Register (mscratchcswl)
Visible to Intel only — GUID: pbp1734315260803
Ixiasoft
4.3.13.5.3. Using Triggers
A debugger can use hardware triggers to halt a hart (or enter Debug Mode) when a certain event occurs. In Nios® V processor, the supported trigger type is address/data match trigger. Thus, the associated events are related to address and data trigger implementation only. When a debugger wants to set a trigger, the debugger writes the desired configuration, and then reads back to see if that configuration is supported.
Name | Address | Description |
---|---|---|
tdata1 | 0x105c | action=1, match=0, m=1, s=1, u=1, execute=1 |
tdata2 | 0x80001234 | address |
Name | Address | Description |
---|---|---|
tdata1 | 0x4159 | timing-1, action=1, match=0, m=1, s=1, u=1, load=1 |
tdata2 | 0x80007f80 | address |
Name | Address | Description |
---|---|---|
tdata1 0 | 0x195a | action=1, chain=1, match=2, m=1, s=1, u=1, store=1 |
tdata2 0 | 0x80007c80 | start address (inclusive) |
tadata1 1 | 0x11da | action=1, match=3, m=1, s=1, u=1, store=1 |
tdata2 1 | 0x80007cf0 | end address (exclusive) |
Name | Address | Description |
---|---|---|
tdata1 | 0x10da | action=1. match=1, m=1, s=1, u=1. store=1 |
tdata2 | 0x81237fff | 16 bits to match exactly, then 0, then all ones |
Name | Address | Description |
---|---|---|
tdata1 0 | 0x41a59 | timing=1, action=1, chain=1, match=4, m=1, s=1. u=1, load=1 |
tdata2 0 | 0xfff03090 | Mask for low half, then match for low half |
tadata1 1 | 0x412d9 | timing=1, action=1, match=5, m=1, s=1, u=1, load=1 |
tdata2 1 | 0xefff8675 | Mask for high half, then match for high half |