System Console fails to open service with Cyclone V FPGA

[CHatz]

All of the sudden,

System Console fails to open the service path when connected to a Cyclone V FPGA.

I have been using System Console to test a Cyclone V based board for a long time. Suddenly, when

connected to the Cyclone V FPGA, it fails to open the path. The error messages are:

Feb 22, 2023 11:50:42 AM com.altera.debug.core
INFO: Executing startup script C:\Users\costas.hatzinikolaou\system_console\system_console_rc.tcl

Feb 22, 2023 11:50:42 AM com.altera.debug.core
SEVERE: open_service: Path cannot be found

Feb 22, 2023 11:50:42 AM com.altera.debug.core
SEVERE: Failed to run the script: C:\Users\costas.hatzinikolaou\system_console\system_console_rc.tcl

When I connect to an Arria 10 FPGA, it works fine. When I type the command:

"set m_path [lindex [get_service_paths master] 0]", I get the following response:

"/devices/10AS027E(1|2|3|4)|10AS027H1|..@1#USB-1/(link)/JTAG/(110:132 v1 #0)/phy_0/master".

I tried multiple boards with Cyclone V and different PCs and System Console fails to open the service with all of them.

[CHatz]

The problem has been resolved.

[ShengN_Intel]

Hi,

I’m glad that your question has been addressed, I now transition this thread to community support.

Btw, the error message "open_service: Path cannot be found" suggests that System Console is unable to find the JTAG connection to the Cyclone V FPGA. It's always better to take note a few things below:

1. Make sure the JTAG connection is properly established between your PC and the Cyclone V FPGA board. Check the JTAG connections and cables to ensure they are properly connected and functional. You can also try restarting the FPGA board and your PC to see if that resolves the issue.
2. Check that the Quartus software is properly configured to connect to the Cyclone V FPGA board. You can do this by opening the Quartus software and selecting "Assignments" -> "Device" -> "Device and Pin Options". Make sure the correct device and pin options are selected for your Cyclone V FPGA board.
3. Try using a different JTAG cable or adapter to see if that resolves the issue.

Thanks,

Best regards,

Sheng

p/s: If any answer from the community or Intel Support are helpful, please feel free to give best answer or rate 4/5 survey.

[RichardTanSY_Intel]

.