ContributionsMost RecentMost LikesSolutionsRe: Quartus is not recognising the Stratix 10 chip on my Stratix 10 development kit. Hello @Daire_C_Intel, I am running into the same issue on my board. Can I know what was the solution that worked for you? That would be helpful Thanks, Ranjith Re: Quartus 23.4 shows 0.0 BER but negative eye height values @ZiYing_Intel Please check my comments. I have updated my responses on 02-20-2024 Please scroll up Thanks, Ranjith Re: Quartus 23.4 shows 0.0 BER but negative eye height values @ZiYing_Intel Here is another autosweep showing the same issue Attached Thanks, Ranjith Re: Quartus 23.4 shows 0.0 BER but negative eye height values Hi @ZiYing_Intel I am sweeping different values for main tap as shown in the attached PDF. Still negative eye height with zero BER exists, please refer .pdf attached Thanks, Ranjith Re: Quartus 23.4 shows 0.0 BER but negative eye height values Hello @ZiYing_Intel This is the FPGA part number AGFB027R31C2E2V I have ensured that the RX channel is receiving data before starting eye measurement Re: Quartus 23.4 shows 0.0 BER but negative eye height values Adding more details: The insertion loss between the FPGAs is ~15db. Quartus 23.4 shows 0.0 BER but negative eye height values Hi, I am running BER test for 2 FPGAs. I am transmitting from Tx pin of first FPGA and receiving on Rx pin on second FPGA. Using Quartus 23.4 here. Both are Agilex F-tile F-series FPGAs. There is a total trace length of 13 inches between the FPGAs and the speed is 28Gbps NRZ PRBS31. I set up a autosweep to sweep through different tap values in order to tune the channel I notice that the results show negative eye height for many iterations but the corresponding BER is zero (see attached pdf) How can this be possible? Negative eye height means that the eye is closed. In this case we should expect maximum BER Please help me understand what is going on here Thanks, Ranjith Re: Quartus 23.3 transceiver toolkit fails to load using TCL Hi @Kshitij_Intel , I was able to fix this issue. In "device_initialization" file, I replaced the string "AGFB027R24C2E2V" with the short version of itself i.e the string "AGFB027R24C" This fixed the issue Thanks, Ranjith Re: Quartus 23.3 transceiver toolkit fails to load using TCL Hi @Kshitij_Intel, Yes. I did modify the TCL script and added it to the path shown in screenshot Also, attaching the TCL script here as a .txt file (unable to upload .tcl files here) Still the same error exists: Jan 17, 2024 1:28:43 PM com.altera.debug.core SEVERE: java.lang.Exception: can't read "device_path": no such variable while executing "string length $device_path" invoked from within "if { [string length $device_path] == 0 } { error "Specified $device_name device name, $device_die_name is not found. Please make sure the board is..." Thanks, Ranjith Re: Quartus 23.3 "Channel closed" error Hi @Kshitij_Intel , I switched to Q23.4 and have not seen this issue occurring. So, yes, this issue can be considered fixed Thanks, Ranjith