Forum Discussion
Cyclone V SoC 5CSXC6 Series GXB Utilization and Limitations
- 21 days ago
Hi Brian,
Thank you for the update.
Just to clarify, the legacy database I referred to is our internal database for legacy devices. Unfortunately, there is limited information available regarding this wrong data issue. Based on the available info, I believe it was originally initiated from a customer-reported case.
You are also correct that the placement rules are enforced within Quartus. Since these rules are built into the tool, they cannot be overridden through a TCL command.
I apologize for any inconvenience this may cause.
OK.
For wrong data, you kept referring to legacy database, this is from internal FAE / staffs only?
Do wrong data reports from customers or internal smoke / sanity tests?
There is no way we can use with newer version no override no tcl command to bypass fitter rules on coexist?
Thanks,
Brian
Hi Brian,
Thank you for the update.
Just to clarify, the legacy database I referred to is our internal database for legacy devices. Unfortunately, there is limited information available regarding this wrong data issue. Based on the available info, I believe it was originally initiated from a customer-reported case.
You are also correct that the placement rules are enforced within Quartus. Since these rules are built into the tool, they cannot be overridden through a TCL command.
I apologize for any inconvenience this may cause.
- BrianSune_Froum21 days ago
Contributor
I guess we had this more than enough on understanding the whold story.
I deeply appreciate the sharing and assisting on this ticket.
I will close and report as solution.
So I think 17.x is still worth to keep.
Thanks,Brian