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

FMC Address Pins #19

Closed
kaolpr opened this issue Jun 4, 2020 · 7 comments
Closed

FMC Address Pins #19

kaolpr opened this issue Jun 4, 2020 · 7 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@kaolpr
Copy link
Member

kaolpr commented Jun 4, 2020

Both FMC slots have the same GA address. Connect GA1 of FMC2 to 3V3PAUX.

@kaolpr kaolpr added the bug Something isn't working label Jun 4, 2020
@kaolpr kaolpr added this to the AFCZ v1.1 milestone Jun 4, 2020
@gkasprow
Copy link
Collaborator

gkasprow commented Jun 5, 2020

why? We have I2C switch so why not to keep the same addressing?

@kaolpr
Copy link
Member Author

kaolpr commented Jun 8, 2020

Indeed ANSI/VITA 57.1 in rule 5.82 states that GA codes should be unique with IPMI I2C bus. However, I see no reason not to differentiate the slots. It feels like more natural to me. After all, these GA pins are there for a reason and one can expect GA codes to be different in two slots, though specification does not impose that.

Is there any particular reason to do it in the way it is currently implemented?

@gkasprow
Copy link
Collaborator

gkasprow commented Jun 8, 2020

So far the only reason was that some ICs used on FMCs do not support 4 unique addresses that can be implemented in an easy way. Some ICs, especially from Texas have address pins that support multi-level logic. When building a multi-level I2C mux tree it's nice to have the same chips under the same addresses, but I'm not very fixed on that idea.

@filipswit
Copy link
Collaborator

How about adding resistors to GA1 of FMC2?

@gkasprow
Copy link
Collaborator

gkasprow commented Jun 9, 2020

that's OK. But as I said, I personally don't really care if we do it one or another way.

@gkasprow
Copy link
Collaborator

gkasprow commented Jun 9, 2020

I used geographical addressing in 16-FMC carrier box for JET experiment. It was somehow helpful to identify which FMC was which :)
https://www.ohwr.org/project/sac-18-fmc/wikis/home

@kaolpr
Copy link
Member Author

kaolpr commented Jun 10, 2020

@filipswit GA1 of FMC2 should be connected to 3P3VAUX according to Rule 5.83.

filipswit pushed a commit that referenced this issue Jun 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants