Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
21615 Discussions

[Stratix V] Capturing Eye Scan on Multiple Channels using tcl script

Altera_Forum
Honored Contributor II
‎03-01-2016 10:10 PM
1,285 Views

Hi, 

 

I'm trying to capture an eye scan using the EyeQ block from the Transceiver Reconfiguration controller. I have written a script and it works for logical channel 0. When I try to use the same script and capture an eye on a different channel, it does not seem to work. I have modified the code to adjust the location of the different pattern checker and to set the logical channel address for the PMA block and the EyeQ block. Does anyone have any suggestions on how to figure out why it isn't working? I am able to capture an eye using the TTK on both channels (I'm just trying to get away from using the TTK), therefore, I know my hardware set up is correct. I think there must be some register I need to set that I just don't know about it.  

 

In my Qsys block the reconfiguration controller is at address 0x800. The data pattern checker 1 is at 0xaa0.  

Thanks!
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎04-13-2016 11:03 PM
601 Views

There was nothing wrong with my tcl script. The issue was with how the signal was being capture in tcl vs the ttk.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.