I have a Hackrf in mint condition - for various reasons with busy schedule I
could not use it.
I would like to sell it now - if any body interested - please let me know.
73
Tony
-----Original Message-----
From: hackrf-dev-requ...@greatscottgadgets.com
Sent: Friday, May 05, 2017 10:59 AM
To: hackrf-dev@greatscottgadgets.com
Subject: HackRF-dev Digest, Vol 56, Issue 2
Send HackRF-dev mailing list submissions to
hackrf-dev@greatscottgadgets.com
To subscribe or unsubscribe via the World Wide Web, visit
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
or, via email, send a message with subject or body 'help' to
hackrf-dev-requ...@greatscottgadgets.com
You can reach the person managing the list at
hackrf-dev-ow...@greatscottgadgets.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of HackRF-dev digest..."
Today's Topics:
1. Re: Troubles with multiple HackRFs (Cinaed Simson)
2. Re: Troubles with multiple HackRFs (Cinaed Simson)
----------------------------------------------------------------------
Message: 1
Date: Thu, 4 May 2017 19:48:04 -0700
From: Cinaed Simson <cinaed.sim...@gmail.com>
To: hackrf-dev@greatscottgadgets.com
Subject: Re: [Hackrf-dev] Troubles with multiple HackRFs
Message-ID: <49dc3468-71f9-7c2b-b705-70fc2c14e...@gmail.com>
Content-Type: text/plain; charset=windows-1252
On 05/03/2017 09:56 AM, Fernando wrote:
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'm using 2 HackRF's and the udev rules are installed.
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.
The problem arises when you have 2 HackRF's plugged in, and one is being
use and the other one isn't.
If hackrf_info encounters the device being used first, it exits with an
error and it doesn't query the other device.
If hackrf_info encounters the device not being used first, it prints out
the info for the device, moves on to the second device and then
generates the normal busy error.
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@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
------------------------------
Message: 2
Date: Thu, 4 May 2017 20:14:46 -0700
From: Cinaed Simson <cinaed.sim...@gmail.com>
To: hackrf-dev@greatscottgadgets.com
Subject: Re: [Hackrf-dev] Troubles with multiple HackRFs
Message-ID: <6683ee47-f73b-8e4d-7c7d-0ffdc64e1...@gmail.com>
Content-Type: text/plain; charset=windows-1252
On 05/03/2017 09:56 AM, Fernando wrote:
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.
The serial numbers are different and they are not zero - although
there's a large zero prefix.
The "Device Arguments" field in gnuradio is the last 8 characters of the
serial number displayed by hackrf_info, e.g.,
hackrf=c894567e
where
c894567e
was extracted from the serial number
Serial number: 0000000000000000406464c8c894567
If you can't get them both to work at the same time, then you need to
post the output of
hackrf_info
while both HackRF's are not being used.
-- Cinaed
Any ideas ?
Thanks in advance for your help,
Pierre.
_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
------------------------------
Subject: Digest Footer
_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
------------------------------
End of HackRF-dev Digest, Vol 56, Issue 2
*****************************************
_______________________________________________
HackRF-dev mailing list
HackRF-dev@greatscottgadgets.com
https://pairlist9.pair.net/mailman/listinfo/hackrf-dev
