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

SPI SS Pin is Incorrectly Bound. #3

Open
xusine opened this issue Jun 10, 2020 · 3 comments · May be fixed by #4
Open

SPI SS Pin is Incorrectly Bound. #3

xusine opened this issue Jun 10, 2020 · 3 comments · May be fixed by #4

Comments

@xusine
Copy link

xusine commented Jun 10, 2020

According to the official XDC file, the SPI SS pin should be mapped to F16, while in this project the port is bound to T16. This may cause unsuccessful data transmission.

@xusine xusine changed the title SPI SS Pin is Incorrectly bound. SPI SS Pin is Incorrectly Bound. Jun 10, 2020
rdoursenaud added a commit to EMATech/pynq-z1_board_files that referenced this issue Jan 8, 2022
Swap F16 and T16 to match Digilent master XDC
Fixes cathalmccabe#3
@rdoursenaud
Copy link

rdoursenaud commented Jan 8, 2022

I was about to PR these board files upstream at https://github.com/Digilent/vivado-boards

While preparing to do so, I red the notes from https://github.com/Digilent/vivado-boards/blob/master/README.md
According to the notes, the swap was due to Digilent/vivado-boards#5.

Since this board is now retired, I guess it would make sense to follow the master XDC convention.

@cathalmccabe Please let me know what you think.

@cathalmccabe
Copy link
Owner

That would seem to make sense for this Rev C, however I don't have a board I can test this on right now.

@rdoursenaud
Copy link

@cathalmccabe Thanks for replying.
I’ll keep using my own fork for now and report back if I encounter any issues.
Anybody stumbling upon this issue can also try it from my PR/fork and let us know.

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 a pull request may close this issue.

3 participants