Incorrect printline by using different memory segments

Hi. Not problem being new to this. We all are learning new things everyday!!

So for FPGA's Quartus goes through the logic, optimizes it, then places it in various places in the physical chip, and routes it all together. If the design is very fast, or very large, it may or may not be able to meet the timing requirement's of the design, so the TimeQuestAnalyzer checks your designs actual timing against a desired timing required by the constraints file (.SDC file) to make sure it meets specs. Quartus is pretty smart in that if you define a PLL it usually gets the basic PLL timings in the design for you based on the PLL settings, but it's not ALWAYS correct.

So Understanding the tool and the constraints file is critical for a stable design. I would focus a bit of working with this tool and understanding it. Especially around IO timing (The trickiest part). Make sure all you clocks are defined, and they have reasonable frequencies. Note: cross clock domain signals will almost ALWAYS fail timing, unless the clocks are handled with care and have related frequencies. So special logic must be used here to insure proper functionality (Fifos, Flancter circuits, etc)

The Timing warning is stating that you don't have any clock uncertainty applied. Clock uncertainty is that due to jitter and other effects, you are not exactly certain when the clock edge will occur, so you need some margin to handle this. The derive_clock_uncertainty is a command that will use ALTERA's recommend uncertainty values for their internal clock trees and PLL's so it's an easy way to apply it to all clocks, and it will work for ALTERA FPGA's.

On the Memory Test Template: Yes I was talking about the one in the Eclipse IDE. I typically target this initially to run in an internal SRAM segment so I can test the rest of the memories. (The only problem being your internal segment must be large enough to hold all the code space).

The default test pattern is ok, but not the best. I usually modify it for my specific needs. Especially to track down board issues like open/shorts.

Hope this helps point you in the right direction anyway..

Pete