|
|
# VHDL coding
|
|
|
|
|
|
-----
|
|
|
|
|
|
## VHDL Training
|
|
|
|
|
|
- See [Training](/Training#vhdl)
|
|
|
|
|
|
-----
|
|
|
|
|
|
## VHDL Coding Guidelines
|
|
|
|
|
|
Using the similar coding styles will ease re-useability. Many projects
|
... | ... | @@ -19,6 +27,8 @@ complex modules. |
|
|
- White Rabbit core collection - Development - [Coding
|
|
|
style](https://www.ohwr.org/project/wr-cores/wikis/Development-todo#coding-style)
|
|
|
|
|
|
-----
|
|
|
|
|
|
## Wishbone bus
|
|
|
|
|
|
Many Open designs use the Wishbone specification. You may want to
|
... | ... | @@ -57,11 +67,11 @@ at CERN, I think they are still valid and useful. |
|
|
future upgrades of hardware that still will work with old software
|
|
|
that doesn't know about added or hidden possibilities.
|
|
|
3. Interrupt status register (showing the cause of an interrupt):
|
|
|
actually the same as 4. But make the most significant bit an OR of
|
|
|
all the other bits, likely combined with an interrupt mask register.
|
|
|
With a single assembly instruction (check if negative) you can see
|
|
|
if any of the bits is set. This would make software go faster if it
|
|
|
has to scan many devices to check who has interrupted.
|
|
|
actually the same as rule 1. But make the most significant bit an OR
|
|
|
of all the other bits, likely combined with an interrupt mask
|
|
|
register. With a single assembly instruction (check if negative) you
|
|
|
can see if any of the bits is set. This would make software go
|
|
|
faster if it has to scan many devices to check who has interrupted.
|
|
|
|
|
|
### General
|
|
|
|
... | ... | @@ -85,5 +95,5 @@ at CERN, I think they are still valid and useful. |
|
|
|
|
|
-----
|
|
|
|
|
|
Erik van der Bij - 6 November 2015
|
|
|
Erik van der Bij - 27 November 2015
|
|
|
|