[USRP-users] Advise on how to modifying HDL design E310 to add custom blocks

Derek Kozel derek.kozel at ettus.com
Tue Oct 3 06:45:37 EDT 2017

Hello Brais,

The HDL design does have a top block and is composed of usefully divided
sub blocks. It is not however designed using the graphical Vivado workflow,
but a source based one. Here is the top block:

Your application however sounds exactly like what the RFNoC architecture
was designed for. This architecture, which the E310 implements, allows you
to add in a self contained block of functional logic wrapped by an
interface supplied by Ettus. I recommend reading this application note and
possibly watching this video which introduces the architecture and leads
through the creation of a sample RFNoC block.


If you only want to add a filter or two there is already an FIR block which
you could either directly make use of or make hopefully minor modifications
to meet your needs.


On Thu, Sep 21, 2017 at 4:48 PM, Brais Ares via USRP-users <
usrp-users at lists.ettus.com> wrote:

> Hello,
> We want to add some blocks to HDL design in E310 device. We followed the
> instructions to build Vivado project and it worked okay.
> Thing is the built design when opened in Vivado looks this way
> <https://www.dropbox.com/s/5w7ari9xlpth4e9/hdl_hierarchy.JPG?dl=0> ...
> where design sources hierarchy is kind of complex. I was expecting a top
> module or at least not that much sources.
> Is there no way to see the design as a block design (like in a typical
> Vivado workflow)?
> Adding just a few filters to this design implies reverse-engineering what
> is going on in most of these source files...
> ​Any advice in how to proceed/start is appreciated.
> Regards,
> Brais.​
> _______________________________________________
> USRP-users mailing list
> USRP-users at lists.ettus.com
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20171003/87bd7532/attachment-0002.html>

More information about the USRP-users mailing list