Forum Discussion
New ContributorError ID 18694: Still not resolved ???
- Hi,
hard to believe that you need to refer to weird workarounds like this...
Check your private message folder.
Regards,
Frank
Super ContributorHi,
for your info, error 18694 is still occurring with recent Quartus Prime Pro 26.1
Regards Frank
ShengN_alteraHi Frank,
Could you post the full error id?
Possible provide the design for debug purpose?
- FvM
Hi Sheng,
thanks for your interest. What we see is expected behaviour according to above quoted 5.6.6.2.2. Guideline which requires refclock for SERDES RX being originated from a dedicated clock pin of same IO bank. Problem is that non-dedicated refclock source was possible in earlier Quartus versions and that it's strictly enforced by Quartus even for SERDES designs with rather uncritical clock speed. Previous statements suggested that this could be an unwanted effect, thus I verified that the behaviour is still present in latest Quartus Prime Pro 26.1. Error ID is 18694, as described in thread title. I append a test design with two SERDES instances located in bank 2F and 2G, both driven by bank 2F reference clock.
Regards Frank
- ShengN_altera
Hi Frank,
Please continue to use the INI to avoid the error. I had raised a new ticket to engineering team to fix this issue. Hopefully the problem will be fixed in future release.
