-
Notifications
You must be signed in to change notification settings - Fork 14
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
pmod_led does not match the Tang Primer 25K pinout #11
Comments
@harbaum According to the schematic, s1 connects with H11 and s2 with H10. Also, it seems that the LXES15AAA1 will give them a GND bias, I guess. |
Yes, H10 and H11, that's what I wrote. And no, D1 and D2 don't give a noticable GND bias. They bascially latch to the high state once pressed without pulldown enabled in the FPGA. I am sure C1 and C2 will discharge over time. But that does not happen within a few seconds. Didn't try to wait longer ... |
The problem is that these demos probably are what users try first. E.g. the HDMI demo also does not work for me. And it also has a misconfigured LED. So without getting an HDMI output I checked if I at least the LED would be blinking as that's what I expected from a first glance at the code. It didn't! So I assumed something fundamenally wrong with my board. An the fact that this pmod_led demo also didn't do anything even supported that assumption. |
PR: #16 |
The pin assignments of the pmod_led demo does not match the Tang Primer 25K. E.g. the "key" in this example is assigned to K6. But the keys on Tang Primer 25K base board are on H10 and H11. K6 is USB_N
TangPrimer-25K-example/pmod_led/src/pmod_led.cst
Line 69 in 434ef83
Furthermore the button S1 on H11 is active high and does not have a pull-down. The pull-down in the FPGA thus needs to be enabled and the polarity reversed.
The text was updated successfully, but these errors were encountered: