Forum Discussion
Occasional Contributorwhat's the main concern to set or not set associated clk and reset
The Component Editor knows nothing about the functionality of your custom component. As such, you have to specify the standard interface signal roles of your top-level ports (clock, reset, etc.) and the associated clock and reset for each standard interface (Avalon, AXI).
For the example you mention, it sounds like those signals are making up a conduit instead of a standard interface, confirmed by your screen capture. As such, associated clock and reset are not required for this type of interface. I think you may see warnings if you use the component in a system, but they're just warnings, not errors. You can set associated clock and reset since the Component Editor gives you the option, but I don't think it will cause any issues if you don't.
#iwork4intel
Frequent ContributorHi, Xiaoqiang
The conduit is for you to define the external interface of your IP.
You can add another interface, for example Avalon slave to your IP.
In addition, you can add a clock input and a reset input to your IP. And then you can use them as associated clock and reset. The clock input and reset input here allow you to connect them in the Platform Designer.
Thanks.
Eric
Occasional ContributorHello Eric,
I understand it's ok for standard interface such as Avalon-mm.
But my initial question is for external interface, and I am not sure clk and reset makes sense or not for such interface. Basically it's answered by your colleague. It's not needed.
Anyway, thank you very much for advice!
