In my noob viewpoint, the advantage of using this component is the possibility of the tool to provide to the designer the ability to have a visual way to assign clocks to other modules through the same avalon interface, avoiding sync errors. Just a guess...
As far as I know, one is used for internal use only within the same design, and the other is used to export clocks among different clock domains. I'm not expert on this, but also learning, so may be wrong.
Assume that you want to run NIOS in the QSYS project. You will need the clock source so that you can assign your own clock.
I did not use clock bridge before, so I don't know about it.
Assume that you want to run NIOS in the QSYS project. You will need the clock source so that you can assign your own clock.
I did not use clock bridge before, so I don't know about it.
So let me make a reflective question: Is there any drawback on using the clock source done with Qsys ? Considering that all the other stuffs are supposedly connected and visualised in graphical mode, don't you agree that making this way turn the project more easy to support/debug ?
It's really a matter of preference.
I really dislike the Qsys's single dimension layout. It becomes too busy and crowded very quickly. Therefore I prefer keeping the number of components to a minimum.
don't you agree that making this way turn the project more easy to support/debug ?
Not really. Unless you require the extra synchronous reset (native to the clock source component) it's just another dial on an already crowded dashboard. Why not export your clock instead ?