--- Quote Start ---
If the device (SX vs ST) have the same logic density, then their IDCODE will be the same:
https://documentation.altera.com/#/00005773-AA$NT00080225 Now if the density is different, when you use FPGA manager to program the FPGA image, you can code in such a way that the FPGA manager returns error to the program if the attempt to program the FPGA is unsuccessful (which is the case when you program a part with mismatch image). Presumably then you can load the second image which is correct for the aforementioned device. I know this is not pretty... but could be something :)
--- Quote End ---
Thank you. I had feared something like this because when I use "auto detect" for devices using Quartus Programmer it gives me an option for which device to use. That's just plain silly that Altera can't put different device IDs in each chip.
Or is the implication that a build for the ST D5 would run on the SX C5?
Final question - is there a Linux driver to run the Scan Manager? Or am I going to have to write some code myself if I use this method? The other option is to embed the device type in my FPGA build, so that the ARM can query my register. At least I can then make the builds have a unique code for each different chip!
Honored Contributor
