Forum Discussion
Hi sstrell
I would prefer 1x QSF file if possible -- the device migration list ensures everything is otherwise compatible across the prospective devices so why have multiple QSF files -- say for instance we discover an transceiver assignment change improves transceiver performance then we would have to edit multiple QSF files (via Quartus GUI of course) to keep them in synch functionally
Regards
Steve
That's your call then. I thought the only thing you wanted was to quickly switch devices and I/O assignments, but if there are other things that may change and need to match between the different revisions, then it might not be the best way to go.
You could instead use Tcl scripting in the .qsf for this type of stuff.
- Steve-Mowbray-ENL1 year ago
Occasional Contributor
thanks sstrell -- was just checking there wasnt a quick and easy GUI method of switching devices from the Quartus GUI
- sstrell1 year ago
Super Contributor
Switching devices is easy in the GUI (Assignments menu -> Device). It's just that many assignments get blown away when you switch devices and you also may have to regenerate IP.
- Steve-Mowbray-ENL1 year ago
Occasional Contributor
Hi sstrell certainly that was what I was concerned about -- I did an experiment and it appears that the only assignment that gets stomped in QSF is the DEVICE_MIGRATION_LIST which is easy enough recreated -- regenerate the the QSYS and it seems to work -- will use this method with extreme caution going forward...