# P\_sequencer is a null object access

**URL:** <https://verificationacademy.com/forums/t/p-sequencer-is-a-null-object-access/34713>\
**Category:** UVM\
**Tags:** UVM, p\_sequencer\
**Created:** [July 20, 2018, 8:02pm UTC](https://verificationacademy.com/forums/t/p-sequencer-is-a-null-object-access/34713 "2018-07-20T20:02:57Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cgales](https://verificationacademy.com/forums/letter_avatar_proxy/v4/letter/c/ccd318/32.png) [@cgales](https://verificationacademy.com/forums/u/cgales)\
**Post date:** [July 24, 2018, 2:55pm UTC](https://verificationacademy.com/forums/t/p-sequencer-is-a-null-object-access/34713/4 "2018-07-24T14:55:08Z")

</div>

_In reply to [zz8318](https://verificationacademy.com/forums/t/p-sequencer-is-a-null-object-access/34713/3):_

It’s hard to use something if it is generating errors. There is never a need to use p\_sequencer, and I consider the ‘legacy’ excuse to be very poor.

However, after getting off my soap box, you should never see a null p\_sequencer handle if everything occurs in the correct phases. All of the build\_phase() should be complete prior to any run\_phase() execution. I’m assuming that you are calling send() in the run\_phase()?

You should also make sure to use:

```verilog

m_trans = my_trans::type_id::create("m_trans");

```

instead of calling new(). This will ensure that p\_sequencer is assigned correctly.

---

_[View the full topic](https://verificationacademy.com/forums/t/p-sequencer-is-a-null-object-access/34713)._
