[prev in list] [next in list] [prev in thread] [next in thread]
List: usrp-users
Subject: Re: [USRP-users] [RFNoC] E310 Radio Redo
From: Martin Braun via USRP-users <usrp-users () lists ! ettus ! com>
Date: 2016-02-26 15:49:22
Message-ID: CAFOi1A4BRzEVairGrerBUWnRHO39jTOfqA6sY3=+BcUmLDmskw () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
It requires 2015.4, like the rest of rfnoc.
Martin
On 25 Feb 2016 20:14, "Weidong Wang" <wwd_usrp@hotmail.com> wrote:
> Hi Martin,
> Does it work only with vivado 2015.4 or we can still use 2015.2?
> Thanks
> Weidong
>
> Envoy=C3=A9 de mon iPad
>
> > Le 25 f=C3=A9vr. 2016 =C3=A0 16:16, Martin Braun via USRP-users <
> usrp-users@lists.ettus.com> a =C3=A9crit :
> >
> > We recently published a new branch for RFNoC on our uhd and fpga
> > repositories:
> >
> > https://github.com/EttusResearch/uhd/tree/rfnoc-radio-redo
> > https://github.com/EttusResearch/fpga/tree/rfnoc-radio-redo
> >
> > The name implies what we've been working on: 'Radio Redo' is our
> > redesign of the radio blocks, making them behave exactly like any other
> > block. More importantly, we are splitting up functionality into what wa=
s
> > previously all folded into the radio. The DSP components (DDC, DUC,
> > CORDIC) are now removed from the radio block, thus freeing up a lot of
> > FPGA resources on the E310. For RFNoC developers, this means more space
> > for custom blocks.
> >
> > Note we're releasing this code in the middle of a development cycle, to
> > make sure everyone gets access to this, and can see where we're going
> > with RFNoC. Because this is an early-access branch, a few caveats apply=
:
> >
> > - X300 support is not yet included. Once X300 is working, we will
> > actually fold this branch back into rfnoc-devel and remove it again.
> > Note that the X310 has plenty of space for RFNoC blocks even without
> > this change, so if that's your primary platform, simply continue to wor=
k
> > off of rfnoc-devel.
> > - We're not providing pre-built images for this branch right now. You
> > can build E310 images off of the fpga branch (listed above), and pick
> > the RFNoC blocks you want to test out.
> > - We're trying our best to keep APIs locked down, but there are still
> > chances of API changes.
> >
> > Thanks, everyone, for using and running RFNoC, and I hope this will be
> > useful to people out there!
> >
> > Cheers,
> > Martin
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > USRP-users@lists.ettus.com
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
[Attachment #5 (text/html)]
<p dir="ltr">It requires 2015.4, like the rest of rfnoc.</p>
<p dir="ltr">Martin </p>
<div class="gmail_quote">On 25 Feb 2016 20:14, "Weidong Wang" <<a \
href="mailto:wwd_usrp@hotmail.com">wwd_usrp@hotmail.com</a>> wrote:<br \
type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Martin,<br> Does it work only \
with vivado 2015.4 or we can still use 2015.2?<br> Thanks<br>
Weidong<br>
<br>
Envoyé de mon iPad<br>
<br>
> Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users <<a \
href="mailto:usrp-users@lists.ettus.com">usrp-users@lists.ettus.com</a>> a écrit \
:<br> ><br>
> We recently published a new branch for RFNoC on our uhd and fpga<br>
> repositories:<br>
><br>
> <a href="https://github.com/EttusResearch/uhd/tree/rfnoc-radio-redo" \
rel="noreferrer" target="_blank">https://github.com/EttusResearch/uhd/tree/rfnoc-radio-redo</a><br>
> <a href="https://github.com/EttusResearch/fpga/tree/rfnoc-radio-redo" \
rel="noreferrer" target="_blank">https://github.com/EttusResearch/fpga/tree/rfnoc-radio-redo</a><br>
><br>
> The name implies what we've been working on: 'Radio Redo' is our<br>
> redesign of the radio blocks, making them behave exactly like any other<br>
> block. More importantly, we are splitting up functionality into what was<br>
> previously all folded into the radio. The DSP components (DDC, DUC,<br>
> CORDIC) are now removed from the radio block, thus freeing up a lot of<br>
> FPGA resources on the E310. For RFNoC developers, this means more space<br>
> for custom blocks.<br>
><br>
> Note we're releasing this code in the middle of a development cycle, to<br>
> make sure everyone gets access to this, and can see where we're going<br>
> with RFNoC. Because this is an early-access branch, a few caveats apply:<br>
><br>
> - X300 support is not yet included. Once X300 is working, we will<br>
> actually fold this branch back into rfnoc-devel and remove it again.<br>
> Note that the X310 has plenty of space for RFNoC blocks even without<br>
> this change, so if that's your primary platform, simply continue to work<br>
> off of rfnoc-devel.<br>
> - We're not providing pre-built images for this branch right now. You<br>
> can build E310 images off of the fpga branch (listed above), and pick<br>
> the RFNoC blocks you want to test out.<br>
> - We're trying our best to keep APIs locked down, but there are still<br>
> chances of API changes.<br>
><br>
> Thanks, everyone, for using and running RFNoC, and I hope this will be<br>
> useful to people out there!<br>
><br>
> Cheers,<br>
> Martin<br>
><br>
><br>
> _______________________________________________<br>
> USRP-users mailing list<br>
> <a href="mailto:USRP-users@lists.ettus.com">USRP-users@lists.ettus.com</a><br>
> <a href="http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com" \
rel="noreferrer" target="_blank">http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com</a><br>
</blockquote></div>
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic