Can't Get To Xell :(

[DivinityCycle]

I'm working on getting the RGH going on a Falcon system.
The following has gone according to plan:
-I updated my NAND-X to software version 3 using my CK3i and Flash Magic
-I wrote Falcon.xsvf to my CoolRunner chip via my NAND-X and nandpro
-I got a pair of matching NAND dumps using JTAG Tool
-I generated an ecc file from my verified-good NAND dump using 360 MultiBuilder 0.3
-I flashed the ECC file to my 360 via JTAG Tool, no errors encountered
-My CoolRunner is jumpered correctly (PHAT mode and Norm as opposed to programming mode)
-I still have my JTAG QSB hooked up but have it jumpered to OFF
-I triple-checked my solder points.
-I have tried both Composite and VGA outputs, as I have read Xell will not do component or HDMI.

At this point my system should be able to boot to Xell and give up the CPU key.

I forgot to mention, I verified its a Falcon in the following way:
-With nothing else attached, no memory devices appear in System > Memory
-The console-side power connection has the six main pins with no middle piece.

However, all the system does is reboot endlessly with a blinking green center light on the ROL. The CoolRunner's main red LED is on constantly whenever the system is plugged into AC power, and I get a brief green LED flash on the CoolRunner every time the system reboots.

The system currently has no HDD or DVD drive attached and no network cable inserted.

Any advice, guys?

 

[seanr28]

try creating the ecc with python, all the automated ecc fle generation system appear to cause some issues with certain types of 360.

Try that and let me know how you get on.

 

[360xobox]

Did you get any warning messages from using 360 MultiBuilder 0.3 when generating your ecc ?

 

[cypher21]

try the troubleshoot solution mentioned here: http://team-xecuter.com/forums/showthread.php?t=74857

 

[Mickey3177]

The red light should always be on and the green light flash is the cool runner glitching, is the fan acting strange?. I couldn't get my falcon to come either in till I used Jtag tools 4.23 and created the .ecc Xell file, and then it came right up, I know some people said that Jtag tools was buggy but it's worked the best for me so far.

 

[Mickey3177]

Can you put up some pictures of your soldering points, they might look good but you could still have cross bridging somewhere. Also use a meter and check for continuity/connection and cross bridging

 

[Akilles]

Use 360 multibuilder v0.2 not v0.3

 

[Martin C]

Can you confirm your CB value in 360 Flash dump tool?

 

[Chura]

-I have tried both Composite and VGA outputs, as I have read Xell will not do component or HDMI.

Sorry for jumping in, but is that so ?
HDMI cant be used ? can someone clarify or point me to info ?

 

[aclark20]

Sorry for jumping in, but is that so ?
HDMI cant be used ? can someone clarify or point me to info ?

HDMI + Xell Worked on my Falcon.

 

[Martin C]

Xell reloaded supports AV and HDMI.

Confirmation on your CB version please?

 

[DivinityCycle]

The plot thickens! It looks like this system is actually a Jasper 16MB model, as opposed to a Falcon.

I updated my CoolRunner using NandPRO 3 via commandline:

nandpro xsvf: Jasper.xsvf

Output:

D:\Desktop\NANDPro3>nandpro xsvf: Jasper.xsvf
NandPro v3.0a by Tiros

Looking for usb interface device
Compression InSize:0x593E OutSize:0x27F0
Arm Version:0003
Sending compressed data:0x27F0 bytes
Executing File
Successfully executed file

still same symptoms

I was able to locate 360 Flash Dump Tool v0.97

Running that same NAND dump through 360 Multi Builder 0.2 gets this output:

 * found flash image, unpacking...
ECC'ed - will unecc.
Found 2BL (build 6750) at 00008000
Found 4BL (build 8453) at 00011a40
Found 5BL (build 1888) at 000171c0
 * found decrypted CD
 * found (hopefully) decrypted CB
 * found XeLL binary, must be linked to 1c000000
 * we found the following parts:
SMC: 2.3
CB_A: 6750
CB_B: missing
CD (image): 8453
CD (decrypted): 8453
 * checking for proper 1BL key... ok
 * checking if all files decrypted properly... ok
 * checking required versions... ok
 * this image will be valid *only* for: jasper
 * patching SMC...
CRC32: 5b3aed00
patchset "Jasper, version 2.3" matches, 1 patch(es)
 * zero-pairing...
 * constructing new image...
 * base size: 70000
 * No separate recovery Xell available!
 * Flash Layout:
0x00000000..0x000001ff (0x00000200 bytes) Header
0x00000200..0x00000fff (0x00000e00 bytes) Padding
0x00001000..0x00003fff (0x00003000 bytes) SMC
0x00004000..0x00007fff (0x00004000 bytes) Keyvault
0x00008000..0x00011a3f (0x00009a40 bytes) CB_A 6750
0x00011a40..0x00017a3f (0x00006000 bytes) CD 8453
0x00017a40..0x000bffff (0x000a85c0 bytes) Padding
0x000c0000..0x000fffff (0x00040000 bytes) Xell (backup)
0x00100000..0x0013ffff (0x00040000 bytes) Xell (main)
 * Encoding ECC, please wait ...
------------- Written to image_00000000.ecc
Press any key to continue . . .

I gotta run but I'll post solder point pics ASAP

 

[Martin C]

What do you mean, the plot thickens???

The FIRST thing you should have done after dumping the NAND is open it in 360 Flash Dump Tool. It would have told you two vital things:

1. The motherboard revision
2. (more importantly) Your CB value as not all Falcons and Jaspers can be done.

Schoolboy error of EPIC proportions.

 

[DivinityCycle]

it gets even dumber, m8. I somehow managed to miss the instruction "boot up using the eject button to get Xell".
Tried that, worked first time!
~facedesk~

I am looking at the HTTP interface where I have both my DVD key and CPU key! sfdlkjshdflkjfsdhsdflkjhdfslkjdsflkjj!!!!

Thanks to all of you for your quick and knowledgeable assistance!

 

[Martin C]

If you've flashed the ecc image, you shouldn't need to boot with eject as Xell is resident in the normal boot address.

Glad you got it working though!

 

[blastagator]

My Falcon ONLY outputted to HDMI (for whatever reason) so try that and see if it is working. A friend of mine had the same problem.

 

[Martin C]

This is why I don't even bother with hooking it up to a TV!