KaosEngineer

The first 64MBs has to be good. IIRC, XBlast OS's RAM test only tests/checks the additional 64MBs installed when a 128MB upgrade is done. There is an Xbox application, xbmemcheck, that tests RAM but if your console is not even booting to a replacement dashboard, you won't be able to run it. xbmemcheck.rar Edit: You may be able to run it by creating a boot disc with this app. Make an XISO disc image with QWIX or C-Xbox Tool then burn it to DVD-R media. Buring to CD-RW media may work if your Xbox's DVD drive is one that can read them. The Xbox BIOS attempts to load/run the default.xbe file read from the DVD drive before loading the dashboard off the hard drive.

Xeucter2 BIOS Manager (X2BM 2.3 is the last release.) You need a short ( less than 3 foot long I believe was mentioned somewhere; however, I believe I used a shielded cable that was longer) 25-pin straight through DB-25 printer cable, not a serial cable.

XBlast resizing a BIOS will write 4 copies of one BIOS to the 1MB flash of the X2.6CE modchip. You will have the same BIOS on both banks. That's just the stupid way the X2.x lite modchips work. Edit: The BIOS you flash fills the entire 1MB flash memory chip on the modchip, not a specific bank. On my X2 pro modchip, you selected the bank you wanted to flash (one of the 4 256KB banks or one of the 2 512KB banks or the entire 1MB bank of the modchip) and flashed it with the correct size dot bin file. Edit: Actually with Evox it didn't have to be the correct size if the selected bank was 512KB and you were flashing a 256KB BIOS it wrote it two times to fill the entire 512KB bank. If you create a 1MB file with 4 separate BIOS concatenated together you can select each one separately using the bank select switches for the 4 256KB banks.

Ok, that's good. No problem with the late reply. Next Step Look for any extraenous solder splashes or tiny balls of solder on the surface of the motherboard or between chip pins that may be connecting two or more traces or pins of a chip together that should not be.

You must create a 1MB-sized (2 x 512KB ) resized BIOS dot bin file to flash an X2.6CE modchip. When flashing the modchip, it writes to the entire 1MB flash not just the single bank selected on the bank selection switch. The X2.6CE has 2 512KB banks so you have to resize a 256KB sized BIOS, like the majority of original and modified BIOSes are, to 512KBs then contatenate two of these BIOSes into one 1MB sized file. I had / well have an X2 pro modchip that allowed you to flash a single bank based on the switch selection but the lite modchips don't work the same way. The entire flash is overwritten. P.S. I've not used a X2.x Lite modchip to verify what I have said. I've only used an X2 pro which allowed 256KB, 512KB or a 1MB do bin file to be flashed to the modchip. 256KB and 512KB dot bin files allowed selection of a specific bank to be flashed.

You beat me to posting the info. However I'd not read down this far in the thread before I posted.

You are off on the required cluster sizes. Max supported Partition size | Cluster Size 256 GB | 16 KB 512 GB | 32 KB 1024 GB | 64 KB ----------These next few I'm not certain of since I've not used M8 Titan patched or CerBIOS---------- 2048 GB | 128 KB 4096 GB | 256 KB 8192 GB | 512 KB

Check the voltage level present on the collector of the transistor at location Q7C2. It should be at a stable 3.3Vdc level. The collector is the pin on the side by itself.

Try again later. Google has download limits in place that prevent it from being downloaded. It may remove the download restriction after 15 minutes or it may take several hours before it can be downloaded again.

The new PSU you installed has both v1.0/1.1 and v1.2-1.4 connectors. Verify that the 3.3Vdc standby level is present at the motherboard's power supply connector. (Brown wired pin on the connector below) The voltage level at the resistor that has the power button signal going through it to the SMC (PIC processor) should drop to 0Vdc when the power button is pressed and return to ~3.3Vdc when the button is not depressed.

U6F1 on a v1.0-1.4 revision motherboard. I'm not sure what's being used on a v1.6 motherboard. The location I traced the CPU's THERMDC and THERMDA (thermal diode signals to - BGA pad AA15 and AB16) end up at an unpopulated SMD 8-pin set of pads at location U3B1. i know that the SMBus address where the supposed temp readings are being read from for a v1.6 motherboard are different than for v1.0-1.4 motherboards . The value used as the CPU temp is 5 to 10 degrees C higher on a v1.6 than a v1.0-1.4 motherboard.

Yes, the CPU has a thermal diode in it that connects to the ADM1032 dual temp sensor for the value to be read from it across the SMBus. The other temp sensor is built-into the ADM1032 which simply reads the ambient air temperature around the chip. Edit: I do not know if there's a similar temp sensor in the GPU. Originally dashboards stated that the two temps were that of the CPU and GPU. But the GPU was actually the ambient air temperature inside the Xbox by the ADM1032 chip - U6F1. Later revisions of replacement dashboards started labeling this temp as the motherboard temp.

