# False posedge event indication on a signal  

**URL:** <https://verificationacademy.com/forums/t/false-posedge-event-indication-on-a-signal/46178>\
**Category:** SystemVerilog\
**Tags:** systemverilog-interface, Clocking-Block\
**Created:** [February 15, 2024, 3:46pm UTC](https://verificationacademy.com/forums/t/false-posedge-event-indication-on-a-signal/46178 "2024-02-15T15:46:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vlad](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/v/3bc359/32.png) [@Vlad](https://verificationacademy.com/forums/u/Vlad)\
**Post date:** [February 15, 2024, 3:46pm UTC](https://verificationacademy.com/forums/t/false-posedge-event-indication-on-a-signal/46178/1 "2024-02-15T15:46:35Z")

</div>

Hi ,  
I have a signal which is part of clocking block , defined as follows :

```auto
interface my_if (input sample_clk) ;
clocking cb_clk @(posedge sample_clk);
           input sig1;
 endclocking : cb_clk 
endinterface 

```

I see the odd behaviour when @(posedge my\_if\_inst.cb\_clk.sig1) is fired once clock start ticking and sig1 is high constant .  
This is false indication as in my case I want to catch the rising edge of the signal .  
Any ideas for this behaviour and how to avoid this .  
Attaching the image when in red circle the sig1 is raised and in blue circle when clk is fired and where the @posedge is indicated

 ![Screenshot 2024-02-15 173126](https://verificationacademy.com/forums/uploads/default/original/2X/2/297d8b87d6ba3a4f6cd2c719f2f09ffafad23d9a.png)

---

<div class="post-metadata">

**Author:** ![dave\_59](https://verificationacademy.com/forums/user_avatar/verificationacademy.com/dave_59/32/4499_2.png) [@dave\_59](https://verificationacademy.com/forums/u/dave_59)\
**Post date:** [February 16, 2024, 5:26pm UTC](https://verificationacademy.com/forums/t/false-posedge-event-indication-on-a-signal/46178/2 "2024-02-16T17:26:12Z")

</div>

It seems like you have a conflicting set of requirements. Clocking block inputs sample on your `sample_clk` and that synchronizes any change on `cb_clk.sig1` with that clock. If you are looking for changes, asynchronous to that clock, then you don’t use a clocking block.
