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

Gateware to determine connections #100

Open
cdwijs opened this issue Oct 22, 2022 · 3 comments
Open

Gateware to determine connections #100

cdwijs opened this issue Oct 22, 2022 · 3 comments

Comments

@cdwijs
Copy link

cdwijs commented Oct 22, 2022

I would like to create gateware that shows what ball of the FPGA goes to what point on the headers.

On each pin, I would like to output a train of pulses, that indicate the ball. First a preamble, and then 2 burst indicating the row and column That way I can look at an LED to figure out the connection.

For example:
A2: 10101010101010000010000010010000 (and then repeat)
G4: 10101010101010000010010010010010010010000010010010010000
C4: 10101010101010000010010010000010010010010000

Has this already been done?
What is the best way to proceed?

@tomverbeure
Copy link
Collaborator

The more common approach is to assign each IO pin their own UART that outputs a unique l, fixed, number, and to use an oscilloscope or logic analyzer (such as a Saleae or compatible) that has built-in UART decoding functionality.

It’s not very hard to make that yourself. Chances are that you can find such a design somewhere on the web.

Tom

@cdwijs
Copy link
Author

cdwijs commented Oct 22, 2022

Where can I find the file that defines where all the connections are in the FPGA?

@cdwijs
Copy link
Author

cdwijs commented Oct 22, 2022

Here's the part of LiteX that uses the information from this repository:
https://github.com/litex-hub/litex-boards/blob/master/litex_boards/platforms/colorlight_5a_75e.py

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

2 participants