-
Bug
-
Resolution: resolved
-
Major
-
None
-
None
-
I am facing an issue with Delaye3Patch module when it is configured as following:
- Non zero DELAY_VALUE
- DELAY_MODE in TIME
Issue: The patch automatically increment the tap value to set DELAY_MODE. However, it is the wrong behavior as the DELAY_VALUE is set in ps and not in taps.
Why: As the CNTOUTVALUE is different from the DELAY_VALUE (expected because of the DELAY_VALUE mode), the IDLE_S state detects a difference and increment the CNTINVALUE up to to the DELAY_VALUE.
Suggested fix (implemented and simulated): I added an additional step named CHECK_CNT_S. IT handles the logic previously located in the IDLE_S state. Then, the IDLE_S has been changed to wait for a load command. The FSM goes to CHECK_CNT_S after loading where the logic check if the CNTINVALUE has to be inc/dec. Finally, if the FSM has reached the expect value, it goes back to IDLE_S and wait for a new LOAD_S.
Side effect: no new value can be load until busy signal goes back to low.