Hi, 
Guest
Pic
Sign In

usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

setting up gr-fosphor on uhd 4

IZ
Ivan Zahartchuk
Sun, Feb 14, 2021 3:36 PM

Hello. I want to create a graph to run gr-fosphor for usrp e310 but I
haven't found any examples or at least uhd_image_builder.py to build
firmware. Tell me if this is possible and what resources you can look at in
this direction.

Hello. I want to create a graph to run gr-fosphor for usrp e310 but I haven't found any examples or at least uhd_image_builder.py to build firmware. Tell me if this is possible and what resources you can look at in this direction.
AR
Aaron Rossetto
Mon, Feb 15, 2021 2:07 PM

On Sun, Feb 14, 2021 at 9:37 AM Ivan Zahartchuk via USRP-users <
usrp-users@lists.ettus.com> wrote:

Hello. I want to create a graph to run gr-fosphor for usrp e310 but I

haven't found any examples or at least uhd_image_builder.py to build
firmware. Tell me if this is possible and what resources you can look at in
this direction.

Running gr-fosphor on an E310 with UHD 4.0 is indeed possible--it is demoed
in the marketing video at https://www.youtube.com/watch?v=zQVky5b2XFo, and
a basic GNU Radio flowgraph is also shown.

On the RFNoC side, you will need to construct an RFNoC image for the E310
with a graph that includes the FFT and Fosphor blocks, for example:

Radio -> DDC -> FFT -> Fosphor -> SEPx2

(Note that the Fosphor block has two separate outputs, both of which must
be connected to stream endpoints to allow the data to be returned to the
host computer.) I'd recommend watching the RFNoC 4 workshop at
https://www.youtube.com/watch?v=M9ntwQie9vs for a walkthrough of how to
specify and build a custom RFNoC graph image and update the USRP to use it.

The Fosphor support for the GNU Radio 3.8 and UHD 4.0 combination is in the
gr-ettus repo at https://github.com/EttusResearch/gr-ettus in the
maint-3.8-uhd4.0 branch. Make sure that you have all the necessary Qt
dependencies installed and that ENABLE_QT=ON is set when you are running
cmake to build gr-ettus. It is a good idea to study the output of cmake to
confirm that dependencies were detected and the support included before
building and installing.

Getting the flowgraph right is very important for the Fosphor block to work
correctly. I recommend starting with the following flowgraph, which is
essentially the same one shown in the video I linked above (I hope this
image shows up!):

[image: image.png]

  • Red boxes (FFT size): The ‘FFT Length’ parameter on the FFT block on the
    ‘FFT Bins’ parameter on the Qt Fosphor Display block must have the same
    value. The radio must also have spp=N in its Block Args, where N is the FFT
    size specified in the other two blocks.
  • Blue boxes (bandwidth): The ‘Output Rate (Hz)’ parameter on the DDC block
    and ‘Sample Rate’ parameter on the Qt Fosphor Display block must have the
    same value.
  • Green value (frequency): The ‘Center Frequency (Hz)’ parameter on the
    radio block and ‘Center Frequency’ parameter on the Qt Fosphor Display
    block must have the same value.

The Rx Streamers must have the following configuration:

  • The Number of Channels parameter must be 1.
  • The Args parameter must have the string ‘spp=N’, where N is the FFT size
    value configured on the radio, FFT block, and Qt Fosphor block.
  • The Vector Length parameter must be N, where N is the FFT size.
  • The Wire Format and Output Type parameters must be Byte.

I hope this is helpful to you and to all others attempting to use the RFNoC
Fosphor block with UHD 4.0 and GR 3.8.

Best regards,
Aaron

