pothosware / SoapyBladeRF

Soapy SDR plugin for the Blade RF
https://github.com/pothosware/SoapyBladeRF/wiki
23 stars 19 forks source link

SdrAngel SoapySDR and BladeRF #24

Closed GkvJeep closed 5 years ago

GkvJeep commented 5 years ago

Hi . https://github.com/f4exb/sdrangel/issues/248

guruofquality commented 5 years ago

Not entirely sure why. I guess all of the settings will get called and their defaults applied? Does this work for you? https://github.com/pothosware/SoapyBladeRF/commit/bfb06500baa772b0bbf925ef176da74e652e97fb

GkvJeep commented 5 years ago

New problems. jump_to_bootloader next

guruofquality commented 5 years ago

lol, ok i made that jump to bootloader false too: https://github.com/pothosware/SoapyBladeRF/commit/04f798e6a4c76ab1fb2f3cf19af068f9d473781d

GkvJeep commented 5 years ago

This I myself corrected. ;-)) It seems to work. The question is different. [error] bladeRF: Invalid erase setting "false" p.s And change Buffer Count, by default 0.

guruofquality commented 5 years ago

And change Buffer Count, by default 0.

0 is automatic

    SoapySDR::ArgInfo xfersArg;
    xfersArg.key = "transfers";
    xfersArg.value = "0";
    xfersArg.name = "Num Transfers";
    xfersArg.description = "Number of async USB transfers. Use 0 for automatic";
    xfersArg.units = "bytes";
    xfersArg.type = SoapySDR::ArgInfo::INT;
    xfersArg.range = SoapySDR::Range(0, 32);
    streamArgs.push_back(xfersArg);

Invalid erase setting "false"

Its just an error print, not action is actually taken. I think the errors prints are wrong FWIW and should be changed, but they should not stop you at this point. Hopefully :-)

PS, copy paste terminal output, its just text, no need for a screenshot

GkvJeep commented 5 years ago

Hi Josh. Change resetArg.value to false.

// Device reset
SoapySDR::ArgInfo resetArg;
resetArg.key = "reset";
resetArg.value = "true";
resetArg.name = "Reset Device";
resetArg.description = "Reset the device, causing it to reload its firmware from flash.";

Konstantin.

guruofquality commented 5 years ago

Should be fixed now, thank!