Cascaded CNTs clock on falling edge

Hi, 

I ll check and come back to you

Thanks 

AB

Hi, 

Kindly check the properties CNT/DLY block , I think edge select is falling for  CNT block 

Thanks 

AB

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:

Edge select:

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.

• Both: both rising and falling edges of the pulse are delayed;
• Falling: only falling edge delayed;
• Rising: only rising edge delayed;
• High Level (Re)set: When RESET IN is high, the counter is reset to 0. When SET IN is high, the counter is set to the design counter value;

So that's not the problem. And the CNTs clock on the rising edge when cascading is not used.

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:

Edge select:

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.

• Both: both rising and falling edges of the pulse are delayed;
• Falling: only falling edge delayed;
• Rising: only rising edge delayed;
• High Level (Re)set: When RESET IN is high, the counter is reset to 0. When SET IN is high, the counter is set to the design counter value;

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

Hi, 

We are checking , I will get back to you shortly

Thanks

AB

AB, what's the latest on this? Are you able to recreate this?

Hi, 

There was some bug, our software team has fixed the same . Its will be added in next model

Thanks 

AB

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,

...Craig

Hi, 

V 6.45.002 does not include new model – fix is not included as well

Thanks 

AB

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"? 

...Craig

Hi AB - any answer about this?

Thanks,

...Craig

Hi, 

It will be added in upcoming Go configure version .

Thanks 

AB