04-10-2018 06:39 AM - edited 04-10-2018 06:40 AM
My IP is connected to ARM in zynq. Since it is one to one communication.i think it is not necessary to add axi-interrconnect
why is axi interrconnect included when running connection automation?
is it possible to remove axi interrconnect? Or, what is the advantages of including axi interconnect?
04-10-2018 06:50 AM
@tommhk2002 AXI interconnect is not an actual component. It is just a placeholder where the Vivado automated scripts can insert whatever necessary to make the ends compatible - clock adapters, width adapters, protocol adapters, etc. It will save you tons of manual work. In the simplest case, where it connects one-to-one and no adaptation is required, the AXI interconnect will degenerate to just a shell. You can actually click on the "+" sign and see what's inside. (Hint: do it only AFTER validation - it is during validation that most checks are performed).
04-10-2018 07:07 AM
thanks for reply.
one more question. Master_A run at 500 MHz, and slave_A run only at 100MHz.
Master_A wants to send data to slave_A, since two clk freq are not same.
So, placing an axi-interconnect between Master_A and slave_A is the right solution?
04-10-2018 07:33 AM