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

blocking assignments #2

Open
abehnke opened this issue May 10, 2023 · 0 comments
Open

blocking assignments #2

abehnke opened this issue May 10, 2023 · 0 comments

Comments

@abehnke
Copy link

abehnke commented May 10, 2023

Thanks for making this project. I have it working on a DE0-Nano - Cyclone IV - EP4CE22F17C6.

I changed the following: I used IP_TOOL_NAME "ALTPLL" for the clock so I had it divide down the 50Mhz to 2.5Mhz.

The project worked fine. I noticed that in the "always @()" blocks you are using "<=". It is my understand that in an "always @()" block only "=" should be used (?). In fact, the reference (Cummings) you mentioned says:

"Guideline #3: When modeling combinational logic with an always block, use blocking assignments"

So, I when through all the code and mass changed the "<=" to "=" in those "always @(*)" blocks. The result is: it sounds the same.

Also, in controller.v, I placed a "coeff_out = 0;" in the "always @(*)" to prevent a latch warning.

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