usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsRe: [USRP-users] [RFNoC] E310 Radio Redo
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é de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users <
usrp-users@lists.ettus.com> a écrit :
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 was
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 work
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
Martin,
After install the Vivado version 2015.4, when I run ./setupenv.sh and
make E310_RFNOC, I received such errors messages.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
./setupenv.sh
Setting up a 64-bit FPGA build environment for the USRP-E3x0...
-Vivado: Found (/opt/Xilinx/Vivado/2015.4/bin)
find: `/opt/mentor/modelsim': No such file or directory
Environment successfully initialized.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
make E310_RFNOC
make -f Makefile.e300.inc bin NAME=E310_RFNOC ARCH=zynq
PART_ID=xc7z020/clg484/-1 RFNOC=1 E310=1 EXTRA_DEFS="RFNOC=1 E310=1"
make[1]: Entering directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
BUILDER: Checking tools...
- GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
- Python 2.7.6
- ERROR: Vivado not found in environment. Please run setupenv.sh
make[1]: *** [.check_tool] Error 1
make[1]: Leaving directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
make: *** [E310_RFNOC] Error 2
It looks like makefile can't find the installed Vivado, but the
setupenv.sh shows the environment successfully initialized.
And I need to and vivado to $PATH myself, so I can compile the fpga code.
Did I miss some other configurations?
Best regards,
Weidong
On 16-02-26 10:49 AM, Martin Braun wrote:
It requires 2015.4, like the rest of rfnoc.
Martin
On 25 Feb 2016 20:14, "Weidong Wang" <wwd_usrp@hotmail.com
mailto: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é de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> a
écrit :
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 was
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 work
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 mailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
That's totally normal if you don't have modelsim.
Best regards,
Marcus
On 02/26/2016 08:14 PM, wwd via USRP-users wrote:
Martin,
After install the Vivado version 2015.4, when I run ./setupenv.sh and
make E310_RFNOC, I received such errors messages.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
./setupenv.sh
Setting up a 64-bit FPGA build environment for the USRP-E3x0...
-Vivado: Found (/opt/Xilinx/Vivado/2015.4/bin)
find: `/opt/mentor/modelsim': No such file or directory
Environment successfully initialized.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
make E310_RFNOC
make -f Makefile.e300.inc bin NAME=E310_RFNOC ARCH=zynq
PART_ID=xc7z020/clg484/-1 RFNOC=1 E310=1 EXTRA_DEFS="RFNOC=1 E310=1"
make[1]: Entering directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
BUILDER: Checking tools...
- GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
- Python 2.7.6
- ERROR: Vivado not found in environment. Please run setupenv.sh
make[1]: *** [.check_tool] Error 1
make[1]: Leaving directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
make: *** [E310_RFNOC] Error 2
It looks like makefile can't find the installed Vivado, but the
setupenv.sh shows the environment successfully initialized.
And I need to and vivado to $PATH myself, so I can compile the fpga code.
Did I miss some other configurations?
Best regards,
Weidong
On 16-02-26 10:49 AM, Martin Braun wrote:
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é de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>>
a écrit :
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 was
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 work
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 mailto: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
Try 'source ./setupenv.sh', otherwise your environment changes won't
persist.
Cheers,
M
On 02/26/2016 11:14 AM, wwd wrote:
Martin,
After install the Vivado version 2015.4, when I run ./setupenv.sh and
make E310_RFNOC, I received such errors messages.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
./setupenv.sh
Setting up a 64-bit FPGA build environment for the USRP-E3x0...
-Vivado: Found (/opt/Xilinx/Vivado/2015.4/bin)
find: `/opt/mentor/modelsim': No such file or directory
Environment successfully initialized.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
make E310_RFNOC
make -f Makefile.e300.inc bin NAME=E310_RFNOC ARCH=zynq
PART_ID=xc7z020/clg484/-1 RFNOC=1 E310=1 EXTRA_DEFS="RFNOC=1 E310=1"
make[1]: Entering directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
BUILDER: Checking tools...
- GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
- Python 2.7.6
- ERROR: Vivado not found in environment. Please run setupenv.sh
make[1]: *** [.check_tool] Error 1
make[1]: Leaving directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
make: *** [E310_RFNOC] Error 2
It looks like makefile can't find the installed Vivado, but the
setupenv.sh shows the environment successfully initialized.
And I need to and vivado to $PATH myself, so I can compile the fpga code.
Did I miss some other configurations?
Best regards,
Weidong
On 16-02-26 10:49 AM, Martin Braun wrote:
It requires 2015.4, like the rest of rfnoc.
Martin
On 25 Feb 2016 20:14, "Weidong Wang"
<mailto:wwd_usrp@hotmail.comwwd_usrp@hotmail.com> wrote:
Hi Martin,
Does it work only with vivado 2015.4 or we can still use 2015.2?
Thanks
Weidong
Envoyé de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> a
écrit :
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 was
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 work
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 mailto:USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Sorry, hit "send" too fast; I wanted to say that not finding
/opt/mentor/modelsim is normal.
You should source the setupenv script, ie. run
. ./setupenv.sh
(notice "dot space dot slash setupenv.sh")
or
source setupenv.sh
Best regards,
Marcus
On 02/26/2016 08:24 PM, Marcus Müller wrote:
That's totally normal if you don't have modelsim.
Best regards,
Marcus
On 02/26/2016 08:14 PM, wwd via USRP-users wrote:
Martin,
After install the Vivado version 2015.4, when I run ./setupenv.sh and
make E310_RFNOC, I received such errors messages.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
./setupenv.sh
Setting up a 64-bit FPGA build environment for the USRP-E3x0...
-Vivado: Found (/opt/Xilinx/Vivado/2015.4/bin)
find: `/opt/mentor/modelsim': No such file or directory
Environment successfully initialized.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
make E310_RFNOC
make -f Makefile.e300.inc bin NAME=E310_RFNOC ARCH=zynq
PART_ID=xc7z020/clg484/-1 RFNOC=1 E310=1 EXTRA_DEFS="RFNOC=1 E310=1"
make[1]: Entering directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
BUILDER: Checking tools...
- GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
- Python 2.7.6
- ERROR: Vivado not found in environment. Please run setupenv.sh
make[1]: *** [.check_tool] Error 1
make[1]: Leaving directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
make: *** [E310_RFNOC] Error 2
It looks like makefile can't find the installed Vivado, but the
setupenv.sh shows the environment successfully initialized.
And I need to and vivado to $PATH myself, so I can compile the fpga code.
Did I miss some other configurations?
Best regards,
Weidong
On 16-02-26 10:49 AM, Martin Braun wrote:
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é de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users
<usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>>
a écrit :
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 was
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 work
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 mailto: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
Thanks, Marcus and Martin.:-)
On 16-02-26 02:31 PM, Marcus Müller via USRP-users wrote:
Sorry, hit "send" too fast; I wanted to say that not finding
/opt/mentor/modelsim is normal.
You should source the setupenv script, ie. run
. ./setupenv.sh
(notice "dot space dot slash setupenv.sh")
or
source setupenv.sh
Best regards,
Marcus
On 02/26/2016 08:24 PM, Marcus Müller wrote:
That's totally normal if you don't have modelsim.
Best regards,
Marcus
On 02/26/2016 08:14 PM, wwd via USRP-users wrote:
Martin,
After install the Vivado version 2015.4, when I run ./setupenv.sh
and make E310_RFNOC, I received such errors messages.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
./setupenv.sh
Setting up a 64-bit FPGA build environment for the USRP-E3x0...
-Vivado: Found (/opt/Xilinx/Vivado/2015.4/bin)
find: `/opt/mentor/modelsim': No such file or directory
Environment successfully initialized.
wwd@wwd-X550LA:~/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300$
make E310_RFNOC
make -f Makefile.e300.inc bin NAME=E310_RFNOC ARCH=zynq
PART_ID=xc7z020/clg484/-1 RFNOC=1 E310=1 EXTRA_DEFS="RFNOC=1 E310=1"
make[1]: Entering directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
BUILDER: Checking tools...
- GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
- Python 2.7.6
- ERROR: Vivado not found in environment. Please run setupenv.sh
make[1]: *** [.check_tool] Error 1
make[1]: Leaving directory
`/home/wwd/Ettus/Rfnoc/pybombs/src/uhd-rfnoc-radio-redo/fpga-src/fpga-rfnoc-radio-redo/usrp3/top/e300'
make: *** [E310_RFNOC] Error 2
It looks like makefile can't find the installed Vivado, but the
setupenv.sh shows the environment successfully initialized.
And I need to and vivado to $PATH myself, so I can compile the fpga
code.
Did I miss some other configurations?
Best regards,
Weidong
On 16-02-26 10:49 AM, Martin Braun wrote:
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é de mon iPad
Le 25 févr. 2016 à 16:16, Martin Braun via USRP-users
<usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com>> a écrit :
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 was
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 work
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 mailto: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
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com