RGH Falcon won't boot to xell

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
Hey everyone, I've been having some problems with my Falcon while trying to do the RGH hack. Originally, I was going to do it on my slim, but I had problems with my coolrunner not wanting to glitch, so I switched it over to my phat console (the falcon I'm having trouble with).

I originally tried using the QSBs for my nandx install, but the pads were torn from one of them, so I felt they were useless and opted for a different method of wiring it seen here (note: sorry my pics are such low quality. I've never had a reason to invest in a nice camera):



I used a jumper to connect my coolrunner's power and the blue and green cables for my nandx to the points to keep the install somewhat cleaner.

I know my NAND image is good because I've flashed it back and had it booting. I've been using Jtag Tool to create my .ecc images, as well as flashing my coolrunner board. My coolrunner has the constant red light, and will flash green like it's supposed to, but it just refuses to glitch?

I used the alt point for the STBY_CLK point since the point near the hana chip is so tiny (it made it impossible to place the fan shroud back on without dislodging the wire).

Any help is welcomed, and if and more information/pictures are required please let me know and I will do my best to accommodate you all.

Pics of my install:









(This one was a rush... don't point it out xD )
 

Statecowboy

BANNED
Feb 23, 2005
713
0
Midwest USA
Have you unplugged the power from the console when you programmed the coolrunner? A pic of your jumpers would be nice, it's a little blurry.

Also, I assume you re-flashed your coolrunner after reading your falcon nands?
 
Last edited:

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
The jumpers basically just act as a median for the coolrunner power and the nandx cables. I'll get a picture of it for you tomorrow.

And yes, I did reflash the board.

EDIT: I just remembered that I unplugged the wire for the coolrunner from the jumper when I flashed the board. So it wasn't receiving power at the time.
 
Last edited:

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
Aside from there being a history with your Coolrunner (not working on another console), CPU_PLL_BYPASS has too much exposed wire.

Is the debug light flashing every 4-5 secs?
 

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
The light does flash. How should I go about positioning/protecting the wire from interference?

EDIT: I'm also under the assumption that the failed attempt on my slim was just bad soldering.
 
Last edited:

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
Unfortunately I can't at this time (I don't have access to my computer right now). As soon as I do I'll post the log.
 

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
I had read that Jtag tool caused some problems with .eccs... I tried multi builder previously with no results. I'll give J-Runner a go and see what happens.
 

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
I just attempted using J-Runner to create my .ecc and flash it, but my console still didn't boot to xell...

Here is my J-Runner log for those interested:


===================================================
Thursday, April 05, 2012 11:03:48 AM



No Updates Found


Checking Files
Finished Checking Files
Initializing Nand..
Comparing...
Nands are the same
Getting info from ip...
Connection TimeOut
* found flash image, unpacking....
ECC'ed - will unecc.
UnECC'ed
* found decrypted CD
* found XeLL binary, must be linked to 0x1c000000
* we found the following parts:
SMC: 1.6
CB_A: 5771
CB_B: missing
CD (image): 8453
CD (decrypted): 8453
* this image will be valid *only* for: falcon
* patching SMC...
Patching Falcon version 1.6 SMC at offset 0x12A3
* zero-pairing...
* constructing new image...
* base size: 70000
* encrypting CB...
7B67DFF4AE33BEEDB39398E8D6CCDE44
* encrypting CD...
* No separate recovery Xell available!
* Flash Layout:
0x0..0x1FF (0x200 bytes) Header
0x200..0xFFF (0xE00 bytes) Padding
0x1000..0x3FFF (0x3000 bytes) SMC
0x4000..0x7FFF (0x4000 bytes) Keyvault
0x8000..0x1133F (0x9340 bytes) CB_A 5771
0x11340..0x1733F (0x6000 bytes) CD 8453
0x17340..0xBFFFF (0xA8CC0 bytes) Padding
0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)
0x100000..0x13FFFF (0x40000 bytes) Xell (main)
* Encoding ECC...

100%
------------- Written into output\image_00000000.ecc
Initializing Nand..
Arm Version: 3
Flash Config: 0x01198010 -- Here I wrote the original NAND back --
Writing Nand
Done!

Exited!

Arm Version: 3
Flash Config: 0x01198010 -- And here I wrote the .ecc image to the fresh NAND --
Writing Nand
Done!

Exited!
 
Last edited:

Goldensavage

VIP Member
Jul 26, 2009
3,332
0
Essex, UK
Just a quick question, i know you have the TX sticker over the chip, but where did you get your coolrunner?

Are you sure it is an official coolrunner and not a third party one. The writing looks crisp enough for an original, but with the sticker over the chip, it is hard to tell.
 

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
Just a quick question, i know you have the TX sticker over the chip, but where did you get your coolrunner?

Are you sure it is an official coolrunner and not a third party one. The writing looks crisp enough for an original, but with the sticker over the chip, it is hard to tell.
I bought it from Modchip Central along with my nandx.

Statecowboy said:
Have you bridged the onboard cap on top of the Coolrunner (for Phats) as recommended?
No. I didn't know there was a recommendation to do this. Could you point me to this information?
 

bloodhoundgang1

Junior Member
Dec 3, 2011
14
0
This was originally my first attempt at one, but I had to put it off a few months ago because my schedule's been crammed lately. I only just now had renewed interest in picking this back up.
 

Martin C

VIP Member
Jan 10, 2004
35,981
0
Scotland, UK
www.team-xecuter.com
In which case I would be tempted to find someone local to you who does them (if possible) and get them to have a look. It may help you isolate the cause. Little things like the rate of the debug light flashing, its duration lit etc might help. It may even be an issue on the coolrunner itself after previous attempts.

EDIT - can you get a closer image of CPU_PLL_BYPASS?