New Contributor
Regular ContributorHi pdi_eng,
May I know the error code number, please? Or perhaps you could provide the error screenshot. What version of Quartus you're using now? Try use a later/latest version. In the meantime, you may take a look at a few KDB below which may be applicable to this issue:
Error (209025): Can’t recognize silicon ID for device 1
Error: Can't recognize silicon ID for device 1
Error(19099): Can't recognize silicon ID for device 1
Regards,
Fakhrul
New ContributorHI Fakhrul,
Here is how my programming goes:
Info (209060): Started Programmer operation at Tue Apr 18 09:06:50 2023
Info (209016): Configuring device index 1
Info (209017): Device 1 contains JTAG ID code 0x020F30DD
Info (209007): Configuration succeeded -- 1 device(s) configured
Error (209025): Can't recognize silicon ID for device 1
Error (209012): Operation failed
Info (209061): Ended Programmer operation at Tue Apr 18 09:07:07 2023
Our customer provided us with a PC to do the programming and test, so I don't have a say in updating to the latest Quartus, but I am using Quartus II version 12.1 build 177.
This is what my programming environment looks like:
The KDB "Error: Can't recognize silicon ID for device 1" looks like my same error but I don't have a separate connector to program the EPCS device directly.
Is the only other possible problem a noisy TCK?
