Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Distinguish between actual flip flops and software variables #6

Open
jotego opened this issue Feb 8, 2021 · 0 comments
Open

Distinguish between actual flip flops and software variables #6

jotego opened this issue Feb 8, 2021 · 0 comments

Comments

@jotego
Copy link

jotego commented Feb 8, 2021

It seems that variables in the opm_t structure are registers in the original design, but some of them are not.

One such example is lfo_out2_b. This variable is stored in function OPM_DoLFOMult and accessed in function OPM_DoLFO1. Both functions are called one after the other in the same clock cycle. Thus lfo_out2_b is actually a way to transfer a variable from one function to the other within the same clock cycle. This is confusing as most members of the opm_t structure seem to represent registers.

Maybe a suffix for this kind of software variables would be advisable. Maybe _soft or _wire would be good.

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

No branches or pull requests

1 participant