01-13-2016 12:16 PM
I changed data in "gt_rom_init_tx.dat" and the same changed data is copied into "gt_rom_init_rx.dat" file and I also made sure that there are enough transitions in changed bytes. I didn't alter the whole data file, I altered one portion of it. Actual data "000000003e3d3c3b0000" and changed it to "00000000060504970000" data in both TX and RX file.
I am expecting no errors but, in simulation I am observing error. Without doing this it's all working fine. Where I am going wrong?
It's written in the UG if needed ".dat" files can be modified by the user.
Second problem is gt0_rxcommadet_i toggling even for unmodified data where there are no errors. Isn't this signal should remain 1 after comma is detected?
01-14-2016 05:00 AM
01-14-2016 06:19 AM
01-14-2016 06:41 AM
I opened these files location and changed the data and saved it. Did I do it correctly?
01-14-2016 07:21 AM
For all, I used default GT wizard example and altered "gt_rom_init_tx.dat" and "gt_rom_init_tx.dat" files. But I made sure that both are same.
01-18-2016 01:42 AM
01-18-2016 04:41 AM
These are the results for default GT wizard exaple design. I didn't change the ".dat" file, TX and RX are not matched or they are out of synchronous? But this is error free simulation, according to UG, track data goes high.
How CDR_lock functions? because, If I change ".dat" file to all zeros, still CDR_lock signal goes high. I am expecting it to go to zero when there are no enough transitions in data.
01-21-2016 03:41 AM
01-21-2016 03:44 AM
01-21-2016 04:41 AM
01-21-2016 04:46 AM
01-21-2016 05:53 AM
01-25-2016 03:16 AM