In the meantime, I can give you a work-around if you want to follow this wiki page on building the code from source.
First, following the instructions in the linked wiki page, fetch the lastest code from master (changeset 7c0969a44deca4583ce5aa6dc3f8dc32a1ab7a82 at the time of writing).
To start, just go through a normal build to ensure you've got your environment up and running. Without a device plugged in, you can do a bladeRF-cli.exe -e 'version' to see the bladeRF-cli and libbladeRF version info, and verify you're running the newly built code.
Next, change this line from:
Code: Select all
return result;
to
Code: Select all
return 0
Once you've made that change, you should be able to run bladeRF-cli.exe -L X to erase the FPGA from flash, disabling the autoload.
Once that succeeds, restore the above line of code to its original state.
Next, check out this wiki page on where you can store FPGA bitstreams (the .rbf) on your host machine such that libbladeRF will automatically load them for you. If you're always using a host machine with the bladeRF, this solution is faster than the flash-autoload and you can this sort of tricky situation you're currently in. To update the FPGA, you'd just need to replace a file on your host machine.
Best regards,
Jon