Editing Motherboards

The motherboard refers to the hardware of the PSP that contains all of the physical parts of the PSP as well as the nand image. To date, there are 8 motherboards created for the PSPs. The TA-075/79, TA-081 and the TA-082/086 series are existent on Phats, while the TA-085 and TA-085v2 exists on Slims.

]

==Information on Motherboards==

All motherboards has an onboard flash chip that contains the PSP's nand image. That nand image contains flash0-5, and the IDStorage Keys. Also, the motherboard contains the Tachyon, Baryon, Pommel, Kirk, and Spock. Here is an explanation of each:

*nand - An image of flash0-3 and the IDStorage Keys of a PSP. It is stored on the onboard flash chip.
*Flash0 - Contains the PSPs Primary Firmware.
*Flash1 - Used to store the XMB settings, network configurations, the background image in 2.00 and above, and the Custom Theme in 3.70 and above.
*Flash2 - In firmwares 3.00 and up, this contains the half of the DRM for Sony's official PS1 emulator (the other half being in the flash0)
*Flash3 - Currently unused and about 1 MiB in size although in custom firmwares it can be used along with flash2 to redirect firmware elements such as fonts.
*Flash4 - Cannot be mounted. It is suspected that it is unformatted and may be for future use hence why it cannot be read.
*Flash5 - Cannot be mounted. It is suspected that it is unformatted and may be for future use hence why it cannot be read.
*IDStorage Keys - PSP-specific keys that store info such as MAC Address, Region, etc, and are used for operation of PSP.
*Tachyon - Possibly the version of the chip which contains the CPU, ME and GPU.
*Baryon - Version number of the PSP's System Control chip.
*Pommel - The PSP's GPIO/watchdog which handles system events and shuts down in the event of a crash.
*Kirk - The PSP's main decryption/verification chip.
*Spock - The secondary decryption chip, only used to decrypt data from the UMD discs.

==TA-079 Series==
The very first version of the Phat/Classic PSP were shipped out with the TA-079 motherboards. So far, there has been 2 revisions of this motherboard with v3 adding in a new WiFi card. It is not known whether the second or third versions of the TA-079 had security features implemented to prevent downgrades or homebrew to be ran.

==TA-082 Series==
Before [[Sony]] saw the 2.50/2.60 downgrader they made a new motherboard for the PSP called TA-082, with a different Manufacturers [[Clock Generator]] Vendor ID. When a TA-082 is downgraded below firmware 2.50, the older firmware IPL won't recognise the new Clock Generator ID, and the PSP will fail to boot, appearing [[brick|bricked]].

