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 singleRX example to work correctly with LimeSDR Mini V2 #389

Merged
merged 1 commit into from Jan 5, 2024

Conversation

sergeyvfx
Copy link
Contributor

The issue this commit fixes is that running singleRX example does not show any samples streaming, and logs shows: RX data rate: 0 MB/s.

The fix follows the initialization order in basicRX.cpp where the TX channel is enabled alongside with the RX channel right after the LMS_Init(). With this fix running singleRX example shows samples streamed: RX data rate: 32.1454 MB/s.

This is a bit counter-intuitive API from developers perspective (as in, intuitively question is why TX channel is needed for RX-only application). So it does feel like that perhaps the fix needs to be done somewhere deeper in the driver or in gateware to increase clarity of API. However, that'd be a deeper change, if it happens. In any case, until such possible change the proposal is to fix the issue in the same way as it is done in the other example.

The motivation to get the example fixed is because this is something that new LimeSDR users run into as some of their first steps, so having examples properly working solves initial confusion and possible frustration.

The issue this commit fixes is that running singleRX example does
not show any samples streaming, and logs shows: RX data rate: 0 MB/s.

The fix follows the initialization order in basicRX.cpp where the
TX channel is enabled alongside with the RX channel right after
the LMS_Init(). With this fix running singleRX example shows samples
streamed: RX data rate: 32.1454 MB/s.

This is a bit counter-intuitive API from developers perspective (as
in, intuitively question is why TX channel is needed for RX-only
application). So it does feel like that perhaps the fix needs to be
done somewhere deeper in the driver or in gateware to increase
clarity of API. However, that'd be a deeper change, if it happens.
In any case, until such possible change the proposal is to fix the
issue in the same way as it is done in the other example.

The motivation to get the example fixed is because this is something
that new LimeSDR users run into as some of their first steps, so
having examples properly working solves initial confusion and possible
frustration.
@rjonaitis rjonaitis merged commit e353507 into myriadrf:master Jan 5, 2024
4 checks passed
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.

None yet

2 participants