Assistance Required: HackRF One

[s-awal]

Have you read the HackRF documentation?

no

What outcome were you hoping for?

I recently purchased a HackRF One and am experiencing issues setting it up on my Windows 11 PC. While I have successfully installed the drivers and attempted to connect the device, my PC does not recognize the HackRF One, and I am unable to upload any code to it.

The steps I have taken so far:

1. Connected the HackRF One directly to a USB port on my PC.
2. Installed the required drivers using Zadig.
3. Attempted to use GNU Radio on both native Windows 11 and through Windows Subsystem for Linux (WSL).

Unfortunately, none of these steps have resolved the issue. I would greatly appreciate your guidance to help me get the device running correctly. Could you please provide detailed troubleshooting steps or confirm if there are specific compatibility issues with Windows 11 or WSL? Additionally, let me know if any further information about my setup is required. Thank you for your time and support.

What outcome actually happened?

I cannot find hackrf device

What operating systems are you seeing the problem on?

windows 11 and WSL-2 (ubuntu)

What is the output of hackrf_info?

hackrf_info version: 2023.01.1
libhackrf version: 2023.01.1 (0.8)
No HackRF boards found.

Are you using any third-party software?

N/A

Are you using any third-party hardware?

N/A

[Sasszem]

Have you tried different USB cables? Some charger-only cables have fooled me in the past.

Where you ran hackrf_info? Inside WSL or outside it?

[s-awal]

I have tried using different USB cables, including the one that came with the box. I ran hackrf_info inside WSL.

…

________________________________ From: László Baráth ***@***.***> Sent: Saturday, November 30, 2024 3:53 PM To: greatscottgadgets/hackrf ***@***.***> Cc: Md Sadik Awal ***@***.***>; Author ***@***.***> Subject: Re: [greatscottgadgets/hackrf] Assistance Required: HackRF One (Issue #1511) Note: This message originated from outside the FIU Faculty/Staff email system. Have you tried different USB cables? Some charger-only cables have fooled me in the past. Where you ran hackrf_info? Inside WSL or outside it? — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/greatscottgadgets/hackrf/issues/1511*issuecomment-2509313674__;Iw!!FjuHKAHQs5udqho!M2htWzZ3eLAs1bvG6C6mVsilMuroqMHjVG8rtSZYBrxPUylg_tJHMU2a561n7KGqAjMOfDLu4zRCCypOj5SbzxqwW-s$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/BD25HSQWH33CSQ4PVBBXHST2DIQU5AVCNFSM6AAAAABSTQB7XOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGMYTGNRXGQ__;!!FjuHKAHQs5udqho!M2htWzZ3eLAs1bvG6C6mVsilMuroqMHjVG8rtSZYBrxPUylg_tJHMU2a561n7KGqAjMOfDLu4zRCCypOj5Sb5SluQkQ$>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[miek]

Running inside WSL complicates things because you have to do some extra setup to pass the device through to WSL, otherwise it won't show up even if it's working correctly.

When you plug in the device, does Windows play the usual sound to indicate a device has been connected? Does it show up in Device Manager?

If so, you should be able to run hackrf_info natively (pre-built tools can be downloaded from the latest CI run: https://github.com/greatscottgadgets/hackrf/actions/runs/12398431913#artifacts if needed).