Xilinx Vivado: Block Design, Address Range of each module end point
Consider a design where the PS (Zynq ARM A9) is connected to multiple peripherals where the addressing is depicted below.
As highlighted in the purple below, why is the minimum accessible of each endpoint module (even if the module is my own IP) always at a range of four kilobytes? Is it related to something ARM processor specific?
I have tried to modify the address range of my own IP as shown below to a smaller number but it never has any effect.
According to notes under Table 3-9: AXI Crossbar Master Interface-Related Parameters in PG059 AXI Interconnect Product Guide, the size of all address range must be a power of 2, determined by 2 ** Mmm_Aaa_ADDR_WIDTH.
Since the master of AXI-Interconnect in your design is probably connected to the AXI4 GP Slave interface of PS system, the Mmm_Aaa_BASE_ADDR is greater than or equal to 12, i.e. the minimum address range that can be assigned to each IP core is at least 4KBytes (4096) as shown in your pictures.
From a design perspective, if you do not run out of memory space to allocate for your IP cores, a bigger range may be better as it reduces the bits needed for comparison in the AXI interconnect, resulting in lower hardware resource consumption, and possibly improved speed (faster achievable AXI clock) and easier placement and routing with timing constraints.
- How to implement HDMI pass-through on XILINX FPGA (Artix-7)
- Petalinux 2021.1 doesn't recognize the machine name for ZCU106
- NEC Infrared Transmission Protocol in C lanc on Xilinx
- Armv7 MMU on the ZYNQ-7000 not starting the virtualization
- Xilinx Vivado 2023 IP block design issue: Unable to connect output of RTL module to AXI GPIO output that is connected to LED
- Where to force xilinx ISE to use block-rams?
- Is CRC Calculation Faster on Xilinx Alveo U280 FPGA Using a Custom Algorithm or a Lookup Table?
- How to implement pipelined floating point accumulation in II=1 in Vitis/Vivado HLS?
- Timing simulation in Vivado giving an error
- Is it possible to tie ports high always high outside of top module?
- How to fix [Common 17-1293] error in Xilinx Vivado?
- How to initialize contents of inferred Block RAM (BRAM) in Verilog
- Implementing hardware that divides an 8 bit number by 3 (11) in binary
- Can SYSCLK be included in FPGA Xilinx vivado testbenches?
- Isim not running
- how to add python in xilinx vitis
- Timing closure problems in FIFO
- Xilinx Vivado schematic for if else statements
- difference between Xilinx solarflare scaleout onlod, solarflare onload, and solarflare TCPDirect?
- Inferring a True Dual Port RAM (Xilinx and Intel compatible) in Verilog
- 'case item is unreachable' in Vivado synthesis process
- Why does the Inferred Latch error occur during the synthesis process?
- What is the granularity of the AXI-ACE protocol?
- Restricting Verilog parameters
- Vitis HLS Pointer to Pointer is not supported for variable when initializing struct array
- Vitis PetaLinux build cant fetch required files while building an application project
- Address of a struct used to set MSI Base address, how does it work? (in Xilinx PCIe RC driver)
- How To Convert .bit file to .bin
- of_node_name_eq for device tree node label
- using xilinx cores in modelsim via .do file