Vita Guides: Difference between revisions

From PlayStation Hardware Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 23: Line 23:




== What kind of QAF Tokens are there and what do they do ==
{| class="wikitable"
! Name !! Flags !! Notes
|-
| QAF_QATEAM_E || 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 || for "QualityAssurance Team" units (early)
|-
| QAF_QATEAM_MINI_E || 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 || for "QualityAssurance Team" units
|-
| QAF_QATEAM_FULL_E || 11 00 00 00 00 00 0F 04 64 00 00 00 04 00 00 03 || for "QualityAssurance Team" units
|-
| QAF_SYS_DEV_I|| 33 00 00 00 00 00 07 05 73 01 00 01 06 03 03 01 || for DevKits used for "System Development"
|-
| QAF_MGVIDEO_DEV_I|| 33 00 00 00 00 00 07 05 73 01 00 11 06 02 03 01 || for DevKits used for "MagicGate Video Development"
|-
| QAF_MGVIDEO_ADV_I|| 33 00 00 00 00 00 07 05 73 01 00 11 06 03 03 01 || for DevKits used for "MagicGate Video Development"
|}
The "_E" / or "_I" suffix indicates the Firmware the token is for. (External / Internal)
<br>





Revision as of 09:42, 28 June 2023

How to check if a DevKit's Firmware is Internal/External

Activate and try run a game cartridge. If there is an error it is most likely internal. To confirm it needs to be dumped and the modules checked.


How to check if a DevKit has been activated before & when

Lorem Ipsum


How to check if there is a QAF token installed

In any case dumping NVS is the savest way to tell for sure if and which kind of token is installed!

CEX (Retails)

Dumping NVS or using Apps to check and display the token name. (eg: PSVident or QAFUtility [PCSI90043])

DEX (TestKits)

When the Kit is activated for a very long time there most likely is an active QA Token installed.

TOOL (DevKits)

When the Kit is activated for a very long time there most likely is an active QA Token installed. For DevKits you can often tell from the Console Output alone as it will have additional debug output. It is however possible that there is an inactive token still installed while the firmware was reverted to external for example. In that case only dumping NVS can tell.


What kind of QAF Tokens are there and what do they do

Name Flags Notes
QAF_QATEAM_E 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 for "QualityAssurance Team" units (early)
QAF_QATEAM_MINI_E 01 00 00 00 00 00 0D 04 64 00 00 00 04 00 00 03 for "QualityAssurance Team" units
QAF_QATEAM_FULL_E 11 00 00 00 00 00 0F 04 64 00 00 00 04 00 00 03 for "QualityAssurance Team" units
QAF_SYS_DEV_I 33 00 00 00 00 00 07 05 73 01 00 01 06 03 03 01 for DevKits used for "System Development"
QAF_MGVIDEO_DEV_I 33 00 00 00 00 00 07 05 73 01 00 11 06 02 03 01 for DevKits used for "MagicGate Video Development"
QAF_MGVIDEO_ADV_I 33 00 00 00 00 00 07 05 73 01 00 11 06 03 03 01 for DevKits used for "MagicGate Video Development"

The "_E" / or "_I" suffix indicates the Firmware the token is for. (External / Internal)


How to re-activate a DevKit

Lorem Ipsum


How to re-activate a TestKit

Lorem Ipsum


How to dump a DevKit

Lorem Ipsum


How to dump a MemoryCard

Lorem Ipsum