Hi,

I am building an OFDM receiver on X310 using RFNoC. When I run the
rfnoc_ofdm.grc example in the gr-ettus examples, I met the "timeout on chan
0" failure once I enable the RFNoC: OFDM Sync block. The other blocks seems
to be fine, say the FIFO and FFT block, but if enable the Sync block, the
flow blocks and the output is as below:

---------------------------- terminal output -----------------------------
Generating: '/home/sdrn/rfnoc/src/gr-ettus/examples/rfnoc/ofdm_tester.py'

Executing: /usr/bin/python2 -u
/home/sdrn/rfnoc/src/gr-ettus/examples/rfnoc/ofdm_tester.py
<string>:1: VisibleDeprecationWarning: using a non-integer number instead
of an integer will result in an error in the future
<string>:1: VisibleDeprecationWarning: using a non-integer number instead
of an integer will result in an error in the future

/home/sdrn/rfnoc/src/gr-ettus/examples/rfnoc/ofdm_tester.py:71:
VisibleDeprecationWarning: using a non-integer number instead of an integer
will result in an error in the future
  self.S = S = numpy.sqrt(13.0/6) * [0, 0, 0, 0, 0, 0, 0, 0, 1+1j, 0, 0, 0,
-1-1j, 0, 0, 0, 1+1j, 0, 0, 0, -1-1j, 0, 0, 0, -1-1j, 0, 0, 0, 1+1j, 0, 0,
0, 0, 0, 0, 0, -1-1j, 0, 0, 0, -1-1j, 0, 0, 0, 1+1j, 0, 0, 0, 1+1j, 0, 0,
0, 1+1j, 0, 0, 0, 1+1j, 0, 0, 0, 0, 0, 0, 0]
[INFO] [UHDlinux; GNU C++ version 5.4.0 20160609; Boost_105800;
UHD_4.0.0.rfnoc-ofdm-408-gf3a40f9a]
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Determining maximum frame size...
[INFO] [X300] Maximum frame size: 8000 bytes.
[INFO] [X300] Setup basic communication...
[INFO] [X300] Loading values from EEPROM...
[INFO] [X300] Setup RF frontend clocking...
[INFO] [X300] Radio 1x clock:200
[INFO] [RFNOC] [DMA FIFO] Running BIST for FIFO 0...
[INFO] [RFNOC] pass (Throughput: 1300.5MB/s)
[INFO] [RFNOC] [DMA FIFO] Running BIST for FIFO 1...
[INFO] [RFNOC] pass (Throughput: 1301.1MB/s)
[INFO] [RFNOC RADIO] Register loopback test passed
[INFO] [RFNOC RADIO] Register loopback test passed
[INFO] [RFNOC RADIO] Register loopback test passed
[INFO] [RFNOC RADIO] Register loopback test passed
[INFO] [CORES] Performing timer loopback test...
[INFO] [CORES] Timer loopback test passed
[INFO] [CORES] Performing timer loopback test...
[INFO] [CORES] Timer loopback test passed
[INFO] [RFNOC] Assuming max packet size for 0/FIFO_0
timeout on chan 0
timeout on chan 0
timeout on chan 0
timeout on chan 0
timeout on chan 0
timeout on chan 0


<string>:1: VisibleDeprecationWarning: using a non-integer number instead
of an integer will result in an error in the future

>>> Done (return code -15)
<string>:1: VisibleDeprecationWarning: using a non-integer number instead
of an integer will result in an error in the future
<string>:1: VisibleDeprecationWarning: using a non-integer number instead
of an integer will result in an error in the future
---------------------------- terminal output -----------------------------

My OS is ubuntu 16.04.04 (Linux sdrn-OptiPlex-9020 4.10.0-30-generic
#34~16.04.1-Ubuntu SMP Wed Aug 2 02:13:56 UTC 2017 x86_64 x86_64 x86_64
GNU/Linux) and I follow the RFNOC tutorial to install uhd, gnuradio and
gr-ettus using Pybomb. I switch the branch to rfnoc-ofdm on both uhd and
gr-ettus (I also tried rfnoc-devel branch and get the same output). The
uhd_usrp_probe command can found the SchmidlCox module successfully as
below:
-------------- uhd_usrp_probe output------------------
|   |   |   |   Name: ad9146
|   |   |   |   Gain Elements: None
|   |     _____________________________________________________
|   |    /
|   |   |       RFNoC blocks on this device:
|   |   |
|   |   |   * DmaFIFO_0
|   |   |   * Radio_0
|   |   |   * Radio_1
|   |   |   * FFT_0
|   |   |   * SchmidlCox_0
|   |   |   * Block_0
|   |   |   * OFDMDemap_0
|   |   |   * OFDMEq_0
|   |   |   * DDC_0
|   |   |   * FIFO_0
|   |   |   * FIFO_1
|   |   |   * FIFO_2
|   |   |   * FIFO_3
-------------- uhd_usrp_probe output------------------

I noticed some users have similar issues (
http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2016-March/019145.html),
but are different from mine.
Any hints to solve this problem?

Thanks

-- 
Best regards,
Qing
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com

Reply via email to