Editing MechaCon

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 3: Line 3:
There are two known main variants of it.
There are two known main variants of it.


The earlier one is based on the 16-bit SPC970 CPU core, running at 33.8688 Mhz, and was used on earlier boards up to GH-022. Chip name starts with "CXP10". GH-014 and earlier motherboards including GH-016 board come with a 100-pin QFP package. GH-017 up to GH-022 motherboards including GH-015 board come with a 136-ball BGA package.
The earlier one is based on the 16-bit SPC970 CPU core, running at 33 Mhz, and was used on earlier boards up to GH-022. Chip name starts with "CXP10". GH-014 and earlier motherboards including GH-016 board come with a 100-pin QFP package. GH-017 up to GH-022 motherboards including GH-015 board come with a 136-ball BGA package.


The newer one is ARM-based (Sony SR11 core, 32-bit, ARM7TDMI, running ARM v4t little endian using both 32-bit ARM and 16-bit Thumb code), codenamed "Dragon", and used from GH-023 onwards. Chip name starts with "CXR7". Comes in a 164-ball BGA package. RAM installed is 16384 bytes/16KiB, but firmware (checked on 5.12) can use up to 13024 bytes of memory.
The newer one is ARM-based (Sony SR11 core, 32-bit, ARM7TDMI, running ARM v4t little endian using both 32-bit ARM and 16-bit Thumb code), codenamed "Dragon", and used from GH-023 onwards. Chip name starts with "CXR7". Comes in a 164-ball BGA package.


The "Dragon" variant also fulfills the functions that were undertaken by the separate [[SysCon]] chip on earlier boards up to GH-022, as well as the [[RTC]]+EEPROM chip, which was separate on earlier boards (or dedicated EEPROM and RTC chips on even earlier boards).
The "Dragon" variant also fulfills the functions that were undertaken by the separate [[SysCon]] chip on earlier boards up to GH-022, as well as the [[RTC]]+EEPROM chip, which was separate on earlier boards (or dedicated EEPROM and RTC chips on even earlier boards).
Line 15: Line 15:
Dragon has the die of the combined Rohm RTC+EEPROM chip inside its own chip package, however, the EEPROM pins are exposed on the package, and the connection between Dragon and the RTC+EEPROM is done externally on the motherboard.
Dragon has the die of the combined Rohm RTC+EEPROM chip inside its own chip package, however, the EEPROM pins are exposed on the package, and the connection between Dragon and the RTC+EEPROM is done externally on the motherboard.


Every MechaCon has a 3.5 V TTL UART interface exposed on test pads that was used by service centers for example to readjust the drive and write calibration data etc. Today it can be used with tools like PMAP (currently only supports consoles with SPC970 MechaCon, support for Dragon is highly experimental) to readjust the drive mechanism after fitting a replacement laser assembly etc. For electrically connecting to the interface, see [[Test points/MechaCon UART]]. For the communication protocol, see [[MechaCon/UART_commands]].
Every MechaCon has a 3.5 V TTL UART interface exposed on test pads that was used by service centers for example to readjust the drive and write calibration data etc. Today it can be used with tools like PMAP (currently only supports consoles with SPC970 MechaCon, support for Dragon is highly experimental) to readjust the drive mechanism after fitting a replacement laser assembly etc. See [[Test points/MechaCon UART]]. For the communication protocol, see [[MechaCon/UART_commands]].


