JTAG Falcon R-JTAG w/Demon RRoD 0020 error on Stock NAND

[tr4ckerz]

I have finished another R-JTAG installation, this time on Falcon with Demon setup. Everything went flawlessly, after some tweaking I finished up with almost perfectly booting console (RATER score of gently under 9). Freeboot image went into Demon NAND.

The problem appeared on stock NAND side where I'm getting RRoD (0020) while trying to boot to stock. This is my first Falcon where I encountered such problem.

After some searching I found that several users here have reported similar behavior on Falcons R-JTAG w/Demon and I can confirm that this one behaves same and that the "trick" with switching the NAND works the same for me:

1. I'm getting RRoD (0020) every time while trying to boot to stock. What did I notice is that the green debug LED on R-JTAG board does not even blink.

2. As soon I boot freeboot from Demon NAND (which I can without single problem) and then I switch the NAND using button on Demon front panel, console powers off (blue LED on Demon front panel does not lit) and I can boot to stock. This time the green debug LED on R-JTAG board flashing once prior to boot from stock NAND.

3. In this state I can boot to stock as many times I want with no problem. Until I switched the NAND back to Demon OR unplugged the power cord. After that I'm again getting RRoD (0020) when trying to boot to stock.

Conclusion: When powering off the console by common way OR switching NAND using !DSWITCH application I'm not able to boot to stock (RRoD 0020). Green debug LED on R-JTAG board does not even try to blink. Only way to boot to stock is to switch the NAND using button on Demon front panel while console is powered on from Demon NAND (as described in point 2. above)

This method is a bit annoying not to mention that I'm not sure if this could not leave some records about unsuccessful boot in stock NAND and thus unsafe for connecting to Live (just thoughts).

Is there anything I can do to eliminate this problem before I send this console back to customer or is this general problem related to particular consoles?

P.S. In case this is a problem related to soldering and wiring I will add detailed pictures later tonight as soon I can. Sorry about that.

 

[Scrufdog]

Welcmoe to my world. This problem is occurring more and more with this specific problem. Apparently there us still a little disbelief of this happening among the higher ups of TX, but hopefully a fix is coming soon.

 

[Martin C]

OP - desolder the R-JTAG and then repeat the above steps. Obviously the DemoN NAND won't boot.

but hopefully a fix is coming soon.

From where?

 

[Scrufdog]

From where?

I dunno, just hoping.

 

[Martin C]

I dunno, just hoping.

If you remove the R-JTAG and the console still does it, surely that's proof enough it's not an R-JTAG issue?

 

[Scrufdog]

Mine and others worked fine after you removed the rjtag and flashed everything stock. One guys worked fine with RGH2 but not rjtag. Instead of looking for negatives with this possible issue, how do we find anyone with an rjtag and demon combo that works?

 

[Martin C]

Yes - this was tested long before release.

 

[Scrufdog]

Alrighty then, back to the original subject...

 

[Martin C]

In the cases of R-JTAG being removed and the console performing properly, did you try powering the R-JTAG from the J-RP v2 'programmer' cable and desoldering the 5v wire from the R-JTAG board?

 

[tr4ckerz]

Thank you guys for your inputs.

Sorry for a bit late reply I had no chance get back to this problem sooner.

So I did several tries and here are my findings:

OP - desolder the R-JTAG and then repeat the above steps. Obviously the DemoN NAND won't boot.

1. I desoldered R-JTAG (specifically 5V line from R-JTAG board) and wrote stock image into Demon NAND. In this state the console boots into stock dashboard from both (X360 and Demon) NANDs with no problems. Does not matter if I have switch on the bottom QSB ON or OFF, worked both.

2. Without any other changes but having 5V line soldered back to R-JTAG board (switch on bottom QSB set to ON), the console boots from X360 NAND with no problem. Debug LED on R-JTAG board behaves as it should, i.e. blinks once solid green prior to boot.

3. Without any other changes I wrote freeboot image back to Demon NAND. Since then, the console behaves the same as at the beginning as described in OP, i.e. when trying to boot from X360 NAND then getting RRoD (0020). In this state the green debug LED either does not even try to blink prior to boot or blinks once very weakly.

In the cases of R-JTAG being removed and the console performing properly, did you try powering the R-JTAG from the J-RP v2 'programmer' cable and desoldering the 5v wire from the R-JTAG board?

I tried this without positive result. I noticed it doesn't matter which way the R-JTAG board is powered, nor disconnecting DVD drive and HDD doesn't affect anything. It seems to me that only thing that affects the described problem is freeboot image written into Demon NAND.

