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

Clock and trigger controls #8

Open
guruofquality opened this issue May 28, 2016 · 0 comments
Open

Clock and trigger controls #8

guruofquality opened this issue May 28, 2016 · 0 comments

Comments

@guruofquality
Copy link
Contributor

Referencing this issue, SoapyBladeRF should support the clock source API and trigger source API so it can be used to sync multiple bladerfs -- and be used in SoapyMultiSDR.

  • Use the setClockSource() family of calls to wrap the reference clock master/slave api
  • Use the setTimeSource() family of calls to wrap the trigger signal config API
  • Using the new SOAPY_SDR_TRIGGER flag to cause the trigger when working with the streaming api. This usage is documented with the trigger signal api as an example.
  • Use the setHardwareTime(time, "TRIGGER") API to initiate the trigger, automatically sync'ing the time offsets. This will work a lot like the existing BLADERF_GPIO_TIMESTAMP, but for multiple boards. Internally, the boards must do a receive to get the latest timestamp and adjust the offset. This process will have to re-do itself automatically upon sample rates changes (also like the current BLADERF_GPIO_TIMESTAMP method).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant