configuration
1091 TopicsArchitectural feedback: <1ns Async Egress Gate + SHA3-256 XOR core on Agilex 7 (896 logic cells)
Hi everyone, I’ve been developing a hardware-native cyber defense protocol (RQSD-CD v1.0 / Project Trident) designed to protect vital infrastructure (like undersea fiber backbones and 6G edge nodes) against physical sabotage and post-quantum interception. The core has been synthesized with zero errors in Altera Quartus Prime Pro 26.1.1 targeting an Agilex 7 fabric, occupying 896 logic cells. The architecture relies on three parallel hardware pillars: 1. Dynamic Ingress Failover: Continuous hardware-level health monitoring across 3 parallel channels with a 0us switch-over to backup paths. 2. Post-Quantum Cipher Core: A synchronous SHA3-256 bitwise XOR matrix utilizing hardware-native entropy, paired with an inverse Reversal Core for lossless decryption. 3. Asynchronous Egress Gate: An intelligent 3-step pulsed crash counter to filter out transient network drops. On the 3rd consecutive failure, it bypasses the system clock (rising_edge(clk)) to force the physical I/O pins into a High-Impedance ('Z') state in < 1ns. My question to the senior FPGA architects here: Since Prong 3 intentionally operates asynchronously outside the clock domain to achieve sub-nanosecond physical isolation, how would you best mitigate potential metastability issues on the downstream bus during that exact switching instant on an Agilex 7? I’ve published the baseline HDL code (trident_core_base.vhd), the pulsed testbench, and the Questa RTL simulation waveforms on GitHub for architectural review (IP registered under Benelux i-DEPOT 158618): https://github.com/avanessen81-design/RQSD-CD-Protocol-v1.0-Project-Trident Any critical feedback on the timing constraints or async gate behavior is much appreciated!3Views0likes2CommentsRequest for OrCAD Capture (.dsn) schematic files for Agilex 5 E-Series Development Kit
Hello, We are supporting a customer who is designing a custom board based on the Agilex 5 E-Series Development Kit [Agilex® 5 Dev Kits / DK-A5E013BM16AEA]. The customer wants to use the development kit schematic as a reference for their own board. On the kit’s documentation page, we can only find the schematic in Cadence Design Entry HDL format. However, the customer’s design environment is OrCAD Capture(version 16.6), so they cannot open or reuse these files directly. Could you please let us know: Is an OrCAD Capture version of the schematic (.dsn / .opj project) available for this development kit?If not, is there any recommended way to convert the Design Entry HDL files to OrCAD Capture, or another format that can be shared (for example, an EDIF netlist)? Any guidance or download link would be greatly appreciated. Thank you.26Views0likes3CommentsMAX 10 DA vs DD devices, can the same programming file be used?
We are considering using both DA and DD variants of the MAX 10, for example 10M50DAF484 and 10M50DDF484. According to the device ordering information, the DD option adds Flash Access Control compared with the DA option. Could you please clarify the following: Can the same Quartus-generated .pof programming file be used to program both the DA and DD devices, assuming the density, package, speed grade, and FPGA design are otherwise identical? Or must the Quartus project target the exact DA/DD device and generate a separate .pof for each OPN? If separate files are required, what is different in the generated programming data? Does the answer change if we are not using the DD Flash Access Control feature? Our goal is to determine whether DA and DD devices can be used interchangeably in production without maintaining separate FPGA programming files. Thank youSolved32Views0likes2CommentsHPS and SDM bank IO standard confirmation
Hi, We are working with the Agilex 5 FPGA and referring to the device datasheet, which indicates that the HPS and SDM I/O pins support the 1.8 V LVCMOS I/O standard. However, when we configure these pins in Quartus Prime and select 1.8 V LVCMOS as the I/O standard, Quartus reports an error. When we configure the voltage as 1.8 V only, the assignment is accepted successfully. We would like clarification on the following points: Are the HPS and SDM I/O pins compatible with the 1.8 V LVCMOS I/O standard? If 1.8 V LVCMOS is supported, why does Quartus Prime report an error when this standard is selected? Should we specify the I/O standard as 1.8 V LVCMOS, or should we use only the 1.8 V voltage assignment for these pins? Is there any specific configuration, constraint, or Quartus setting required to enable 1.8 V LVCMOS operation on these pins? Please confirm the recommended configuration and clarify whether using the 1.8 V assignment without explicitly specifying LVCMOS is electrically and functionally equivalent. Kindly find the attachment for your reference.43Views0likes2CommentsClarification on BGA Ball/Pin Pattern for Altera FPGA Devices
Hi Team, We are created PCB footprints for the following Altera FPGA devices: AGIB022R31A2E2VCNL – BGA-3184 A3CY050BB18BE7S – BGA-538 A3CY135BB23CE7S – BGA-931 While reviewing the manufacturer package drawings and creating the footprints, we observed that the ball/pin pattern uses different pad arrangements and the pitch between the pins/balls is not uniform in some areas. Could you please clarify whether there is a specific design or manufacturing reason for using these different ball/pin patterns and pitch arrangements?23Views0likes1CommentFPGA simulation and real HW behavior discrepancy
Dear Altera Quartus 18.1 sim lib could try 20.1 or newer but not sure this is due to Quartus version as it is sim lib. I am encounter an unexplainable experiment result that contradicts simulation and real HW. Background when interfacing a DQS DQ readout a IDDR with CCD sync flops are used. For these primitives, it should expected 1 + 2 and clock +ve edge should expect data push out. [A] This can simply considered as early push out but it should not act as such. With the use of "__ALTERA_STD__METASTABLE_SIM" we expected some metastable on the output. [B] Now things are more reasonable where 2 +ve clocks are expected. If we consider a full data w/o xx, things become unrecognizable. [C] The most interesting part when apply on real HW, it do produce correct data and the latencies do obeyed. altddio_in#( .intended_device_family ( "Cyclone IV E" ), .invert_input_clocks ( "ON" ), .lpm_hint ( "UNUSED" ), .lpm_type ( "altddio_in" ), .power_up_high ( "OFF" ), .width ( 8 ) )ddi_d_l( .aclr (reset), .datain (foo[7:0]), .inclock (bar[0]), .dataout_h (foobar_h[0+:8]), .dataout_l (foobar_l[0+:8]), .aset (1'b0), .inclocken (1'b1), .sclr (1'b0), .sset (1'b0) ); + altera_std_synchronizer_bundle#( .width (foobar_bw *2), .depth (2) )async_flops( .clk (clock), .reset_n (~reset), .din (foobar), .dout (foobar_ccd) );362Views0likes7Comments