Fix hard coded pin paths at different locations making use of the testbench_top variable #59
+3
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi All,
Needed to add the options[:testbench_top] called also for forced signals in the template/probe.tcl.erb.
I also modified the origen_sim/origen_tester/api.rb, which also has a hard coded 'origen.dut' in the sim_capture function.
So the hard coded path: origen.dut or origen.debug is now removed from the template/probe.tcl
I noticed it is also present at other locations: like in template/empty.svcf (and others), which makes that default setup signals cannot be found, in case a different testbench_top is used (i.o. 'origen') => problem is that this emty.svcf (and others) is not an .erb file, and is not compiled in origen_sim => it would be nice to have that implemented, but I am not sure how.