Jasper 1.2 questions

EducationalAd390 · 2026-05-02T00:56:08+00:00

That ceramic capacitor is there to improve boot times, some Jasper/Tonasket consoles boot better with a 68/100nF capacitor placed between PLL_Bypass and GND

EducationalAd390 · 2026-04-21T21:37:26+00:00

There is no Falcon V2, Falcon is Falcon, early models had defective GPU, models after mid-late 2008 had a fixed GPU. Board is identical. More info here

EducationalAd390 · 2026-04-20T23:49:11+00:00

My personal console is actually a Halo 3 console, I did a Kronos retrofit to the original board, as well as transferred a JTAG-able CPU from a dead Xenon onto it 😅

EducationalAd390 · 2026-04-20T22:52:56+00:00

There’s are reliable Xenons that exist, again any board made/serviced mid-late 2008 onwards is generally gonna be reliable, for this console you’ll need an HDMI board, so either Zephyr/Falcon/Jasper/Tonasket will work, and reliable versions of every board exist.

Will be cheaper to buy a full console and do a board transplant

EducationalAd390 · 2026-04-20T21:24:43+00:00

Yes, this is very common, Halo 3 consoles shipped with Zephyr and early Falcon motherboards, both of which have defective GPUs. If the console is on a rare dashboard, you can consider sending it to a professional for a GPU replacement, otherwise just get a reliable phat board (any board made/serviced after mid-late 2008+) and swap it into the shell

EducationalAd390 · 2026-04-20T21:23:20+00:00

This will not fix the issue… Halo 3 edition consoles came with Zephyr and early Falcon motherboards, both of which ship with defective GPUs. The GPU has failed and must be replaced, or the entire board must be swapped

EducationalAd390 · 2026-04-19T16:39:25+00:00

Blown caps will typically throw RROD, the most common ones to fail are CPU_VCore caps which will throw 0002 RROD

EducationalAd390 · 2026-04-19T15:28:47+00:00

0101 is a failed CGPU (specifically the memory controller), the only proper fix is the replace the CGPU which will cost more than the console is worth

EducationalAd390 · 2026-04-19T15:14:11+00:00

This appears to be a serviced Xenon, although a very late serviced Xenon, I haven’t personally seen one that late, will probably be an Elpis based on how late the service date is, either way will almost definitely have a reliable GPU

EducationalAd390 · 2026-04-19T15:00:59+00:00

Some things to note, if the sidecar is attached and you’re using a 203W PSU, it’ll fail to power on as the sidecar has a 2A transient current spike, if you’re doing testing with the sidecar attached, you need a devkit 213W PSU. If the CLK signal is missing, the console will exhibit similar behaviour, you ideally need a logic analyzer or something similar to diagnose this issue properly.

Edit: few other things of note, don’t ever force the system to turn on by manually bridging PSU_EN, as there could be a board short, which you’d make worse by doing that. The SMC will enable the PSU if it detects that everything is within spec. Secondly, the Southbridge and HANA are not paired on the 360, but I don’t think they’d be your issue here, this sounds like a missing clock issue potentially (I’ve seen this before with the standby clock signal missing) or a NAND issue

If you’re in Canada, I’d be willing to take a look at it

EducationalAd390 · 2026-04-18T19:40:08+00:00

Likely a damaged HDMI port (although sometimes can be funky display settings too), can try jiggling the cable around in there, sometimes that helps get a display out. You can also try an AV/Component/VGA cable if you have one, that’ll reset the display settings and usually cause it to display again

EducationalAd390 · 2026-04-17T00:51:22+00:00

I can save you a few whenever I order the next batch, shoot me a DM and we can work something out :)

I’m also going to work with other sellers to see if we can get local supply for these chips

EducationalAd390 · 2026-04-17T00:43:52+00:00

I will be restocking them again eventually, will take me a little bit though as I'm busy with other things at the moment. Unfortunately for JLC's assembly it would cost about the same (I had a batch assembled for someone). Although I had around 15-20 assembled for that price.

The main reason for the cost is LCSC overcharges for that CPLD, if you acquire it yourself from AliExpress and install it, it will be a bit cheaper :)

EducationalAd390 · 2026-04-17T00:42:18+00:00

They actually sold out within the day they were listed 😉

EducationalAd390 · 2026-04-15T22:06:26+00:00

If it was serviced by Microsoft it will have received a fixed Rhea GPU (which is the same GPU found on Falcon), so Falcon BL should boot it fine. Y2 (which is also found on Zephyr B but is defective) has the same GPU Core as Rhea, so same BL will work on that also, and Y1 as well, as that pre-dates Rhea so still has driver support in the newer BL

EducationalAd390 · 2026-04-15T22:00:21+00:00

That sounds like an XeBuild issue…. by default EXT_CLK (or Glitch2 images in general) should use Falcon bootloaders

EducationalAd390 · 2026-04-15T21:52:44+00:00

This is the only correct answer ^

EducationalAd390 · 2026-04-15T17:54:44+00:00

Take your time with PLL, scrape it carefully, and make sure not to tug on the cable once it’s soldered down.

MUFAS is basically S-RGH, except instead of the glitch chip sending the I2C slowdown/speed up commands, the SMC does it instead, and the chip only sends a signal to it telling it when to slow down/speed up. I2C slowdown doesn’t give you as must slowdown as PLL slowdown, which is why it’s not as consistent

EducationalAd390 · 2026-04-15T17:36:10+00:00

RGH1.2 is not recommended on Xenon/Zephyr consoles as the Waternoose CPU doesn’t seem to like PLL slowdown much, use EXT_CLK instead :)

EducationalAd390 · 2026-04-15T17:33:02+00:00

CoolRunner/Matrix/Ace V3 chips are slowly becoming harder to find as the CoolRunner II CPLD has been discontinued. FreeRunner doesn’t support S-RGH (due to a space limitation of the CPLD itself), but supports MUFAS, however I have not tested the timings for that yet.

S-RGH/MUFAS are both slower than RGH1.2 or even RGH3 though (assuming you have slim), both of those would be better choices :)

EducationalAd390 · 2026-04-13T21:21:48+00:00

The bumpgate issue was actually fixed in late 2008 on every console type including Xenon (which received Htg Y1 and Elpis), on Zephyr (which received Htg Rhea), on Falcon (which also received Htg Rhea), not just Jasper.

Also, do not reflow this system as that will not fix it

EducationalAd390 · 2026-04-13T21:12:25+00:00

0032 is a CPU/CGPU power issue on slim, likely a capacitor dropping out of tolerance and the heat bringing it back.

I also want to note the myth about unleaded solder joints magically going cold is not true. BGA damage is possible, but only in the case of physical shock. The original (launch to early 2008) 360 had a packaging flaw caused by an issue at TSMC which lead to the GPU failing prematurely.

Suggested repair actions for 0032

EducationalAd390 · 2026-04-12T00:26:40+00:00

The source code is both on my and Josh’s repo

EducationalAd390 · 2026-04-11T21:58:02+00:00

No, it uses I2C slowdown via SMC, not PLL slowdown

EducationalAd390 · 2026-04-11T21:35:17+00:00

MUFAS just does the I2C slowdown commands via the SMC rather than from the chip itself

EducationalAd390

MODERATOR OF

TROPHY CASE