You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running uhd 3.15-LTS that I compiled myself. The txrx_loopback_to_file example crashes with a failed in pthread_mutex_lock when I have a transmit on one USRP and receive on another. The example runs successfully if the TX and RX device are the same. I've attached valgrind output, in case that is helpful. UPDATE: the issue persists on the master branch as well.
Command used and output:
./txrx_loopback_to_file --tx-args="addr0=192.168.10.2" --rx-args="addr0=192.168.10.3" --tx-freq 1200e6 --rx-freq 1200e6 --tx-ant "TX/RX" --rx-ant "RX2" --tx-rate 2e6 --rx-rate 2e6 --wave-type SINE --wave-freq 1000 --type=float --nsamps=3000000`
Creating the transmit usrp device with: addr0=192.168.10.2...
[INFO] [UHD] linux; GNU C++ version 6.4.0; Boost_107200; UHD_3.15.0.0-7-g8d228dbe
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Creating the receive usrp device with: addr0=192.168.10.3...
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using TX Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N200r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: SBX/CBX RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: SBX/CBX TX
Using RX Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: N200r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: SBXv3 RX
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: SBXv3 TX
Setting TX Rate: 2.000000 Msps...
Actual TX Rate: 2.000000 Msps...
Setting RX Rate: 2.000000 Msps...
Actual RX Rate: 2.000000 Msps...
Setting TX Freq: 1200.000000 MHz...
Actual TX Freq: 1200.000000 MHz...
Setting RX Freq: 1200.000000 MHz...
Actual RX Freq: 1200.000000 MHz...
Checking TX: LO: locked ...
Checking RX: LO: locked ...
Setting device timestamp to 0...
terminate called after throwing an instance of 'boost::wrapexcept<boost::lock_error>'
what(): boost: mutex lock failed in pthread_mutex_lock: Invalid argument
Aborted
However, if I run it such that the TX and RX are the same USRP (--tx-args="addr0=192.168.10.2" --rx-args="addr0=192.168.10.3"), then it runs without issues.
Setup Details
I'm running linux kernel 4.14.52-gentoo (x86_64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz GenuineIntel GNU/Linux), and I've built the code by checking out the 3.15-LTS branch of this repo.
I have two USRP N200 devices, probe info as follows:
I'm running uhd 3.15-LTS that I compiled myself. The txrx_loopback_to_file example crashes with a failed in pthread_mutex_lock when I have a transmit on one USRP and receive on another. The example runs successfully if the TX and RX device are the same. I've attached valgrind output, in case that is helpful. UPDATE: the issue persists on the master branch as well.
Command used and output:
However, if I run it such that the TX and RX are the same USRP (
--tx-args="addr0=192.168.10.2" --rx-args="addr0=192.168.10.3"
), then it runs without issues.Setup Details
I'm running linux kernel 4.14.52-gentoo (x86_64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz GenuineIntel GNU/Linux), and I've built the code by checking out the 3.15-LTS branch of this repo.
I have two USRP N200 devices, probe info as follows:
out.txt
The text was updated successfully, but these errors were encountered: