Skip to content

Conversation

splinedrive
Copy link
Contributor

No description provided.

@Paebbels
Copy link
Member

Thanks for contributing to this project.

Please split your XDC file into one file per logical interface.

@splinedrive
Copy link
Contributor Author

I can split but is their a naming convention regarding pins?

@Paebbels
Copy link
Member

Paebbels commented Oct 1, 2022

Have a look at KC705.

I saw LEDs in your file, so that would be GPIO.LED.xdc file with CmodA7_GPIO_LED... pins.

@Paebbels
Copy link
Member

Paebbels commented Oct 1, 2022

Btw. don't comment out pins, they can be all active.

Commenting is not needed because:

  • by adding multiple XDC files, you "activate" the matching interfaces like LEDs, buttons, Ethernet etc.
  • in Vivado you can disable a file to deactivate an interface.

Furthermore, by having logical pin groups in files, you can also have matching pins timings or other clock and placement constraints close by, so others won't miss adding them to the project.

@Paebbels
Copy link
Member

Paebbels commented Oct 1, 2022

Oh, and you can read in the projects documentation e.g. starting here: https://hdl.github.io/constraints/Structure.html

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

Successfully merging this pull request may close these issues.

2 participants