(if your Python install script (easy_install / pip) canât find yaml - you This might be obvious for some, but I had to find out the hard wayâŠĢ. Make sure when you download libopencm3 from Hereâs some notes (maybe useful for others trying to do this) and oneġ. Iâve just managed to install the toolchain for building custom firmware Here’s the relevant line in /blinky/build/CMakeFiles//build.makeĭfu-suffix -vid=0x1fc9 -pid=0x000c -did=0x0 -s 0 -a _tmp.dfu it lists its options, so somehow it seems to be invoked in a wrong way. dfu version I only get the help message from dfu-suffix, i.e. The steps are explained in the Readme.Īfter that I got a working blinky.bin, hooray! The build system uses cmake so you have to do that first. Just typing ‘make’ as the Wiki suggests () When you cd into the blinky folder for your first build: (if your Python install script (easy_install / pip) can’t find yaml - you have to pick one of the packages that are listed when doing a search for it. Make sure your Python install includes it.
This might be obvious for some, but I had to find out the hard way…Ģ. Make sure when you download libopencm3 from that it ends up in the libopencm3 folder of the HackRF distribution Here’s some notes (maybe useful for others trying to do this) and one problem:ġ.
I’ve just managed to install the toolchain for building custom firmware under Mac OS X. Out of date, the following has a very detailed gist of what you need to
If you were using Ubuntu/Debian/RPi to upgrade the firmware, although How they install the firmware in the factory see:
It is not quite as easy as just the above two commands, it is To a working state (This mode only needs to be used if "lsusb" does notĭisplay the HackRF vendor and product ID "1d50:6089" when plugged into Hardcoded into a ROM inside the ARM CPU that you can return your HackRF (confirm that the upgrade worked, that the version is what you expected)Īnd even if you messed up really badly, there is a special DFU mode (when it is finished with no errors - unplugging the HackRF and plugging $ hackrf_cpldjtag -x firmware-bin/hackrf_cpld_default.xsvf (Once it has finished with no errors - unplugging the HackRF and $ hackrf_spiflash -w firmware-bin/hackrf_one_usb_rom_to_ram.bin Should be working fine, so it should be safe to proceed) "|hackrf_open() failed: HACKRF_ERROR_NOT_FOUND (-5)"|) then your HackRF (if both of the above commands exited with no error messages (e.g. If "hackrf_info" works then you have some versionĬommands using the firmware binary release would be:Ĭonfirm that your hackrf works before attempting to upgrade the firmware: (CPLD code) and "hackrf_one_usb_rom_to_ram.bin" (ARM firmware)Ħ> Compile and install the tools under Linux as described here (If you Upgrading the firmware is not rocket science, it is basically twoĬommands one to upgrade the firmware and one to upgrade the CPLD code.ģ> download the latest release (at the time of writing this is "releaseĢ015.07.2", so I'm clicking on "hackrf-2015.07.2.zip" )ĥ> the binary firmware and binary CPLD are in the firmware-bin folderįor a normal upgrade these would be called "hackrf_cpld_default.xsvf"