Re: [USRP-users] Having complications with my build
You should probably post this on the srsLTE mailing list. http://www.softwareradiosystems.com/mailman/listinfo/srslte-users Ron On 4/16/19 20:28, Nehemiah Chan via USRP-users wrote: Hi everyone, I am totally to srsLTE. I am using two computers Ubuntu 16.04 with B210 and Ubuntun 18.04 with bladeRF. Here below are the outputs for srsepc, srsenb and srsue, pi@pi:~/srsLTE/srsenb$ sudo srsenb enb.conf.example Built in Release mode using commit 429ee90 on branch master. --- Software Radio Systems LTE eNodeB --- Reading configuration file enb.conf.example... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-release Opening USRP with args: type=b200,master_clock_rate=30.72e6 [INFO] [B200] Detected Device: B210 [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Asking for clock rate 30.72 MHz... [INFO] [B200] Actually got clock rate 30.72 MHz. Setting frequency: DL=2685.0 Mhz, UL=2565.0 MHz [INFO] [B200] Asking for clock rate 11.52 MHz... [INFO] [B200] Actually got clock rate 11.52 MHz. Setting Sampling frequency 11.52 MHz eNodeB started === Type to view trace pi@pi:~/srsLTE/srsepc$ sudo srsepc epc.conf.example [sudo] password for pi: Sorry, try again. [sudo] password for pi: Built in Release mode using commit 429ee90 on branch master. --- Software Radio Systems EPC --- Reading configuration file epc.conf.example... HSS Initialized. MME GTP-C Initialized MME Initialized. MCC: 0xf001, MNC: 0xff01 SP-GW Initialized. Received S1 Setup Request. S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 S1 Setup Request - TAC 7, B-PLMN 0 S1 Setup Request - Paging DRX 2 Sending S1 Setup Response SCTP Association Shutdown. Association: 88 Deleting eNB context. eNB Id: 0x19b Releasing UEs context No UEs to be released Received S1 Setup Request. S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 S1 Setup Request - TAC 7, B-PLMN 0 S1 Setup Request - Paging DRX 2 Sending S1 Setup Response ^CDeleting eNB context. eNB Id: 0x19b Deleting UE context in HSS. IMSI: 001010123456780 Deleting UE context in HSS. IMSI: 001010123456789 --- exiting --- pi@pi-ubuntu:~/srsLTE/srsue$ sudo srsue ue.conf.example Reading configuration file ue.conf.example... Built in Release mode using commit 429ee901 on branch master. --- Software Radio Systems LTE UE --- Opening RF device with 1 RX antennas... [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501; UHD_3.15.0.git-84-g164d76dc Opening USRP with args: Error opening UHD: code 11 Opening bladeRF... Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz Waiting PHY to initialize... ... Attaching UE... Searching cell in DL EARFCN=3400, f_dl=2685.0 MHz, f_ul=2565.0 MHz set RX frequency to 268500 set TX frequency to 256500 Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz ... Found Cell: PCI=1, PRB=50, Ports=1, CFO=1.3 KHz Set RX sampling rate 11.52 Mhz, filter BW: 10.00 Mhz Found PLMN: Id=00101, TAC=7 Setting PDN protocol to IPv4 Random Access Transmission: seq=19, ra-rnti=0x2 Random Access Transmission: seq=39, ra-rnti=0x2 Random Access Transmission: seq=22, ra-rnti=0x2 Random Access Transmission: seq=6, ra-rnti=0x2 Random Access Transmission: seq=20, ra-rnti=0x2 Random Access Transmission: seq=44, ra-rnti=0x2 Random Access Transmission: seq=11, ra-rnti=0x2 Random Access Transmission: seq=4, ra-rnti=0x2 Random Access Transmission: seq=28, ra-rnti=0x2 Random Access Transmission: seq=50, ra-rnti=0x2 Warning: Detected Radio-Link Failure Srsue -- bladeRF> info Board: Nuand bladeRF (bladerf1) Serial #: 54548816f628f3ba6703dc275e26b9d2 VCTCXO DAC calibration: 0x9121 FPGA size: 115 KLE FPGA loaded: yes Flash size: 32 Mbit USB bus: 2 USB address: 20 USB speed: SuperSpeed Backend: libusb Instance: 0 bladeRF> version bladeRF-cli version: 1.7.1-git-1da130cb libbladeRF version: 2.2.0-git-1da130cb Firmware version: 2.3.2 FPGA version: 0.8.0 (configured by USB host) --- srsenb and srsepc pi@pi:~$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-release [INFO] [B200] Detected Device: B210 [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [
[USRP-users] Having complications with my build
Hi everyone, I am totally to srsLTE. I am using two computers Ubuntu 16.04 with B210 and Ubuntun 18.04 with bladeRF. Here below are the outputs for srsepc, srsenb and srsue, pi@pi:~/srsLTE/srsenb$ sudo srsenb enb.conf.example Built in Release mode using commit 429ee90 on branch master. --- Software Radio Systems LTE eNodeB --- Reading configuration file enb.conf.example... [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-release Opening USRP with args: type=b200,master_clock_rate=30.72e6 [INFO] [B200] Detected Device: B210 [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Asking for clock rate 30.72 MHz... [INFO] [B200] Actually got clock rate 30.72 MHz. Setting frequency: DL=2685.0 Mhz, UL=2565.0 MHz [INFO] [B200] Asking for clock rate 11.52 MHz... [INFO] [B200] Actually got clock rate 11.52 MHz. Setting Sampling frequency 11.52 MHz eNodeB started === Type to view trace pi@pi:~/srsLTE/srsepc$ sudo srsepc epc.conf.example [sudo] password for pi: Sorry, try again. [sudo] password for pi: Built in Release mode using commit 429ee90 on branch master. --- Software Radio Systems EPC --- Reading configuration file epc.conf.example... HSS Initialized. MME GTP-C Initialized MME Initialized. MCC: 0xf001, MNC: 0xff01 SP-GW Initialized. Received S1 Setup Request. S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 S1 Setup Request - TAC 7, B-PLMN 0 S1 Setup Request - Paging DRX 2 Sending S1 Setup Response SCTP Association Shutdown. Association: 88 Deleting eNB context. eNB Id: 0x19b Releasing UEs context No UEs to be released Received S1 Setup Request. S1 Setup Request - eNB Name: srsenb01, eNB id: 0x19b S1 Setup Request - MCC:001, MNC:01, PLMN: 61712 S1 Setup Request - TAC 7, B-PLMN 0 S1 Setup Request - Paging DRX 2 Sending S1 Setup Response ^CDeleting eNB context. eNB Id: 0x19b Deleting UE context in HSS. IMSI: 001010123456780 Deleting UE context in HSS. IMSI: 001010123456789 --- exiting --- pi@pi-ubuntu:~/srsLTE/srsue$ sudo srsue ue.conf.example Reading configuration file ue.conf.example... Built in Release mode using commit 429ee901 on branch master. --- Software Radio Systems LTE UE --- Opening RF device with 1 RX antennas... [INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106501; UHD_3.15.0.git-84-g164d76dc Opening USRP with args: Error opening UHD: code 11 Opening bladeRF... Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz Waiting PHY to initialize... ... Attaching UE... Searching cell in DL EARFCN=3400, f_dl=2685.0 MHz, f_ul=2565.0 MHz set RX frequency to 268500 set TX frequency to 256500 Set RX sampling rate 1.92 Mhz, filter BW: 2.50 Mhz ... Found Cell: PCI=1, PRB=50, Ports=1, CFO=1.3 KHz Set RX sampling rate 11.52 Mhz, filter BW: 10.00 Mhz Found PLMN: Id=00101, TAC=7 Setting PDN protocol to IPv4 Random Access Transmission: seq=19, ra-rnti=0x2 Random Access Transmission: seq=39, ra-rnti=0x2 Random Access Transmission: seq=22, ra-rnti=0x2 Random Access Transmission: seq=6, ra-rnti=0x2 Random Access Transmission: seq=20, ra-rnti=0x2 Random Access Transmission: seq=44, ra-rnti=0x2 Random Access Transmission: seq=11, ra-rnti=0x2 Random Access Transmission: seq=4, ra-rnti=0x2 Random Access Transmission: seq=28, ra-rnti=0x2 Random Access Transmission: seq=50, ra-rnti=0x2 Warning: Detected Radio-Link Failure Srsue -- bladeRF> info Board:Nuand bladeRF (bladerf1) Serial #: 54548816f628f3ba6703dc275e26b9d2 VCTCXO DAC calibration: 0x9121 FPGA size:115 KLE FPGA loaded: yes Flash size: 32 Mbit USB bus: 2 USB address: 20 USB speed:SuperSpeed Backend: libusb Instance: 0 bladeRF> version bladeRF-cli version:1.7.1-git-1da130cb libbladeRF version: 2.2.0-git-1da130cb Firmware version: 2.3.2 FPGA version: 0.8.0 (configured by USB host) --- srsenb and srsepc pi@pi:~$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-release [INFO] [B200] Detected Device: B210 [INFO] [B200] Operating over USB 3. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Performing register loopback test... [INFO] [B
[USRP-users] RFNoC graph->Connect and pkt_size and "spp"
Hi, I am using UHD with custom RFNoC images from a custom C++ app. I am having some trouble understanding the implications of "packet sizes". I looked over some previous posts related to this topic (such as "difference between vlen and pkt_size in XML") but still don't quite understand. (Note: I do understand the math relation between samps_per_packet and bytes_per_packet, so no explanation needed there). A few comments: - When constructing an RFNoC graph, the graph->Connect() function includes a "pkt_size" parameter, which defaults to zero, but produces a warning message if the default value is used - When getting an rx or tx streamer, the streamer args include the argument "spp" that the user can provide - Some of the XML files contain an "spp" argument Now, a few questions: - I believe that in the FPGA, the actual packet sizes are determined by the "tlast" wire. Perhaps in the Radio block (as a source), the "spp" argument will actually dictate this "tlast" assertion such that the xbar packet size will match "spp"?? - What is affected by "pkt_size" in the graph->connect() function? I just tried to create a typical RFNoC graph with Radios, DDCs, DUCs, & DmaFIFO and I purposely used unique, arbitrary pkt_sizes for each link in the graph and the graph creation occurred with no warnings and streaming occurred with no warnings. But, this was just a simple test case. - How about with the rx or tx streamers: does the "spp" arg need to match anything (such as the actual packet length determined from "tlast" on the stream coming from say the DDC)? Thanks for any help. Rob ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] (no subject)
Just wanted to follow up on this, because I thought of something in the
shower this morning.
If you compile your block controller as a shared library and you want your
block to be initialized/used with the default UHD apps, you can use
LD_PRELOAD to ensure the block registration happens at runtime. For
instance:
$ LD_PRELOAD=/usr/local/lib/librfnoc-clabs.so uhd_usrp_probe
--args=addr=192.168.10.2
...if your RFNoC controller is registered inside that .so, it will be
loaded and registered for uhd_usrp_probe.
Just a helpful trick if you want to (for instance) use rfnoc_rx_to_file to
test your block, since it has the option to specify a custom block to
insert between the radio and the host.
Nick
On Tue, Apr 9, 2019 at 10:51 AM John Medrano
wrote:
> Thank you.
>
> Using:
>
> set(RFNOC_MYMOD_LIB_OPT -Wl,--whole-archive rfnoc-mylib
> -Wl,--no-whole-archive)
> target_link_libraries(rfnoc_myapp ${RFNOC_MYMOD_LIB_OPT} <...the rest of
> your libs...>)
>
> We are able to use our controller.
>
> On Mon, Apr 8, 2019 at 11:52 AM Nick Foster wrote:
>
>> OK, I looked further into it. UHD registers out-of-tree block controllers
>> using the UHD_RFNOC_BLOCK_REGISTER macro, which under the hood creates a
>> static function and a fixture which calls it before main(). Problem is,
>> when linking your out-of-tree executable, the linker sees that the static
>> fixture is never explicitly called from your program, and it optimizes it
>> out. So your block is never getting registered.
>>
>> There's a number of ways to fix it. I don't know how UHD does it
>> internally. If you are linking your library statically, you can do
>> something like the following in the CMakeLists.txt for the application (not
>> the library):
>>
>> set(RFNOC_MYMOD_LIB_OPT -Wl,--whole-archive rfnoc-mylib
>> -Wl,--no-whole-archive)
>> target_link_libraries(rfnoc_myapp ${RFNOC_MYMOD_LIB_OPT} <...the rest of
>> your libs...>)
>>
>> Using --whole-archive will force the linker to include all the contents
>> of your custom static lib in the application. This includes the static
>> constructor.
>>
>> If you're linking dynamically, this may or may not be a problem for you.
>> If it is, you can do something like
>> set_target_properties(rfnoc_myapp PROPERTIES LINK_WHAT_YOU_USE TRUE)
>>
>> ...which sets the -Wl,--no-as-needed linker flag, indicating to the
>> linker that it should include dynamic libraries that aren't explicitly
>> called. This isn't a great solution as it can result in linking to
>> libraries which really aren't used.
>>
>> You can debug this approach by calling the UHD_STATIC_BLOCK macro in your
>> library and just having it print something to stdout. If you don't see the
>> print in your application, it's not linking static objects correctly.
>>
>> Nick
>>
>> On Mon, Apr 8, 2019 at 8:24 AM John Medrano
>> wrote:
>>
>>> Hello,
>>>
>>> We have verified that library is being linked.
>>>
>>> When we run nm | grep
>>>
>>> We see the following:
>>> 00030310 W _ZNK3uhd7device314get_block_ctrlINS_5rfnoc19>> name>_block_ctrlEEEN5boost10shared_ptrIT_EERKNS2_10block_id_tE
>>> 0023d6e0 V _ZTIN3uhd5rfnoc19_block_ctrlE
>>> 00034b00 V _ZTSN3uhd5rfnoc19_ctrlE
>>>
>>> We continue to get same error.
>>>
>>> We have several blocks and we tried with all of them with same result.
>>>
>>>
>>> On Wed, Mar 27, 2019 at 4:36 PM Nick Foster
>>> wrote:
>>>
Make very sure that your program is actually linking in the library
correctly. Linkers are weird and their interaction with build systems is
often unpredictable and sometimes perverse. Find the symbols in the
compiled library with nm and see that they aren't undefined. Use make
VERBOSE=1 to see the library actually being used.
Nick
On Wed, Mar 27, 2019 at 2:55 PM John Medrano
wrote:
> Thank you for the response.
>
> I have added to CMakeList.txt:
>
> find_library(SLADEW_LIB gnuradio-SLADEW)
> if(NOT SLADEW_LIB)
> message(FATAL_ERROR "SLADEW library not found")
> endif()
>
> add later I add:
>
> target_link_libraries(rfnoc_freqmod ${UHD_LIBRARIES}
> ${Boost_LIBRARIES} ${SLADEW_LIB})
>
> It compiles fine but I still get same messages on start up.
>
> Please advise:
> John
>
>
> On Wed, Mar 27, 2019 at 3:00 PM Nick Foster
> wrote:
>
>> Your program needs to be linked against the library which your custom
>> block controller is compiled into, if in fact your block is using a
>> custom
>> block controller.
>>
>> uhd_usrp_probe and the other UHD utilities aren't linked against the
>> custom library. This isn't generally a problem since the utilities and
>> examples don't make use of your custom block.
>>
>> Nick
>>
>> On Wed, Mar 27, 2019, 1:26 PM John Medrano via USRP-users <
>> usrp-users@lists.ettus.com> wrote:
>>
>>> Hello,
>>>
>>> We have a custom RFNOC block that we have
Re: [USRP-users] Analog filters on ubx-160
On 04/16/2019 09:00 AM, Armin Schmidt via USRP-users wrote: Hallo everyone, I saw, that I can set over the UHD-API analog filters on the USRP's. Were can I find more informations about it? What kind of filters can I set and how? We use x310 USRP's with UBX-160 daugtherboards. Many thanks for your help, Armin Schmidt I think you may be thinking of the filter-bank on the TwinRx. The UBX-160 doesn't have a filter-bank. ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
[USRP-users] Accessing GPS Location Data with Device3
Hello, Using multi_usrp we were able to access our GPS data on X310 device. Using RFNoc Device3 we can set clock and access time, is there a way to also access GPS data? Our system is written in C++. Please advise. Thank you ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
[USRP-users] Analog filters on ubx-160
Hallo everyone, I saw, that I can set over the UHD-API analog filters on the USRP's. Were can I find more informations about it? What kind of filters can I set and how? We use x310 USRP's with UBX-160 daugtherboards. Many thanks for your help, Armin Schmidt ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
