Editing Test points/MechaCon UART

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 11: Line 11:
* GH-008, GH-016, GH-017, GH-018, GH-029, GH-036, GH-040
* GH-008, GH-016, GH-017, GH-018, GH-029, GH-036, GH-040


=How to connect=
=Notes=
To enable the UART interface, the console must be put into testmode by pulling the TEST_MODE0 test point to ground. The interface operates at '''57600 baud 8N1''' (automatically set correctly by PMAP and the official service tools) and rather non-standard '''3.5 V'''.
 
3.3 V signal levels work fine for communication, but care must be taken not to additionally connect an internal 3V3 voltage regulator, which is provided on some USB UART interfaces, to the console, since this will conflict with the console's own 3V5 voltage regulation and could damage the USB device and/or the console. On such interfaces, it should suffice to '''just connect Rx, Tx and GND'''. Even better would be to use a RS-232-to-TTL level shifter, which can take the 3V5 voltage as reference directly from the console itself.
 
==Notes==
*'''RX''' and '''TX''' are sometimes swapped in these pictures. This is due to the contributors not having unified their naming conventions, with some marking RX and TX as seen from the MechaCon's side and others marking RX and TX as seen from the PC's (or it's interface's) side. If you can't establish a connection one way, you should try swapping RX and TX and try again. There are plans for unifying the naming in the future.
*'''RX''' and '''TX''' are sometimes swapped in these pictures. This is due to the contributors not having unified their naming conventions, with some marking RX and TX as seen from the MechaCon's side and others marking RX and TX as seen from the PC's (or it's interface's) side. If you can't establish a connection one way, you should try swapping RX and TX and try again. There are plans for unifying the naming in the future.
*The '''3.3V''' marked on most pictures are '''actually 3.5V''', since that's what MechaCon runs off. If you are using e.g. a RS232-to-TTL level shifter (like e.g. a MAX3232-based level shifter), the PS2's 3.5V need to be connected to your level shifter's Vcc. However, it should not be connected to anything that has it's own 3.3V regulator (like e.g. some USB-to-TTL converters), since the regulator on the PS2's board and your converter will end up in a feedback loop, potentially causing damage. There are plans for unifying the naming in the future.
*The '''3.3V''' marked on most pictures are '''actually 3.5V''', since that's what MechaCon runs off. If you are using e.g. a RS232-to-TTL level shifter (like e.g. a MAX3232-based level shifter), the PS2's 3.5V need to be connected to your level shifter's Vcc. However, it should not be connected to anything that has it's own 3.3V regulator (like e.g. some USB-to-TTL converters), since the regulator on the PS2's board and your converter will end up in a feedback loop, potentially causing damage. There are plans for unifying the naming in the future.
Please note that all contributions to PS2 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS2 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)