Interesting...the THERMDC and THERMDA (thermal diode signals) from the CPU only go to that missing chip's location (U3B1). I know that the dashboard's reported CPU temp on v1.6 Xbox's is always higher than on previous Xbox revisions. And, the temp sensor's I2C (SMbus) address is different on a v1.6 motherboard. I need do more research and track down any documentation on the Xbox's GPU. Questions to be answered: Does it have a thermal diode? If so, which BGA pads of the GPU are they? And, do they connect to the Xyclops chip?

Oops wrong chip name - the MS custom Xyclops chip, not the Xcalibur video encoder.

Okay, I'll have to do a bit more tracing the signals to see if they go beyond there. You could use a multimeter to measure resistance from pin 2 and 3 to pins of the edit: Xcalibur Xyclops chip. I believe they go into it instead of having the ADM1032 chip. I'd never tried to figure out where they connected before. Odd... Edit: Oops, not thinking straight it seems. The temp sensor not integrated into the video encoder, MS custom Xcalibur chip, but the Xyclops chip.

Wait a minute. I traced the THERMDA and THERMDC signals from the CPU to the IC U3B1 pins 2 and 3. The pictures I used were component-free hi-res scans from the now defunct web site diy.sickmods.net. What is the IC at U3B1 on a v1.6 motherboard? Is it an ADM1032 just like used on v1.0-1.4 motherboards? The chip is simply at a different location on a v1.6 motherboard - U3B1 instead of U6F1.

Do you have a larger SATA hard drive installed with a cheap IDE-to-SATA adapter? Most of the cheap IDE-to-SATA adapters are slow starting after a reset and the Xbox will FRAG. If you power cycle the console, does it boot properly? What do you mean by Christmas lights: Red/Green or Red/Green/Yellow flashing?

one of the two vias at the end of the new wire.

Follow the trace going off to the right from the test pad that was pulled off to find a via. Cut a long enough piece of kynar insulated 30 AWG wire-wrap wire to solder from that via to the via on the left of the picture where the trace pulled off of the PCB.

The CPU temp sensor diode connects from the CPU pads to the edit: Xcalibur Xyclops chip. I've not traced down which pins of the edit: Xcalibur Xyclops they connect to. CPU BGA Pads: THERMDA = AA15 THERMDC = AB16 The traces make their way moving from top to bottom side of the PCB several times along their journey to the edit: Xcalibur Xyclops chip. Image of the CPU BGA pads (Edit: Opps I forgot the D in THERMDA and THERMDC). And, these traces are already making there jump from the top to the bottom side of the PCB moving at an angle down and to the right of each PAD to a via.

One or two of the traces from the CPU temp sensor diode to the edit: Xcalibur Xyclops may be damaged resulting in a FALSE positive overheating condition.

Hmm, the contacts of the cable or connector on the back of the Xbox may be dirty and/or corroded. Clean them all with 90%+ isopropyl alcohol and/or electronic contact spray cleaner.

I believe the temp sensor on v1.6 Xboxes is part of the custom edit: Xcalibur Xyclops chip. The custom edit: Xcalibur Xyclops chip replaced the TSOP, PIC processor (System Management Controller) and temp sensor all in one package.

What do you mean by this statement? You see the Evox shield in the upper left hand corner of the start up animation when you power on the system. Source: https://www.reddit.com/r/originalxbox/comments/ui3t5u/my_xbox_boots_up_with_that_evox_logo_what_do_i/ If so, that's the indication that an Evolution-X BIOS is being used. Two Software Components used to Modify an Original Xbox Team Evolution-X created many versions of both of these software components: 1. Modified BIOS/kernel that removed/disabled the security features built into the stock BIOS/kernel. Evolution-X created several different modified BIOS/kernel releases: for v1.0 Xboxes only: 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, and 2.6 (most likely many older v0.x and v1.x releases too) for v1.1 Xboxes only: 3.6 for v1.0 or v1.1 Xboxes: D.6 v1.0-v1.6 (MULTI_VERSION): M7 v1.0-v1.6b (MULTI_VERSION): M8 and M8plus their final release. 2. Replacement Dashboard Evolution-X created several releases of their replacement dashboard - Evolution-X Dash (a.k.a., Evoxdash / RemoteX). The last release being v+3935. Source: https://www.se7ensins.com/forums/threads/every-modded-xbox-dahsboard.433141/ BIOS / Kernel Version Since the Kernel version is 5838 from the previously posted UnleashX System Info page, it is either the Evolution-X M8 or M8plus BIOS. You cannot tell exactly which from the kernel version value alone. Team Evolution-X didn't change the kernel version for every BIOS they released to better identify which one you have installed. They left the kernel version the same as the original Xbox BIOS it is based upon. Here 5838 is the stock v1.6 Xbox's BIOS/kernel version number.

Serial Number: 104637740806 Format of information that can be determined from the serial number value: LNNNNNNYWWFF L = factory line number this Xbox was made on NNNNNN = number of this Xbox made during its week (WW) of production Y = Year produced = 200Y - 2004 WW = Week of the year produced --> 8th week of 2004. FF = factory this Xbox was produced in. 02 = Mexico, 03 = Hungary, 05 = China, 06 = Taiwan --> Taiwan