myriadrf / libxtrx

High-level XTRX API library
Apache License 2.0
28 stars 27 forks source link

Trouble opening devices using xtrx_open #18

Open itchy5 opened 5 years ago

itchy5 commented 5 years ago

I'm not able to open a specific device using osmocom in GNU Radio or Soapy in python using dev=pcie:///dev/xtrx0 (or pcie:///dev/xtrx1). In GNU Radio it fails after xtrx_open_list with no error output. In Soapy it simply defaults to xtrx0 every time. If I leave dev empty everything works fine, transmit, receive, tuning, etc. Additionally, xtrx_fft example works fine with either device, which is odd.

My goal here is to get two xtrx devices receiving together (4 channel mimo).

EDIT: I've manually compiled all source repos since the images repo isn't properly tracking the latest commits. However, Soapy is still defaulting to xtrx0. Here is what I'm using for initialization in python: args = dict(dev="/dev/xtrx1", loglevel="2") print args sdr = SoapySDR.Device(args)

and the corresponding output: {'loglevel': '2', 'dev': '/dev/xtrx1'} 10:48:09.368261 DEBUG: xtrxllpciev0_discovery:264 [PCIE] pcie: Found 'pcie:///dev/xtrx0' 10:48:09.368292 DEBUG: xtrxllpciev0_discovery:264 [PCIE] pcie: Found 'pcie:///dev/xtrx1' [INFO] Make connection: 'pcie:///dev/xtrx0' CPU Features: SSE2+ SSE4.1+ AVX- FMA- [INFO] Created: 'pcie:///dev/xtrx0'

If I manually set const std::string& dev = "/dev/xtrx1"; in SoapyXTRX.cpp I correctly initialize the second device. [INFO] Created: '/dev/xtrx1'

curtcorum commented 3 years ago

Please see #20