Controller Interface (Sega Mega Drive)

the mega drive controller has two main variants, that act differently both have the exact same pins and work on all consoles, but games specifically drive the controller reading and can choose to read 6 button controllers in a special way if they desire here is the pinout looking into the console port from the front overview the general idea of the controller interface is very simply the game (via the sega asic) controls the select pin (pin 7 on the controller port) this select pin when high reads a certain set of buttons, when low reads another set of buttons for example when high pin 6 reads b, when low it reads a that is about as complicated as the 3 button controller is (explained in more detail below) the 6 button controller uses a trick where it toggles the select pin rapidly (under 12ms between toggles) and if on the third low pulse in under 12ms the controller sends left, right, up and down all low then this tells the console/game that it is a 6 button controller after that low pulse the next high pulse will then expect to read the additional buttons x, y, z and mode more detail about each specific controller type is below note the game is responsible for controlling the select pin, so all pins including select will sit high (due to pull up resistors) until the game decides it wants to read the controller this means typically while the sega logo is displayed and the game hasn't started fully, you won't see activity on the select pin after a few seconds and the game loads fully, you start to see the pulses this is a good way to detect if your console is running a game if you get no video output, to diagnose if the video out could be the problem, or if the game has successfully loaded select pin the select button (pin 7) is an output from the console and an input to the controller, in which the console sets the pin high or low more specifically, it is the game that directly controls if the select pin is high or low, and it is up to the game to do this whenever it wants and in whatever order it wants some games like sonic for example send the select pin low for a short pulse every 20ms approximately whereas games like mortal kombat ii do the opposite and keep select low most of the time and pulse high briefly i/o control it is important to understand how the console (so the sega asic) controls the pins to explain how things happen every pin (including select) is pulled high via a pull up resistor the sega asic has a transistor at the gates of each pin that is either disconnected (hi z) meaning it doesn't influence or control the pin at all, as if its not connected, therefore lets the pins float to 5v, or when it wants to control them sinks them to ground this is important in how the controller detect works controller detect this is the point at which the console tries to detect if a controller is connected, as well as what kind (3 button or 6 button) the console sends the select pin low after being high, and right after that checks if the right and left pins get pulled low too this works because the controller is wired to a multiplexer chip where the left and right pins should be shorted to ground when the select pin is low if there is no controller inserted, there is nothing driving the left and right pins low, so they stay high when the select pin is low for the 6 button controller, there is a semiconductor ic with logic that detects more advanced pulses we will discuss later the pulses low and high when reading button presses are bet ween 4 7us in length so a low pulse is between 4 7us, and a high pulse is the gap between consecutive reads (after the low pulse or 4 low pulses for 6 buttons), is around 20ms this means games read the button inputs every 20ms on average 3 button interface for the 3 button interface, there is no microcontroller or advanced logic, simply a directly wired single 74hc157 quad 2 input multiplexer the multiplexer has its select pin wired to the select pin of the console this ic allows the controller buttons all to be wired as inputs, and based on the select pin being high or low, have 2 different outputs hopefully the above diagram makes it pretty simple to understand the controller simply sends the up and down signals always low if pressed, or floating high if not when select is high, left, right, b and c pull the output pins low if pressed, or high if not when select is low, left and right are grounded always, and a and start pull the output pins low if pressed, or high if not 6 button interface the 6 button pad is functionally identical to the 3 button pad but with 3 extra buttons x, y and z, as well as a mode button some games do not function with the 6 button controller to fix this, sega added a mode button on the top right of the controller if held while the system is booting, the controller will act like a three button pad note i tested this myself on shaq fu and the controller doesn't change to a 3 button type response, it remains as 6 button so i presume some games perhaps do this and others don't, as it is the game that controls the select pin not the controller so that behaviour is entirely up to the game to choose many 6 button games make use of the mode button in game the way the 6 button pad works is supported games would toggle the select in rapidly 4 times low, within 12ms on the third toggle low, if the controller responded by sending the up and down pins low as well as left and right, then the game knew it had a 6 button controller connected here is shaq fu (a game that supports 6 button controllers) without a controller plugged in and here is with a 6 button controller connected but no buttons pressed notice how the up, down, left and right are all low on the third low pulse this is the trigger for detecting the 6 button controller here is a 3 button controller connected when using a game that supports 6 buttons notice how it simply replies with left and right low but up and down remain high therefore, the game knows that all reads are simply the 3 button controller reads notice also the start button glitches when select rises ignore this, it is just interference on the logic probes here is the comparison between a 6 button and 3 button controller connected when there is a 6 button game inserted here are where the buttons are read the 6 button controller acts like a 3 button controller for the first 2 low pulses, but on the third low (if done in under 12ms) the 6 button controllers send the up and down low as well as left and right triggering the 6 button mode now the next rise is when the x, y, z and mode buttons can be read the 4th low pulse can read the start and a buttons again, and on all official controllers i've tested the remaining buttons are all 5v during this 4th pulse finally, the select should rise again for a 4th time to reset the controller this means the next low pulse (usually in 20ms time) will start this 4 pulse cycle again during the idle select pin being high the controller buttons can be read (so up, down, left, right, b and c)