Honored Contributor
Honored ContributorI am working with a BeMicro With Cyclone IV and Quartus 12.0 Build 263 SP2. I have some questions and observations.
Question: I am running the tutorial. When you compile the Quartus 12.0 project, which verilog files contain the ID and Timestamp so we can always check what the SOF image contains? Can someone explain more about how the time stamp works with a limited time SOF? I assume the timestamp is a static value determined at the time Qsys generates its files, and the timeout of the SOF is independent from the time stamp. I would like to know for sure. When you program the Cyclone IV and the dialog pops up with the timer, does it matter if the dialog is cleared? I assume it is just a time counter that has nothing to do with the activity of the Cyclone IV. But I want to be sure. Observation: When the console error occurs, the fix is to close Eclipse and reopen it. The console error occurs even when the ID and Timestamp are ok. Somehow restarting Eclipse clears the problem. I have verified on two different days when I got stuck that this ultimately fixes the problems. This problem is absolutely crippling and leaves every user with a very bad impression. You feel helpless and everyone keeps saying if the ID and time stamp are correct it should work. No, there is some state-full behavior in Eclipse that clears it. This is a clearly a bug or very bad interface design problem. It would be nice to know the order dependencies of this problem or a way to reset things in Eclipse so you don't have to restart it. Even regenerating the BSP does not clear it. At least if there was a simple work around documented in the forum people could get unstuck.
