xboxdevwiki - User contributions [en]

Kernel Debug

2026-04-01T03:06:38Z

CrunchBite: Fix typos and broken link

Only enabled in debug kernels, a Xbox with serial port can be kernel debugged with windbg.
Only executable that have debugging switched on can be debugged over serial as well(?) {{citation needed}}
{FIXME| Explain with more details ;) }

XEMU emulates this serial port, which uses a [[Super_I/O]].

== KD Commands ==

{| class="wikitable"
! Command
! Description
|-
| <code>CTRL+B</code>
| Exit the kernel debugger.
|-
| <code><ENTER></code>
| Repeat the last command you entered.
|-
| <code>?</code>
| Display a quick reference of basic debugger commands.
|-
| <code>.help</code>
| List meta‑commands available in the debugger.
|-
| <code>!help</code>
| List the extension commands provided by debugger plugins.
|-
| <code>x MODULE!SYMBOL</code>
| Show symbols within a module (supports wildcards). e.g. <code>Vidya!*</code> lists all symbols starting with “Vidya”.
|-
| <code>db ADDRESS</code>
| Dump raw bytes at the specified address, with any printable ASCII alongside.
|-
| <code>dd ADDRESS</code>
| Dump memory as 32‑bit words starting at the given address.
|-
| <code>df ADDRESS</code>
| Dump memory as floating‑point values from the given address.
|-
| <code>dds ADDRESS</code>
| Dump 32‑bit words and resolve any that match symbol names—handy for spotting return addresses on the stack.
|-
| <code>dt TYPE ADDRESS</code>
| Display the fields of a structure type at a memory address. Add <code>-b</code> to recurse into nested structures.
|-
| <code>rM 54</code>
| Show FP/MMX/XMM register contents (note the uppercase “M”).
|-
| <code>rM 1fd</code>
| Show all CPU registers.
|-
| <code>p</code>
| Step over the next instruction (runs calls/interrupts without entering them).
|-
| <code>t</code>
| Step into the next instruction (enters calls and interrupts).
|-
| <code>bp ADDRESS</code>
| Set a breakpoint at the specified instruction address.
|-
| <code>bp ADDRESS "commands"</code>
| Create a breakpoint that executes a sequence of commands when hit (semicolon‑separated).
|-
| <code>ba w1 ADDRESS</code>
| Set a data breakpoint on writes to one byte at ADDRESS. Use “r” for reads, or “2”/“4” for word/dword sizes.
|-
| <code>bl</code>
| List all active breakpoints.
|-
| <code>bc INDEX</code>
| Clear the breakpoint with the given index (as shown by <code>bl</code>).
|-
| <code>!memusage</code>
| Display a summary of free memory pages and usage by category.
|-
| <code>!heap 0 -a</code>
| Dump detailed heap entries for all heaps (can generate a lot of output).
|-
| <code>!handle 0 7</code>
| List all open handles in the system (files, threads, etc.).
|-
| <code>!poolused 3</code>
| Report how pool memory is allocated across different tags.
|-
| <code>!poolfind TAG</code>
| List every pool allocation marked with the four‑character TAG.
|-
| <code>.reboot</code>
| Restart the console.
|-
| <code>.sympath</code>
| Show the current symbol search paths.
|-
| <code>.sympath PATH</code>
| Change the symbol path to PATH; use <code>.reload</code> to apply.
|-
| <code>.echotimestamps</code>
| Toggle timestamps on debug messages and break notifications.
|}
{| class="wikitable"
! Command
! Description
|-
| <code>r</code>
| Shows the current register values.
|-
| <code>kp</code>
| Displays the call stack with function parameters and line numbers. If <code>kp</code> isn’t supported in your debugger version, use <code>kb</code> instead.
|-
| <code>dd esp L80</code>
| Dumps raw stack memory as DWORDs starting at <code>esp</code> (the stack pointer). <code>L80</code> specifies length 0x80 (128 DWORDs), letting you inspect local variables on the stack.
|-
| <code>ln eip</code> <code>u xxxxxxxx xxxxxxxx</code>
| Lists symbols around the current instruction pointer (<code>eip</code>) so you can see where the crash happened, for example:
:<code>(00011050) YourGame!main+0x9</code> 
:<code>(0001109d) YourGame!DebugBreak.Next</code>
Then use those addresses with <code>u</code> to disassemble that code range (e.g. <code>u 00011050 0001109d</code>).
|-
| <code>!process 0 7</code>
| Shows details about the current process and prints a call stack for each thread.
|-
| <code>dd nt!KeTickCount L1</code>
| Displays the kernel tick count (milliseconds since boot, excluding debugger pauses). Divide the result by 1,000 for seconds or by 3,600,000 for hours.
|}

Xbe

2026-03-25T04:11:42Z

CrunchBite: Add missing link(s) for XBE logo format

{{DISPLAYTITLE:XBE}}
XBE files (XBox Executable) are the main files that are executed in the Xbox System. In official games, these files are created by game developers, and then signed by Microsoft.

The file structure is adapted from Windows PE files. It is very similar, however it has important changes for the Xbox. The file is composed of an image header, a certificate, a collection of section headers, a collection of library versions, thread local storage data, a Microsoft bitmap, and the sections that contain the code and resources.

= Image Header =

The image header contains the information that describes where the other parts of the executable are located within the file, and how the executable should be treated and loaded. It has the following layout (all fields are little-endian):

