Data and Diagrams of how the NES reads the controller (a VERY interesting find!)

Da Slippery Minx

New member
So, I really don't know where this thread is best placed, obviously it's both hardware and OS Logic related but I don't see much in the way for the best place to put this. Suggestions are welcome.

So! I was trying to figure out what limitations either the controller or NES hardware had in terms of potentially attaining/making a controller that had additional buttons (lately it seems like web searches try to get you to buy buy buy, instead of learn learn learn... But! I stumped upon an interest gem or two in regards to how the NES interprets the controller, AND I found out a JUICY fact!: 2 of the pin ports that are in the connector aren't, used, meaning the pins don't make ANY electrical contact with the NES it's self!

What lead me down this search is because I've been wanting to find a way to add more buttons to the controller. For for all your ubermench programmers and such, do you think it's possible to for the NES to attain some kind of new code or modify existing code to facilitate more buttons on a controller? OR, maybe there's a way for the NES to interpret Turbo button actions as an entirely different function (as another button,) ie: have it interpret the speed of the turbo function and make it a totally different function that ISN'T turbo.

Info links are here:
This one is a bit more in depth: http://taylorbooth.com/NESController.htm
this one is a bit redundant but still relevant: https://tresi.github.io/nes/
 

dale_coop

Moderator
Staff member
The wiki of NESdev has a LOT of documentation about reading NES controllers (all kind of controllers) with ASM code.
 

Da Slippery Minx

New member
Thank you Dale! More great info from you, I'm amazing that my web search didn't show this NESdev wiki page o_O. I'll be sure to check it out often.
 
Top Bottom