usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

setting up gr-fosphor on uhd 4

JP
Jonathon Pendlum
Wed, May 19, 2021 7:56 PM

Hi Julian,

Does the segfault go away if you build gr-ettus with the flag
-DCMAKE_BUILD_TYPE=Debug?

Jonathon

On Wed, May 19, 2021 at 2:34 PM jcasallas2019@gmail.com wrote:

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_ptrgr::block, int) () from /usr/local/lib/libgnuradio-runtime.so.3.8.2git
#5  0x00007f85f379675c in gr::tpb_thread_body::tpb_thread_body(boost::shared_ptrgr::block, boost::shared_ptrboost::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_wrappergr::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


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

Hi Julian, Does the segfault go away if you build gr-ettus with the flag -DCMAKE_BUILD_TYPE=Debug? Jonathon On Wed, May 19, 2021 at 2:34 PM <jcasallas2019@gmail.com> wrote: > 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 > > > _______________________________________________ > 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 9:36 PM

It works…which is good but a brief explanation would be great to add it to the report.

It works…which is good but a brief explanation would be great to add it to the report.
PA
Paul Atreides
Wed, May 19, 2021 11:46 PM

Just for sanity, this is the post I used to get all the settings correct.
So far it’s the only documentation I can find for how to set up UHD 4.0 with fosphor.

http://ettus.80997.x6.nabble.com/USRP-users-setting-up-gr-fosphor-on-uhd-4-td16532.html

I also had some issues with the QT window locking up the widget controls, so I used zmq sockets to pipe the 2 byte streams into another flowgraph that hosts the fosphor display.

<end transmission>

On May 19, 2021, at 13:11, jcasallas2019@gmail.com wrote:


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


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

Just for sanity, this is the post I used to get all the settings correct. So far it’s the only documentation I can find for how to set up UHD 4.0 with fosphor. http://ettus.80997.x6.nabble.com/USRP-users-setting-up-gr-fosphor-on-uhd-4-td16532.html I also had some issues with the QT window locking up the widget controls, so I used zmq sockets to pipe the 2 byte streams into another flowgraph that hosts the fosphor display. <end transmission> > On May 19, 2021, at 13:11, jcasallas2019@gmail.com wrote: > >  > 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 > > _______________________________________________ > 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
Thu, May 20, 2021 6:42 PM

When I rebuilt gr-ettus with the flag -DCMAKE_BUILD_TYPE=Debug, the graph flow runs and the data is being displayed just fine. I do not get any segmentation fault this time.

When I rebuilt gr-ettus with the flag -DCMAKE_BUILD_TYPE=Debug, the graph flow runs and the data is being displayed just fine. I do not get any segmentation fault this time.