New Contributor
New ContributorThose are both good ideas. Here is what I have done and see.
I have now "built" the core in the same version(20.1) of Quartus as I am using to "compile" the code. I don't think this made any differences. I am "compiling" 5 different flavors/functions that go into the same hardware. All flavors have the exact same top levels of code and the exact same flash interfaces (Generic Serial Flash Interface and Remote Update), but they each have a different set of other functions they perform. Of these 5 flavors, one of them behaves correctly. An interesting (hopefully unrelated) observation is that the 4 flavors that don't work are all in the 70% full range and the the 1 flavor that does work is in the 20% full range. In my mind, this was leading me down a timing issue road, but I am baffled by fact the error exhibits itself in exactly the same way for every build (two of the middle address bits get lost somewhere), and it is telling me that everything is constrained and meeting timing.
As for the license, I don't see anything specific related to the Generic Serial Flash Interface IP core in the "License Setup" tool. I see listed products like 0005, 0057, 0001, 0004, Reed-Solomon, Viterbi, Triple-Speed Ethernet, Nios II, ......... and all these have a different date next to them. I see the following dates 2022.12, 2021.12, 2018.10, 2012.08, 2011.07, 2011.08. I am not sure how these dates relate to specific software versions, and I am not sure which license on this list would relate to the Generic Serial Flash Interface. I am assuming that these dates relate to a specific version of software and I don't know what dates apply to Quartus 20.1.
Thanks for continuing to look at this.
