Fixed input clock/reset port name inference during stitching #347
+2
−2
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.
When stitching, the BD global clock/reset input ports are produced by making external the clock/reset of the first IP in the dataflow. The stitching logic assumed that the name of those clock/reset signals on the first ip is ap_clk/ap_rst_n and if this is not the case, the stitching fails.
The fix utilizes the known port names to infer the correct BD global clock/reset names after making the ports external.