Additionaly, at least the SPC970-based MechaCon (both, QFP and BGA revisions) provides an I²C interface with SDA and SCL being exposed on test pads next to the MechaCon.
Additionaly, at least the SPC970-based MechaCon (both, QFP and BGA revisions) provides an I²C interface with SDA and SCL being exposed on test pads next to the MechaCon.
Line 49: Line 49:
1.03_0    (0x030100) | CXP101064-602R  | A-chassis DTL-T10000, DTL-H10000
1.03_0    (0x030100) | CXP101064-602R  | A-chassis DTL-T10000, DTL-H10000
---------------------|-----------------|-------------------------------------------------------------------------------------
---------------------|-----------------|-------------------------------------------------------------------------------------
unknown  (0x020027) | CXP102064-651R  | All Namco System 246 and 256 arcade systems
1.06_0    (0x060100) | CXP102064-001R  |
1.06_0    (0x060100) | CXP102064-001R  |
1.07_0    (0x070100) | CXP102064-003R  | A-chassis DTL-T10000
1.07_0    (0x070100) | CXP102064-003R  | A-chassis DTL-T10000
Line 58: Line 59:
2.04_2    (0x040202) | CXP102064-201R  | C-chassis SCPH-30003/4 (UK/Europe)
2.04_2    (0x040202) | CXP102064-201R  | C-chassis SCPH-30003/4 (UK/Europe)
2.04_3    (0x040203) | CXP102064-301R  | C-chassis SCPH-30002 (AU/NZ)
2.04_3    (0x040203) | CXP102064-301R  | C-chassis SCPH-30002 (AU/NZ)
2.04_10  (0x0A0202) | CXP102064-651R  | All Namco System 246 and 256 arcade systems
2.05_0    (0x050200) | CXP102064-702R  | B-chassis DTL-H30001, DTL-H30002
2.05_0    (0x050200) | CXP102064-702R  | B-chassis DTL-H30001, DTL-H30002
2.06_1    (0x060201) | CXP102064-102R  | B/C/D-chassis SCPH-30001 (US)
2.06_1    (0x060201) | CXP102064-102R  | B/C/D-chassis SCPH-30001 (US)
Line 76: Line 76:
2.14_2    (0x0e0202) | CXP102064-204R  |
2.14_2    (0x0e0202) | CXP102064-204R  |
2.14_3    (0x0e0203) | CXP102064-304R  | D-chassis SCPH-30002/SCPH-35002 (AU/NZ)
2.14_3    (0x0e0203) | CXP102064-304R  | D-chassis SCPH-30002/SCPH-35002 (AU/NZ)
2.??_1    (0x??????) | CXP102064-105R  | D-chassis SCPH-35001 (US)
---------------------|-----------------|-------------------------------------------------------------------------------------
---------------------|-----------------|-------------------------------------------------------------------------------------
3.00_1    (0x000301) | CXP103049-101GG | F-chassis SCPH-30001 R (USA) with separate EEPROM and RTC
3.00_1    (0x000301) | CXP103049-101GG | F-chassis SCPH-30001 R (USA) with separate EEPROM and RTC
Line 301: Line 300:
! colspan="2" |Offset!!Size!!Description  
! colspan="2" |Offset!!Size!!Description  
|- {{cellcolors|lightgrey}} |
|- {{cellcolors|lightgrey}} |
| colspan="2" |0x198||0x8||48-bit MAC address. On Dragon FATs (MechaCon version 5.xx) filled with FF. On 70k exists but has no effect. EECONF reads this value with SCMD 0x37/55 and writes this value to addresses 0xFFFE0188 and 0xFFFE018C on IOP
| colspan="2" |0x198||0x8||48-bit MAC address. On Dragon FATs (MechaCon version 5.xx) filled with FF. On 70k exists but has no effect.
|-
|-
| rowspan="4" |<abbr title="MAC address: 0x198-0x19F"><small>MAC address</small></abbr>||0x198||3||Organizationally unique identifier (OUI). On 70k always 00:04:1F and has no effect. On Deckard units can be 00:13:15, 00:15:C1, 00:19:C5, 00:1D:0D, 00:1F:A7, 00:24:8D, 28:0D:FC, A8:E3:EE. Full list unknown. By OUI registration date, console manufacture date can be partially evaluated.
| rowspan="4" |<abbr title="MAC address: 0x198-0x19F"><small>MAC address</small></abbr>||0x198||3||Organizationally unique identifier (OUI). On 70k always 00:04:1F and has no effect. On Deckard units can be 00:13:15, 00:15:C1, 00:19:C5, 00:1D:0D, 00:1F:A7, 00:24:8D, 28:0D:FC, A8:E3:EE. Full list unknown. By OUI registration date, console manufacture date can be partially evaluated.
Line 456: Line 455:
| rowspan="16" |<abbr title="Config 0 (EEGS): 0x270-0x2BF"><small>EEGS</small></abbr>|| 0x270||1||Unknown, 0x00 or 0x01 or 0x02, looks like it controls HDD
| rowspan="16" |<abbr title="Config 0 (EEGS): 0x270-0x2BF"><small>EEGS</small></abbr>|| 0x270||1||Unknown, 0x00 or 0x01 or 0x02, looks like it controls HDD
|-
|-
|0x271|| 1||Unknown, 0x03 or 0x00; From EECONF, 0xFFFE0190 on IOP gets set to this value if config available otherwise falls back to 0x03
|0x271|| 1||Unknown, 0x03 or 0x00
|-
|-
|0x272||13|| Unknown, always zero
|0x272||13|| Unknown, always zero
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)

Template used on this page: