Since a few days I've problem in 'Initialize Connections' with following Messages:
ERROR: The connection to the hardware drivers could not be established.
Before this Messages everything has worked properly, so it can said that the Project with its Platform-Designer and the generated .sof-File can be excluded for the root-case of my problem.
Unluckely the Error-Message didn't helped me. A restart of my Computer inclusive the whole HW-DUT didn't helped too. With another Computer from my workmate the Connection-Initialization works.
Before I've had this problem, I've installed a few stuffs for Python (incl. Perl64). Maybe there could be the problem, but how to solve?
Did someone of you had the same problem as I right now?
Thanks for any Helps!
Thank you for joining this Intel Community.
I apologize for the delay in response as the case just re-route to me today.
I would like to clarify on few thing below:
- Which Quartus version are you using? Is it same Quartus version used on another Computer from your workmate ?
- What memory protocol (DDR3 or etc) used and what device ?
Also, on the connected host computer, please do the following:
1) On command line (Nios II Command Shell is an easy way to do this, which can be launched from Qsys -> Tools menu), type "jtagconfig -n" and paste what it returns.
2) Open System Console and load the design. Paste the messages in the lower left corner, and then what the following returns: "get_service_paths issp", "get_service_paths master", "get_service_paths sld".
Based on my past experience, this error could also be due to issue with the JTAG logic not meeting timing for the current speed. You may also want to try on debug step below and see if this make any changes on the test result.
First, specify the speed of TCK. Use jtagconfig -d
In order to rule out if this is an issue with the JTAG logic not meeting timing for the current speed, please reduce the TCK speed. For example, if you are currently at 24MHz, please try again at 16MHz.
Type the following command to change the TCK frequency:
jtagconfig --setparam <cable number> JtagClock 16M
- <cable number> is the download cable to be modified.
Hopefully this is helpful. Let me know your feedback.
I've have to correct my answer... I've registered, that the clock-speed-reduction didn't have the successful impact. moreover one of the above mentioned instruction...? Actually I can connect with 24M, but only with Qsys and Systemconsole opened... But is this the solution at the end? For me it's still 'trial and error'...
I am sincerely sorry for the delay in response due to recent workload.
Glad to know that after reducing the TCK speed from 24M to 16M and its works. 😊
Regarding your question below:
How is it possible that the timing isn’t met with the same set-up? Was my Computer getting faster so that USB-Blaster II comes in trouble?
Ans: I believed its due to the hardware variable itself. Even with same setup, but still the PC used is different. The USB-Blaster/JTAG could be operating with different speed in different PC. So, what we recommend customer is always tune the TCK speed. If 16M doesn't work then try with 6M. Plus, we didn't faced any issue launching EMIF toolkit at our side with our setup.
Also, you mentioned that you can connect with 24M with Qsys and system console opened. I am sorry but this seems like doesn't make sense to me as I don't see any relationship between the EMIF toolkit performance with this 2 platforms mentioned (qsys and system console opened).
Hope this clear.