The problem appears when using the hackrf for TX even if there is only one hackrf plugged. Osmocon source makes the hackrf work with hackrf=0 or even leving the field in blank, but osmocon sink fails with the same parameters. However using the serial number works as much for one as for the other.
thanks for the help El 27/02/17 a las 19:38, Chris Kuethe escribió: > try using the hackrf's serial number (d291f43, 5671743) rather than > the index (0, 1) > > On Sat, Feb 25, 2017 at 5:26 AM, Fernando Peral > <ferna...@samara.com.es <mailto:ferna...@samara.com.es>> wrote: > > Hi! > > > I have a HackRF. I'm testing it. > > It works well receiving in GRC with osmocon source, but when > trying to transmit with osmocon sink I receive an error > > FATAL: Failed to open HackRF device (-5) HACKRF_ERROR_NOT_FOUND > > > It is like if it were a problem of permissions, but it is not, the > HackRF is working great receiving. > > > I Have tried with two HackRF, one transmiting one receeiving, this > it the block diagram > > I have updated the firmware of both of them to the last one (2017-02) > > > this is the error output > > Using Volk machine: sse4_a_64_orc > > gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.9 > > built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri > hackrf bladerf rfspace airspy redpitaya > > Using HackRF One with firmware 2017.02.1 > > gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.9 > > built-in sink types: uhd hackrf bladerf redpitaya file > > Number of USB devices: 19 > > USB device 1d50:6089: 000000000000000071c469c82d291f43 skip > > USB device 1d50:6089: 000000000000000071c469c825671743 skip > > > FATAL: Failed to open HackRF device (-5) HACKRF_ERROR_NOT_FOUND > > > Trying to fill up 1 missing channel(s) with null sink(s). > > This is being done to prevent the application from crashing > > due to gnuradio bug #528. > > > The first one is receiving (numer 1), the second (number 0) is the > one wich fails > > > Using ubuntu 16.04 LTS. > > > Any clues? > > > regards > > > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio> > > > > > -- > GDB has a 'break' feature; why doesn't it have 'fix' too?
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