A method of checking whether or not a TA-082 motherboard is installed on a PSP without voiding the warranty is shown [http://psp.about.com/od/homebrew/ig/TA-082-Motherboard-Tutorial/index.htm here].

On 27 December 2006, a TA-082 downgrader was released by Dark AleX, Mathieulh and harleyg allowing PSPs with 2.71 firmware and TA-082 or TA-086 motherboard to downgrade to 1.50. It appears that the downgraded units behave like any other non-TA-082s and after this process it is possible to upgrade to 2.71 SE, 3.XX OE or any other version of firmware, custom or official. However, problems do exist as a side effect of the downgrade. In order to allow the motherboard accept the 1.50 IPL some keys in the motherboards IDStorage are corrupted. This has led to many problems in downgraded PSPs.

These range from:
*Connection errors in AD-HOC.
*Brightness issues. (Upon the initial boot up of a downgraded TA-082 PSP, users may be greeted by a blank screen. Pressing the brightness button will resolve this issue)
*Battery issues. (If a PSP is shut off under 12% battery the PSP will not restart until the AC adapter is plugged in.)

One of the problems faced was the USBHOSTFS function of the PSP was corrupted after a TA-082 downgrade. The USBHOSTFS function is used in some homebrew programs and communication with the PS3. This however has been fixed in a release from a homebrew developer [http://lan.st/showthread.php?t=431 here]. Also Using the NOOBZ 2.80 and 3.03 downgraders does not create this problem since they do not change the IDStorage keys associated with the USBHOSTFS function. Only the 2.71 downgrader corrupts the USBHOSTFS IDStorage keys. 

There is a reported fix for these problems found  [http://forums.maxconsole.net/showthread.php?t=44871 here]. The latest version of this is idreset v7 (for people who downgraded using the Dark AleX 2.71 TA-082 downgrader) which is found  [http://forums.maxconsole.net/showthread.php?t=44871&page=8 here] or idcopy v1 (for people who downgraded with NOOBZ 2.80 TA-082 downgrader) which is found  [http://forums.maxconsole.net/showthread.php?t=44871&page=11 here]. This has been reported to fix most or all of the problems associated with these downgraders. These fixes are for TA-082 and TA-086 PSPs only.
It is also possible to use a modified 1.50 IPL to boot the 1.50 on TA-082/TA-086 without modifying IdStorage.

The official Sony updates 3.30+ now check for these corrupted keys, and will refuse to install if it finds them.  Users on homebrew enabled PSPs can restore the keys and then upgrade to 3.30+, but those who have corrupt keys and have upgraded to firmwares 3.10 or 3.11 are now stuck.  They cannot upgrade to any newer firmware but also cannot use homebrew to change the keys or downgrade.  Now that a user-mode exploit has been found on these firmwares (with the Illuminati exploit) it is hoped that this may pave the way towards a kernel mode exploit which would be able to reset the IDStorage keys to allow upgrading. If a kernel mode exploit can not be found the only solutions would be to purchase and install a mod-chip or use the Pandora's Battery as a downgrader.

3.71 M33 Custom Firmware fixes the IDStorage before upgrading. It automatically checks if it is a TA-082/TA-086 before fixing it. 

Newer downgraders have been built with these issues in mind.  The only problem that remains with the latest downgrader (3.50 "Illuminati" exploit) is the brightness issue. However, a fix (which makes the PSP read from firmware 2.71 files when controlling brightness) can be applied to downgraded PSPs, thereby eliminating this problem as well (However, one must remove these added files prior to using the recovery downgrade / official update otherwise it can results in a brick). Alternatively, some have suggested this could be fixed with keycleaner, it has been reported not resolving the brightness issue.
TA-079 up to TA-081 motherboards are not affected by these problems.

==TA-085 Series==
The currently released PSP Slim series are known to use a TA-085 motherboard, with the recent release of the TA-085 v2, and later on the TA-088 series. The only extra security in the TA-085v2 motherboard revision is the inability to write to the PSP battery's EEPROM, so a Pandora battery cannot be created on a TA-085 v2. However, a battery already with the Pandora EEPROM code can still be used, allowing regular custom firmware installation. No other abilities have been discovered yet. TA-085v1 Slims function normally and are still able to write to the battery's EEPROM.

==TA-086 Series==
Please refer to the TA-082 series section. Everything in it pertains to this as well.

==TA-088 Series==
Recently, TA-088 has been found in the newer Slims in Asia. (Particularly the Mint Green one) The TA-088 functions similar to the TA-085v2, and blocks the ability to write the battery's EEPROM while the PSP can still read it. The TA-088 has been incorrectly referred to as the TA-085v3 as motherboard identification tools referred to it as the TA-085, and it has been renamed to the TA-088. As time went on, Slims with different revisions to the TA-088 motherboard has been released, and are confirmed to be Pandora-proof. The TA-088v2 first reported being shipped with Slims in the Asia continent, has a patched tachyon that disabled the loading of all current Pandora Initial Program Loaders (ipl), but however did not defeat the loading of custom firmware ipls. The ability to flash custom firmware via Despertar Cementerio will be fixed with the newest release (version 6) which uses a new kernel, therefore allowing Pandora to work again. A third revision to the TA-088 came weeks later. Dubbed the TA-088v3, this motherboard is completely Pandora-proof as discovered by Silverspring of the M33 Team. According to Silverspring, a new Tachyon has been inserted into these motherboards, and patched the loading of any IPL's before the PSP booted up. If this patch is correctly applied, Pandora is defeated on all TA-088v3's until a new development comes through.

==TA-090 Series==
There has been reports that the TA-090 has shown up in a PSP-2000.  There has been confirmed reports by Alek that it is also in the PSP-3000.  This is the reason for the v1/2 listed below.  The PSP-2000 version of the TA-090 is hackable with pandora. However, The PSP-3000 version of TA-090 Pandora's battery does not even turn on the PSP.

==Tachyon / Baryon / Pommel's==

PSP-100x<BR>
TA-079v1.  Tachyon: 0x00140000, Baryon: 0x00306000, Pommel: 0x00000103<BR>
TA-079v2.  Tachyon: 0x00200000, Baryon: 0x00306000, Pommel: 0x00000103<BR>
TA-079v3.  Tachyon: 0x00200000, Baryon: 0x00040600, Pommel: 0x00000103 (Not Sure if this one is correct)<BR>
TA-081....    Tachyon: 0x00300000, Baryon: 0x00040600, Pommel: 0x00000103<BR>
TA-082....    Tachyon: 0x00400000, Baryon: 0x00114000, Pommel: 0x00000112<BR>
TA-086....    Tachyon: 0x00400000, Baryon: 0x00121000, Pommel: 0x0000<BR>
<BR>
PSP-200x<BR>
TA-085.....    Tachyon: 0x00500000, Baryon: 0x0022B200, Pommel: 0x00000123<BR>
TA-085v2..  Tachyon: 0x00500000, Baryon: 0x00234000, Pommel: 0x00000123<BR>
TA-088v1..  Tachyon: 0x00500000, Baryon: 0x00243000, Pommel: 0x00000123<BR>
TA-088v2a Tachyon: 0x00500000, Baryon: 0x00243000, Pommel: 0x00000123<BR>
TA-088v2b Tachyon: 0x00.........., Baryon: 0x00..........., Pommel: 0x0000<BR>
TA-088v3..  Tachyon: 0x00.........., Baryon: 0x00..........., Pommel: 0x0000<BR>
TA-090v1..  Tachyon: 0x00.........., Baryon: 0x00..........., Pommel: 0x0000<BR>
<BR>
PSP-300x<BR>
TA-090v2..  Tachyon: 0x00.........., Baryon: 0x00..........., Pommel: 0x0000<BR>