You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HDBeditor correctly creates external ports for custom FUs that are present in tta0.vhdl but the testbench (proch_arch.vhdl) has no instantiation of those ports so they have to be added manually. To access the ports globally, also the testbench.vhdl has to be corrected accordingly.
The text was updated successfully, but these errors were encountered:
Hi,
Yep, you seem to be correct. Would be a nice feature to have the external ports to propagate also through to the testbench, and probably not too difficult to implement. Unfortunately, I don't have time to look into it closer right now, but this should eventually be corrected.
There's also the question what to do with those external ports in the end. I guess propagating to the top-most level of the testbench would be the minimal thing, and then let the RTL compilation fail if the user doesn't map any signals into them. After all, implementing the testing for external signals is left for the user to manage. Sometimes the user could want to map them outside of the testbench or alternatively instantiate their own testbench component inside the autogenerated one.
HDBeditor correctly creates external ports for custom FUs that are present in tta0.vhdl but the testbench (proch_arch.vhdl) has no instantiation of those ports so they have to be added manually. To access the ports globally, also the testbench.vhdl has to be corrected accordingly.
The text was updated successfully, but these errors were encountered: