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

Problem with v3.1 on Raspberry Pi v4 and Raspbian Buster #144

Closed
mglimmer opened this issue Feb 27, 2020 · 3 comments
Closed

Problem with v3.1 on Raspberry Pi v4 and Raspbian Buster #144

mglimmer opened this issue Feb 27, 2020 · 3 comments

Comments

@mglimmer
Copy link

I have tried building the new 3.1 version on a RPi 4 with Raspbian Buster using the same method I used with v3.01 and I am having a problem. The build appears to be successful, but when testing it using rtl_airband -f, it returns to a command prompt instead of going to the waterfall display.

The output before returning to the command prompt is:
Detached kernel driver
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
Allocating 10 zero-copy buffers

Any suggestions what I am doing wrong?

@szpajder
Copy link
Collaborator

szpajder commented Feb 28, 2020 via email

@mglimmer
Copy link
Author

Thank you! Moving the FFT from the GPU to the CPU resolved all of the problems.

I used the option PLATFORM=armv8-generic, because the RPi4 should support 64-bit.

If you update the WIKI to note the RPi4 changes, you may also want to note the library dependency that is needed in Raspbian to run the FFT code on the CPU:
sudo apt-get install libfftw3-dev

@szpajder szpajder changed the title Problem with v3.1 on Raspbian Buster Problem with v3.1 on Raspberry Pi v4 and Raspbian Buster Feb 29, 2020
@szpajder
Copy link
Collaborator

Wiki has been updated.

Closing.

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