I started working on the AXI 5 but when it came to implementation i observed that AXI4 and AXI5 are giving the same latency. Whether using VALID-READY or CREDIT based system, what is the advantage of AXI5 credit-based System?? How AXI4 and AXI5 works in multi master and multi slave situation?
It's surprising to expect a direct difference in latency, as the protocol itself and the underlying handshake logic (VALID-READY) in AXI5 haven't been rewritten from scratch to speed up each individual clock cycle—it's still an evolution, not a revolution.
The main advantage of the credit-based system and the innovations in AXI5 in general lies elsewhere: scaling to multi-master/multi-slave topologies. In classic AXI4 with VALID-READY, large interconnects and long communication lines begin to experience horrific frequency drops due to combinatorial delays in the acknowledgement logic, plus the risk of deadlocks and buffer congestion in network bridges (NoCs) increases. The credit-based scheme allows for effective data flow control on the fly without being tied to each clock cycle, eliminating bottlenecks in multi-module systems.
By the way, when designing complex bus architectures and recalculating throughput or latency budgets for such topologies, it's very helpful to have all the calculations and metrics at hand - Lendry300 is especially handy for this, so nothing gets lost during simulations.
In short, don't look at a single transaction cycle in a simple testbench, but at the system's behavior under real-world load in a multi-core environment with crossbars. That's where AXI5 really shines.