{| class="wikitable
|-
! Offset
! Size
! Name
! Description
|-
! 0x0000
! 0x0004
| Magic Number
| This field must always equal 0x48454258 ("XBEH")
|-
! 0x0004
! 0x0100
| Digital Signature
| 256 Bytes. This is where a game is signed. Only on officially signed games is this field worthwhile.
|-
! 0x0104
! 0x0004
| Base Address
| Address at which to load this .XBE. Typically this will be 0x00010000.
|-
! 0x0108
! 0x0004
| Size of Headers
| Number of bytes that should be reserved for headers.
|-
! 0x010C
! 0x0004
| Size of Image
| Number of bytes that should be reserved for this image.
|-
! 0x0110
! 0x0004
| Size of Image Header
| Number of bytes that should be reserved for the image header. The header size varies by XDK version, but is at least 0x178.
|-
! 0x0114
! 0x0004
| TimeDate
| Time and Date when this image was created. UNIX timestamp format.
|-
! 0x0118
! 0x0004
| Certificate Address
| Address to a [[#Certificate|Certificate]] structure, after the .XBE is loaded into memory.
|-
! 0x011C
! 0x0004
| Number of Sections
| Number of sections contained in this .XBE.
|-
! 0x0120
! 0x0004
| Section Headers Address
| Address to an array of SectionHeader structures, after the .XBE is loaded into memory.
|-
! 0x0124
! 0x0004
| Initialization Flags
| Various flags for this .XBE file. Known flags are:

MountUtilityDrive = 0x00000001
FormatUtilityDrive = 0x00000002
Limit64Megabytes = 0x00000004
DontSetupHarddisk = 0x00000008
|-
! 0x0128
! 0x0004
| Entry Point
| Address to the Image entry point, after the .XBE is loaded into memory. This is where execution starts.

This value is encoded with an XOR key. Considering this is far too weak to be considered security, I assume this XOR is a clever method for discerning between Debug/Retail .XBE files without adding another field to the .XBE header. The XOR key is dependant on the build:

Beta = 0xE682F45B, Debug = 0x94859D4B, Retail = 0xA8FC57AB

To encode an entry point, you simply XOR the real entry point with either Debug or Retail key, depending on if you want the XBox to see this as a Debug or Retail executable.

To decode an entry point, you XOR with the debug key, then check if it is a valid entry point. If it is not, then you try again with the retail key.

Note: The Kernel Image Thunk Address member of this header must also be encoded as described later in this document.
|-
! 0x012C
! 0x0004
| TLS Address
| Address to a [[#TLS Table|TLS]] (Thread Local Storage) structure.
|-
! 0x0130
! 0x0004
| Stack Size
| Default stack size. As the Xbox does not allow for stacks to grow, this needs to be copied from the SizeOfStackReserve PE field, not SizeOfStackCommit!
|-
! 0x0134
! 0x0004
| PE Heap Reserve
| Copied from the PE file this .XBE was created from.
|-
! 0x0138
! 0x0004
| PE Heap Commit
| Copied from the PE file this .XBE was created from.
|-
! 0x013C
! 0x0004
| PE Base Address
| Copied from the PE file this .XBE was created from.
|-
! 0x0140
! 0x0004
| PE Size of Image
| Copied from the PE file this .XBE was created from.
|-
! 0x0144
! 0x0004
| PE Checksum
| Copied from the PE file this .XBE was created from.
|-
! 0x0148
! 0x0004
| PE TimeDate
| Copied from the PE file this .XBE was created from (UNIX timestamp format).
|-
! 0x014C
! 0x0004
| Debug PathName Address
| Address to the debug pathname (i.e. "D:\Nightlybuilds\011026.0\code\build\xbox\Release\simpsons.exe").
|-
! 0x0150
! 0x0004
| Debug FileName Address
| Address to the debug filename (i.e. "simpsons.exe")
|-
! 0x0154
! 0x0004
| Address to the UTF-16 debug filename (i.e. L"simpsons.exe")
| UTF-16 Debug FileName Address
|-
! 0x0158
! 0x0004
| Kernel Image Thunk Address
| Address to the Kernel Image Thunk Table, after the .XBE is loaded into memory. This is how .XBE files import kernel functions and data.

This value is encoded with an XOR key. Considering this is far too weak to be considered security, I assume this XOR is a clever method for discerning between Debug/Retail .XBE files without adding another field to the .XBE header. The XOR key is dependant on the build:

Beta = 0x46437DCD, Debug = 0xEFB1F152, Retail = 0x5B6D40B6

To encode a kernel thunk address, you simply XOR the real address with either Debug or Retail key, depending on if you want the XBox to see this as a Debug or Retail executable.

To decode a kernel thunk address, you XOR with the debug key, then check if it is a valid address. If it is not, then you try again with the retail key.

The Kernel Thunk Table itself is simply an array of pointers to Kernel imports. There are 366 possible imports, and the table is terminated with a zero dword (0x00000000). Typically the values in this table can be generated with the following formula:

KernelThunkTable[v] = ImportThunk + 0x80000000;

so, for example, the import PsCreateSystemThreadEx, which has a thunk value of 255 (0xFF) would be...

KernelThunkTable[v] = 0xFF + 0x80000000; // (0x800000FF)

When the .XBE is loaded by the OS (or the CXBX Emulator), all kernel imports are replaced by a valid function or data type address. In the case of CXBX, the import table entry at which (KernelThunkTable[v] & 0x1FF == 0xFF) will be replaced by &cxbx_PsCreateSystemThreadEx (which is a wrapper function).

Note: The Entry Point member of this header must also be encoded as described earlier in this document.
|-
! 0x015C
! 0x0004
| Non-Kernel Import Directory Address
| Address to the Non-Kernel Import Directory. It is typically safe to set this to zero.
|-
! 0x0160
! 0x0004
| Number of Library Versions
| Number of Library Versions pointed to by Library Versions Address.
|-
! 0x0164
! 0x0004
| Library Versions Address
| Address to an array of LibraryVersion structures, after the .XBE is loaded into memory.
|-
! 0x0168
! 0x0004
| Kernel Library Version Address
| Address to a LibraryVersion structure, after the .XBE is loaded into memory.
|-
! 0x016C
! 0x0004
| XAPI Library Version Address
| Address to a LibraryVersion structure, after the .XBE is loaded into memory.
|-
! 0x0170
! 0x0004
| Logo Bitmap Address
| Address to the Logo Bitmap (Typically a "Microsoft" logo). The format of this image is described [https://xbdev.net/fileformats/xbe/NonOfficialXBEFileFormat.pdf here.] This field can be set to zero, meaning there is no bitmap present.
|-
! 0x0174
! 0x0004
| Logo Bitmap Size
| Size (in bytes) of the Logo Bitmap data. The format of this image is described [https://xbdev.net/fileformats/xbe/NonOfficialXBEFileFormat.pdf here.]
|-
! 0x0178
! 0x0008
| Unknown1
| The meaning of this field hasn't been figured out yet. It only exists on XBEs built with an XDK version >= 5028.
|-
! 0x0180
! 0x0004
| Unknown2
| The meaning of this field hasn't been figured out yet. It only exists on XBEs built with an XDK version >= 5455.
|}

== LibraryVersion Table ==
{| class="wikitable
|-
! Offset
! Size
! Name
! Description
|-
! 0x0000
! 0x0008
| Library Name
| 8-byte ASCII-name of this library. (i.e. "XAPILIB")
|-
! 0x0008
! 0x0002
| Major Version
| Major version for this library (2-byte WORD).
|-
! 0x000A
! 0x0002
| Minor Version
| Minor version for this library (2-byte WORD).
|-
! 0x000C
! 0x0002
| Build Version
| Build version for this library (2-byte WORD).
|-
! 0x000E
! 0x0002
| Library Flags
| Various flags for this library. The fields are:

QFEVersion = 0x1FFF (13-Bit Mask)
Approved = 0x6000 (02-Bit Mask)
Debug Build = 0x8000 (01-Bit Mask)
|}

== TLS Table ==

The TLS Table contains all the information needed by the XBE to properly set up thread-local storage. It is structurally identical to the TLS Directory found in PE32 files<ref>https://docs.microsoft.com/en-us/windows/win32/debug/pe-format#the-tls-section</ref>, and can be directly copied from there. If the XBE does not use any thread-local storage, this table may be omitted, and the respective field in the image header set to zero.

{| class="wikitable
|-
! Offset
! Size
! Name
! Description
|-
! 0x0000
! 0x0004
| Raw Data Start
| Absolute (i.e. not an RVA) address of start of the TLS variable data in the program image.
|-
! 0x0004
! 0x0004
| Raw Data End
| Absolute (i.e. not an RVA) address of end of the TLS variable data in the program image.
|-
! 0x0008
! 0x0004
| Address of Index
| Absolute (i.e. not an RVA) address of the TLS Index variable.
|-
! 0x000C
! 0x0004
| Address of Callbacks
| Absolute (i.e. not an RVA) address of the null-terminated TLS callback functions table.
|-
! 0x0010
! 0x0004
| Size of Zero Fill
| The number of bytes following the raw data that should be set to zero in memory.
|-
! 0x0014
! 0x0004
| Characteristics
| Describes alignment.
|}

= Certificate =

Each Xbox executable has a certificate that contains information about the title.

* Time and date when the certificate was created
* Title ID
* Title name
* Alternative title IDs
* Allowed types of media that the executable can be run from (HD, DVD, CD, etc.)
* Game region
* Game ratings
* Disk number
* Version
* LAN key raw data used for [[System Link]]
* Signature key raw data (used to sign [[Xbox Savegame System|savegames]])
* Alternate signature keys
* Original size of the certificate
* Online service name (not present in early executables)
* Run time security flags (not present in early executables)

=== Title ID ===

A title ID is usually 2 ASCII letters for the publisher, followed by a u16 integer game number (Above 2000 for non-original Xbox games)

{| class=wikitable
! Publisher ID !! Name
|-
| AC || Acclaim Entertainment
|-
| AH || ARUSH Entertainment
|-
| AP || Aquaplus
|-
| AQ || Aqua System
|-
| AS || ASK
|-
| AT || Atlus
|-
| AV || Activision
|-
| AY || Aspyr Media
|-
| BA || Bandai
|-
| BL || Black Box
|-
| BM || BAM! Entertainment
|-
| BR || Broccoli Co.
|-
| BS || Bethesda Softworks
|-
| BU || Bunkasha Co.
|-
| BV || Buena Vista Games
|-
| BW || BBC Multimedia
|-
| BZ || Blizzard
|-
| CC || Capcom
|-
| CK || Kemco Corporation {{citation needed|reason=Did they realy swapped the ASCII letters? is KC a curced acroniem in Japan? Just want to be sure its Kemco|date=May 2017}}
|-
| CM || Codemasters
|-
| CT || CTO S.p.A.
|-
| CV || Crave Entertainment
|-
| DC || DreamCatcher Interactive
|-
| DX || Davilex
|-
| EA || Electronic Arts (EA)
|-
| EC || Encore inc
|-
| EL || Enlight Software
|-
| EM || Empire Interactive
|-
| ES || Eidos Interactive
|-
| FI || Fox Interactive
|-
| FS || From Software
|-
| GE || Genki Co.
|-
| GV || Groove Games
|-
| HE || Tru Blu (Entertainment division of Home Entertainment Suppliers)
|-
| HP || Hip games
|-
| HU || Hudson Soft
|-
| HW || Highwaystar
|-
| IA || Mad Catz Interactive
|-
| IF || Idea Factory
|-
| IG || Infogrames
|-
| IL || [[Interlex Corporation]]
|-
| IM || Imagine Media
|-
| IO || Ignition Entertainment
|-
| IP || Interplay Entertainment
|-
| IX || InXile Entertainment {{citation needed}}
|-
| JA || Jaleco
|-
| JW || JoWooD
|-
| KB || Kemco {{citation needed|reason=CK is also Kemco, is this a diferent subsidairy or country based? Just want to be sure its Kemco|date=May 2017}}
|-
| KI || Kids Station Inc. {{citation needed|reason=Games info page was in japanese, I dont read japanese. but this seemed very logicaly the publisher, can a japanese reader confirm?|date=May 2017}}
|-
| KK || KiKi
|-
| KN || Konami
|-
| KO || KOEI
|-
| KT || Konami Tokyo
|-
| KU || Kobi and/or GAE (formerly Global A Entertainment){{citation needed|reason=What name did the publisher use at the time of release?|date=May 2017}}
|-
| LA || LucasArts
|-
| LS || Black Bean Games (publishing arm of Leader S.p.A.)
|-
| MD || Metro3D
|-
| ME || Medix
|-
| MI || Microïds
|-
| MJ || Majesco Entertainment
|-
| MM || Myelin Media
|-
| MP || MediaQuest {{citation needed|reason=Where is the P? I dont trust my source yet... but seems close|date=May 2017}}
|-
| MS || Microsoft Game Studios
|-
| MW || Midway Games
|-
| MX || Empire Interactive {{citation needed|reason=What happend to the publisher, who published this game?|date=May 2017}}
|-
| NK || NewKidCo
|-
| NL || NovaLogic
|-
| NM || Namco
|-
| OX || Oxygen Interactive
|-
| PC || Playlogic Entertainment
|-
| PL || Phantagram Co., Ltd.
|-
| RA || Rage
|-
| SA || Sammy
|-
| SC || SCi Games
|-
| SE || SEGA
|-
| SN || SNK
|-
| SS || Simon & Schuster
|-
| SU || Success Corporation
|-
| SW || Swing! Deutschland
|-
| TA || Takara
|-
| TC || Tecmo
|-
| TD || The 3DO Company (or just 3DO)
|-
| TK || Takuyo
|-
| TM || TDK Mediactive
|-
| TQ || THQ
|-
| TS || Titus Interactive
|-
| TT || Take-Two Interactive Software
|-
| US || Ubisoft
|-
| VC || Victor Interactive Software
|-
| VN || Vivendi Universal (just took Interplays publishing rights) {{citation needed}}
|-
| VU || Vivendi Universal Games
|-
| VV || Vivendi Universal Games {{citation needed}}
|-
| WE || Wanadoo Edition
|-
| WR || Warner Bros. Interactive Entertainment {{citation needed}}
|-
| XD || ''Xbox demo disk? (Japan?)''
|-
| XI || XPEC Entertainment and Idea Factory
|-
| XK || ''Xbox kiosk disk?'' {{citation needed}}
|-
| XL || ''Xbox special bundled or live demo disk?'' {{citation needed}}
|-
| XM || Evolved Games {{citation needed|reason=Probably not, game "Malice"|date=May 2017}}
|-
| XP || XPEC Entertainment
|-
| XR || Panorama
|-
| XX || Microsoft Windows Media Center Extender for Xbox
|-
| YB || YBM Sisa (South-Korea)
|-
| ZD || Zushi Games (formerly Zoo Digital Publishing)
|}

The title ID seems to double the information from the [[Xbox Game Disc]] mastering code etched into the ring or readable from the DMI.
The game number is expressed in 3 decimal digits here which suggests that it will always be below 1000.

'''Examples''':

[[FIFA Soccer 2003]]:
* DMI and mastering code: EA02302E (Meaning: publisher EA, game number 023, version 02, region Europe)
* Title ID: 45410017 [EA-023]

[[Halo: Combat Evolved]]:
* DMI and mastering code: MS00402A (Meaning: publisher Microsoft, game number 004, version 02, region America)
* Title ID: 4D530004 [MS-004]

[[Halo: Combat Evolved]]:
* DMI and mastering code: MS00404E (Meaning: publisher Microsoft, game number 004, version 04, region Europe)
* Title ID: 4D530004 [MS-004]

== Allowed media types ==
Allowed media types off which the executable is allowed to be run from. The following values are known:
{| class=wikitable
! Media type !! Value
|-
|HARD_DISK || 0x00000001
|-
|DVD_X2 || 0x00000002
|-
|DVD_CD || 0x00000004
|-
|CD || 0x00000008
|-
|DVD_5_RO || 0x00000010
|-
|DVD_9_RO || 0x00000020
|-
|DVD_5_RW || 0x00000040
|-
|DVD_9_RW || 0x00000080
|-
|DONGLE || 0x00000100
|-
|MEDIA_BOARD || 0x00000200
|-
|NONSECURE_HARD_DISK || 0x40000000
|-
|NONSECURE_MODE || 0x80000000
|-
|MEDIA_MASK || 0x00FFFFFF
|}

= Sections =
The sections are described by the section headers. The section headers start right after the certificate and contain describe where in the file the actual sections reside. Each header contains a 20 byte SHA-1 hash of the section that is checked by the Xbox to ensure the integrity of the sections.

The SHA-1 hash is computed by prepending the length of the section (excluding any padding) as an unsigned 32-bit integer followed by the contents of the section itself.

At least two sections are always present in an Xbox executable: .text and .rdata. There might be more sections that contain either executable code or resources such as images, text, etc.

== .text ==

The .text section contains all x86 subroutines to be executed by the [[CPU|processor]].

== .rdata ==

The .rdata section contains the [[Kernel|kernel thunk table]]. The ordinals in the table are to be resolved to the kernel's actual calling routine, when loaded.

= Xbox Alpha executable format =

Binaries from early Xbox development (Alpha units), are using a different binary format. There are no known public tools that can read them.
Known differences include that the first bytes of the file are 'XE' instead the 'XBEH' from the final XBE format. The format is rumored to be more like the Windows PE format.{{citation needed}}

= Resources and links =
* [http://www.caustik.com/cxbx/download/xbe.htm .XBE File Format 1.1]

[[Category:Fileformats]]

Xbox Debug Monitor

2025-10-29T01:48:20Z

CrunchBite: Correct XBDM.dll path

The '''Xbox Debug Monitor''' ('''XBDM''') is a feature of Xbox Development Kits that provides remote debugging, file management, console discovery, and other services on TCP/UDP port 731. It is loaded by debug kernels at startup from <code>E:\xbdm.dll</code> and its configuration is read from <code>E:\xbdm.ini</code>. XBDM is distinct from KD and uses a different wire protocol.

==Name Answering Protocol==

An Xbox Development Kit (XDK) can be assigned a ''debug name'' that identifies it on the local network. XBDM provides the ability to resolve a debug name to an IP address ([[#Forward Lookup|forward lookup]]), resolve an IP address to a debug name ([[#Reverse Lookup|reverse lookup]]), and [[#Console Discovery|discover]] all XDKs on the local network using a very simple UDP-based protocol.

{|class="wikitable" style="margin: 0 auto; text-align: center;"
|+Name Answering Protocol Packet
|-
! style="border-bottom:none; border-right:none;"| ''Offsets''
! style="border-left:none;"| Octet
! colspan="8" | 0
! colspan="8" | 1
|-
! style="border-top: none" | Octet
! Bit!!0!!1!!2!!3!!4!!5!!6!!7!!8!!9!!10!!11!!12!!13!!14!!15
|-
! 0
! 0
| colspan="8" | Type || colspan="8" | Name Length
|-
! 2
! 16+
| colspan="16" | Name
|}

A NAP packet contains 3 fields, the last of which is variable-length. The minimum length of a NAP packet is 2 bytes and the maximum is 257. Invalid packets are silently dropped by XBDM.

; Type
: This unsigned 8-bit field may contain the values 1 (lookup), 2 (reply), or 3 (wildcard).
; Name Length
: This unsigned 8-bit field specifies the length of the Name field and should be a value from 0 to 255. For Type 3 packets, this field should always be 0. For Type 1 and Type 2 packets, this field should never be 0.
; Name
: This variable-length field contains the ASCII-encoded debug name for Type 1 and Type 2 packets. The number of bytes in this field is given by the Length field. It should not contain any <code>NUL</code> characters.

===Forward Lookup===

To resolve a debug name to an IP address, send a Type 1 NAP packet containing the debug name to be resolved to UDP address 255.255.255.255:731. The XDK with that name will respond with a Type 2 NAP packet and its IP address can be retrieved from the UDP header. There is no way to prevent multiple XDKs being assigned the same debug name, so it's possible that the client may receive replies from multiple IP addresses.

===Reverse Lookup===

To resolve an IP address to a debug name, send a Type 3 NAP packet with no name (length 0) to the IP address on UDP port 731. Assuming the target is actually an XDK, it will respond with a Type 2 NAP packet containing its name. This is very similar to the Console Discovery process (below), except that by sending the wildcard packet to a single IP address, only that XDK will respond.

===Console Discovery===

To discover all XDKs on the local network, send a Type 3 NAP packet with no name (length 0) to the UDP address 255.255.255.255:731. Each XDK will respond with a Type 2 NAP packet containing its name. As with a forward lookup, the client may receive multiple replies with the same name, but different IP addresses.

==Remote Debugging and Control Protocol==

The Remote Debugging and Control Protocol (RDCP) is a text-based protocol transmitted over a TCP connection on port 731. RDCP resembles protocols like FTP and SMTP, making it possible to communicate with XBDM using just a Telnet client in many cases.

When a connection is established, XBDM sends <code>201- connected</code> (or <code>200- connected</code> in version 3944) followed by <CR><LF> (that is, a carriage return character followed by a line feed character). The RDCP client is then free to send a [[#Commands|command]] followed by <CR><LF> or <CR><NUL>.

After executing a command, XBDM replies with a response line consisting of a three-digit status code and message of the form <code>999- message text<CR><LF></code>. Note that unlike similar protocols, the <code>-</code> (dash) is always present in responses and messages cannot span multiple lines.

===Status codes===

In responses, 2xx status codes indicate success and 4xx codes indicate failure. Most codes have a default message, but some commands leave the message field empty while others use the message field to hold whatever data was requested by the client or additional information about an error.

====2xx Success====

; 200- OK
: Standard response for successful execution of a command.
; 201- connected
: Initial response sent after a connection is established. The client does not need to send anything to solicit this response.
; 202- multiline response follows
: The response line is followed by one or more additional lines of data terminated by a line containing only a <code>.</code> (period). The client must read all available lines before sending another command.
; 203- binary response follows
: The response line is followed by raw binary data, the length of which is indicated in some command-specific way. The client must read all available data before sending another command.
; 204- send binary data
: The command is expecting additional binary data from the client. After the client sends the required number of bytes, XBDM will send another response line with the final result of the command.
; 205- connection dedicated
: The connection has been moved to a dedicated handler thread (see [[#Connection dedication]]).

====4xx Failure====

; 400- unexpected error
: An internal error occurred that could not be translated to a standard error code. The message is typically more descriptive, such as "out of memory" or "bad parameter".
; 401- max number of connections exceeded
: The connection could not be established because XBDM is already serving the maximum number of clients (4).
; 402- file not found
: An operation was attempted on a file that does not exist.
; 403- no such module
: An operation was attempted on a module that does not exist.
; 404- memory not mapped
: An operation was attempted on a region of memory that is not mapped in the page table.
; 405- no such thread
: An operation was attempted on a thread that does not exist.
; 406-
: An attempt to set the system time with the <code>[[#cmd_setsystime|setsystime]]</code> command failed. This status code is undocumented.
; 407- unknown command
: The command is not recognized.
; 408- not stopped
: The target thread is not stopped.
; 409- file must be copied
: A move operation was attempted on a file that can only be copied.
; 410- file already exists
: A file could not be created or moved because one already exists with the same name.
; 411- directory not empty
: A directory could not be deleted because it still contains files and/or directories.
; 412- filename is invalid
: The specified file contains invalid characters or is too long.
; 413- file cannot be created
: The file cannot be created for some unspecified reason.
; 414- access denied
: The file cannot be accessed at the connection's current privilege level (see [[#Security]]).
; 415- no room on device
: The target device has run out of storage space.
; 416- not debuggable
: The title is not debuggable.
; 417- type invalid
: The performance counter type is invalid.
; 418- data not available
: The performance counter data is not available.
; 420- box not locked
: The command can only be executed when security is enabled (see [[#Security]]).
; 421- key exchange required
: The client must perform a key exchange with the <code>[[#cmd_keyxchg|keyxchg]]</code> command (see [[#Security]]).
; 422- dedicated connection required
: The command can only be executed on a dedicated connection (see [[#Connection dedication]]).

===Connection dedication===

'''Connection dedication''' is the process of moving a client connection from the ''global server thread'' to a ''threaded command handler thread'' with the <code>dedicate</code> command.

By default, commands sent to XBDM are processed on the global server thread. Built-in commands and custom command handlers registered with <code>DmRegisterCommandProcessor</code> are run on this thread and may only execute kernel APIs. Commands that need to call CRT or XAPI functions must run in a threaded command handler, registered with <code>DmRegisterCommandProcessorEx</code> or <code>DmRegisterThreadedCommandProcessor</code>.

A client that has not dedicated its connection will receive a <code>422- dedicated connection required</code> response if it tries to execute a threaded command on the global server thread. After dedicating itself to a threaded command handler, the client can no longer send built-in or non-threaded commands until it re-dedicates itself to the global server thread.

===Security===

TODO

===Commands===

''See also: [[XBDM commands by version]]''

A command consists of a name and zero or more parameters separated by whitespace characters. The format of the parameters is defined by the command, but most commands use the form <code>key=value</code>. Parameter values that contain whitespace characters must be surrounded by double quotes (e.g. <code>"some value"</code> or <code>key="some value"</code>).

In the command descriptions below, the following data types are used:

{| class="wikitable" style="margin: 0 auto"
! Type !! Description
|-
| DWORD || A 32-bit integer in hexadecimal format (e.g. <code>0x1234ABCD</code>).
|-
| QWORD || A 64-bit integer in hexadecimal format, but prefixed with 0q instead of 0x (e.g. <code>0q0123456789ABCDEF</code>).
|-
| STRING || An ASCII-encoded string, optionally surrounded by double quotes.
|}

====adminpw (Set administrator password)====

{{XBDM command|version=4039+|text=adminpw none|privs=manage}}

Clear the administrator password.

{{XBDM command|version=4039+|text=adminpw passwd=QWORD|privs=manage}}

Set the administrator password to the value of the <code>passwd</code> parameter. Note that <code>passwd</code> is a 64-bit integer instead of a string. The details of the conversion from a string password to a 64-bit integer are currently unknown.

====altaddr====
====authuser (Authenticate user)====
====boxid====
====break====
====bye (Close connection)====
====capcontrol/capctrl====
====continue====
====crashdump====
====d3dopcode====
====dbgname (Get/set debug name)====
====dbgoptions====
====debugger====
====debugmode====
====dedicate (Dedicate connection)====
====deftitle====
====delete (Delete file or directory)====

{{XBDM command|text=delete name=STRING dir}}

Deletes a file or directory.

To delete a directory, the optional <code>dir</code> attribute must be present.

====dirlist (List files in directory)====
====dmversion (Get debug monitor version)====
====drivefreespace (Get free space on drive)====
====drivelist (List drive letters)====

{{XBDM command|text=drivelist}}

Returns a string which contains the drive-letter for each accessible drive.

====dvdblk (Read block from DVD)====
====dvdperf====
====fileeof====
====flash (Flash BIOS image)====
====fmtfat (Format FAT partition)====
====funccall====
====getcontext (Get thread context)====
====getd3dstate (Get Direct3D state)====
====getextcontext (Get extended thread context)====

====getfile (Download file)====

{{XBDM command|text=getfile name=STRING}}

Retrieve the entire contents of the named file.
The received data is prefixed with a 32 bit little endian value, which contains the number of bytes which have been read.

{{XBDM command|text=getfile name=STRING offset=DWORD size=DWORD}}

Retrieve <code>size</code> bytes starting at <code>offset</code> from the named file.
The received data is prefixed with a 32 bit little endian value, which contains the number of bytes which have been read.

====getfileattributes (Get file attributes)====
====getgamma (Get gamma table)====
====getmem (Read memory)====
====getmem2 (Read memory)====
====getpalette====
====getpid====
====getsum (Generate memory checksums)====

{{XBDM command|version=5120+|text=getsum addr=DWORD length=DWORD blocksize=DWORD}}

Generates one or more checksums from memory.

The function will return <code>length</code> divided by <code>blocksize</code> 32-bit little endian checksums for the memory starting at virtual address <code>addr</code>.

The <code>addr</code>, <code>length</code> and <code>blocksize</code> must be multiples of 8.
Picking bad values can lead to crashes.

Each checksum is equal to <code>ReverseBitOrder(CRC32(address + blockoffset, blocksize) XOR 0xFFFFFFFF)</code> for the respective block.

====getsurf====
====getuserpriv (Get user's privilege level)====
====getutildrvinfo (Get utility drive information)====
====go====
====gpucount (Toggle GPU counters)====
====halt====
====irtsweep====
====isbreak====
====isdebugger====
====isstopped====
====kd (Enable/disable kernel debugger)====
====keyxchg (Perform key exchange)====
====lockmode====
====lop====
====magicboot (Boot into new title)====

{{XBDM command|text=magicboot title=STRING debug}}

Boots into another title, specified by the path to XBE in <code>title</code>.

If the optional <code>debug</code> is provided, XBDM will remain loaded while the title is running.

====memtrack====
====mkdir (Create directory)====
====mmglobal====
====modlong====
====modsections====
====modules====
====nostopon====
====notify====
====notifyat====
====pbsnap====
====pclist (List performance counters)====
====pdbinfo====
====pssnap====
====querypc (Query performance counter)====
====reboot====
====rename (Rename file)====
====resume====
====screenshot (Take screenshot)====
====sendfile (Upload file)====
====servname====
====setconfig====
====setcontext (Set thread context)====
====setfileattributes (Set file attributes)====
====setsystime (Set system time)====
====setuserpriv (Set user's privilege level)====
====signcontent====
====stop====
====stopon====
====suspend====
====sysfileupd (Update system file)====
====systime (Get system time)====
====threadinfo (Get thread information)====
====threads (List threads)====
====title====
====user====
====userlist (List users)====
====vssnap====
====walkmem====
====writefile====
====xbeinfo====
====xtlinfo====

==See Also==

* [[Xbox Neighborhood]] – An XDK tool that utilizes the XBDM protocols

==External Links==

* [https://github.com/Ernegien/ViridiX ViridiX] – An open-source collection of Xbox debugging libraries and tools written in C#.
* [https://github.com/docbrown/xbdm-rs xbdm-rs] - An open-source XBDM client written in Rust.

Microsoft XDK

2023-12-27T00:29:02Z

CrunchBite: Update link to codeasm's list

The official XDK (Xbox Development Kit) was only released to licensed developers. However, it got leaked a couple of times.

== List of known versions ==
{| class="wikitable"
! Version
! Comments
|-
! 3424
| April 2001 XDK and SDK (03.01.01 - New for April XDK release)
|-
! 3521
| May 2001 XDK
|-
! 3823(*)
| August 2001 XDK (Preview)
|-
! 3911(*)
| August 2001 XDK ((Final) (build on WIN2000 5. 2134/2195 ? 5.1.2258.400)
|-
! 3925(*)
| September 2001 XDK
|-
! 3936(*)
|
|-
! 3937(*)
|
|-
! 3941(*)
|
|-
! 3944(*)
| October 2001 XDK / RTM
|-
! 3948(*)
|
|-
! 3950(*)
|
|-
! 4020(*)
| Seen on an official Xbox recovery tool
|-
! 4034(*)
|
|-
! 4039(*)
| November 2001 XDK
|-
! 4134(*)
| December 2001 XDK
|-
! 4242(*)
| February 2002 XDK
|-
! 4361
| March 2002 XDK
|-
! 4400
| Source tree leak
|-
! 4432
| April 2002 XDK
|-
! 4531
| May 2002 XDK
|-
! 4627
| June 2002 XDK
|-
! 4721
| July 2002 XDK
|-
! 4831
| August 2002 XDK
|-
! 4928
| September 2002 XDK
|-
! 5028
| October 2002 XDK
|-
! 5120
| November 2002 XDK
|-
! 5233
| December 2002 XDK
|-
! 5344
| February 2003 XDK
|-
! 5455
| April 2003 XDK
|-
! 5558
| June 2003 XDK
|-
! 5659
| August 2003 XDK
|-
! 5788
| November 2003 XDK
|-
! 5849
| December 2003 XDK
|-
! 5849
| .16
|-
! 5933
| uncertain number - Dxbx code mentions 5911 (wich seemed incorrect)
|-
! 5960
| last official dashboard
|}

(*) : Earlier XDK's contained libraries with different versions numbers. Before or around XDK version 4361, all libraries in the XDK were given the same version number.

Note : An even more complete listing can be found here : https://www.codeasm.com/xbox/Kernel_Dash_versions.htm#classic (Old link: https://web.archive.org/web/20171224225821/http://codeasm.com/xbox/files/Xbox%20Kernel_Dash_XDK%20versions.txt)

Power Supply

2019-09-20T00:51:54Z

CrunchBite: Added xbox 1.3 power usage measurements

It's either a Foxlink{{citation needed}} or Delta Electronics power supply for most xboxes.
Some are rumored to be shipped with a Minebea brand and 1.6 xboxes are found with a "tuscany" made probably by Samsung.

On a 1.0 xbox supply, there seems to be 2{{citation needed|reason=2 per region, or 2 overall? and, what about foxlink?}} types for the US 120V and EU 240V market.

The standby voltage powers the [[SMC]] which handles turning on and off the system.
The Xbox supply needs a voltage (3V3?) on it's power-on line to leave the standby mode.
This results in the other voltages being supplied.

=== Delta Electronics ===
The marks are on the PCB with a check next to them:
* Delta Electronics DPSN-96-AP-1 should be the EU 240V one{{citation needed}}
* Delta Electronics DPSN-96-AP is the US 120V one

There is a link J11 under CR1 (right side of the coil under it) that might make the difference between 120V and 240V.
It also seems that the Bridge rectifier is bigger on the US models.
This could make sense as it has to handle double the current. So, before experimenting with this it might be worth to check if the installed type can handle 2.3 amps.

The rated output currents are also noted on the PCB

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.075A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

=== Foxlink Technology LTD ===

{{FIXME|reason=I don't own any US xboxes to compare US foxlinks with}}On the lower heatsink, there is a sticker with the following markings and versions:
* MODEL: FTPS-0001 REV:B {{citation needed}} (120V)
* MODEL: FTPS-0002 REV:B (from a 2002 PAL (240V))
* MODEL: FTPS-0002 REV:H (from a 2003 PAL (240V))
* MODEL: FTPS-0002 REV:G {{citation needed}} (240V)
* MODEL: FTPS-0007 REV:B {{citation needed}} (120V) (are these after the powercord recall?)
* MODEL: FTPS-0007 REV:D {{citation needed}} (120V) (are these after the powercord recall?)

The rated output currents are also noted on the sticker

96W Max output power

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.045A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

==== Powercord recall ====

Microsoft started an powercord recall, or more like a replacement program [https://web.archive.org/web/20050301093947/http://www.xbox.com:80/en-US/news/0502/powercordannouncement.htm xbox.com]for what appeared to be Foxlink powersupplies having a bad powerplug connector on the back of the console and where installed in 1.0 and 1.1 Xboxes.{{citation needed}}.
Microsoft tried to resolve this by offering free replacement powercords and advising to trow out the old ones. [https://web.archive.org/web/20120722175134/http://www.xbox-scene.com/xbox1data/sep/EEpAEAylAluZlwSlOJ.php More to the power cord replacement than meets the eye?]{{FIXME|reason=why is this link here and where could / should it be instead? I think it's misplaced here}}.

From the Microsoft powercord replacement FAQ:

: '''Does my console require a replacement cord?'''
: If it was manufactured before October 23, 2003, your console requires a replacement cord (except for consoles purchased in Continental Europe, where consoles manufactured prior to January 13, 2004 require a replacement cord). Consoles manufactured after October 23, 2003 (after January 13, 2004 for consoles purchased in Continental Europe) do not require replacement cords because design improvements to the cord and console already protect against the problems that are addressed by the replacement cords.[https://web.archive.org/web/20050223041403/http://replacements.webprogram.com:80/en-us/faqs.asp#Q-7]

The old page describing how to order has been archived here: [https://web.archive.org/web/20050223060900/http://replacements.webprogram.com:80/en-us/programoverview.asp]
One would either receive a thicker but very similar powercord or an actual [https://simple.wikipedia.org/wiki/GFCI GFI] (Ground Fault Circuit Interrupter). a online form would then be used to determine which type of cable you receive by means of serial number. {{FIXME|reason=I cant seem to find a source for these details yet, but I personally requested 2, 1 for my own Xbox (a 1.4, with a confirmed Delta. never replaced it.) and received a normal cable (EU). A friends xbox was older, 1.1/1.2?) and we got a european fusebox brick for his. looks like the UK one, but with the Benelux plug. It was all for free in Europe I remember the part number on my normal cable to be different (higher) for the newer one... ill check if I have it in the original box still}}

===== AFCI =====

A video of whats inside an european (UK) "AFCI" [https://www.youtube.com/watch?v=C0wQikAO-yA]

An european AFCI ordered from MS for free had the following on the bottom label.
{| class="wikitable"
| Part number
| X800925-100
|-
|
| 200-240V~,50/60HZ, 610mA
|-
| MFG Code
| DN0855
|}

The cable that is wired to the AFCI has the following markings:
{| class="wikitable"
! top
! bottom
|-
| JI-HAW
| JHT-031
|}
===== Old and New cords =====

The replacement cable has the following markings:{{citation needed}}
{| class="wikitable"
! top
! bottom
|-
| JHT-031
| {{citation needed}}
|}

The older cable that needed replacement was:
{| class="wikitable"
! top
! bottom
|-
| NITTO SS
| W41-27854
|-
| JHT-013
| N15905
|-
| JI-HAW
|
|-
| E147422
|
|}
Presumably this one doesn't come with tighter tolerances.

=== Samsung "TUSCANY"===
Found in 1.6 xboxes and seems to be made by Samsung (or atleast the main transformer is, which also has the detail label on it)
{{FIXME|reason=There are TUSCANY powersuplies in some 1.6 xboxes?}}
* PSCD101301A

=== Minebea ===
{{FIXME|reason=There are in the UK, Minebea powersuplies in some xboxes?}}

* MS001A096EMJ

{|
!Minebea Electronics UK LTD
!(circuit board)
|-
|DWG No.
|1 R26PA-SE300393 REV: E
|-
|PART No.
|1 1612100002
|-
|
|0234-3
|-
!Sticker:
|
|-
|NMB Technologies Corp
|Power Supply Division
|-
|Made in
|Thailand
|-
|Model:
|MS001A096EMJ
|-
|REV:
|08
|-
|AC INPUT:100-120V
|2A 47-63Hz
|}

== Connector pinout ==

=== Xbox 1.0 and 1.1 ===

The power supply connector for 1.0 and 1.1 is a single column of pins described by the following chart. Pin 1 is the connector pin closest to the back of the Xbox.

{| class="wikitable"
! Pin || Usage
|-
| Pin 1 || PowOK
|-
| Pin 2 || PowON
|-
| Pin 3 || GND
|-
| Pin 4 || GND
|-
| Pin 5 || GND
|-
| Pin 6 || GND
|-
| Pin 7 || +3.3V Standby
|-
| Pin 8 || +3.3V
|-
| Pin 9 || +5V
|-
| Pin 10 || +5V
|-
| Pin 11 || +5V
|-
| Pin 12 || +12V
|}

=== Xbox 1.2, 1.3, 1.4, and 1.5 ===
The power supply connector for the 1.2, 1.3, 1.4, and 1.5 xboxes is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK || Pin 1 || PowON
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || +3.3V
|-
| Pin 4 || +3.3V || Pin 4 || None
|-
| Pin 5 || None || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +3.3V Standby
|-
| Pin 7 || None || Pin 7 || GND
|-
| Pin 8 || +5V || Pin 8 || +5V
|-
| Pin 9 || +5V || Pin 9 || None
|-
| Pin 10 || +5V || Pin 10 || +12V
|}

=== Xbox 1.6 ===
The connector for the 1.6 Xbox is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox. This is the same connector as a 1.2, 1.3, 1.4, and 1.5 xboxes, with a different pinout.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK (3.3V Standby) || Pin 1 || PowON (3.3V)
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || None
|-
| Pin 4 || None || Pin 4 || None
|-
| Pin 5 || GND || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +5V (0.12V Standby)
|-
| Pin 7 || GND || Pin 7 || GND
|-
| Pin 8 || +5V Standby || Pin 8 || +5V Standby
|-
| Pin 9 || +5V Standby || Pin 9 || GND
|-
| Pin 10 || +5V Standby || Pin 10 || +12V (0.532V Standby)
|}

== Real world power usage ==

DC amperage as measured on with a Fluke 376 clamp meter around the PSU to Motherboard connections. HDD not included in measurements and the DVD drive and controller rumble were not used.
AC wattage measured at 120v 60Hz using a 'KILL A WATT' meter includes all system components but DVD drive and controller rumble were not used.

{| class="wikitable"
! XBOX V1.0 || Power off || Unleash X || Halo 2 Menu || DolphinClassic || Maximum Observed
|-
| GND || 0A || 5.9A || 5.8A || 6.0A || 6.2A
|-
| 3.3v Standby || 0.2A || 0.3A || 0.3A || 0.3A || 0.3A
|-
| 3.3v || 0A || 2.5A || 2.2A || 2.7A || 2.7A
|-
| 5v || 0A || 7.1A || 7.2A || 7.0A || 7.2A
|-
| 12v || 0A || 0.3A || 0.4A || 0.4A || 0.4A
|-
| ~120VAC || 2.1W || 67.4W || 65.3W || 68.5W || 68.5W
|-
|}

{| class="wikitable"
! XBOX V1.3 || Power off || Unleash X || Halo 2 Menu || DolphinClassic || Maximum Observed
|-
| GND || 0A || 8.5A || 8.1A || 8.6A || 8.6A
|-
| 3.3v Standby || 0.4A || 0.5A || 0.5A || 0.5A || 0.5A
|-
| 3.3v || 0A || 3.7A || 2.9A || 3.7A || 3.7A
|-
| 5v || 0A || 6.4A || 6.7A || 6.5A || 6.7A
|-
| 12v || 0A || 0.2A || 0.3A || 0.2A || 0.3A
|-
| ~120VAC || 1.2W || 64.6W || 62.2W || 64.3W || 64.6W
|-
|}

TODO: Measure other hardware revisions and more usage scenarios.

== Related links ==

* [http://brandonw.net/consoles/xbox/ Describes how to turn an ATX Power-Supply to Xbox PSU]
* [https://web.archive.org/web/20060421203325/https://msmvps.com/blogs/matthewsoft/archive/2005/02/17/36238.aspx Powercord recall blog with exacter cable numbers]

Power Supply

2019-09-01T17:36:49Z

CrunchBite: /* Real world power usage */

It's either a Foxlink{{citation needed}} or Delta Electronics power supply for most xboxes.
Some are rumored to be shipped with a Minebea brand and 1.6 xboxes are found with a "tuscany" made probably by Samsung.

On a 1.0 xbox supply, there seems to be 2{{citation needed|reason=2 per region, or 2 overall? and, what about foxlink?}} types for the US 120V and EU 240V market.

The standby voltage powers the [[SMC]] which handles turning on and off the system.
The Xbox supply needs a voltage (3V3?) on it's power-on line to leave the standby mode.
This results in the other voltages being supplied.

=== Delta Electronics ===
The marks are on the PCB with a check next to them:
* Delta Electronics DPSN-96-AP-1 should be the EU 240V one{{citation needed}}
* Delta Electronics DPSN-96-AP is the US 120V one

There is a link J11 under CR1 (right side of the coil under it) that might make the difference between 120V and 240V.
It also seems that the Bridge rectifier is bigger on the US models.
This could make sense as it has to handle double the current. So, before experimenting with this it might be worth to check if the installed type can handle 2.3 amps.

The rated output currents are also noted on the PCB

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.075A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

=== Foxlink Technology LTD ===

{{FIXME|reason=I don't own any US xboxes to compare US foxlinks with}}On the lower heatsink, there is a sticker with the following markings and versions:
* MODEL: FTPS-0001 REV:B {{citation needed}} (120V)
* MODEL: FTPS-0002 REV:B (from a 2002 PAL (240V))
* MODEL: FTPS-0002 REV:H (from a 2003 PAL (240V))
* MODEL: FTPS-0002 REV:G {{citation needed}} (240V)
* MODEL: FTPS-0007 REV:B {{citation needed}} (120V) (are these after the powercord recall?)
* MODEL: FTPS-0007 REV:D {{citation needed}} (120V) (are these after the powercord recall?)

The rated output currents are also noted on the sticker

96W Max output power

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.045A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

==== Powercord recall ====

Microsoft started an powercord recall, or more like a replacement program [https://web.archive.org/web/20050301093947/http://www.xbox.com:80/en-US/news/0502/powercordannouncement.htm xbox.com]for what appeared to be Foxlink powersupplies having a bad powerplug connector on the back of the console and where installed in 1.0 and 1.1 Xboxes.{{citation needed}}.
Microsoft tried to resolve this by offering free replacement powercords and advising to trow out the old ones. [https://web.archive.org/web/20120722175134/http://www.xbox-scene.com/xbox1data/sep/EEpAEAylAluZlwSlOJ.php More to the power cord replacement than meets the eye?]{{FIXME|reason=why is this link here and where could / should it be instead? I think it's misplaced here}}.

From the Microsoft powercord replacement FAQ:

: '''Does my console require a replacement cord?'''
: If it was manufactured before October 23, 2003, your console requires a replacement cord (except for consoles purchased in Continental Europe, where consoles manufactured prior to January 13, 2004 require a replacement cord). Consoles manufactured after October 23, 2003 (after January 13, 2004 for consoles purchased in Continental Europe) do not require replacement cords because design improvements to the cord and console already protect against the problems that are addressed by the replacement cords.[https://web.archive.org/web/20050223041403/http://replacements.webprogram.com:80/en-us/faqs.asp#Q-7]

The old page describing how to order has been archived here: [https://web.archive.org/web/20050223060900/http://replacements.webprogram.com:80/en-us/programoverview.asp]
One would either receive a thicker but very similar powercord or an actual [https://simple.wikipedia.org/wiki/GFCI GFI] (Ground Fault Circuit Interrupter). a online form would then be used to determine which type of cable you receive by means of serial number. {{FIXME|reason=I cant seem to find a source for these details yet, but I personally requested 2, 1 for my own Xbox (a 1.4, with a confirmed Delta. never replaced it.) and received a normal cable (EU). A friends xbox was older, 1.1/1.2?) and we got a european fusebox brick for his. looks like the UK one, but with the Benelux plug. It was all for free in Europe I remember the part number on my normal cable to be different (higher) for the newer one... ill check if I have it in the original box still}}

===== AFCI =====

A video of whats inside an european (UK) "AFCI" [https://www.youtube.com/watch?v=C0wQikAO-yA]

An european AFCI ordered from MS for free had the following on the bottom label.
{| class="wikitable"
| Part number
| X800925-100
|-
|
| 200-240V~,50/60HZ, 610mA
|-
| MFG Code
| DN0855
|}

The cable that is wired to the AFCI has the following markings:
{| class="wikitable"
! top
! bottom
|-
| JI-HAW
| JHT-031
|}
===== Old and New cords =====

The replacement cable has the following markings:{{citation needed}}
{| class="wikitable"
! top
! bottom
|-
| JHT-031
| {{citation needed}}
|}

The older cable that needed replacement was:
{| class="wikitable"
! top
! bottom
|-
| NITTO SS
| W41-27854
|-
| JHT-013
| N15905
|-
| JI-HAW
|
|-
| E147422
|
|}
Presumably this one doesn't come with tighter tolerances.

=== Samsung "TUSCANY"===
Found in 1.6 xboxes and seems to be made by Samsung (or atleast the main transformer is, which also has the detail label on it)
{{FIXME|reason=There are TUSCANY powersuplies in some 1.6 xboxes?}}
* PSCD101301A

=== Minebea ===
{{FIXME|reason=There are in the UK, Minebea powersuplies in some xboxes?}}

* MS001A096EMJ

{|
!Minebea Electronics UK LTD
!(circuit board)
|-
|DWG No.
|1 R26PA-SE300393 REV: E
|-
|PART No.
|1 1612100002
|-
|
|0234-3
|-
!Sticker:
|
|-
|NMB Technologies Corp
|Power Supply Division
|-
|Made in
|Thailand
|-
|Model:
|MS001A096EMJ
|-
|REV:
|08
|-
|AC INPUT:100-120V
|2A 47-63Hz
|}

== Connector pinout ==

=== Xbox 1.0 and 1.1 ===

The power supply connector for 1.0 and 1.1 is a single column of pins described by the following chart. Pin 1 is the connector pin closest to the back of the Xbox.

{| class="wikitable"
! Pin || Usage
|-
| Pin 1 || PowOK
|-
| Pin 2 || PowON
|-
| Pin 3 || GND
|-
| Pin 4 || GND
|-
| Pin 5 || GND
|-
| Pin 6 || GND
|-
| Pin 7 || +3.3V Standby
|-
| Pin 8 || +3.3V
|-
| Pin 9 || +5V
|-
| Pin 10 || +5V
|-
| Pin 11 || +5V
|-
| Pin 12 || +12V
|}

=== Xbox 1.2, 1.3, 1.4, and 1.5 ===
The power supply connector for the 1.2, 1.3, 1.4, and 1.5 xboxes is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK || Pin 1 || PowON
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || +3.3V
|-
| Pin 4 || +3.3V || Pin 4 || None
|-
| Pin 5 || None || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +3.3V Standby
|-
| Pin 7 || None || Pin 7 || GND
|-
| Pin 8 || +5V || Pin 8 || +5V
|-
| Pin 9 || +5V || Pin 9 || None
|-
| Pin 10 || +5V || Pin 10 || +12V
|}

=== Xbox 1.6 ===
The connector for the 1.6 Xbox is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox. This is the same connector as a 1.2, 1.3, 1.4, and 1.5 xboxes, with a different pinout.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK (3.3V Standby) || Pin 1 || PowON (3.3V)
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || None
|-
| Pin 4 || None || Pin 4 || None
|-
| Pin 5 || GND || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +5V (0.12V Standby)
|-
| Pin 7 || GND || Pin 7 || GND
|-
| Pin 8 || +5V Standby || Pin 8 || +5V Standby
|-
| Pin 9 || +5V Standby || Pin 9 || GND
|-
| Pin 10 || +5V Standby || Pin 10 || +12V (0.532V Standby)
|}

== Real world power usage ==

DC amperage as measured on a v1.0 Xbox with a Fluke 376 clamp meter around the PSU to Motherboard connections. HDD not included in measurements and the DVD drive and controller rumble were not used.

AC wattage measured at 120v 60Hz using a 'KILL A WATT' meter includes all system components but DVD drive and controller rumble were not used.
{| class="wikitable"
! || Power off || Unleash X || Halo 2 Menu || DolphinClassic || Maximum Observed
|-
| GND || 0A || 5.9A || 5.8A || 6.0A || 6.2A
|-
| 3.3v Standby || 0.2A || 0.3A || 0.3A || 0.3A || 0.3A
|-
| 3.3v || 0A || 2.5A || 2.2A || 2.7A || 2.7A
|-
| 5v || 0A || 7.1A || 7.2A || 7.0A || 7.2A
|-
| 12v || 0A || 0.3A || 0.4A || 0.4A || 0.4A
|-
| ~120VAC || 2.1W || 67.4W || 65.3W || 68.5W || 68.5W
|-
|}
TODO: Measure other hardware revisions and more usage scenarios.

== Related links ==

* [http://brandonw.net/consoles/xbox/ Describes how to turn an ATX Power-Supply to Xbox PSU]
* [https://web.archive.org/web/20060421203325/https://msmvps.com/blogs/matthewsoft/archive/2005/02/17/36238.aspx Powercord recall blog with exacter cable numbers]

Power Supply

2019-09-01T17:35:51Z

CrunchBite: /* Real world power usage */

It's either a Foxlink{{citation needed}} or Delta Electronics power supply for most xboxes.
Some are rumored to be shipped with a Minebea brand and 1.6 xboxes are found with a "tuscany" made probably by Samsung.

On a 1.0 xbox supply, there seems to be 2{{citation needed|reason=2 per region, or 2 overall? and, what about foxlink?}} types for the US 120V and EU 240V market.

The standby voltage powers the [[SMC]] which handles turning on and off the system.
The Xbox supply needs a voltage (3V3?) on it's power-on line to leave the standby mode.
This results in the other voltages being supplied.

=== Delta Electronics ===
The marks are on the PCB with a check next to them:
* Delta Electronics DPSN-96-AP-1 should be the EU 240V one{{citation needed}}
* Delta Electronics DPSN-96-AP is the US 120V one

There is a link J11 under CR1 (right side of the coil under it) that might make the difference between 120V and 240V.
It also seems that the Bridge rectifier is bigger on the US models.
This could make sense as it has to handle double the current. So, before experimenting with this it might be worth to check if the installed type can handle 2.3 amps.

The rated output currents are also noted on the PCB

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.075A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

=== Foxlink Technology LTD ===

{{FIXME|reason=I don't own any US xboxes to compare US foxlinks with}}On the lower heatsink, there is a sticker with the following markings and versions:
* MODEL: FTPS-0001 REV:B {{citation needed}} (120V)
* MODEL: FTPS-0002 REV:B (from a 2002 PAL (240V))
* MODEL: FTPS-0002 REV:H (from a 2003 PAL (240V))
* MODEL: FTPS-0002 REV:G {{citation needed}} (240V)
* MODEL: FTPS-0007 REV:B {{citation needed}} (120V) (are these after the powercord recall?)
* MODEL: FTPS-0007 REV:D {{citation needed}} (120V) (are these after the powercord recall?)

The rated output currents are also noted on the sticker

96W Max output power

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.045A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

==== Powercord recall ====

Microsoft started an powercord recall, or more like a replacement program [https://web.archive.org/web/20050301093947/http://www.xbox.com:80/en-US/news/0502/powercordannouncement.htm xbox.com]for what appeared to be Foxlink powersupplies having a bad powerplug connector on the back of the console and where installed in 1.0 and 1.1 Xboxes.{{citation needed}}.
Microsoft tried to resolve this by offering free replacement powercords and advising to trow out the old ones. [https://web.archive.org/web/20120722175134/http://www.xbox-scene.com/xbox1data/sep/EEpAEAylAluZlwSlOJ.php More to the power cord replacement than meets the eye?]{{FIXME|reason=why is this link here and where could / should it be instead? I think it's misplaced here}}.

From the Microsoft powercord replacement FAQ:

: '''Does my console require a replacement cord?'''
: If it was manufactured before October 23, 2003, your console requires a replacement cord (except for consoles purchased in Continental Europe, where consoles manufactured prior to January 13, 2004 require a replacement cord). Consoles manufactured after October 23, 2003 (after January 13, 2004 for consoles purchased in Continental Europe) do not require replacement cords because design improvements to the cord and console already protect against the problems that are addressed by the replacement cords.[https://web.archive.org/web/20050223041403/http://replacements.webprogram.com:80/en-us/faqs.asp#Q-7]

The old page describing how to order has been archived here: [https://web.archive.org/web/20050223060900/http://replacements.webprogram.com:80/en-us/programoverview.asp]
One would either receive a thicker but very similar powercord or an actual [https://simple.wikipedia.org/wiki/GFCI GFI] (Ground Fault Circuit Interrupter). a online form would then be used to determine which type of cable you receive by means of serial number. {{FIXME|reason=I cant seem to find a source for these details yet, but I personally requested 2, 1 for my own Xbox (a 1.4, with a confirmed Delta. never replaced it.) and received a normal cable (EU). A friends xbox was older, 1.1/1.2?) and we got a european fusebox brick for his. looks like the UK one, but with the Benelux plug. It was all for free in Europe I remember the part number on my normal cable to be different (higher) for the newer one... ill check if I have it in the original box still}}

===== AFCI =====

A video of whats inside an european (UK) "AFCI" [https://www.youtube.com/watch?v=C0wQikAO-yA]

An european AFCI ordered from MS for free had the following on the bottom label.
{| class="wikitable"
| Part number
| X800925-100
|-
|
| 200-240V~,50/60HZ, 610mA
|-
| MFG Code
| DN0855
|}

The cable that is wired to the AFCI has the following markings:
{| class="wikitable"
! top
! bottom
|-
| JI-HAW
| JHT-031
|}
===== Old and New cords =====

The replacement cable has the following markings:{{citation needed}}
{| class="wikitable"
! top
! bottom
|-
| JHT-031
| {{citation needed}}
|}

The older cable that needed replacement was:
{| class="wikitable"
! top
! bottom
|-
| NITTO SS
| W41-27854
|-
| JHT-013
| N15905
|-
| JI-HAW
|
|-
| E147422
|
|}
Presumably this one doesn't come with tighter tolerances.

=== Samsung "TUSCANY"===
Found in 1.6 xboxes and seems to be made by Samsung (or atleast the main transformer is, which also has the detail label on it)
{{FIXME|reason=There are TUSCANY powersuplies in some 1.6 xboxes?}}
* PSCD101301A

=== Minebea ===
{{FIXME|reason=There are in the UK, Minebea powersuplies in some xboxes?}}

* MS001A096EMJ

{|
!Minebea Electronics UK LTD
!(circuit board)
|-
|DWG No.
|1 R26PA-SE300393 REV: E
|-
|PART No.
|1 1612100002
|-
|
|0234-3
|-
!Sticker:
|
|-
|NMB Technologies Corp
|Power Supply Division
|-
|Made in
|Thailand
|-
|Model:
|MS001A096EMJ
|-
|REV:
|08
|-
|AC INPUT:100-120V
|2A 47-63Hz
|}

== Connector pinout ==

=== Xbox 1.0 and 1.1 ===

The power supply connector for 1.0 and 1.1 is a single column of pins described by the following chart. Pin 1 is the connector pin closest to the back of the Xbox.

{| class="wikitable"
! Pin || Usage
|-
| Pin 1 || PowOK
|-
| Pin 2 || PowON
|-
| Pin 3 || GND
|-
| Pin 4 || GND
|-
| Pin 5 || GND
|-
| Pin 6 || GND
|-
| Pin 7 || +3.3V Standby
|-
| Pin 8 || +3.3V
|-
| Pin 9 || +5V
|-
| Pin 10 || +5V
|-
| Pin 11 || +5V
|-
| Pin 12 || +12V
|}

=== Xbox 1.2, 1.3, 1.4, and 1.5 ===
The power supply connector for the 1.2, 1.3, 1.4, and 1.5 xboxes is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK || Pin 1 || PowON
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || +3.3V
|-
| Pin 4 || +3.3V || Pin 4 || None
|-
| Pin 5 || None || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +3.3V Standby
|-
| Pin 7 || None || Pin 7 || GND
|-
| Pin 8 || +5V || Pin 8 || +5V
|-
| Pin 9 || +5V || Pin 9 || None
|-
| Pin 10 || +5V || Pin 10 || +12V
|}

=== Xbox 1.6 ===
The connector for the 1.6 Xbox is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox. This is the same connector as a 1.2, 1.3, 1.4, and 1.5 xboxes, with a different pinout.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK (3.3V Standby) || Pin 1 || PowON (3.3V)
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || None
|-
| Pin 4 || None || Pin 4 || None
|-
| Pin 5 || GND || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +5V (0.12V Standby)
|-
| Pin 7 || GND || Pin 7 || GND
|-
| Pin 8 || +5V Standby || Pin 8 || +5V Standby
|-
| Pin 9 || +5V Standby || Pin 9 || GND
|-
| Pin 10 || +5V Standby || Pin 10 || +12V (0.532V Standby)
|}

== Real world power usage ==

DC amperage as measured on a v1.0 Xbox with a Fluke 376 clamp meter around the PSU to Motherboard connections. HDD not included in measurements and the DVD drive and controller rumble were not used.

AC wattage measured at 120v 60Hz using a 'KILL A WATT' meter.
{| class="wikitable"
! || Power off || Unleash X || Halo 2 Menu || DolphinClassic || Maximum Observed
|-
| GND || 0A || 5.9A || 5.8A || 6.0A || 6.2A
|-
| 3.3v Standby || 0.2A || 0.3A || 0.3A || 0.3A || 0.3A
|-
| 3.3v || 0A || 2.5A || 2.2A || 2.7A || 2.7A
|-
| 5v || 0A || 7.1A || 7.2A || 7.0A || 7.2A
|-
| 12v || 0A || 0.3A || 0.4A || 0.4A || 0.4A
|-
| ~120VAC || 2.1W || 67.4W || 65.3W || 68.5W || 68.5W
|-
|}
TODO: Measure other hardware revisions and more usage scenarios.

== Related links ==

* [http://brandonw.net/consoles/xbox/ Describes how to turn an ATX Power-Supply to Xbox PSU]
* [https://web.archive.org/web/20060421203325/https://msmvps.com/blogs/matthewsoft/archive/2005/02/17/36238.aspx Powercord recall blog with exacter cable numbers]

Power Supply

2019-08-30T02:23:26Z

CrunchBite: Added "real world power usage" section

It's either a Foxlink{{citation needed}} or Delta Electronics power supply for most xboxes.
Some are rumored to be shipped with a Minebea brand and 1.6 xboxes are found with a "tuscany" made probably by Samsung.

On a 1.0 xbox supply, there seems to be 2{{citation needed|reason=2 per region, or 2 overall? and, what about foxlink?}} types for the US 120V and EU 240V market.

The standby voltage powers the [[SMC]] which handles turning on and off the system.
The Xbox supply needs a voltage (3V3?) on it's power-on line to leave the standby mode.
This results in the other voltages being supplied.

=== Delta Electronics ===
The marks are on the PCB with a check next to them:
* Delta Electronics DPSN-96-AP-1 should be the EU 240V one{{citation needed}}
* Delta Electronics DPSN-96-AP is the US 120V one

There is a link J11 under CR1 (right side of the coil under it) that might make the difference between 120V and 240V.
It also seems that the Bridge rectifier is bigger on the US models.
This could make sense as it has to handle double the current. So, before experimenting with this it might be worth to check if the installed type can handle 2.3 amps.

The rated output currents are also noted on the PCB

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.075A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

=== Foxlink Technology LTD ===

{{FIXME|reason=I don't own any US xboxes to compare US foxlinks with}}On the lower heatsink, there is a sticker with the following markings and versions:
* MODEL: FTPS-0001 REV:B {{citation needed}} (120V)
* MODEL: FTPS-0002 REV:B (from a 2002 PAL (240V))
* MODEL: FTPS-0002 REV:H (from a 2003 PAL (240V))
* MODEL: FTPS-0002 REV:G {{citation needed}} (240V)
* MODEL: FTPS-0007 REV:B {{citation needed}} (120V) (are these after the powercord recall?)
* MODEL: FTPS-0007 REV:D {{citation needed}} (120V) (are these after the powercord recall?)

The rated output currents are also noted on the sticker

96W Max output power

{| class="wikitable"
| Power Rail
| Rated Current
|-
| 3.3V Standby
| 0.045A
|-
| 3.3V
| 4.8A
|-
| 5V
| 13.2A
|-
| 12V
| 1.2A
|}

==== Powercord recall ====

Microsoft started an powercord recall, or more like a replacement program [https://web.archive.org/web/20050301093947/http://www.xbox.com:80/en-US/news/0502/powercordannouncement.htm xbox.com]for what appeared to be Foxlink powersupplies having a bad powerplug connector on the back of the console and where installed in 1.0 and 1.1 Xboxes.{{citation needed}}.
Microsoft tried to resolve this by offering free replacement powercords and advising to trow out the old ones. [https://web.archive.org/web/20120722175134/http://www.xbox-scene.com/xbox1data/sep/EEpAEAylAluZlwSlOJ.php More to the power cord replacement than meets the eye?]{{FIXME|reason=why is this link here and where could / should it be instead? I think it's misplaced here}}.

From the Microsoft powercord replacement FAQ:

: '''Does my console require a replacement cord?'''
: If it was manufactured before October 23, 2003, your console requires a replacement cord (except for consoles purchased in Continental Europe, where consoles manufactured prior to January 13, 2004 require a replacement cord). Consoles manufactured after October 23, 2003 (after January 13, 2004 for consoles purchased in Continental Europe) do not require replacement cords because design improvements to the cord and console already protect against the problems that are addressed by the replacement cords.[https://web.archive.org/web/20050223041403/http://replacements.webprogram.com:80/en-us/faqs.asp#Q-7]

The old page describing how to order has been archived here: [https://web.archive.org/web/20050223060900/http://replacements.webprogram.com:80/en-us/programoverview.asp]
One would either receive a thicker but very similar powercord or an actual [https://simple.wikipedia.org/wiki/GFCI GFI] (Ground Fault Circuit Interrupter). a online form would then be used to determine which type of cable you receive by means of serial number. {{FIXME|reason=I cant seem to find a source for these details yet, but I personally requested 2, 1 for my own Xbox (a 1.4, with a confirmed Delta. never replaced it.) and received a normal cable (EU). A friends xbox was older, 1.1/1.2?) and we got a european fusebox brick for his. looks like the UK one, but with the Benelux plug. It was all for free in Europe I remember the part number on my normal cable to be different (higher) for the newer one... ill check if I have it in the original box still}}

===== AFCI =====

A video of whats inside an european (UK) "AFCI" [https://www.youtube.com/watch?v=C0wQikAO-yA]

An european AFCI ordered from MS for free had the following on the bottom label.
{| class="wikitable"
| Part number
| X800925-100
|-
|
| 200-240V~,50/60HZ, 610mA
|-
| MFG Code
| DN0855
|}

The cable that is wired to the AFCI has the following markings:
{| class="wikitable"
! top
! bottom
|-
| JI-HAW
| JHT-031
|}
===== Old and New cords =====

The replacement cable has the following markings:{{citation needed}}
{| class="wikitable"
! top
! bottom
|-
| JHT-031
| {{citation needed}}
|}

The older cable that needed replacement was:
{| class="wikitable"
! top
! bottom
|-
| NITTO SS
| W41-27854
|-
| JHT-013
| N15905
|-
| JI-HAW
|
|-
| E147422
|
|}
Presumably this one doesn't come with tighter tolerances.

=== Samsung "TUSCANY"===
Found in 1.6 xboxes and seems to be made by Samsung (or atleast the main transformer is, which also has the detail label on it)
{{FIXME|reason=There are TUSCANY powersuplies in some 1.6 xboxes?}}
* PSCD101301A

=== Minebea ===
{{FIXME|reason=There are in the UK, Minebea powersuplies in some xboxes?}}

* MS001A096EMJ

{|
!Minebea Electronics UK LTD
!(circuit board)
|-
|DWG No.
|1 R26PA-SE300393 REV: E
|-
|PART No.
|1 1612100002
|-
|
|0234-3
|-
!Sticker:
|
|-
|NMB Technologies Corp
|Power Supply Division
|-
|Made in
|Thailand
|-
|Model:
|MS001A096EMJ
|-
|REV:
|08
|-
|AC INPUT:100-120V
|2A 47-63Hz
|}

== Connector pinout ==

=== Xbox 1.0 and 1.1 ===

The power supply connector for 1.0 and 1.1 is a single column of pins described by the following chart. Pin 1 is the connector pin closest to the back of the Xbox.

{| class="wikitable"
! Pin || Usage
|-
| Pin 1 || PowOK
|-
| Pin 2 || PowON
|-
| Pin 3 || GND
|-
| Pin 4 || GND
|-
| Pin 5 || GND
|-
| Pin 6 || GND
|-
| Pin 7 || +3.3V Standby
|-
| Pin 8 || +3.3V
|-
| Pin 9 || +5V
|-
| Pin 10 || +5V
|-
| Pin 11 || +5V
|-
| Pin 12 || +12V
|}

=== Xbox 1.2, 1.3, 1.4, and 1.5 ===
The power supply connector for the 1.2, 1.3, 1.4, and 1.5 xboxes is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK || Pin 1 || PowON
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || +3.3V
|-
| Pin 4 || +3.3V || Pin 4 || None
|-
| Pin 5 || None || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +3.3V Standby
|-
| Pin 7 || None || Pin 7 || GND
|-
| Pin 8 || +5V || Pin 8 || +5V
|-
| Pin 9 || +5V || Pin 9 || None
|-
| Pin 10 || +5V || Pin 10 || +12V
|}

=== Xbox 1.6 ===
The connector for the 1.6 Xbox is two columns. Pin 1, Column 1 being the top left pin. Pin 1, Column 2 being the top right pin. The top being the side closest to the back of the Xbox. This is the same connector as a 1.2, 1.3, 1.4, and 1.5 xboxes, with a different pinout.

{| class="wikitable"
! Pin Column 1 || Usage || Pin Column 2 || Usage
|-
| Pin 1 || PowOK (3.3V Standby) || Pin 1 || PowON (3.3V)
|-
| Pin 2 || GND || Pin 2 || GND
|-
| Pin 3 || None || Pin 3 || None
|-
| Pin 4 || None || Pin 4 || None
|-
| Pin 5 || GND || Pin 5 || GND
|-
| Pin 6 || GND || Pin 6 || +5V (0.12V Standby)
|-
| Pin 7 || GND || Pin 7 || GND
|-
| Pin 8 || +5V Standby || Pin 8 || +5V Standby
|-
| Pin 9 || +5V Standby || Pin 9 || GND
|-
| Pin 10 || +5V Standby || Pin 10 || +12V (0.532V Standby)
|}

== Real world power usage ==

As measured on a v1.0 Xbox with a Fluke 376 clamp meter around the PSU to Motherboard connections. HDD not included in measurements and the DVD drive and controller rumble were not used.
{| class="wikitable"
! || Power off || Unleash X || Halo 2 Menu || DolphinClassic || Maximum Observed
|-
| GND || 0A || 5.9A || 5.8A || 6.0A || 6.2A
|-
| 3.3v Standby || 0.2A || 0.3A || 0.3A || 0.3A || 0.3A
|-
| 3.3v || 0A || 2.5A || 2.2A || 2.7A || 2.7A
|-
| 5v || 0A || 7.1A || 7.2A || 7.0A || 7.2A
|-
| 12v || 0A || 0.3A || 0.4A || 0.4A || 0.4A
|-
|}
TODO: Measure other hardware revisions and more usage scenarios.

== Related links ==

* [http://brandonw.net/consoles/xbox/ Describes how to turn an ATX Power-Supply to Xbox PSU]
* [https://web.archive.org/web/20060421203325/https://msmvps.com/blogs/matthewsoft/archive/2005/02/17/36238.aspx Powercord recall blog with exacter cable numbers]