Inconsistent tval validity conditions

[j0106223]

In Table 4, Instruction interface signals states that tval is ignored unless itype = 1.
However, on page 19 it is stated as follows, which shows inconsistent tval validity conditions:

The information presented in a block represents a contiguous sequence of instructions starting at iaddr, all of which retired in the same cycle. Note that if itype is 1 or 2 (indicating an exception or an interrupt), the number of instructions retired may be zero. cause and tval are only defined if itype is 1 or 2. If iretire = 0 and itype = 0, the values of all other signals are undefined.

[j0106223]

BTW, there is a typo in 4.1.2 Relationship between RISC-V core and the encoder.
In the following sentence:

Implement a separate instance of the interface per hart. Each instance can be connected to a
separate encoder instance, allowing all harts to be traced concurrently. Alternatively, external
muxing may be used in conjunction with a single encoder in order to trace one particular hart at a time;

The last semicolon should be replaced with a period.

[IainCRobertson]

Jack, Thanks for pointing this out - I'll leave this open and fix as part of the next update. cause is valid if itype is 1 or 2, but tval only when itype is 1. Iain From: JACK-YEH ***@***.***> Sent: 12 August 2025 04:37 To: riscv-non-isa/riscv-trace-spec ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [riscv-non-isa/riscv-trace-spec] Inconsistent tval validity conditions (Issue #250) [https://avatars.githubusercontent.com/u/48269434?s=20&v=4]j0106223 left a comment (riscv-non-isa/riscv-trace-spec#250)<#250 (comment)> BTW, there is a typo in 4.1.2 Relationship between RISC-V core and the encoder. In the following sentence: Implement a separate instance of the interface per hart. Each instance can be connected to a separate encoder instance, allowing all harts to be traced concurrently. Alternatively, external muxing may be used in conjunction with a single encoder in order to trace one particular hart at a time; The last semicolon should be replaced with a period. - Reply to this email directly, view it on GitHub<#250 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALQOPSQ2CIN2RIX6JSVXNM33NFOPLAVCNFSM6AAAAACDVETA7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZXGU4DENJTGA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>