Time-Appliance-Project icon indicating copy to clipboard operation
Time-Appliance-Project copied to clipboard

EEPROM write protect input driven by +1.5V signal

Open wisxxx opened this issue 3 years ago • 3 comments

wisxxx avatar Sep 21 '21 02:09 wisxxx

Looking at "Timingcard_SCHEMATICS_BETA_V1.pdf", the AT24MAC402 serial EEPROM WP input (p. 4,A5) is driven by the EXT_EEPROM_WP signal from the FPGA board (pin P1A-44, p. 6,B5) and a 10K pullup to +3.3V.

The AT24MAC402 is operating on +3.3V. VIL min is specified as VCC x 0.7 = +2.31 V.

The FPGA pin driving the signal to P1A-A44 (net B34_L21_P) is driven by Bank 34, which is a +1.5V block.

  • Does the 10k pullup to +3.3V guarantee a valid logic high into the EEPROM? It seems to depend on a very large output resistance in the FPGA buffer, given the 10K pullup value.
  • Can the FPGA output reliably sustain the back-drive (nominal 180 uA)?

ref: AC7100 FPGA SoM schematic "AC7100B_SDM.pdf" (p. 6,D2; p.12,D4), "AC7100B User Manual.pdf".

wisxxx avatar Sep 21 '21 03:09 wisxxx

Hi @wisxxx,

Thank you for a great issue.

This is correct. The WP has been moved to a 3.3V bank in the next version we are evaluating.

AlphaBetaPhi avatar Sep 21 '21 06:09 AlphaBetaPhi

EEPROM write protect is +1.5V signal in new FPGA description

File: PinoutConstraint.xdc, lInes: 75-77

#EEPROM
set_property PACKAGE_PIN V9 [get_ports EepromWp_DatOut]
set_property IOSTANDARD **LVCMOS15** [get_ports EepromWp_DatOut]

wisxxx avatar Jun 04 '22 04:06 wisxxx

Not fixed in file: Time-Appliance-Project/blob/master/Time-Card/FPGA/Open-Source/Implementation/Xilinx/TimeCard/Constraints/PinoutConstraint.xdc

Is fixed (moved to pin AA13) in file: Time-Appliance-Project/blob/master/Time-Card/FPGA/Open-Source/Implementation/Xilinx/TimeCard_Production/Constraints/PinoutConstraint.xdc

wisxxx avatar Jan 13 '23 00:01 wisxxx

Just to clarify: The constraint files are for two different hardware versions. That's why they are different. The FPGA pinout constraints are simply configured that it matches with the hardware. So you will never see a "fix" in the constraints file since they are related to a specific hardware.

thschaub avatar Jan 13 '23 08:01 thschaub

Fixed in recent FPGA pushes.

wisxxx avatar Jan 30 '23 16:01 wisxxx