The device_browser.py failed in connection browser. Have no ideas on how to fix it.

Hi Chris

My name is Stephen and I work at Arm.  The error log file will be in the .metadata folder in your Arm DS workspace.  

You should also be able to see the errors in the Error Log view, which you can open with:
Window > Show view > Other > General > Error Log.

The log file might be quite long, but please find the relevant section relating to this error, and copy an extract here.  That might help to reveal the problem.

https://developer.arm.com/documentation/101469/2023-1/Introduction-to-Arm-Development-Studio/Debug-probes

says:
====
If you are using the Intel FPGA Download Cable debug probes, Arm Debugger can connect to NX5, Agilex 7, Arria V SoC, Arria 10 SoC, Cyclone V SoC and Stratix 10 boards. To enable the connections, ensure that the environment variable QUARTUS_ROOTDIR is set and contains the path to the Quartus tools installation directory:
* On Windows, this environment variable is usually set by the Quartus tools installer.
* On Linux, you might have to manually set the environment variable to the Quartus tools installation path. For example, ~/<quartus_tools_installation_directory>/qprogrammer.

For information on installing device drivers for Intel FPGA Download Cable and Intel FPGA Download Cable II, consult your Quartus tools documentation.
====

See also the Intel FPGA Download Cable User Guide at:

https://www.intel.com/content/www/us/en/docs/programmable/683076

In particular,

https://www.intel.com/content/www/us/en/docs/programmable/683076/current/installing-the-driver-on-linux.html

says the Intel FPGA Download Cable is supported for Linux, but apparently only for RedHat.  Maybe that's the problem?

You could try asking on the Intel Community at

https://community.intel.com

Hope this helps,

Stephen

Hi Chris

My name is Stephen and I work at Arm.  The error log file will be in the .metadata folder in your Arm DS workspace.  

You should also be able to see the errors in the Error Log view, which you can open with:
Window > Show view > Other > General > Error Log.

The log file might be quite long, but please find the relevant section relating to this error, and copy an extract here.  That might help to reveal the problem.

https://developer.arm.com/documentation/101469/2023-1/Introduction-to-Arm-Development-Studio/Debug-probes

says:
====
If you are using the Intel FPGA Download Cable debug probes, Arm Debugger can connect to NX5, Agilex 7, Arria V SoC, Arria 10 SoC, Cyclone V SoC and Stratix 10 boards. To enable the connections, ensure that the environment variable QUARTUS_ROOTDIR is set and contains the path to the Quartus tools installation directory:
* On Windows, this environment variable is usually set by the Quartus tools installer.
* On Linux, you might have to manually set the environment variable to the Quartus tools installation path. For example, ~/<quartus_tools_installation_directory>/qprogrammer.

For information on installing device drivers for Intel FPGA Download Cable and Intel FPGA Download Cable II, consult your Quartus tools documentation.
====

See also the Intel FPGA Download Cable User Guide at:

https://www.intel.com/content/www/us/en/docs/programmable/683076

In particular,

https://www.intel.com/content/www/us/en/docs/programmable/683076/current/installing-the-driver-on-linux.html

says the Intel FPGA Download Cable is supported for Linux, but apparently only for RedHat.  Maybe that's the problem?

You could try asking on the Intel Community at

https://community.intel.com

Hope this helps,

Stephen

Hi Stephen,  

Thanks a lot for your kindness and detailed information!

You are right! I get the error log and it shows that

Error:Failed to load client library libjtag_client.so. Please ensure that the environment vairable QUARTUS_ROOTDIR is correctly defined.

And I also checked the driver setting of my cable and it seems right. And the download cale always works fine in Linux. 

But now I met a problem of setting the QUARTUS_ROOTDIR. 

There is some original settings related with quartus,you can get the location of Quartus:

export PATH="$PATH:/tools/intel/intelFPGA_pro/23.4/quartus/bin"
export PATH="$PATH:/tools/intel/intelFPGA_pro/23.4/qsys/bin/"

And I tried to set  QUARTUS_ROOTDIR in three ways.
export QUARTUS_ROOTDIR="/tools/intel/intelFPGA_pro/23.4/quartus/bin"
or export QUARTUS_ROOTDIR="/tools/intel/intelFPGA_pro/23.4/quartus"
or export QUARTUS_ROOTDIR="/tools/intel/intelFPGA_pro/23.4" 

But they all failed every time after I restart the DS IDE and tried the connection. The same issue of device_browser still exists.

Is there anyway that I can prove that DS recognize the definition of QUARTUS_ROOTDIR? Is there any version limitations to Quartus and DS? Maybe I need to set the path of QUARTUS_ROOTDIR to $PATH?

Thanks a lot for your great help!

Hi again

Is there a "qprogrammer" folder?  If so, try:
export QUARTUS_ROOTDIR="/tools/intel/intelFPGA_pro/23.4/qprogrammer"

That works for us here (though admittedly on Windows, and with an older version of Quartus...).

On Linux, you might also need to set permissions in udev/rules.d as shown at

https://www.intel.com/content/www/us/en/support/programmable/support-resources/download/dri-usb-b-lnx.html

You must have system administration (root) privileges to configure the Intel FPGA Download Cable drivers.

That document seems to show that the drivers are only supported for RedHat Linux Enterprise, not Ubuntu.
You'll need to ask Intel about whether Ubuntu is supported.

Sorry, but I don't think we can offer much more help here.  Please try asking on the Intel Community at

https://community.intel.com

Stephen

Dear Stephen,

Please accept my apologies for the delayed response.

I attempted to install the older version of Quartus that still includes the qprogrammer directory, but unfortunately, the installation was unsuccessful. Despite this setback, I want to express my sincere gratitude for your persistent efforts to assist me, even though our systems were asynchronous. Your kindness and willingness to help have been invaluable.

Moving forward, I plan to reach out to Intel AE to further investigate and resolve this issue.

Thank you again for your generous support throughout this process.

Best regards,

Chris

Hey mate,have you resolved the above issue.