ContributorYes, so as I said, why don't you just tap the right hand side signals?
Super ContributorI don't understand. You can tap the exact signals that are in your struct, so why is it still an issue that you can't tap the struct itself? The signals are physical. The struct is for organizing in the code with no specific relation to the hardware.
If you go into the Technology Map Viewer, I will bet you will not see the struct names there either, further confirming they are not physical. Signal Tap can only tap actual signals.
Contributor"why is it still an issue that you can't tap the struct itself" - I don't know why... this is why I'm asking
Here is a simple example - the struct named 'ab' could not be seen/tapped in the 'top' hierarchy by SignalTap (only signals i0 and i1 could be tapped/seen):
//////////////////////////////////////////////////////////////////////////////////////////////////// package pkg; typedef struct packed { logic a; logic b; } ab_s; endpackage //////////////////////////////////////////////////////////////////////////////////////////////////// module top import pkg::*; ( input i0, input i1 ); ab_s ab; assign ab.a = i0; assign ab.b = i1; sub sub_i ( .ab (ab), .out() ); endmodule //////////////////////////////////////////////////////////////////////////////////////////////////// module sub import pkg::*; ( input ab_s ab, output logic out ); assign out = ab.a^ab.b; endmodule
But inside of the 'sub' hierarchy, the signals ab.a and ab.b could be tapped/seen by the SignalTap.
