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
The using static statement allows easy board switching, provided the boards have the same named components. It would also be trivial to write a bait-n-switch class that simply maps items based on compile directives, i.e.:
The
TopLevelInput
andTopLevelOutput
busses should be map-able to pins on the target board.This could be implemented with an attribute, like this:
The generated VHDL will then be augmented with a constraint file that maps the relevant pins.
This can be further simplified with a board configuration class, i.e.:
The user code can then map it like this:
The
using static
statement allows easy board switching, provided the boards have the same named components. It would also be trivial to write a bait-n-switch class that simply maps items based on compile directives, i.e.:The board can then be used with:
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: