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.

Sign up for GitHub

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

Jump to bottom

FMC VIO_B_M2C not connected #32

Closed
kaolpr opened this issue Oct 4, 2022 · 2 comments
Closed

FMC VIO_B_M2C not connected #32

kaolpr opened this issue Oct 4, 2022 · 2 comments
Milestone
v1.2

Comments

@kaolpr
Copy link
Member

kaolpr commented Oct 4, 2022

It looks like a wider problem with our open-source FMC ecosystem. VIO_B_M2C should be provided by the mezzanine and be used to supply IO for HBxx signals. See VITA57 rule 6.8: "The carrier card shall utilize VIO_B_M2C as the supply voltage to the FPGA to provide the signaling standards on HBxx_y signals."

Now, Shuttler leaves those lines floating.

Most of OHWR-related carriers just ignore those lines (AFC3, AFC4, AFCK, AFCKU) and supply HB IO from VADJ (or fixed 1.8V). DIOT FMC Carrier do have an assembly option to choose between VIO_B_IO and fixed 1.8V, but EEM FMC Carrier does not.

Everything is fine as long as you use affected FMC with one of those carriers. However, trying to use it with some FMC-complient carrier (e.g. Digilent Genesys2 orTrenz TEF1001), results in unpowered (or rather partially powered via signal lines) FPGA bank.

Also trying to use FMC-complient FMC with one of those carriers may lead to having incompatibility of the electric levels.

This can be easily solved with passing through VADJ to VIO_B_M2C as an assembly variant.
@kaolpr kaolpr mentioned this issue Oct 4, 2022
Open
@kaolpr kaolpr mentioned this issue Nov 25, 2022
Open
@kaolpr kaolpr added this to the v1.1 milestone Mar 20, 2023
@maciejprzybysz maciejprzybysz modified the milestones: v1.1, v1.2 Jan 22, 2024
@maciejprzybysz maciejprzybysz mentioned this issue Jan 22, 2024
Open
14 tasks
maciejprzybysz added a commit that referenced this issue Mar 14, 2024
@maciejprzybysz
v1.2rc1
93f2f98 
Issues fixed:

- [x]  TEMP_ALARM does not turn off N3V0A PS #41
- [x]  [FMC_DAC_PSU] Wrong PN in R130 #37
- [x]  FMC VIO_B_M2C not connected #32
- [x]  HW issues #30 (remove R12/R13)
- [x]  Schematics details #27
- [ ]  AFE AUX PSU connection crossed #35 -> (AUX PSU will be changed accordingly)
- [x]  mechanical issues #31
- [x]  Shuttler analog bandwidth  #36 -> 33pF caps -> ~12MHz BW.

Other fixes:

- [x] Shuttler FMC stackup adjusted
- [x] Added missed templates
- [x] P_version project parameter added
- [x] Shuttler AFE stackup table added
- [x] Shuttler AFE - FTG added
- [x] Shuttler AFE - keepout for NPTH added
@gkasprow
Copy link
Member

shouldn't we set R12 as DNP?

maciejprzybysz added a commit that referenced this issue Apr 3, 2024
@maciejprzybysz
v1.2rc2
11c4cc7 
Issues fixed:

- [x]  TEMP_ALARM does not turn off N3V0A PS #41
- [x]  [FMC_DAC_PSU] Wrong PN in R130 #37
- [x]  FMC VIO_B_M2C not connected #32
- [x]  HW issues #30 (remove R12/R13)
- [x]  Schematics details #27
- [ ]  AFE AUX PSU connection crossed #35 -> (AUX PSU will be changed accordingly)
- [x]  mechanical issues #31
- [x]  Shuttler analog bandwidth  #36 -> 33pF caps -> ~12MHz BW.

Other fixes:

- [x] Shuttler FMC stackup adjusted
- [x] Added missed templates
- [x] P_version project parameter added
- [x] Shuttler AFE stackup table added
- [x] Shuttler AFE - FTG added
- [x] Shuttler AFE - keepout for NPTH added
- [x] R12 marked as DNP
@maciejprzybysz
Copy link
Member

Updated in v1.2rc2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.2
Development

No branches or pull requests
3 participants
@gkasprow @kaolpr @maciejprzybysz