On Sun, Feb 14, 2021 at 9:37 AM Ivan Zahartchuk via USRP-users < usrp-users@lists.ettus.com> wrote: > Hello. I want to create a graph to run gr-fosphor for usrp e310 but I haven't found any examples or at least uhd_image_builder.py to build firmware. Tell me if this is possible and what resources you can look at in this direction. Running gr-fosphor on an E310 with UHD 4.0 is indeed possible--it is demoed in the marketing video at https://www.youtube.com/watch?v=zQVky5b2XFo, and a basic GNU Radio flowgraph is also shown. On the RFNoC side, you will need to construct an RFNoC image for the E310 with a graph that includes the FFT and Fosphor blocks, for example: Radio -> DDC -> FFT -> Fosphor -> SEPx2 (Note that the Fosphor block has two separate outputs, both of which must be connected to stream endpoints to allow the data to be returned to the host computer.) I'd recommend watching the RFNoC 4 workshop at https://www.youtube.com/watch?v=M9ntwQie9vs for a walkthrough of how to specify and build a custom RFNoC graph image and update the USRP to use it. The Fosphor support for the GNU Radio 3.8 and UHD 4.0 combination is in the gr-ettus repo at https://github.com/EttusResearch/gr-ettus in the maint-3.8-uhd4.0 branch. Make sure that you have all the necessary Qt dependencies installed and that ENABLE_QT=ON is set when you are running cmake to build gr-ettus. It is a good idea to study the output of cmake to confirm that dependencies were detected and the support included before building and installing. Getting the flowgraph right is very important for the Fosphor block to work correctly. I recommend starting with the following flowgraph, which is essentially the same one shown in the video I linked above (I hope this image shows up!): [image: image.png] - Red boxes (FFT size): The ‘FFT Length’ parameter on the FFT block on the ‘FFT Bins’ parameter on the Qt Fosphor Display block must have the same value. The radio must also have spp=N in its Block Args, where N is the FFT size specified in the other two blocks. - Blue boxes (bandwidth): The ‘Output Rate (Hz)’ parameter on the DDC block and ‘Sample Rate’ parameter on the Qt Fosphor Display block must have the same value. - Green value (frequency): The ‘Center Frequency (Hz)’ parameter on the radio block and ‘Center Frequency’ parameter on the Qt Fosphor Display block must have the same value. The Rx Streamers must have the following configuration: - The Number of Channels parameter must be 1. - The Args parameter must have the string ‘spp=N’, where N is the FFT size value configured on the radio, FFT block, and Qt Fosphor block. - The Vector Length parameter must be N, where N is the FFT size. - The Wire Format and Output Type parameters must be Byte. I hope this is helpful to you and to all others attempting to use the RFNoC Fosphor block with UHD 4.0 and GR 3.8. Best regards, Aaron
Attached image
M
Mike
Thu, Feb 18, 2021 3:19 PM

Aaron,

Can you describe the parameters required by the RFNoC Graph (Device) for
accessing the E310?  Mine is at IP address 10.0.0.19.  I have the FPGA
configured with DDC/FFT/Fosphor and uhd_usrp_probe confirms this.   I
also have recreated the flow-graph that you describe below.  The only
thing I'm missing is the connectivity to the E310.

There was a time that I thought you had to execute part of the flow
graph locally on the ARM and use "zmq" blocks to transfer data to the
host.  But, now I understand that you can stream the data directly to
the host.  I'm just not getting the parameters "Device Address" and
"Device Args" set correctly.

The error I get is:

RuntimeError: LookupError: KeyError: No devices found for ----->
Device Address:
    dev_addr: 10.0.0.19
    type: e31x

Thanks,

Mike

On 2/15/21 9:07 AM, Aaron Rossetto via USRP-users wrote:

On Sun, Feb 14, 2021 at 9:37 AM Ivan Zahartchuk via USRP-users
<usrp-users@lists.ettus.com mailto:usrp-users@lists.ettus.com> wrote:

Hello. I want to create a graph to run gr-fosphor for usrp e310 but

I haven't found any examples or at least uhd_image_builder.py to build
firmware. Tell me if this is possible and what resources you can look
at in this direction.

Running gr-fosphor on an E310 with UHD 4.0 is indeed possible--it is
demoed in the marketing video at
https://www.youtube.com/watch?v=zQVky5b2XFo, and a basic GNU Radio
flowgraph is also shown.

On the RFNoC side, you will need to construct an RFNoC image for the
E310 with a graph that includes the FFT and Fosphor blocks, for example:

Radio -> DDC -> FFT -> Fosphor -> SEPx2

(Note that the Fosphor block has two separate outputs, both of which
must be connected to stream endpoints to allow the data to be returned
to the host computer.) I'd recommend watching the RFNoC 4 workshop at
https://www.youtube.com/watch?v=M9ntwQie9vs for a walkthrough of how
to specify and build a custom RFNoC graph image and update the USRP to
use it.

The Fosphor support for the GNU Radio 3.8 and UHD 4.0 combination is
in the gr-ettus repo at https://github.com/EttusResearch/gr-ettus in
the maint-3.8-uhd4.0 branch. Make sure that you have all the necessary
Qt dependencies installed and that ENABLE_QT=ON is set when you are
running cmake to build gr-ettus. It is a good idea to study the output
of cmake to confirm that dependencies were detected and the support
included before buildingand installing.

Getting the flowgraph right is very important for the Fosphor block to
work correctly. I recommend starting with the following flowgraph,
which is essentially the same one shown in the video I linked above (I
hope this image shows up!):

image.png

  • Red boxes (FFT size): The ‘FFT Length’ parameter on the FFT block on
    the ‘FFT Bins’ parameter on the Qt Fosphor Display block must have the
    same value. The radio must also have spp=N in its Block Args, where N
    is the FFT size specified in the other two blocks.
  • Blue boxes (bandwidth): The ‘Output Rate (Hz)’ parameter on the DDC
    block and ‘Sample Rate’ parameter on the Qt Fosphor Display block must
    have the same value.
  • Green value (frequency): The ‘Center Frequency (Hz)’ parameter on
    the radio block and ‘Center Frequency’ parameter on the Qt Fosphor
    Display block must have the same value.

The Rx Streamers must have the following configuration:

  • The Number of Channels parameter must be 1.
  • The Args parameter must have the string ‘spp=N’, where N is the FFT
    size value configured on the radio, FFT block, and Qt Fosphor block.
  • The Vector Length parameter must be N, where N is the FFT size.
  • The Wire Format and Output Type parameters must be Byte.

I hope this is helpful to you and to all others attempting to use the
RFNoC Fosphor block with UHD 4.0 and GR 3.8.

Best regards,
Aaron

USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Aaron, Can you describe the parameters required by the RFNoC Graph (Device) for accessing the E310?  Mine is at IP address 10.0.0.19.  I have the FPGA configured with DDC/FFT/Fosphor and uhd_usrp_probe confirms this.   I also have recreated the flow-graph that you describe below.  The only thing I'm missing is the connectivity to the E310. There was a time that I thought you had to execute part of the flow graph locally on the ARM and use "zmq" blocks to transfer data to the host.  But, now I understand that you can stream the data directly to the host.  I'm just not getting the parameters "Device Address" and "Device Args" set correctly. The error I get is: RuntimeError: LookupError: KeyError: No devices found for -----> Device Address:     dev_addr: 10.0.0.19     type: e31x Thanks, Mike On 2/15/21 9:07 AM, Aaron Rossetto via USRP-users wrote: > On Sun, Feb 14, 2021 at 9:37 AM Ivan Zahartchuk via USRP-users > <usrp-users@lists.ettus.com <mailto:usrp-users@lists.ettus.com>> wrote: > > > Hello. I want to create a graph to run gr-fosphor for usrp e310 but > I haven't found any examples or at least uhd_image_builder.py to build > firmware. Tell me if this is possible and what resources you can look > at in this direction. > > Running gr-fosphor on an E310 with UHD 4.0 is indeed possible--it is > demoed in the marketing video at > https://www.youtube.com/watch?v=zQVky5b2XFo, and a basic GNU Radio > flowgraph is also shown. > > On the RFNoC side, you will need to construct an RFNoC image for the > E310 with a graph that includes the FFT and Fosphor blocks, for example: > > Radio -> DDC -> FFT -> Fosphor -> SEPx2 > > (Note that the Fosphor block has two separate outputs, both of which > must be connected to stream endpoints to allow the data to be returned > to the host computer.) I'd recommend watching the RFNoC 4 workshop at > https://www.youtube.com/watch?v=M9ntwQie9vs for a walkthrough of how > to specify and build a custom RFNoC graph image and update the USRP to > use it. > > The Fosphor support for the GNU Radio 3.8 and UHD 4.0 combination is > in the gr-ettus repo at https://github.com/EttusResearch/gr-ettus in > the maint-3.8-uhd4.0 branch. Make sure that you have all the necessary > Qt dependencies installed and that ENABLE_QT=ON is set when you are > running cmake to build gr-ettus. It is a good idea to study the output > of cmake to confirm that dependencies were detected and the support > included before buildingand installing. > > Getting the flowgraph right is very important for the Fosphor block to > work correctly. I recommend starting with the following flowgraph, > which is essentially the same one shown in the video I linked above (I > hope this image shows up!): > > image.png > - Red boxes (FFT size): The ‘FFT Length’ parameter on the FFT block on > the ‘FFT Bins’ parameter on the Qt Fosphor Display block must have the > same value. The radio must also have spp=N in its Block Args, where N > is the FFT size specified in the other two blocks. > - Blue boxes (bandwidth): The ‘Output Rate (Hz)’ parameter on the DDC > block and ‘Sample Rate’ parameter on the Qt Fosphor Display block must > have the same value. > - Green value (frequency): The ‘Center Frequency (Hz)’ parameter on > the radio block and ‘Center Frequency’ parameter on the Qt Fosphor > Display block must have the same value. > > The Rx Streamers must have the following configuration: > > - The Number of Channels parameter must be 1. > - The Args parameter must have the string ‘spp=N’, where N is the FFT > size value configured on the radio, FFT block, and Qt Fosphor block. > - The Vector Length parameter must be N, where N is the FFT size. > - The Wire Format and Output Type parameters must be Byte. > > I hope this is helpful to you and to all others attempting to use the > RFNoC Fosphor block with UHD 4.0 and GR 3.8. > > Best regards, > Aaron > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Attached image
J
jcasallas2019@gmail.com
Mon, May 17, 2021 8:24 PM

Hi all,

I tried the same configuration but I got the following error:INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 8000 bytes.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

Traceback (most recent call last):

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module>

main()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main

tb = top_block_cls()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in __init__

self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer(

File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make

return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start)

RuntimeError: ValueError: [rx_stream] Must provide a otw_format!

Do you guys have any idea?

Thanks

Hi all, I tried the same configuration but I got the following error:INFO\] \[UHD\] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff `[INFO] [X300] X300 initialization sequence...` `[INFO] [X300] Maximum frame size: 8000 bytes.` `[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a` `[INFO] [X300] Radio 1x clock: 200 MHz` `Traceback (most recent call last):` ` File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module>` ` main()` ` File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main` ` tb = top_block_cls()` ` File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in __init__` ` self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer(` ` File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make` ` return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start)` `RuntimeError: ValueError: [rx_stream] Must provide a otw_format!` Do you guys have any idea? Thanks
PA
Paul Atreides
Mon, May 17, 2021 10:16 PM

I think you need to manually set the input and output types your RX streamer blocks, don’t use the “automatic” setting.

<end transmission>

On May 17, 2021, at 16:25, jcasallas2019@gmail.com wrote:

Hi all,

I tried the same configuration but I got the following error:INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 8000 bytes.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

Traceback (most recent call last):

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module>

main()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main

tb = top_block_cls()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in init

self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer(

File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make

return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start)

RuntimeError: ValueError: [rx_stream] Must provide a otw_format!

Do you guys have any idea?

Thanks

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

I think you need to manually set the input and output types your RX streamer blocks, don’t use the “automatic” setting. <end transmission> > On May 17, 2021, at 16:25, jcasallas2019@gmail.com wrote: >  > Hi all, > > > > I tried the same configuration but I got the following error:INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff > > [INFO] [X300] X300 initialization sequence... > > [INFO] [X300] Maximum frame size: 8000 bytes. > > [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a > > [INFO] [X300] Radio 1x clock: 200 MHz > > Traceback (most recent call last): > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module> > > main() > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main > > tb = top_block_cls() > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in __init__ > > self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer( > > File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make > > return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start) > > RuntimeError: ValueError: [rx_stream] Must provide a otw_format! > > > > Do you guys have any idea? > > > > Thanks > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com
PA
Paul Atreides
Mon, May 17, 2021 10:17 PM

I think you need to manually set the input and output types your RX streamer blocks, don’t use the “automatic” setting.

<end transmission>

On May 17, 2021, at 16:25, jcasallas2019@gmail.com wrote:

Hi all,

I tried the same configuration but I got the following error:INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 8000 bytes.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

Traceback (most recent call last):

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module>

main()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main

tb = top_block_cls()

File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in init

self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer(

File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make

return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start)

RuntimeError: ValueError: [rx_stream] Must provide a otw_format!

Do you guys have any idea?

Thanks

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

I think you need to manually set the input and output types your RX streamer blocks, don’t use the “automatic” setting. <end transmission> > On May 17, 2021, at 16:25, jcasallas2019@gmail.com wrote: >  > Hi all, > > > > I tried the same configuration but I got the following error:INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff > > [INFO] [X300] X300 initialization sequence... > > [INFO] [X300] Maximum frame size: 8000 bytes. > > [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a > > [INFO] [X300] Radio 1x clock: 200 MHz > > Traceback (most recent call last): > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 354, in <module> > > main() > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 330, in main > > tb = top_block_cls() > > File "/home/wisp/rfnoc_ws/rfnoc-test/examples/rfnoc_gain.py", line 93, in __init__ > > self.ettus_rfnoc_rx_streamer_1 = ettus.rfnoc_rx_streamer( > > File "/usr/local/lib/python3/dist-packages/ettus/ettus_swig.py", line 1423, in make > > return _ettus_swig.rfnoc_rx_streamer_make(graph, num_chans, stream_args, vlen, issue_stream_cmd_on_start) > > RuntimeError: ValueError: [rx_stream] Must provide a otw_format! > > > > Do you guys have any idea? > > > > Thanks > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com
J
jcasallas2019@gmail.com
Tue, May 18, 2021 2:59 PM

Hi,

Thanks I did that and I do not have that error anymore, but now the GUI doe not show and the program terminates with (return error -11).

[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 8000 bytes.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

[WARNING] [0/Radio#0] Setting RX IQ Balance is not possible on this device.

gr::log :DEBUG: rfnoc_rx_streamer0 - Committing graph...

[WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping.

gr::log :DEBUG: rfnoc_rx_streamer1 - Committing graph...

gr::log :DEBUG: rfnoc_rx_streamer1 - Sending start stream command...

gr::log :DEBUG: rfnoc_rx_streamer0 - Sending start stream command...

>>> Done (return code -11)

Hi, Thanks I did that and I do not have that error anymore, but now the GUI doe not show and the program terminates with (return error -11). `[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff` `[INFO] [X300] X300 initialization sequence...` `[INFO] [X300] Maximum frame size: 8000 bytes.` `[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a` `[INFO] [X300] Radio 1x clock: 200 MHz` `[WARNING] [0/Radio#0] Setting RX IQ Balance is not possible on this device.` `gr::log :DEBUG: rfnoc_rx_streamer0 - Committing graph...` `[WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping.` `gr::log :DEBUG: rfnoc_rx_streamer1 - Committing graph...` `gr::log :DEBUG: rfnoc_rx_streamer1 - Sending start stream command...` `gr::log :DEBUG: rfnoc_rx_streamer0 - Sending start stream command...` `>>> Done (return code -11)`
PA
Paul Atreides
Wed, May 19, 2021 1:15 AM

Did you synthesize a custom FPGA image with Fosphor and FFT included?

<end transmission>

On May 18, 2021, at 10:59, jcasallas2019@gmail.com wrote:

Hi,

Thanks I did that and I do not have that error anymore, but now the GUI doe not show and the program terminates with (return error -11).

[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff

[INFO] [X300] X300 initialization sequence...

[INFO] [X300] Maximum frame size: 8000 bytes.

[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a

[INFO] [X300] Radio 1x clock: 200 MHz

[WARNING] [0/Radio#0] Setting RX IQ Balance is not possible on this device.

gr::log :DEBUG: rfnoc_rx_streamer0 - Committing graph...

[WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping.

gr::log :DEBUG: rfnoc_rx_streamer1 - Committing graph...

gr::log :DEBUG: rfnoc_rx_streamer1 - Sending start stream command...

gr::log :DEBUG: rfnoc_rx_streamer0 - Sending start stream command...

Done (return code -11)

USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com

Did you synthesize a custom FPGA image with Fosphor and FFT included? <end transmission> > On May 18, 2021, at 10:59, jcasallas2019@gmail.com wrote: >  > Hi, > > > > Thanks I did that and I do not have that error anymore, but now the GUI doe not show and the program terminates with (return error -11). > > > > [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff > > [INFO] [X300] X300 initialization sequence... > > [INFO] [X300] Maximum frame size: 8000 bytes. > > [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a > > [INFO] [X300] Radio 1x clock: 200 MHz > > [WARNING] [0/Radio#0] Setting RX IQ Balance is not possible on this device. > > gr::log :DEBUG: rfnoc_rx_streamer0 - Committing graph... > > [WARNING] [0/Radio#0] Attempting to set tick rate to 0. Skipping. > > gr::log :DEBUG: rfnoc_rx_streamer1 - Committing graph... > > gr::log :DEBUG: rfnoc_rx_streamer1 - Sending start stream command... > > gr::log :DEBUG: rfnoc_rx_streamer0 - Sending start stream command... > > >>> Done (return code -11) > > > > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-leave@lists.ettus.com
J
jcasallas2019@gmail.com
Wed, May 19, 2021 4:53 PM

Yes. please have a look.

[INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a
[INFO] [X300] Radio 1x clock: 200 MHz
  _____________________________________________________
 /
|       Device: X-Series Device
|     _____________________________________________________
|    /
|   |       Mboard: X310
|   |   revision: 11
|   |   revision_compat: 7
|   |   product: 30818
|   |   mac-addr0: 00:80:2f:22:ff:b4
|   |   mac-addr1: 00:80:2f:22:ff:b5
|   |   gateway: 192.168.10.1
|   |   ip-addr0: 192.168.10.2
|   |   subnet0: 255.255.255.0
|   |   ip-addr1: 192.168.20.2
|   |   subnet1: 255.255.255.0
|   |   ip-addr2: 192.168.30.2
|   |   subnet2: 255.255.255.0
|   |   ip-addr3: 192.168.40.2
|   |   subnet3: 255.255.255.0
|   |   serial: 3176C83
|   |   FW Version: 6.0
|   |   FPGA Version: 38.0
|   |   FPGA git hash: e520e3f-dirty
|   |
|   |   Time sources:  internal, external, gpsdo
|   |   Clock sources: internal, external, gpsdo
|   |   Sensors: gps_servo, gps_gprmc, gps_time, gps_gpgga, gps_locked, ref_locked
|     _____________________________________________________
|    /
|   |       RFNoC blocks on this device:
|   |
|   |   * 0/DDC#0
|   |   * 0/DDC#1
|   |   * 0/DUC#0
|   |   * 0/DUC#1
|   |   * 0/FFT#0
|   |   * 0/Fosphor#0
|   |   * 0/Radio#0
|   |   * 0/Radio#1
|     _____________________________________________________
|    /
|   |       Static connections on this device:
|   |
|   |   * 0/SEP#0:0==>0/DUC#0:0
|   |   * 0/DUC#0:0==>0/Radio#0:0
|   |   * 0/Radio#0:0==>0/DDC#0:0
|   |   * 0/DDC#0:0==>0/SEP#0:0
|   |   * 0/Radio#0:1==>0/DDC#0:1
|   |   * 0/DDC#0:1==>0/SEP#1:0
|   |   * 0/SEP#2:0==>0/DUC#1:0
|   |   * 0/DUC#1:0==>0/Radio#1:0
|   |   * 0/Radio#1:0==>0/DDC#1:0
|   |   * 0/DDC#1:0==>0/SEP#2:0
|   |   * 0/Radio#1:1==>0/DDC#1:1
|   |   * 0/DDC#1:1==>0/SEP#3:0
|   |   * 0/SEP#4:0==>0/FFT#0:0
|   |   * 0/FFT#0:0==>0/SEP#4:0
|   |   * 0/SEP#5:0==>0/Fosphor#0:0
|   |   * 0/Fosphor#0:0==>0/SEP#5:0
|   |   * 0/Fosphor#0:1==>0/SEP#6:0
|     _____________________________________________________
|    /
|   |       TX Dboard: dboard
|   |   ID: UBX-160 v2 (0x007d)
|   |   Serial: 315EA14
|   |     _____________________________________________________
|   |    /
|   |   |       TX Frontend: 0
|   |   |   Name: UBX TX
|   |   |   Antennas: TX/RX, CAL
|   |   |   Sensors: lo_locked
|   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
|   |   |   Connection Type: QI
|   |   |   Uses LO offset: No
|     _____________________________________________________
|    /
|   |       RX Dboard: dboard
|   |   ID: UBX-160 v2 (0x007e)
|   |   Serial: 315EA14
|   |     _____________________________________________________
|   |    /
|   |   |       RX Frontend: 0
|   |   |   Name: UBX RX
|   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   Sensors: lo_locked
|   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
|   |   |   Connection Type: IQ
|   |   |   Uses LO offset: No
|     _____________________________________________________
|    /
|   |       TX Dboard: dboard
|   |   ID: UBX-160 v2 (0x007d)
|   |   Serial: 3158364
|   |     _____________________________________________________
|   |    /
|   |   |       TX Frontend: 0
|   |   |   Name: UBX TX
|   |   |   Antennas: TX/RX, CAL
|   |   |   Sensors: lo_locked
|   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
|   |   |   Connection Type: QI
|   |   |   Uses LO offset: No
|     _____________________________________________________
|    /
|   |       RX Dboard: dboard
|   |   ID: UBX-160 v2 (0x007e)
|   |   Serial: 3158364
|   |     _____________________________________________________
|   |    /
|   |   |       RX Frontend: 0
|   |   |   Name: UBX RX
|   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   Sensors: lo_locked
|   |   |   Freq range: 10.000 to 6000.000 MHz
|   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz
|   |   |   Connection Type: IQ
|   |   |   Uses LO offset: No


THANKS
Yes. please have a look. ``` [INFO] [UHD] linux; GNU C++ version 9.3.0; Boost_107100; UHD_4.0.0.0-50-ge520e3ff [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 8000 bytes. [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [X300] Radio 1x clock: 200 MHz _____________________________________________________ / | Device: X-Series Device | _____________________________________________________ | / | | Mboard: X310 | | revision: 11 | | revision_compat: 7 | | product: 30818 | | mac-addr0: 00:80:2f:22:ff:b4 | | mac-addr1: 00:80:2f:22:ff:b5 | | gateway: 192.168.10.1 | | ip-addr0: 192.168.10.2 | | subnet0: 255.255.255.0 | | ip-addr1: 192.168.20.2 | | subnet1: 255.255.255.0 | | ip-addr2: 192.168.30.2 | | subnet2: 255.255.255.0 | | ip-addr3: 192.168.40.2 | | subnet3: 255.255.255.0 | | serial: 3176C83 | | FW Version: 6.0 | | FPGA Version: 38.0 | | FPGA git hash: e520e3f-dirty | | | | Time sources: internal, external, gpsdo | | Clock sources: internal, external, gpsdo | | Sensors: gps_servo, gps_gprmc, gps_time, gps_gpgga, gps_locked, ref_locked | _____________________________________________________ | / | | RFNoC blocks on this device: | | | | * 0/DDC#0 | | * 0/DDC#1 | | * 0/DUC#0 | | * 0/DUC#1 | | * 0/FFT#0 | | * 0/Fosphor#0 | | * 0/Radio#0 | | * 0/Radio#1 | _____________________________________________________ | / | | Static connections on this device: | | | | * 0/SEP#0:0==>0/DUC#0:0 | | * 0/DUC#0:0==>0/Radio#0:0 | | * 0/Radio#0:0==>0/DDC#0:0 | | * 0/DDC#0:0==>0/SEP#0:0 | | * 0/Radio#0:1==>0/DDC#0:1 | | * 0/DDC#0:1==>0/SEP#1:0 | | * 0/SEP#2:0==>0/DUC#1:0 | | * 0/DUC#1:0==>0/Radio#1:0 | | * 0/Radio#1:0==>0/DDC#1:0 | | * 0/DDC#1:0==>0/SEP#2:0 | | * 0/Radio#1:1==>0/DDC#1:1 | | * 0/DDC#1:1==>0/SEP#3:0 | | * 0/SEP#4:0==>0/FFT#0:0 | | * 0/FFT#0:0==>0/SEP#4:0 | | * 0/SEP#5:0==>0/Fosphor#0:0 | | * 0/Fosphor#0:0==>0/SEP#5:0 | | * 0/Fosphor#0:1==>0/SEP#6:0 | _____________________________________________________ | / | | TX Dboard: dboard | | ID: UBX-160 v2 (0x007d) | | Serial: 315EA14 | | _____________________________________________________ | | / | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _____________________________________________________ | / | | RX Dboard: dboard | | ID: UBX-160 v2 (0x007e) | | Serial: 315EA14 | | _____________________________________________________ | | / | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz | | | Connection Type: IQ | | | Uses LO offset: No | _____________________________________________________ | / | | TX Dboard: dboard | | ID: UBX-160 v2 (0x007d) | | Serial: 3158364 | | _____________________________________________________ | | / | | | TX Frontend: 0 | | | Name: UBX TX | | | Antennas: TX/RX, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz | | | Connection Type: QI | | | Uses LO offset: No | _____________________________________________________ | / | | RX Dboard: dboard | | ID: UBX-160 v2 (0x007e) | | Serial: 3158364 | | _____________________________________________________ | | / | | | RX Frontend: 0 | | | Name: UBX RX | | | Antennas: TX/RX, RX2, CAL | | | Sensors: lo_locked | | | Freq range: 10.000 to 6000.000 MHz | | | Gain range PGA0: 0.0 to 31.5 step 0.5 dB | | | Bandwidth range: 160000000.0 to 160000000.0 step 0.0 Hz | | | Connection Type: IQ | | | Uses LO offset: No THANKS ``` ``` ```
J
jcasallas2019@gmail.com
Wed, May 19, 2021 6:33 PM

I would like to also add the gdb backtrace result for that segmentation fault:

(gdb) bt
#0  0x00007f851c000ee0 in ?? ()
#1  0x00007f85f827cd19 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#2  0x00007f85f827d605 in _Unwind_Resume () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#3  0x00007f85f3de6f03 in gr::ettus::fosphor_display_impl::start() [clone .cold] () from /usr/local/lib/libgnuradio-ettus.so.3.8.0
#4  0x00007f85f374302c in gr::block_executor::block_executor(boost::shared_ptr<gr::block>, int) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git
#5  0x00007f85f379675c in gr::tpb_thread_body::tpb_thread_body(boost::shared_ptr<gr::block>, boost::shared_ptr<boost::barrier>, int) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git
#6  0x00007f85f3789f04 in boost::detail::function::void_function_obj_invoker0<gr::thread::thread_body_wrapper<gr::tpb_container>, void>::invoke(boost::detail::function::function_buffer&) ()
   from /usr/local/lib/libgnuradio-runtime.so.3.8.2git
#7  0x00007f85f37a38f8 in boost::detail::thread_data<boost::function0<void> >::run() () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git
#8  0x00007f85f3c4543b in ?? () from /lib/x86_64-linux-gnu/libboost_thread.so.1.71.0
#9  0x00007f85fa763609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#10 0x00007f85fa89f293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) disas/s  0x00007f85f827d605, +10000

Thanks
I would like to also add the gdb backtrace result for that segmentation fault: ``` (gdb) bt #0 0x00007f851c000ee0 in ?? () #1 0x00007f85f827cd19 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1 #2 0x00007f85f827d605 in _Unwind_Resume () from /lib/x86_64-linux-gnu/libgcc_s.so.1 #3 0x00007f85f3de6f03 in gr::ettus::fosphor_display_impl::start() [clone .cold] () from /usr/local/lib/libgnuradio-ettus.so.3.8.0 #4 0x00007f85f374302c in gr::block_executor::block_executor(boost::shared_ptr<gr::block>, int) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git #5 0x00007f85f379675c in gr::tpb_thread_body::tpb_thread_body(boost::shared_ptr<gr::block>, boost::shared_ptr<boost::barrier>, int) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git #6 0x00007f85f3789f04 in boost::detail::function::void_function_obj_invoker0<gr::thread::thread_body_wrapper<gr::tpb_container>, void>::invoke(boost::detail::function::function_buffer&) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git #7 0x00007f85f37a38f8 in boost::detail::thread_data<boost::function0<void> >::run() () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git #8 0x00007f85f3c4543b in ?? () from /lib/x86_64-linux-gnu/libboost_thread.so.1.71.0 #9 0x00007f85fa763609 in start_thread (arg=<optimized out>) at pthread_create.c:477 #10 0x00007f85fa89f293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) disas/s 0x00007f85f827d605, +10000 Thanks ```
Next page
Empathy v1.0   2026 ©emwd.com
Documentation