Forum Discussion
Hi,
I apologize it took so long to get to conclusions. The issue was so confusing...
The problem is solved by changing all our programming methos from a CPU controlled to a State Machine.
With the CPU programming we had gaps in the avst_clk. Now with the state machine we have 5Mhz continuous clock, 50% duty cycle.
I have found an interesting note in a datasheet declares the following:
Before beginning configuration, do trigger device cleaning by toggling the nCONFIG pin from high to low to high. This nCONFIG transition also returns the device to the configuration state.
I have tried this and it didn't help.
Stability was poor until we have decided to power cycle the Agilex device before each new programming. This solved all problems and now the programming takes 15 seconds and it is very stable.
Thanks for all the help and support
Itzik
- FakhrulA_altera3 days ago
Regular Contributor
Hi,
I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, feel free to open a new thread to get the support from Intel experts. Otherwise, the community users will continue to help you on this thread. Thank you.
Fakhrul