-
Notifications
You must be signed in to change notification settings - Fork 7
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
Comments
why? We have I2C switch so why not to keep the same addressing? |
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? |
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. |
How about adding resistors to GA1 of FMC2? |
that's OK. But as I said, I personally don't really care if we do it one or another way. |
I used geographical addressing in 16-FMC carrier box for JET experiment. It was somehow helpful to identify which FMC was which :) |
@filipswit GA1 of FMC2 should be connected to |
Both FMC slots have the same GA address. Connect
GA1
of FMC2 to3V3PAUX
.The text was updated successfully, but these errors were encountered: