-
Notifications
You must be signed in to change notification settings - Fork 15
Specified clk input/outputs #129
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
base: main
Are you sure you want to change the base?
Conversation
Also update the list of compatible hardware for breakout board & pcie host
cjsha
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I made some changes to address your comments and also updated the list of compatible headstages for breakout board & pcie host.
|
I've made some more edits. Maybe they are a bit of a stretch. But my beef with how things are is that it is hard to understand all the connectivity and capatibilities from a single page/pic. And I understand that the bb is providing access to functionality that is ultimately on the controller, but the user sees the bb.. the controller is tucked away. I think updating the pics to v1.6 of the bb and the new bracket and updating some labels will help. We're taking the updated pics tomorrow @cjsha Do you have the editable documents of these pics that have labels? |
|
@cjsha is this correct? |
I don't know anything about the Harp Clock 1 Input label. I've never used that. |
| .. note:: There may be more IO present on the breakout board than is available | ||
| on a particular host board. For instance, :ref:`pcie_host` has two coaxial | ||
| links, but the breakout board provides four. This is is by design. The breakout | ||
| links, but the v1.5beta breakout board provides four. This is is by design. The breakout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you know what they had in mind for this? I don't foresee future compatible host hardware considering that we got rid of those ports on v1.6. I'm wondering if "This is is by design. The breakout is designed to be compatible with future host hardware." should be totally deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 4 ports on the breakout?
The original idea was that that would allow to connect 2 FMC to a single breakout. But of course, that would have been only true for headstages, the A/DIO would have been unconnected. Which would have been even more confusing. That's what we decided that a breakout should match 1:1 the ports on a FMC
|
@jonnew @aacuevas if either of you could confirm the following, we can merge here:
Once I know this, I'll clear the repo of old pics, update the names in the text so they are linked properly, and covert this draft PR to a final one. Thank you! |
|
@ChucklesOnGitHub the final ones are the last 3 pictures you posted, right? They seem correct. |








addresses #120