BP
Brian Padalino
Sat, Jun 30, 2018 1:27 PM
Appreciate the feedback. Marcus, we have a project using RFNoC blocks on
the X310 to run this workflow, 2x Rx --> Splitstream for each RX --> DDC
for each split stream out --> FFT Sink. We would like to do the same on the
B210. This was overwhelming our CPU + GPU before we switched to RFNoC on
the X310. We can deal with some latency as long as it is within reason.
If you think there is a way to do this workload on the PC without reducing
bandwidth I can give it a try.
I think what Ian was suggesting is that the whole RFNoC framework isn't
going to just work or be easy to port over to the B200 FPGA framework.
From what it sounds like, you have a very specific flowgraph that doesn't
require any re-configuration with how things are connected to each other.
You specifically setup the signal processing chain to do what you're saying
here.
You should be able to port the "guts" of the signal processing chain to the
B200 without the need for RFNoC, per se. All the communication channels
for getting the data streams to the host should live within UHD.
This is a much more tractable problem than trying to get the entire RFNoC
framework shoved into the B200.
Good luck!
Brian
On Sat, Jun 30, 2018 at 5:05 AM Peter Sanchez via USRP-users <
usrp-users@lists.ettus.com> wrote:
> Appreciate the feedback. Marcus, we have a project using RFNoC blocks on
> the X310 to run this workflow, 2x Rx --> Splitstream for each RX --> DDC
> for each split stream out --> FFT Sink. We would like to do the same on the
> B210. This was overwhelming our CPU + GPU before we switched to RFNoC on
> the X310. We can deal with some latency as long as it is within reason.
>
> If you think there is a way to do this workload on the PC without reducing
> bandwidth I can give it a try.
>
I think what Ian was suggesting is that the whole RFNoC framework isn't
going to just work or be easy to port over to the B200 FPGA framework.
>From what it sounds like, you have a very specific flowgraph that doesn't
require any re-configuration with how things are connected to each other.
You specifically setup the signal processing chain to do what you're saying
here.
You should be able to port the "guts" of the signal processing chain to the
B200 without the need for RFNoC, per se. All the communication channels
for getting the data streams to the host should live within UHD.
This is a much more tractable problem than trying to get the entire RFNoC
framework shoved into the B200.
Good luck!
Brian
MM
Marcus Müller
Sun, Jul 1, 2018 9:05 AM
Hi Peter,
hm, I do agree, this sounds like it would be an absolutely reasonable
thing to do on a X310; the B210's master clock rates are way
significantly lower (especially in dual-RX mode), so my hope is that
the overwhelmingness of having software DDC is gone (or you just don't
care about it and do a massive FFT over the whole max 2× 30.72 MS/s
coming from the B210 at most on your GPU and just throw away stuff),
simply because the B210 isn't as much a beast at delivering baseband
samples as is.
To what do you plan to decimate in your DDCs, and how far in spectrum
would these bands be apart?
Best regards,
Marcus
On Sat, 2018-06-30 at 02:03 -0700, Peter Sanchez wrote:
Appreciate the feedback. Marcus, we have a project using RFNoC blocks
on the X310 to run this workflow, 2x Rx --> Splitstream for each RX
--> DDC for each split stream out --> FFT Sink. We would like to do
the same on the B210. This was overwhelming our CPU + GPU before we
switched to RFNoC on the X310. We can deal with some latency as long
as it is within reason.
If you think there is a way to do this workload on the PC without
reducing bandwidth I can give it a try.
Thanks
On Fri, Jun 29, 2018 at 1:35 AM, Marcus Müller <marcus.mueller@ettus.
com> wrote:
To give an uplifting spin to all this:
Now, also, although larger than the one on the B200, the B210's
FPGA
isn't really large unoccupied, so the amount of logic that you
could
even hypothetically put in there is limited. Why's that uplifiting?
That FPGA was chosen for the board because there's usually little
need
to do anything but the hardware interfacing and the DDC/DUC in the
FPGA. The B210 can, with good USB3 controllers, pretty much
directly
hand through its analog bandwidth to a computer. So, unless you
have a
workload that your PC including GPU and whatnot can't achieve, you
don't even have to think about implementing things on the B210's
FPGA –
and frankly, I've got no idea what'd be easy to do on the free
space of
a B210 but impossible on a high-end PC. And a high-end PC is still
cheaper than a ISE14 license.
Only thing that comes into mind is the latency restrictions you
incur
with USB; that's really something that no amount of computing power
on
the host computer side could solve.
So, maybe, if I can encourage you to discuss your specific
application,
we can find a sensible solution on what to put on the SDR
peripheral
device itself, and what to do on your PC?
Best regards,
Marcus
On Thu, 2018-06-28 at 15:56 -0700, Peter Sanchez via USRP-users
wrote:
There is no conceptual reason why you can’t build an RFNoC
on B210, it uses the same USRP3 base architecture and FPGA
files….HOWEVER…. B210 is implemented with a Spartan6 FPGA and
the implementation work for RFNoC is done using Xilinx’s Vivado
design tools which support only the newer FPGA architectures
Zynq (Artix) and Kintex…Spartan6 users are stuck with ISE14
forever, so in practical terms, no, it’s not possible without
completely recreating all that infrastructure.
-Ian
On Jun 28, 2018, at 1:47 PM, Peter Sanchez via USRP-users
Hi All,
Is it possible to generate RFNoC blocks for the B210? I can't
find a lot of information about it. Can some one show me the
there is a website talking about it?
Hi Peter,
hm, I do agree, this sounds like it would be an absolutely reasonable
thing to do on a X310; the B210's master clock rates are way
significantly lower (especially in dual-RX mode), so my hope is that
the overwhelmingness of having software DDC is gone (or you just don't
care about it and do a massive FFT over the whole max 2× 30.72 MS/s
coming from the B210 at most on your GPU and just throw away stuff),
simply because the B210 isn't as much a beast at delivering baseband
samples as is.
To what do you plan to decimate in your DDCs, and how far in spectrum
would these bands be apart?
Best regards,
Marcus
On Sat, 2018-06-30 at 02:03 -0700, Peter Sanchez wrote:
> Appreciate the feedback. Marcus, we have a project using RFNoC blocks
> on the X310 to run this workflow, 2x Rx --> Splitstream for each RX
> --> DDC for each split stream out --> FFT Sink. We would like to do
> the same on the B210. This was overwhelming our CPU + GPU before we
> switched to RFNoC on the X310. We can deal with some latency as long
> as it is within reason.
>
> If you think there is a way to do this workload on the PC without
> reducing bandwidth I can give it a try.
>
> Thanks
>
> On Fri, Jun 29, 2018 at 1:35 AM, Marcus Müller <marcus.mueller@ettus.
> com> wrote:
> > To give an uplifting spin to all this:
> >
> > Now, also, although larger than the one on the B200, the B210's
> > FPGA
> > isn't really large unoccupied, so the amount of logic that you
> > could
> > even hypothetically put in there is limited. Why's that uplifiting?
> >
> > That FPGA was chosen for the board because there's usually little
> > need
> > to do anything but the hardware interfacing and the DDC/DUC in the
> > FPGA. The B210 can, with good USB3 controllers, pretty much
> > directly
> > hand through its analog bandwidth to a computer. So, unless you
> > have a
> > workload that your PC including GPU and whatnot can't achieve, you
> > don't even have to think about implementing things on the B210's
> > FPGA –
> > and frankly, I've got no idea what'd be easy to do on the free
> > space of
> > a B210 but impossible on a high-end PC. And a high-end PC is still
> > cheaper than a ISE14 license.
> >
> > Only thing that comes into mind is the latency restrictions you
> > incur
> > with USB; that's really something that no amount of computing power
> > on
> > the host computer side could solve.
> >
> > So, maybe, if I can encourage you to discuss your specific
> > application,
> > we can find a sensible solution on what to put on the SDR
> > peripheral
> > device itself, and what to do on your PC?
> >
> > Best regards,
> > Marcus
> >
> > On Thu, 2018-06-28 at 15:56 -0700, Peter Sanchez via USRP-users
> > wrote:
> > > Thank you
> > >
> > > On Thu, Jun 28, 2018 at 2:01 PM, Ian Buckley <ianb@ionconcepts.co
> > m>
> > > wrote:
> > > > There is no conceptual reason why you can’t build an RFNoC
> > design
> > > > on B210, it uses the same USRP3 base architecture and FPGA
> > source
> > > > files….*HOWEVER*…. B210 is implemented with a Spartan6 FPGA and
> > all
> > > > the implementation work for RFNoC is done using Xilinx’s Vivado
> > > > design tools which support only the newer FPGA architectures
> > like
> > > > Zynq (Artix) and Kintex…Spartan6 users are stuck with ISE14
> > > > forever, so in practical terms, no, it’s not possible without
> > you
> > > > completely recreating all that infrastructure.
> > > >
> > > > -Ian
> > > >
> > > > > On Jun 28, 2018, at 1:47 PM, Peter Sanchez via USRP-users
> > <usrp-u
> > > > sers@lists.ettus.com> wrote:
> > > > >
> > > > > Hi All,
> > > > > Is it possible to generate RFNoC blocks for the B210? I can't
> > > > find a lot of information about it. Can some one show me the
> > URL if
> > > > there is a website talking about it?
> > > > >
> > > > > Cheers
> > > > > _______________________________________________
> > > > > USRP-users mailing list
> > > > > USRP-users@lists.ettus.com
> > > > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettu
> > s.co
> > > > m
> > > >
> > >
> > > _______________________________________________
> > > USRP-users mailing list
> > > USRP-users@lists.ettus.com
> > > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.co
> > m
>
>