# Driver , Sequencer N Sequence Parameterization

**URL:** <https://verificationacademy.com/forums/t/driver-sequencer-n-sequence-parameterization/38560>\
**Category:** UVM\
**Tags:** Sequencer-N-Sequence-Parameterization, UVM, driver\
**Created:** [January 8, 2021, 5:52pm UTC](https://verificationacademy.com/forums/t/driver-sequencer-n-sequence-parameterization/38560 "2021-01-08T17:52:26Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 9, 2021, 6:47pm UTC](https://verificationacademy.com/forums/t/driver-sequencer-n-sequence-parameterization/38560/4 "2021-01-09T18:47:26Z")

</div>

_In reply to [MICRO\_91](https://verificationacademy.com/forums/t/driver-sequencer-n-sequence-parameterization/38560/3):_

The sequence/sequencer/driver code is quite convoluted to follow. Instead of using pure TLM protocol, or adapting TLM to meet the requirements of the sequences, they branched and created a separate sequencer API.

I don’t think a sequence has to have the exact same parametrization, but I do think it has to have a uvm\_sequence\_item in the same inheritance line to be passed with incompatible casting.

---

_[View the full topic](https://verificationacademy.com/forums/t/driver-sequencer-n-sequence-parameterization/38560)._