How to tell Quartus my Arria10 target system CLKUSR frequency is 100MHz?
Timing analyser reports CLKUSR at 125MHz but target system has 100MHz on this pin to accommodate AS in combination with transceiver calibration as per the manuals -- there doesn't seem to be any consequences as the project seems to run fine but is a bit unsettling40Views0likes6CommentsAgilex 5 configuration via Avalon-ST x8 issues
I have a MAX10 device controlling the configuration of an Agilex 5 device (A5EC065BB23AI4S) set for Avalon-ST x8. We use the MAX10 to translate serial programming from our processor to AvalonST x8 for the Agilex 5. I am able to program both the MAX10 and Agilex 5 device via JTAG and verify we can talk to these devices via SPI busses in the hardware. For the configuration via the MAX10 we bring nCONFIG low and nSTATUS returns from the Agilex 5 low. We next bring nCONFIG back high and nSTATUS returns to high. We start the Avalon-St transfer but never see INIT_DONE go high. The odd thing is we also never see CONF_DONE go low even with nCONFIG low? Any idea what else to check? Below is a pic of the SDM_IO connections from the Agilex5 to the MAX10.7Views0likes1CommentCyclone V SoC 5CSXC6 Series GXB Utilization and Limitations
Dear Intel Altera, I would like to confirm that the 6 channels GXB device: Q1) Do it possible to use all 6 TX / RX GXB Transceivers when Hard PCIe is used. Based on: CV-53004 There are no specific diagram to explains the single PCIe hard core device with only 6 channel case. Q2) Based on the document: CMU PLL will use CH5 and do this simply means there will be one extra for PCIe Hard-Core? Q3) If not understood falsely, Either PCIe X2 GEN1 + 4 custom GXB usage nor PCIe X4 GEN1 + 2 custom GXB usage is possible? And most protocol uses 1,2,4 and the only possible case is PCIe X4 GEN1 + 1 custom GXB? A little more info from CV-53002 So in order for PCIe Hard Core to run x2 or x4 CH4 must be used. As a result for custom TRX there is no way to use CH1 when PCIe is > x1? Thanks, Brian120Views0likes8CommentsGPIO default state before FPGA configuration (weak pull-up vs. pull-down)
Between power-on and FPGA configuration, the GPIO pins are in a tristate condition with a weak pull-up enabled. As a result, the device’s digital outputs are initially driven HIGH and only switch to their intended state (LOW) after the FPGA configuration is complete. This behavior is causing problems for downstream signal evaluation. Questions: Is it possible to modify this default behavior of the GPIO pins before configuration? Specifically, can a pull-down (instead of a weak pull-up) be configured or enforced during the pre-configuration phase? Any guidance or recommended solutions would be appreciated.Solved18Views0likes4CommentsAgilex 5 A5ED043AB23AI2V with pcie and usb 3.1 design issue
Hi, I took the design for the dev kit example design with the device (A5ED065BB32AE4SR0) for PCIe Gen4 x4 and HPS USB 3.1, and I changed the part number to A5ED043AB23AI2V and upgraded the required IPs and started the compilation. I am getting the error... I attached it. I thought this was due to the difference in package B32 vs. B23. For the B23 package, it only has 4c for PCIe and 1c for HPS USB 3.1. For B32, it has 4c and 4b banks also for PCIe and 1c for HPS USB 3.1. Does my part number support the req design with both PCIe Gen4 x4 and HPS USB 3.1? Because individually it is compiling; if not, why...? What is the reason...? If it supports where I am getting wrong. Please help me. Thank you110Views0likes5Comments