Thanks for the quick response. This gives me some things to try.
But maybe you can help a bit - my design is initially configured using the Altera Blaster. The technician loads the correct JIC file based on which device (EPCQ128 or EPCQ128A) is on board. All is good.
But, for remote field update, I was hoping to have an RPD (or other type) of file that would work for either of the 2 config ROM types.
Can I just create the RPD using the variation that has the most dummy clocks and expect it to work for both?
Thanks and regards.
I have tried your suggestion and unfortunately, it does not work. Here is my test:
- Create a JIC file for EPCS128.
- Create a JIC file for EPCQ128.
- Create a JIC file for EPCQ128A.
- Program an EPCQ128A part using each of the three files above - result: 1 and 3 worked.
- Program an EPCQ128 part using each of the three files above - result: only #2 worked.
A file comparison shows that the resulting JIC files for the EPCS128 and the EPCQ128A are identical; the EPCQ128 file is different.
Yet, AN-822 says that with ID Check off, I can migrate from EPCS to EPCQ. I have not found this to be true.
Further, AN-822 says I can migrate from EPCQ to EPCQ-A. I have also found this to be not true.
Can you clarify the contents of AN-822 for the above test cases?
Thank and regards.
- "Program an EPCQ128A part using each of the three files above - result: 1 and 3 worked."
- "Program an EPCQ128 part using each of the three files above - result: only #2 worked."
If you refer my first post i.e. "Operation Commands " from page 4. here we can see that, in EPCQ-A devices, the dummy clock is fixed at 8 and 6 for fast read and extended quad input fast read respectively. Therefore you must regenerate the programming files, such as .pof, .jic, and .rpd. so JIC file created for EPCQ128 may not be valid but in case of EPCS devices the dummy clock is fixed at 8 for fast read, therefore you do not have to regenerate the programming files if all other conditions are met. Table 3 on page 6 defines the need to regenerate the programming files.
Could you please provide bit more information like,
- Quartus Edition/Version used
- Kit used
Let me know if this has helped to resolve your issue.
Thanks for your help on this.
I agree that the text on page 4 points out the issue. But if you look at tables 1,2 and 3, they seem to paint a much rosier picture.
I also see some notes below table 3 which do not appear on my copy of AN-822. Is there a way to get notification when an app note is corrected or updated?
Nonetheless, this is now my issue to try and clean up.
Thanks again for your help with this issue.
Now, on to the next issue: EPCQ256
This part went on End of Life in the spring of 2018.
At the time, I was told that Altera would provide a solution by September of 2018.
So far, I have not heard of any such solution.
Do you have any advice?
As far as further information, I typically use Quartus V17.1, but have also tried all of my tests with V16 and V18.
For Kit Used, there is no kit; I have an installed customer base of about 200 units currently. All testing has been performed on our PCB.
Thanks and regards.