I assume the N3xx code used to use the 2x version and it wasn't renamed when it was switched to 4x. Normally the instance name would correspond to the module name.
I'll see if I can reproduce this on an N310. Wade On Mon, Nov 5, 2018 at 1:58 PM Lundberg, Daniel < daniel.lundb...@gtri.gatech.edu> wrote: > Hi Wade, > > Thanks Wade, I’ve been digging around in those files, and I agree that if > it is invoking the 4x64 version it looks like the limit is 1 GB, not 32 > MB. I am somewhat confused by the existence of both a 2x and a 4x > axi_intercon set of files for the N310. In particular, in n3xx_core.v, > there is a line: > > > > axi_intercon_4x64_256_bd_wrapper axi_intercon_2x64_256_bd_i (… > > > > Why isn’t this: > > > > axi_intercon_4x64_256_bd_wrapper axi_intercon_4x64_256_bd_i (… > > > > Thank you, > > Dan > > > > *From:* Wade Fife <wade.f...@ettus.com> > *Sent:* Monday, November 5, 2018 12:26 PM > *To:* Lundberg, Daniel <daniel.lundb...@gtri.gatech.edu> > *Cc:* usrp-users <USRP-users@lists.ettus.com> > *Subject:* Re: [USRP-users] Memory limitations for N310 using replay block > > > > Hi Dan, > > > > You can use the viv_modify_bd command to open the BD file in Vivado then > use the "Address Editor" tab to change how slave ports map to the master > port, which connects to DRAM. For example, after running "setupenv.sh" you > could run "viv_modify_bd ip/axi_intercon_2x64_256_bd/ > axi_intercon_4x64_256_bd.bd N310" to edit the axi_intercon_2x64_256_bd.bd > file. If you're feeling adventurous, then you could also look at the XML > contents of the BD file directly. The relevant tag is "addressSpaces" then > the "addressOffset" and "range" tags, but it's probably safer to let Vivado > make any changes. > > > > However, as far as I can tell, axi_intercon_4x64_256_bd should already be > configured to handle more than 32 MiB. If that's the file you're using > (which is what's normally referenced in n3xx_core.v) then something else > might be going on. But the 2x64 version looks like it's limited to 32 MiB. > > > > Thanks, > > > > Wade > > > > On Fri, Nov 2, 2018 at 5:07 PM Lundberg, Daniel via USRP-users < > usrp-users@lists.ettus.com> wrote: > > I am following the instructions for using the replay block with the N310 ( > https://kb.ettus.com/Using_the_RFNoC_Replay_Block). I have established > that I can replay play a relatively small file (~5 MB) without issues. > However, for much larger files, I get some strange artifacts on the output > (periodic garbage mixed in with the desired data), and I think I am hitting > the memory limitations described in the following note: > > > > *“Note:* The amount of memory available to the Replay block is limited by > the size of the DRAM on the USRP and how the memory interface is configured > on the USRP. For example, the axi_intercon_2x64_128_bd IP used by the > X310 is configured to give each connected device an address space of > 32 MiB. As a result, the Replay block will be limited to this amount of > memory. The axi_intercon_2x64_128_bd file must be modified if more than > 32 MiB needs to be buffered.” > > > > Can someone comment on the hard limitations in the N310? It has 2 GB of > DRAM, but I do not know how much of that is available, and I also do not > know how to interpret the equivalent axi_intercon*** files for the N310. > Also, there are two axi_intercon* files for the N310, > axi_intercon_2x64_256_bd.bd and axi_intercon_4x64_256.bd.bd. Does > someone have an example of how the appropriate file has been modified for > an N310? > > > > Alternatively, can someone suggest an application note or something > similar to get me started on how to modify the memory management of the > USRP? > > > > Thank you, > > Dan > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
