I'm currently using a custom board with 5CEFA9F31C7N Cyclone V E FPGA chip and Alliance AS4C512M16D3L DDR3 8GB with 1.5V on Quartus II 13.1.
After setting up my timing constraints and generated an IP through MegaWizard, I SignalTapped my local calibrations that resulted with calibrations failed.
After reading through
https://www.altera.com/content/dam/a...if_toolkit.pdf
I know that the EMIF Toolkit can be useful in determining what stage the calibration failed to narrow down the culprit. Is this available for the Cyclone V E?
Page 11 states:
"The UniPHY External Memory Interface Debug Toolkit and EMIF On-Chip Debug Toolkit do not workwith Arria V and Cyclone V SoC devices. Debugging information for Arria V and Cyclone V SoC devicesis available by enabling a debug output report, which contains similar information."
My chip is not an SoC so it would work correct?
I compiled my project (Analysis & Synthesis, ran .tcl scripts for pin assignments, map, and timing, Fitter, then Full Compile), programmed the board and proceeded to start up the toolkit, only to have it timeout on the "Initialize Connections" task. Any insight on this?
I also used the Cyclone V GT Development Kit and was able to calibrate the DDR3 memory on that device with no issues with read/write functionalities. However, Toolkit would still timeout after a few minutes on "Initialize Connections".
-Steve
After setting up my timing constraints and generated an IP through MegaWizard, I SignalTapped my local calibrations that resulted with calibrations failed.
After reading through
https://www.altera.com/content/dam/a...if_toolkit.pdf
I know that the EMIF Toolkit can be useful in determining what stage the calibration failed to narrow down the culprit. Is this available for the Cyclone V E?
Page 11 states:
"The UniPHY External Memory Interface Debug Toolkit and EMIF On-Chip Debug Toolkit do not workwith Arria V and Cyclone V SoC devices. Debugging information for Arria V and Cyclone V SoC devicesis available by enabling a debug output report, which contains similar information."
My chip is not an SoC so it would work correct?
I compiled my project (Analysis & Synthesis, ran .tcl scripts for pin assignments, map, and timing, Fitter, then Full Compile), programmed the board and proceeded to start up the toolkit, only to have it timeout on the "Initialize Connections" task. Any insight on this?
I also used the Cyclone V GT Development Kit and was able to calibrate the DDR3 memory on that device with no issues with read/write functionalities. However, Toolkit would still timeout after a few minutes on "Initialize Connections".
-Steve