-
Notifications
You must be signed in to change notification settings - Fork 21
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
Expose slave mode for individual board execution #321
Comments
+1 to this. That would be really helpful for my RTO calibration On Sun, Feb 21, 2016 at 11:50 AM, Daniel Sank [email protected]
|
@btchiaro how? I've already written the code (see branch 321) but it would help to know how it will be used. |
I'd be using a dac instead of the Agilent to output my calibration sin On Sun, Feb 21, 2016 at 11:53 AM, Daniel Sank [email protected]
|
Why do you need an explicit setting for slave mode for that? |
I latched on to the "individual board execution" in the thread title. I'm On Sun, Feb 21, 2016 at 11:55 AM, Daniel Sank [email protected]
|
We can already do that :) |
How do I invoke that functionality? On Sun, Feb 21, 2016 at 12:01 PM, Daniel Sank [email protected]
|
You get a board that's not in he board group, write some SRAM to it, run it with loop=True, and Bob's your uncle. We already talked about this a while ago but you wanted to go with the Agilent. |
It could be useful to run a board slaved to something else. To support this, it would be nice to allow setting a board to run as a slave directly.
The text was updated successfully, but these errors were encountered: