Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uninitialized value of outputSampleRate variable for RSP1a #31

Open
rmoravcik opened this issue Jan 13, 2021 · 2 comments
Open

Uninitialized value of outputSampleRate variable for RSP1a #31

rmoravcik opened this issue Jan 13, 2021 · 2 comments

Comments

@rmoravcik
Copy link

Hello everyone,

I just received my RSP1a this week and it's working fine on my Ubuntu 20.10 machine. But GQRX is crashing on my RPi3 B+ setup.

I'm using the latest Raspberry Pi OS with self compiled gnuradio-3.8.1, the latest SoapySDRPlay3 and GQRX.

It looks like GQRX is trying to get sample rate during selection of new input device (https://github.com/csete/gqrx/blob/07722f21d0be2b63ae4e5d6f34601ece8625afe6/src/applications/gqrx/receiver.cpp#L221) but SoapySDRPlay3 is returning some uninitialized value different from 0, so GQRX will try to set back this value as sample rate.

And this will cause an crash, because it's not supported sample rate value.

Initializing the value of outputSampleRate variable (for example to 2MHz) will fix the issue for me. Something similar is already done for RSPDuo here:

outputSampleRate = defaultRspDuoOutputSampleRate;
.

Thank you,
Roman

@rmoravcik rmoravcik changed the title Uninitialized outputSampleRate for RSP1a Uninitialized value of outputSampleRate variable for RSP1a Jan 13, 2021
@fventuri
Copy link
Collaborator

Thanks for your feedback @rmoravcik

The issue you are seeing should be addressed by this commit on the support_for_serial_keyword branch: e2ec213

Since that branch has several fixes over the master branch, I'd suggest you give it a try with your RSP - you can find it here: https://github.com/pothosware/SoapySDRPlay3/tree/support_for_serial_keyword

I plan to merge the code from that branch into master as soon as some of the lingering issues with crashes and freezes are solved; see the full discussion here: #23

Franco

@rmoravcik
Copy link
Author

Thank you for your answer @fventuri. That fix for GQRX is exactly solving my problem.

Roman

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants