I am checking the IO signatures, and I am seeing that the axi_mm interface generated in rfnoc_image_core.sv is a bit wonky. I traced it back to the io_signature.yaml definition here:
https://github.com/EttusResearch/uhd/blob/0dede88c6535ae6ffb30b162c83dc01d59d3bfa0/host/include/uhd/rfnoc/core/io_signatures.yml#L63 It states that it's up to 512-bit, 8 channels, and 48-bit address - but the m_axi_wdata and m_axi_rdata is 4192 bits. I think it should be 4096 bits (512*8) but really I think this should follow some parameters that are passed into it? Similar to how the radio interface is defined? Alternatively, the x4xx_core.v file seems to utilise the localparam DRAM_PORTS_PER_BANK - could the IO signature just use a generic like that? https://github.com/EttusResearch/uhd/blob/0dede88c6535ae6ffb30b162c83dc01d59d3bfa0/fpga/usrp3/top/x400/x4xx_core.v#L576 Was this just an oversight or is there a plan to "right-size" this interface based on the parameters passed into it? Thanks, Brian
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
