-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error JTAG ID on Linux when I try to program the Catapult V3(PCI-E version). #1
Comments
I'm pretty sure that the issue is driver related. You can try the following steps:
if (hwData->isHighSpeed)
{
clockDivisor = 1; // -> Increase this value to reduce TCK freq (2,3,4...)
hwData->jtagClock = 15000000;
// Comment the following line to enable 12Mhz master clock instead 60Mhz
// buffer[dwNumBytesToSend++] = FT_OPCODE_DISABLE_DIVIDE_BY_5; // Use 60MHz master clock (disable divide by 5)
} |
@Kharlenkow, It appears that a missing synchronization step was causing incomplete device initialization on Linux systems. Now it's fixed. |
Glad to hear that the problem has been solved!!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for your selfless dedication!!!
I follow your guide step by step. And I successfully programmed my device on Windows 10. However, when I tried to program it on Linux, the issue happened~
Error(209015): Can't configure device. Expected JTAG ID code 0x02E660DD for device 1, but found JTAG ID code 0x026060DD. Make sure the location of the target device on the circuit board matches the device's location in the device chain in the Chain Description File (.cdf).
My Quartus Prime Pro version is 22.3, which is the same as that on Windows. Besides, both of the distributions, Debian 12(Linux Kernel 6.1.0) and Mint 21.2(Linux Kernel 5.15), have this problem.
I don't know whether this is caused by Quartus itself or the driver~
Looking forward to your reply!
The text was updated successfully, but these errors were encountered: