Ondrej Ille

Current state: 1. [x] Merging of two different top hierarchies 2. [ ] Per-file merging mode 3. [x] Folding of coverage with different hierarchy, but the same entity.

Hi @sean-anderson-seco, thanks for hints :) Basically everything you said is correct. I was thinking about implementing this when I was doing first coverage implementation. I did some "research" about...

Yup, thanks, understood. I like the idea of emulating FSM transition tracking by PSL sequences. One thing that would need to be taken care of, is then filtering of the...

Thinking about this again, I think emitting extra process as described above is too complex. Simpler way to achieve the same is to use callback on the FSM state signal....

I'am trying to give a shot at implementing this. To handle enums with arbitrary number of literals, I need to either emit multiple cover tags to track single FSM, or...

> I would rather keep it as a flat array. If we want to solve the #564, we need to be able to insert a tag into the middle of...

OK, I see now that you changed the tag array not to be flat accross the whole design, but only across the current cover scope in: https://github.com/nickg/nvc/commit/1ad3f895f838d9175bb69e188a972be03877bac9#diff-78cc7c5d81397a35561b50dc95f435b72092b6912067aa78e4fcb2ae4178cf77 Was the intention...

OK, I see. Anyway, it helps also with the merging/inserting. If the tag from second `.covdb` does not exist in first one, we simply locate a most suitable scope (that...

@sean-anderson-seco I have implemented the basic FSM coverage, @nickg just merged it. It only tracks FSM state coverage, and NVC considers signals of all user defined enums as FSMs. I...

Hello @sean-anderson-seco , do you think it is OK to close this issue, or would you like to keep it open as a TODO for the transition coverage?