[Hackrf-dev] Troubles with multiple HackRFs

[Fernando]

This problem  (hackrf_open() failed: HACKRF_ERROR_LIBUSB (-1000))  shows
when you have no rights to access the HW, it is necessary to set udev
rules as here ( https://github.com/mossmann/hackrf/wiki/FAQ ) but if you
are using one hackrf that is not your problem.
I have received that error too when using two hackrf with osmocon
source/sink, one is ercogniced an the other isn't  (using hackrf=0 and
hackrf=1), but using the serialnumber
(hackrf=000000000000000071c469c825671743)

hackrf_info returns (now just one hack plugged)

andromeda:/etc/udev/rules.d # hackrf_info
hackrf_info version: 2017.02.1
libhackrf version: 2017.02.1 (0.5)
Found HackRF
Index: 0
Serial number: 000000000000000071c469c825671743
Board ID Number: 2 (HackRF One)
Firmware Version: 2017.02.1 (API:1.02)
Part ID Number: 0xa000cb3c 0x00494758
andromeda:/etc/udev/rules.d #


So, yes, it works with FW 2017.02.1.

regards


El 03/05/17 a las 16:57, Pierre AVITAL escribió:
> Hello,
>
> I have been trying to use 2 HackRFs to try to get a full duplex
> working as well as to test performance requirements for multiple
> HackRF handling.
>
> But I can't get both to function at the same time, as it appears
> nothing HackRF related will work once one of them is in use.
> As far as I've tested, once a hackrf is used in any way (my method was
> using osmosdr's osmocom_fft), any use of libhackrf (even hackrf_info)
> will result in the following :
> hackrf_open() failed: HACKRF_ERROR_LIBUSB (-1000)
>
> Using dmesg, I've found that both hackrf's have the same serial, but
> that being 0, I doubt any hackrfs have different serials, so I don't
> think that's the problem.
> I've tried reinstalling libusb and libhackrf to no avail.
>
> Any ideas ?
>
> Thanks in advance for your help,
> Pierre.
>
>
> _______________________________________________
> HackRF-dev mailing list
> HackRF-dev at greatscottgadgets.com
> https://pairlist9.pair.net/mailman/listinfo/hackrf-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist9.pair.net/pipermail/hackrf-dev/attachments/20170503/efbf3233/attachment.html>