Could these findings get us a bit closer to identify what causes this problem? I'm willing to do other tests if needed.

 

[Martin C]

Ok, so it's not a power drain issue.

Try writing an RGH2 image to the Demon. It obviously won't boot, but let me know what happens.

 

[tr4ckerz]

The console won't boot with RGH2 image loaded in Demon NAND. However, it boots into stock dashboard with no problems from X360 NAND (i.e. no RRoD).

EDIT: The debug LED on R-JTAG board behaves as it should in this configuration, i.e. blinks once solid green prior to boot from stock NAND.

 

[Morgiee101]

I had this problem and until we can get to the bottom of why its happening to just falcons I do the following but im not suggesting you do this as it is not advised by the TX team, I just chose to do it. Boot up glitch image as normal from Demon mode, once booted press the nand switch button and the console will switch off. immediately turn the console back on and so far 100% of the time boots standard nand no problem even with r-jtag and glitch nand on demon. The problem seems to lie between the switching of the nands while powered off.

 

[BrockThunderjam]

I had this problem and until we can get to the bottom of why its happening to just falcons I do the following but im not suggesting you do this as it is not advised by the TX team, I just chose to do it. Boot up glitch image as normal from Demon mode, once booted press the nand switch button and the console will switch off. immediately turn the console back on and so far 100% of the time boots standard nand no problem even with r-jtag and glitch nand on demon. The problem seems to lie between the switching of the nands while powered off.

It's not just Falcons, happens to the Jasper I just did as well. Have a whole thread about it.

 

[Martin C]

The console won't boot with RGH2 image loaded in Demon NAND. However, it boots into stock dashboard with no problems from X360 NAND (i.e. no RRoD).

EDIT: The debug LED on R-JTAG board behaves as it should in this configuration, i.e. blinks once solid green prior to boot from stock NAND.

So with an RGH2 image on the DemoN NAND, you're not getting the 0020 when trying to boot stock on the 360 NAND?

 

[tr4ckerz]

So with an RGH2 image on the DemoN NAND, you're not getting the 0020 when trying to boot stock on the 360 NAND?

Exactly like that Martin.

1. With R-JTAG image (AUD_CLAMP wiring) on the DemoN NAND, the console boots freeboot from DemoN NAND with no problem, however trying to boot stock from the X360 NAND gives RRoD 0020

2. With stock image on both DemoN and X360 NAND, the console boots to stock from both NANDs with no problem, no RRoD

3. With RGH2 image on the DemoN NAND, the console won't boot from DemoN NAND (just trying to glitch and nothing), however boots to stock from X360 NAND with no problem, no RRoD

I had this problem and until we can get to the bottom of why its happening to just falcons I do the following but im not suggesting you do this as it is not advised by the TX team, I just chose to do it. Boot up glitch image as normal from Demon mode, once booted press the nand switch button and the console will switch off. immediately turn the console back on and so far 100% of the time boots standard nand no problem even with r-jtag and glitch nand on demon. The problem seems to lie between the switching of the nands while powered off.

That's what I tried (see OP, point 2.) just to test if it works for me like for everyone else with the same issue. However I won't suggest this method of use to my customer.

 

[Martin C]

Exactly like that Martin.

1. With R-JTAG image (AUD_CLAMP wiring) on the DemoN NAND, the console boots freeboot from DemoN NAND with no problem, however trying to boot stock from the X360 NAND gives RRoD 0020

2. With stock image on both DemoN and X360 NAND, the console boots to stock from both NANDs with no problem, no RRoD

3. With RGH2 image on the DemoN NAND, the console won't boot from DemoN NAND (just trying to glitch and nothing), however boots to stock from X360 NAND with no problem, no RRoD

Ok - can you try building a JTAG image from your stock NAND - do NOT select R-JTAG.

 

[jsinger47]

Ok - can you try building a JTAG image from your stock NAND - do NOT select R-JTAG.

Its not an issue with the nand. The issue is being investigated.

In the case of a spelling error, I blame Tapatalk.

 

[Morgiee101]

Its not an issue with the nand. The issue is being investigated.

In the case of a spelling error, I blame Tapatalk.

Finally its getting looked at as an issue and not a "its not soldered correctly" problem if only I had a spare falcon with demon I would have it ready for any testing needed.

 

[jsinger47]

I did say it was not a NAND problem.

I did not say it was not an install issue.