-
AXI Switch is not intended for use in IP
integrator (IPI) block diagram designs.
- AXI Switch does not participate in any IP integrator automation or metadata propagation.
- AXI Switch does not inherit information from the IP integrator Address Editor. You must manually configure all address decode ranges by setting its user parameters.
- You must manually select the preferred Performance/Area tradeoff (
STRATEGY) for each IP instance; connecting all SI/MI to AXI4-Lite endpoints does not automatically change the STRATEGY to AREA. - For each SI/MI interface on each AXI Switch IP instance, you must manually configure interface properties for compatibility with connected master/slave endpoints or connected cascaded AXI Switch instances.
- AXI Switch converts all WRAP type bursts into INCR type. AXI Switch SI accepts all protocol-compliant WRAP bursts beginning at any target address, but always converts these bursts to a single INCR burst or a series of single-beat transactions.
-
AXI Switch unconditionally packs all
multi-beat bursts to fill the interface data-width.
AXI Switch slave interfaces (SI) accept narrow bursts, in which the
arsizeorawsizesignal indicates data units which are smaller than the interface data-width. In Performance mode, AXI Switch always propagates narrow bursts fully packed through the master interfaces (MI). The modifiable bit of the AXIarcacheorawcachesignal does not prevent packing.When AXI Switch receives a single-beat transaction (
arlen= 0 orawlen= 0) and thearsizeorawsizesignal indicate a data unit smaller than the data-width of the targeted MI, it preserves the narrow size of the single-beat transaction and propagates to the MI, so that the range of address locations originally specified by the master are not exceeded. - AXI Switch does not support FIXED type bursts. Any FIXED burst transaction received at the AXI Switch SI is regarded as a decode error.
- You cannot use AXI ID signals in the system to identify the master
originating an AXI transaction. Instead, AMD recommends
using the
aruserandawusersignals to convey master identification information as needed. - The AXI Switch core does not support
discontinued AXI3 features.
- Atomic locked transactions: This feature was retracted by the AXI4 protocol. A locked transaction is changed to a non-locked transaction and propagated by the MI.
- Write interleaving: This feature was retracted by AXI4 protocol. AXI3 master devices must be configured as if connected to a slave with a write interleaving depth of one.
- The AXI Switch core does not support exclusive access transactions.
- AXI Switch uses round-robin arbitration on all AXI channels.
-
AXI4 Quality of Service
(
arqosandawqos) signals do not influence arbitration priority. QoS signals are propagated from SI to MI. -
AXI Switch neither propagates nor
generates the AXI4
arregionorawregionsignals. - AXI Switch does not support independent reset domains. If any master or slave device connected to AXI Switch is reset, then all connected devices must be reset concurrently.
- AXI Switch does not propagate the AXI Low power interface (C-channel) signals.
- AXI Switch does not time out if the destination of any AXI channel transfer stalls indefinitely. All connected AXI slaves must respond to all received transactions, as required by AXI protocol.
- AXI Switch provides no address remapping.
- AXI Switch does not include conversion or bridging to non-AXI protocols such as advanced peripheral bus (APB).
- AXI Switch does not support the AXI Coherency Extensions (ACE) protocol nor AMBA AXI5 protocol.