PeterL
New Contributor
3 years agobroken chip planner
Chip planner is broken in quartus 22.4 and 23.1 both Windows 10 and Linux versions
22.3 is OK both Windows 10 and Linux
Any solution?
Chip planner is broken in quartus 22.4 and 23.1 both Windows 10 and Linux versions
22.3 is OK both Windows 10 and Linux
Any solution?
Hello,
I see Chip Planner regularly working in QPP 22.4 with different designs.
Regards,
Frank
Hi FvM,
Thanks for tests. It turned out something has happened in device migration settings between 22.3pro and 22.4pro.
I use Cyclone 10CX105YF780E5G and migration device 10CX150YF780E5G. Even when I start new design with migration set, chip planner fails. Without migration, it works fine.
BUT there is a caveat, once you set migration and remove it later through menu, quartus still keeps in QSF file
assignement
set_global_assignment -name DEVICE_MIGRATION_LIST 10CX105YF780E5G
which cause chip planner fail. It must be manually deleted from QSF.
As I need device migration, I need to keep this assignment
So, I consider this behaviour a bug in quartus
Regards
Peter
Hi,
I suspect that this is due to device installation.
What is your target device, can you make sure it has been installed in these versions of Quartus?
Regards,
Nurina
Hi Nurina,
Thanks for reply. I use Cyclone 10GX and it was correctly installed.
I found a bug in quartus, see my reply above
I don't how to pass this to support. With ALTERA I had support account for bugs and problems communication
but with INTEL it was refused
Regards
Peter
Hi Peter,
You may continue to use this thread and I can report this bug for you.
Can you share your design?
Thanks,
Nurina
Hi Nurina,
I share simple example design with assignment (and bug) present
regards
Peter
Thank you.
Can you also share the 22.2 design so I can reproduce the steps? I would like to check if this happens when migrating to other Quartus versions too.
Regards,
Nurina
Hi Peter,
Please ignore my previous comment. I'm able to recreate the project in 22.2.
Regards,
Nurina
Hi Peter,
Thank you for sharing this issue and design with us.
I have reported this issue to engineering team.
Since you have the workaround to this issue, may I know if I can close this case?
Regards,
Nurina
Hi Nurina,
Yes, you can close the case
regards
Peter