discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss-gnuradio] UHD error: _ZN3uhd6device4findERKNS_13device_addr_tEN


From: Zamrath Nizam
Subject: [Discuss-gnuradio] UHD error: _ZN3uhd6device4findERKNS_13device_addr_tENS0_15device_filter_tE
Date: Wed, 18 Mar 2015 16:21:37 +0530

Hi all, 

I have recently installed UHD and GNURadio on Bananapi (armhf) board adding  "deb http://ftp.de.debian.org/debian jessie main" in "/etc/apt/sources.list".

Downloaded GNURadio from "https://packages.debian.org/jessie/armhf/gnuradio/download"
dpkg -i gnuradio_3.7.5-5_armhf.deb
apt-get update

Downloaded UHD from "https://packages.debian.org/wheezy/armhf/uhd-host/download"
dpkg -i uhd-host_3.4.2-1_armhf.deb
apt-get -f install

When I install OpenBTS, built was errored since UHD was not picked up. (uhd.pc was not in "/usr/local/lib/pkgconfig"). 
Therefore, I had to install uhd-master from ettus research git repo and built. And then OpenBTS was built without a problem.

After connecting USRP N210, even though ping process is also okay, 

"uhd_find_devices" gives,
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
uhd_find_devices: symbol lookup error: uhd_find_devices: undefined symbol: _ZN3uhd6device4findERKNS_13device_addr_tENS0_15device_filter_tE

"uhd_usrp_probe" gives,
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
uhd_usrp_probe: symbol lookup error: uhd_usrp_probe: undefined symbol: _ZN3uhd6device4makeERKNS_13device_addr_tENS0_15device_filter_tEj

When running './OpenBTS'",
ALERT 3069485584 10:17:51.9 TRXManager.cpp:434:powerOff: POWEROFF failed with status -1
linux; GNU C++ version 4.9.1; Boost_105500; UHD_003.007.003-0-unknown
Using internal clock reference
./transceiver: symbol lookup error: ./transceiver: undefined symbol: _ZN3uhd6device4findERKNS_13device_addr_tENS0_15device_filter_tE
EMERG 3065672784 10:17:52.5 OpenBTS.cpp:156:startTransceiver: Transceiver quit with status 32512. Exiting.

I have erased the memory and proceeded again with caution but the result was same. Could  anyone please suggest me a resolution? 

Thanks.

Best,
Zamrath Nizam

reply via email to

[Prev in Thread] Current Thread [Next in Thread]