RROD 0020 on Falcon only when POST cable attached - no XELL

akula169

akula169

Junior Member
Jun 16, 2004
19
0
Console Type: Falcon
NAND size: 16
Dashboard version: 2.0.16202
CB version: 5774

I'm working from the stock firmware. It boots normally if I detach the POST cable from the r-jtag board. If I boot with the cable attached, it immediately RROD's 0020. When I detach the POST cable, it will continue to RROD on subsequent reboots until I unplug/plug the power cable. It is difficult to tell from the pictures, but I fluxed and went over the solders on the POST board multiple times - and tested continuity and checked for shorts. I suppose one question would be is if there are alternative points I can test to make sure my solders are good?

I've also tried going directly to a Xell-ReLoaded flash - I get nothing but the same POST as I get with the RROD (below), the only exception is there is no RROD - just a center green light. It sounds as if the fan is PWM pulsing rapidly.

Pointers are appreciated.

Here's the output from Rater POST, the "Post 7C Post 04" pattern continues infinitely
Code: 
[B][B][B][B][B][B][B][B][B][B]Phat Selected
[/B][/B][/B][/B][/B][/B][/B][/B][/B][/B]Version: 10
Power Up
Waiting for POST to change
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
[B][B][B][B][B][B][B][B][B][B]Post 7C 
[/B][/B][/B][/B][/B][/B][/B][/B][/B][/B]
 

Attachments

Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
1. Why do you have a cable connected to the header pin on the R-JTAG? Exactly what have you done with this?
2. You've lifted R2P12. That's not good. You'll have all kinds of issues.
 
akula169

akula169

Junior Member
Jun 16, 2004
19
0
Martin C said:
1. Why do you have a cable connected to the header pin on the R-JTAG? Exactly what have you done with this?
2. You've lifted R2P12. That's not good. You'll have all kinds of issues.
Click to expand...
1. That's how you are able to flash the NAND
2. Actually, somehow it got blown and I had to remove it. I replaced it with a 10k resistor (through-hole) on other points on the board. Prior to replacement, the power button and LEDs did not work. They are fine now.
 
Last edited:
Antalpromille

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
XMonsterModsX said:
the points on the nand x qsb need to be cleanded up. id look at point B as as the biggest issue
Click to expand...
Yeah i agree on that, make sence when its not used for R-jtag :p

OP: looks like two points on your post QSB isnt soldered, resolder and see if it gets better.
 
akula169

akula169

Junior Member
Jun 16, 2004
19
0
XMonsterModsX said:
im talking about to rule it out of the issue of 0020 idk why he soldering stby_clk point but the soldering dosnt look good.
Click to expand...
stby_clk? In the tut pics, C7R112 is the cpu_rst.

Antalpromille said:
Yeah i agree on that, make sence when its not used for R-jtag :p

OP: looks like two points on your post QSB isnt soldered, resolder and see if it gets better.
Click to expand...
I'll go over it again, but it looks good when I look at it with a loupe. Are there other points on the board I can use to test that I made a good connection?

XMonsterModsX said:
the points on the nand x qsb need to be cleanded up. id look at point B as as the biggest issue
Click to expand...
Point B? What point B? I checked the NAND-X solder continuity with a multimeter on the other side of the board. They are good.

skillet34 said:
Um no the rjtag is pre programmed you did not try to flash anything to it did you? no need to have anything connected to the header pin
Click to expand...
Hrm. I have to chalk this one up to the lack of documentation. Hooking that up seemed to be the only way I was able to reflash my stock firmware back to the motherboard (or so I thought), after I was having trouble with the Xell flash. Why is that cable included if we don't need it? If I did indeed overflash the pre-programmed bit on the r-jtag, where can I get the firmware that I need to put back?
 
Last edited:
akula169

akula169

Junior Member
Jun 16, 2004
19
0
XMonsterModsX said:
u ddnt reprogram it. i think your talking about reflashing the nand not the firmware? by point be i meant stby_clk= R4B24
Click to expand...
Oh - above the JTAG QSB? Yeah, that was the alternate connection point for the other side of R2P12 for that 10k resistor I replaced.

So there's no way I accidentally over wrote the stock firmware on the R-JTAG board by having that cable attached?
 
akula169

akula169

Junior Member
Jun 16, 2004
19
0
OK, so I FINALLY managed to get the Xell to reboot and I got the CPU key. I created and flashed the XeBuild image.

How did I do it? I'm not quite sure. First off, it seems I need to disconnect the power brick for a while - that's the only way I can a boot that doesn't start looping the "POST 7C POST 04" output over and over. Really, it seems like I can only get it to boot straight once out of twenty tries.

