unconditional is None # Can only have one unconditional assignment per field about peakrdl-regblock HOT 2 OPEN

Hey Zach!
Thanks for submitting this. I agree that the tool should have provided a better error message here. I usually add assertions to trap conditions that shouldn't ever happen regardless of user input. It looks like you were able to stir up a rare edge-case I didn't expect.

Analyzing this a bit more, the specific conflict that is happening is that an unqualified hw=w policy along with singlepulse describes a field that doesn't quite make sense:

• hw=w (or rw in your case) without a load-enable from we = true implies that hardware will update the value of the field's storage element every clock cycle unconditionally.
• singlepulse = true dictates the field will be cleared back to 0 at the next clock cycle, also unconditionally.

This combination of properties is impossible to satisfy, so it results in an error. The SystemRDL spec doesn't explicitly specify all the possible conflicts you could create, likely because there would be far too many to enumerate in a document 😄 .

I'll definitely fix the error message so that it is more informative.
Thanks again for submitting this!

from peakrdl-regblock.