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

Fix quick_tune parameter error when calling set_frequency on BladeRF1 #883

Closed
wants to merge 4 commits into from
Closed

Conversation

ratzrattillo
Copy link

Fixes the following error when XB-200 board is attached:

[ERROR @ host/libraries/libbladeRF/src/board/bladerf1/bladerf1.c:2398] Consider supplying the quick_tune parameter to bladerf_schedule_retune() when the XB-200 is enabled.

Use quicktune parameters when calling schedule_retune with attached XB-200
}

status = dev->board->schedule_retune(dev, ch, BLADERF_RETUNE_NOW, 0, &qt);
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any chance this right curly bracket } can be on the same line as the else statement?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm trying to make sense of this. If the XB200 is attached, how does bladerf_get_quick_tune() return a bladerf_quick_tune that is for the correct new frequency?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant to fix this issue: #882
But i do not have equipment here to retest at the moment. Maybe i do not understand the error correctly.

@rghilduta
Copy link
Collaborator

Thanks for the submission! Looks good, finally got around to testing! Question, can you please correct this quick stylist issue? c8f72ab#r1119705939

@ratzrattillo
Copy link
Author

Feel free to edit my merge request at any time. I am not picky in that regard ;)

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

Successfully merging this pull request may close these issues.

2 participants