On the rare occasion it did a normal post boot, it was failing just after POST 21. I moved the switches to from 5/7 on to 3/7 on (I'm using aud_clamp) and I was able to get it to glitch on that one successful boot.

After flashing the XeBuild image, I've yet to get it to boot again. I'll keep trying - but its so random.

Nobody else has seen the repeating like this?

Code: 
Phat SelectedVersion: 10
Power Up
Waiting for POST to change
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 0E 
Post 1E - BRANCH 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post FC 
Post 7C 
Post FC 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post FC 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post FC 
Post 04 
Post 7C 
Post 04 
Post FC 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post FC 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post FC 
Post 04 
Post 7C 
Post 04 
Post 7C 
Post 04 
Post FC 
Post 7C 
Post 04 
Post 7C
 
Last edited:
Antalpromille

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
XMonsterModsX said:
u ddnt reprogram it. i think your talking about reflashing the nand not the firmware? by point be i meant stby_clk= R4B24
Click to expand...
maybe you didnt get that the first time since is was being ironic, B point isnt used on R-jtag so stop talking about it. OPs consol boots wich mean that the trace is intact, the point on his QSB doesnt need to be soldered.
 
akula169

akula169

Junior Member
Jun 16, 2004
19
0
Antalpromille said:
maybe you didnt get that the first time since is was being ironic, B point isnt used on R-jtag so stop talking about it. OPs consol boots wich mean that the trace is intact, the point on his QSB doesnt need to be soldered.
Click to expand...
Thanks for clearing that up.

Still waiting to see if anyone knows about (or has experienced) the looping POST.
 
Antalpromille

Antalpromille

VIP Member
Aug 4, 2011
3,146
0
Borås, sweden
akula169 said:
I had not, as no one had suggested it.

Now I just tried 1.2v - no more janky boots! It just glitch booted on the second pass!

Thank you!
Click to expand...
No problem, just happy i could help :)
 
Martin C

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
akula169 said:
I had not, as no one had suggested it.

Now I just tried 1.2v - no more janky boots! It just glitch booted on the second pass!

Thank you!
Click to expand...
It's suggested you try all power options and DIP settings in the documentation.

Glad you finally got there however. Please, next time to NOT connect anything to the headerpin on the R-JTAG board. There is no need.

akula169 said:
Hrm. I have to chalk this one up to the lack of documentation. Hooking that up seemed to be the only way I was able to reflash my stock firmware back to the motherboard (or so I thought), after I was having trouble with the Xell flash. Why is that cable included if we don't need it? If I did indeed overflash the pre-programmed bit on the r-jtag, where can I get the firmware that I need to put back?
Click to expand...
There's no lack of documentation, just lack of reading. It states quite clearly in the installation guide:

Warning
DO NOT - I REPEAT - DO NOT ATTEMPT TO WRITE ANY TIMING FILE TO YOUR R-JTAG. They are pre-programmed. Writing any other timing file to the R-JTAG without instruction from T-X may result in permanently damaging it


The cable is provided with the JR-Programmer v2 as it's a multi-use device so you can write to Rev C/CR3-Lite/DGX (for RGX)/etc. Thankfully you didn't write to it!
 
  • Like
Reactions: gavin_darkglide
akula169

akula169

Junior Member
Jun 16, 2004
19
0
Martin C said:
It's suggested you try all power options and DIP settings in the documentation.

Glad you finally got there however. Please, next time to NOT connect anything to the headerpin on the R-JTAG board. There is no need.



There's no lack of documentation, just lack of reading. It states quite clearly in the installation guide:

Warning
DO NOT - I REPEAT - DO NOT ATTEMPT TO WRITE ANY TIMING FILE TO YOUR R-JTAG. They are pre-programmed. Writing any other timing file to the R-JTAG without instruction from T-X may result in permanently damaging it


The cable is provided with the JR-Programmer v2 as it's a multi-use device so you can write to Rev C/CR3-Lite/DGX (for RGX)/etc. Thankfully you didn't write to it!
Click to expand...
Easy there, bud. The only "documentation" I could find was the collection of jpegs and some terse notes: which is the post that is stickied at the top of this sub-forum. NO MENTION of that cable or the fact it should NOT be connected. I went with common sense and noted the correlation of markings on both the JR2 board and the header's screen print label (TMS,TDI,TDO, etc,etc). The values matched. It made sense to me at the time... especially when things weren't working out as expected. Not all of us are pro-installers. And the rest are not mind-readers.

I'll gladly stand corrected if you could kindly point out some detailed documentation. At least in this forum, there are no instructions pointing out where or how one would go about rewriting timing files. No doubt I saw that big-ass pink warning box... loud and clear. And I clearly had no idea how one would accomplish such a thing anyhow.
 
You must log in or register to reply here.