David Poulin

I've renamed the agent to obi_memory (the self-test env and TB keep the same names). ST TB passes for 2020.3. All files [checked in](https://github.com/Datum-Technology-Corporation/core-v-verif/commit/1ba04c914e33e7fac43732b748485ff3131c9169).

@MikeOpenHWGroup what are the next steps? We still need to write a virtual sequence to duplicate the behavior of the peripherals and different memories (based around `uvma_obi_memory_storage_slv_seq_c`). Has the OBI...

Ok, I'll get going on the virtual sequence. Any name you prefer? I was thinking uvme_cv32e40p_mem_slv_vseq_c

First cut of the new virtual sequences implementing dp_ram.sv and mm_ram.sv for cv32e40p has been issued a pull request: https://github.com/MikeOpenHWGroup/core-v-verif/pull/3

Fix in PR #943

This is the exception to the rule. We have a cfg parameter that is random constrained: `cfg.drv_idle_mode`. One of the options is to drive random data on idle. I think...

> "... lint error because class members randomized with these calls cannot be constrained" cfg.drv_idle_mode is being constrained to create this random behavior. That's why I'd say that this is...

I disagree with the lint rule. While it may make sense to only create the components needed by the agent cfg, it ends up being a nightmare from a TLM...

There's a different reason to keep the sequencer in the mix, but that won't come up until we start using the advanced UVM approach of implementing monitoring loops in sequences....

Fix in PR #943