--- Quote Start ---
error: This transaction did not complete in 60 seconds. System Console is giving up. while executing ...
--- Quote End ---
If you haven't taken the time to understand the SystemConsole code or the design it is controlling, then you have no way of understanding why its failing. This is why I told you earlier, you have to understand the design, and then create your own.
If you create a simulation of your system with two boards, you can check whether the first design is outputting a clock to the second design. If you don't have a simulation, then use an oscilloscope.
No one on this forum will be able to answer questions about software or hardware designs that you are asking questions about when
you have not taken the time to understand them. As soon as you understand them, you'll have no need to ask questions.
Problem solving comes with experience, don't give up the first time something does not work, rather, take it as a challenge and develop problem solving skills.
For example, even without an oscilloscope, you have Modelsim for simulation and SignalTap II for hardware debugging. Take the time to create a Modelsim simulation, and then test the hardware. Use SignalTap II to figure out where you have gone wrong, and keep attacking the problems until you solve them.
I know the procedure for synchronizing two boards works, as I use it all the time, to synchronize a pair of Stratix IV GX development kits. I saw plenty of SMA connectors on the Stratix IV GT SI kit, get out your oscilloscope and start checking there are clocks on the SMA connectors you expect to have clocks.
Cheers,
Dave
Honored Contributor
