You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: