Using GoConfigure SW 6.45.001 with MacOS Monterey 12.7.6, with an SLG46620V.
When I cascade CNTs such that CNT(n) is clocked by CNT(n-1)'s output, CNT(n)'s output changes on the falling edge of its clock.
It used to change on the rising edge of its clock, with older GoConfigure SW, and designs were based on this!
The attached GP file shows every CNT changing its output on the falling edge of its clock (except CNT0, which is clocked directly
from the RC Osc).
Is there a magic option for specifying the active clock edge? (that would be nice!)
Cascaded CNTs - clocked by falling edge.gp4.zip
Hi,
I ll check and come back to you
Thanks
AB
Kindly check the properties CNT/DLY block , I think edge select is falling for CNT block
Hi AB, the different counters have a mix of rising, falling, and both for the Edge Select. But as you can see it is defined as:
In Delay or edge detect mode, select which edge to delay. In Counter Mode with Reset/Set In, select which edge resets the counter to 0.
So that's not the problem. And the CNTs clock on the rising edge when cascading is not used.
Hello AB, do you have any news yet on this?
Were you able to recreate this using the file I had sent?
...Craig
We are checking , I will get back to you shortly
AB, what's the latest on this? Are you able to recreate this?
There was some bug, our software team has fixed the same . Its will be added in next model
Okay, thanks AB!
Hi AB, I tried a very simple design using GoConfigure SW ver 6.45.002 on MacOS and it still shows the same problem where a cascaded counter's output changes on the falling edge of its clock. The design was a new one, but the original file attached still fails also.
You said this problem in 6.45.001 would be fixed in the next SW release but it is still there in 6.45.002.
Please investigate this.
Thanks,
V 6.45.002 does not include new model – fix is not included as well
Hi AB,
So when you said "There was some bug, our software team has fixed the same . Its will be added in next model", what did you mean by "model"?
Hi AB - any answer about this?
It will be added in upcoming Go configure version .
Hi AB, a new model like the 46620?
... Craig
Hi AB, I tried the new 6.46.001 GoConfigure SW, and it still shows the error using the original design file. That was disappointing!
Do the SW developers understand what the problem is that I am describing here? Did they confirm it was fixed with the MacOS version of the 6.46.001 SW?
If they are not clear, please ask them to contact me directly.
They have already fixed it and will be add in coming version. Once it added I ll let you know
Thanks AB.