Hackrf One issue
jakwnd
Framework Topology Connect Error: Pothos::Topology::commit(): Framework Topology Connect Error: SDRSource1.activate(): Exception: Failed to open HackRF device (-5) HACKRF_ERROR_NOT_FOUND
[21:07:41.609000] : Using
[21:07:41.610000] : HackRF One with firmware 2014.08.1
So I was a little confused because its telling me 2 different things, that it cannot open the device and that it is using that same device. I am running Windows 10 64bit. I don't see any input or output from the Hackrf itself when a block diagram is running, however I can use the hackrf tools in PothosSDR\bin\.
Also this is the output from pothosUtil:
C:\Program Files\PothosSDR\bin>PothosUtil.exe --self-tests
2016-01-20 16:16:20 Pothos.PluginLoader.load: Plugin Module Error: Pothos::PluginModule(C:\Program Files\PothosSDR\lib\Pothos\modules\proxy\environment\PythonSupport.dll): failed safe load
Testing /object/tests/test_object_equals... success!
Testing /object/tests/test_object_value... success!
Testing /object/tests/test_object_throw... success!
Testing /object/tests/test_object_mutable... success!
Testing /object/tests/test_object_mutable_copy_assigns... success!
Testing /object/tests/test_convert_numbers... success!
Testing /object/tests/test_convert_complex... success!
Testing /object/tests/test_convert_vectors... success!
Testing /object/tests/test_serialize_null... success!
Testing /object/tests/test_serialize_int... success!
Testing /object/tests/test_serialize_obj... success!
Testing /object/tests/test_compare_to... success!
Testing /framework/tests/test_buffer_chunk_serialization... success!
Testing /framework/tests/test_buffer_convert... success!
Testing /framework/tests/test_dtype_attrs... success!
Testing /framework/tests/test_dtype_throws... success!
Testing /framework/tests/test_dtype_equality... success!
Testing /framework/tests/test_dtype_sizes... success!
Testing /framework/tests/test_dtype_name... success!
Testing /framework/tests/test_dtype_dimensions... success!
Testing /framework/tests/test_auto_ports... success!
Testing /framework/tests/test_generic_shared_buffer... success!
Testing /framework/tests/test_circular_shared_buffer... success!
Testing /framework/tests/test_circular_buffer_manager... success!
Testing /framework/tests/test_generic_buffer_manager... success!
Testing /framework/tests/test_workers... success!
Testing /framework/tests/test_activate_throw... success!
Testing /framework/tests/test_label_constructor... success!
Testing /framework/tests/test_thread_pool... success!
Testing /framework/tests/topology/test_simple_passthrough... success!
Testing /framework/tests/topology/test_nested_passthrough... success!
Testing /framework/tests/topology/test_uneven_passthrough... success!
Testing /framework/tests/topology/test_multisrc_passthrough... success!
Testing /framework/tests/topology/test_multidst_passthrough... success!
Testing /framework/tests/topology/test_shared_passthrough... success!
Testing /framework/tests/topology/test_independent_passthrough... success!
Testing /proxy/remote/tests/test_inception... success!
Testing /proxy/remote/tests/test_remote... success!
Testing /proxy/remote/tests/test_server... success!
Testing /proxy/remote/tests/test_multithread_safe... success!
Testing /proxy/managed/tests/test_containers... success!
Testing /proxy/managed/tests/test_opaque_calls... success!
Testing /proxy/managed/tests/test_wildcard_calls... success!
Testing /proxy/managed/tests/test_inheritance... success!
Testing /callable/tests/test_callable_null... success!
Testing /callable/tests/test_callable_meta... success!
Testing /callable/tests/test_callable_with_methods... success!
Testing /callable/tests/test_callable_with_functions... success!
Testing /callable/tests/test_callable_constructors... success!
Testing /callable/tests/test_callable_overloaded... success!
Testing /callable/tests/test_callable_bind... success!
Testing /callable/tests/test_callable_throwing... success!
Testing /plugin/tests/test_plugin_path... FAIL!
Testing /plugin/tests/test_plugin_registry... ^C
Josh Blum
On 01/20/2016 01:56 PM, jakwnd wrote:
> So I'm trying to use the Hackrf one with Pothos and I have Pothos
> installed, and the SoapySDRUtil can identify and locate the Hackrf except
> that when i try and use it with Pothos I get this in the console:
>
> Framework Topology Connect Error: Pothos::Topology::commit(): Framework
> Topology Connect Error: SDRSource1.activate(): Exception: Failed to open
> HackRF device (-5) HACKRF_ERROR_NOT_FOUND
>
>
> [21:07:41.609000] : Using
> [21:07:41.610000] : HackRF One with firmware 2014.08.1
>
>
> So I was a little confused because its telling me 2 different things, that
> it cannot open the device and that it is using that same device. I am
> running Windows 10 64bit. I don't see any input or output from the Hackrf
> itself when a block diagram is running, however I can use the hackrf tools
> in PothosSDR\bin\.
>
print "HackRF One with firmware" should only be possible from GrOsmoSDR
or older SoapyOsmo.
And so hackrf used to be supported under SoapyOsmo but that didnt work
very well at all -- so we ended up giving it its own dedicated
SoapyHackRF. Any recent PothosSDR installer should have SoapyHackRF and
hack support disabled in SoapyOsmo. And you wouldn't see that print.
I'm guessing that this is just an out of date installer and its
something that we fixed. My suggestion is to uninstall and grab the
latest. I hope that helps.
-josh
Note to self: The SoapyHackRF is actually quite silent when its opening
the device. A think a similar log print would be reassuring.