R-JTAG Falcon won't boot

[gavin_darkglide]

yes the points under the heat sync. but then you will have to run wires to the r-jtag board.

 

[chase]

hey.. link below shows you which post out point goes where on the r-jtag chip.. you'll just have to use the equivalent one on the top side of the 360 mobo

http://team-xecuter.com/forums/showthread.php?t=136258

 

[tigres13]

Okay so I soldered wires to the top points that are under the CPU in replacement of the ones that were messed up on the POST_QSB. I tried the different dips again (470, Aud_Clamp on, default voltage and Dip 7 on) and this is what I am getting now.

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 60 - INIT_KERNEL 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
Post 13 - FSB_CONFIG_TX_STATE 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
Post 18 - FETCH_CONTENTS 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 40 - Entrypoint of CD reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
Post 13 - FSB_CONFIG_TX_STATE 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1B - RC4_DECRYPT 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post 60 - INIT_KERNEL 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Post 20 - CB entry point reached 
Most Fails(cumulative): 0x20
Shutdown

I was also wondering if this spot is supposed to have numbers in it? I have seen pictures of other people's J-Runners and they have these blanks filled in.

Thank you guys for helping me to figure this out. I really appreciate your patience!

 

[Antalpromille]

Your post out doesnt look right, make sure its installed the correct way.

 

[gavin_darkglide]

Post out looks better, but some of the post codes are out of sequence. it looks like you have a wire crossed, or bridged. Write back stock and post the post output from a retail boot. also add pictures of post out repair/alt points.

 

[chase]

please post new detailed pictures of your post out repair, r-jtag board and all soldering

 

[Martin C]

Post out looks better, but some of the post codes are out of sequence. it looks like you have a wire crossed, or bridged. Write back stock and post the post output from a retail boot. also add pictures of post out repair/alt points.

POST OUT does NOT look better.

OP - we're getting beyond the point of being able to help. If you can't solder, since it's a major portion of the install you're just going to fail to boot anything. You'll even get to the point where no-one will be able to sort it for you.

 

[gavin_darkglide]

sorry i was looking at a post out log in a different thread. Martin is right. MY BAD. anyway if i were you i would take martins advice, but if you are anything like me you want the satisfaction of doing it yourself. In my experience this is a bad idea. The first console i ever did i burnt the demon points on, which after about 6 hours i managed to get the alternate points installed to realize that i ended up burning a couple of pads on my on board nand, then i had to do trace repairs. Then i installed the sonus and screwed up the eject point. But even with all the problems i had with my first install, i managed to repair all of the damage and get a dual booting RGH2 system.(Have updated to R-Jtag since then.) Though I screwed up my first install to an extreme magnitude, i have done over 10 systems since then and out of 10 i only had problems with 2(both falcons, 1 wouldnt get past A0 no matter what dips were used, and i went over the soldering for 2 days, the other worked, but in an attempt to fix the 0020 error on stock nand that people are experiencing with there R-Jtag falcons it over heated and and got RROD). So dont feel discoraged every installer makes mistakes.

Please post new pictures, also if you didnt remove post ribbon and do all post out with a wire install. then repost post out.

 

[tigres13]

Here are pictures of the repair work on the POST_QSB.

Unfortunately I managed to snag the CPU_RST point while flipping the system over and tore that point right off the board. I have no luck but am very determined to get this to work despite all of these set backs. Here is a picture of the pad (?) still attached to the blue wire. From what I can tell, there looks like there is a trace going to the piece directly to the left of the now missing piece. I am thinking that I can just glue the point back down, expose the trace and solder it back together. Or could I just leave it be and use the alternate point instead? I haven't tried hooking the system up again since I realized that this point came off because I don't want to do any more damage.

 

[chase]

I thought you were gonna go from top post out points directly to the r-jtag chip ? whats the point of going from top of the board to the bottom, only for it to go back to the top(r-jtag chip) via ribbon cable ?

what type of wire are you using.. you don't have any 30awg ? also, the top post out soldering looks half-ass .. its just a few blobs..

I would send it to a pro.. if you continue at this rate, the 360 will die permanently

 

[Martin C]

If you didn't want to do any more damage, you should have stopped already.

I strongly advise finding someone to finish/fix this for you.

 

[tigres13]

How do I reattach the CPU_RST point?

 

[chase]

so you're not gonna send it out i guess.. you're very determined but it may not be a good thing in this case

use any of the points marked in the picture or you can use the top cpu_rst point shown in the guide.. the picture below is from a xenon board.. yours will not have the C7R112 capacitor .. good luck

 

[Martin C]

OP - if you're not going to take advice given, why are you still asking questions?