Hi James, There are a couple of reasons that you might require a reset when connecting your HackRF.
1) USB power saving - this is enabled by default on many laptops and causes some issues with a device that has previously been connected. You can disable this by following instructions here: https://github.com/mossmann/hackrf/wiki/FAQ#power-saving-and-usb-autosuspend 2) There was an issue with start up on some boards that caused them not to come up first time. It primarily affected HackRFs from a specific manufacturing run and we were able to fix it in software. The fix was included in our 2018.01.1 release here: https://github.com/mossmann/hackrf/releases/tag/v2018.01.1 The fix is the only change between the 2017.02.1 and 2018.01.1 releases, so you can grab the binary firmware from the release archive and flash it without having to update your host tools. If you want to know more about the second issue, Mike wrote an in depth blog post on it: https://greatscottgadgets.com/2018/02-28-we-fixed-the-glitch/ There could be other issues affecting your system, but these are the two that spring to mind immediately. Thanks, Dominic On Fri, 14 Sep 2018 at 12:38, James Brown <j...@seti.net> wrote: > Is there any reason a push of the reset button should be required when > connecting to the USB system? > Would a firmware update fix this? > Found HackRF board 0: > USB descriptor string: 0000000000000000285067dc2d0f3f4b > Board ID Number: 2 (HackRF One) > Firmware Version: 2017.02.1 > Part ID Number: 0xa000cb3c 0x005c4f6a > Serial Number: 0x00000000 0x00000000 0x285067dc 0x2d0f3f4b > _______________________________________________ > 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
