Forum Discussion
Qsys update
- 5 years ago
Hi Ben,
I have sent an email to you. Please help to check.
Best Regards,
Shyan Yew
I am very sorry that I yet to get any update from the engineering. Please allow me to follow up with them on this. I may escalate this issue if still no further response from them.
Regarding the qsys migrate from version 20.3 to 20.4, I did the steps you provided but no success in duplicate the xml error.
1)open quartus project
2)open qsys.qsys (no errors)
3) Sync System infos
4) save (same xml error occurred while saving)
Have the customer try to reinstall the Quartus version 20.4 and try to migrate the qsys 20.3 to 20.4?
Make sure you are using Windows 10. Scrolling back up you had duplicated the error. So did I. Thank you!
- RichardT_altera5 years ago
Super Contributor
Yes, I am using Window10.
The previous error was duplicated when I used the qsys file 20.4 version which was sent the second time by Ben_C through email.
This time I tried to reproduce the same problematic qsys file 20.4 version using the qsys file 20.3 version (sent first time -which does not cause any error initially in Quartus v20.4) by Sync System Info in Platform Designer - the flow that you provided on how to migrate the qsys from 20.3 to 20.4.
The error does not show up at the end, in order word, I can't reproduce the same problematic qsys file 20.4 version by migrating the qsys file 20.3 version from Quartus 20.3 to 20.4. I am trying to debug could this be Quartus setup issue or machine issue. Do you are able to reproduce the problematic qsys file from the good qsys file with a different machine?
Hope to get your understanding.
- Ben_C5 years ago
New Contributor
To reproduce the bug with Sync System infos, you need all the IP files. I tried to reproduce it with just a few IP files to see which ones corrupts the qsys. It wont failt until almost all .ip files are there.
- RichardT_altera5 years ago
Super Contributor
That's explain why I did not get it in the first place.
Seems to me it might not be a standalone IP that may cause the qsys failure.
Do you able to successfully narrow down to which group of IPs that might corrupt the qsys?