Skip to content
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.

Poke for internal registers #215

Open
danielkasza opened this issue Oct 15, 2020 · 1 comment
Open

Poke for internal registers #215

danielkasza opened this issue Oct 15, 2020 · 1 comment

Comments

@danielkasza
Copy link

This is related to #17 and #182.

It would be nice to be able to poke internal registers of modules. It would make it much easier to test modules with complex state machines.

I understand that registers may be removed by transformations. I think it would be acceptable to only support this when registers are somehow marked for modification by tests.

@ekiwi
Copy link
Collaborator

ekiwi commented Nov 5, 2021

The big problem with this feature is that poking registers in a Verilator simulation is very difficult. Not because of the name mapping. Tracking register names and generating the correct flags for Verilator to expose them is do-able. The problem is that Verilator will pre-compute the next value for registers. So if you change the register content from the outside and then continue the simulation, the register value will change back to the pre-computed next value which is not what we want.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants