# APB write cycle assertion

**URL:** <https://verificationacademy.com/forums/t/apb-write-cycle-assertion/38801>\
**Category:** SystemVerilog\
**Tags:** SVA, SystemVerilog\
**Created:** [March 9, 2021, 6:31am UTC](https://verificationacademy.com/forums/t/apb-write-cycle-assertion/38801 "2021-03-09T06:31:28Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![rag123](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/r/eada6e/32.png) [@rag123](https://verificationacademy.com/forums/u/rag123)\
**Post date:** [March 11, 2021, 1:34am UTC](https://verificationacademy.com/forums/t/apb-write-cycle-assertion/38801/5 "2021-03-11T01:34:17Z")

</div>

_In reply to [ben@SystemVerilog.us](https://verificationacademy.com/forums/t/apb-write-cycle-assertion/38801/4):_

Hi Ben,

Thanks for the reply. Yes there are two cases one with wait state and one without wait state.

```verilog

@(posedge pclk) no_wait_write ##0 // generated by the testbench or slave
              $rose (pwrite && psel) |-> ##1 // 1
              $stable(paddr && pwdata) ##0 // 2 
              $rose (penable && pready) ##1 // 3
              pwrite && !psel && !penable); // 4

$stable(paddr && pwdata) // For this line
Are we not expecting the paddr and pwdata to be stable for 2 clks?
```

---

_[View the full topic](https://verificationacademy.com/forums/t/apb-write-cycle-assertion/38801)._
