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

Distinct, cleaned-up and fixed (hopefully) gaming PMOD verilog #17

Open
wants to merge 2 commits into
base: gaming-pmod
Choose a base branch
from

Conversation

psychogenic
Copy link

Couldn't locate the VGA PMOD that I'm pretty certain I have, so I did this semi-blind, just using a scope, but the output is sensible and reacts to button presses as expected.

I have:

  • made various fixes;
  • isolated the gaming_pmod verilog from the sample project, so that it's reusable;
  • changed things to support 2 controllers, have an is_present field to indicate detection, and leverage the 2-bit colours in the sample to actually show the state of both controllers with the bars;
  • commented the module code to assist anyone actually using it

Also of note, something that cause quite a bit of putzing around, was we agreed on pins 4,5,6 but my snespmod docs are using PMOD indexing, and refer to ui_in[5:3], but this driver used ui_in[6:4]. I've left that, but need confirmation (and to edit) the CH32V lib accordingly.

@psychogenic
Copy link
Author

I've updated the snespmod library docs, assuming we were talking TT ui_in numbering. Lemme know if this isn't what we want.

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.

1 participant