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

Connecting Wishbone busses - naming conventions #60

Open
wzab opened this issue Feb 21, 2021 · 0 comments
Open

Connecting Wishbone busses - naming conventions #60

wzab opened this issue Feb 21, 2021 · 0 comments

Comments

@wzab
Copy link
Owner

wzab commented Feb 21, 2021

I have just lost a significant amount of time in one of AGWB-using designs to fix my stupid mistake caused by inconsistent naming of signals.

We usually use signals like below to name the parts of the Wishbone bus:

LINKS_wb_m_o => LINKS_wb_m_o,

LINKS_wb_m_i => LINKS_wb_m_i,

However sometimes one may use signals defined from the slave point of view:
LINKS_wb_s_o, LINKS_wb_s_i...

The problem appears if those two conventions meet in a single block. That happened to me, and resulted in a difficult to spot error. I had two signals - one connected to the master, and another to the slave. The synthesis tool didn't complain, but the design didn't work.

Therefore I suggest to either use only the signals named from the master perspective, or (maybe better) use suffixes describing the direction: LINKS_wb_m2s, LINKS_wb_s2m.

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