JTAG Some E79 help after Xell flash on Falcon please

[mcornbill]

Hi Guys

Ok so I got a Falcon mobo back from Karl the other day. It's booting up fine, was on the 7363 dash, cb exploitable. Updated to 7371, dumped three good nands, jtagged her up with diode method to aud_clamp and dvd_tray points. Powers up to E79 after Xell flash. Flash back to stock nand and powers up fine.

Checked all solder points for continuity and they are good. Checked J2D2.1 and J2D2.2 points and no reading on multimeter (stays on 1). Changed diodes and tried again, still no reading from J2D2.1 and J2D2.2 points.

Does this mean my J2D2.1 and J2D2.2 points are shot? If so then should I try these alternative J2 points show here:

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

Cheers
Mark

Edit: The DVD drive is not plugged in, haven't got one for this console. That wouldn't cause an issue would it as I'm soldering to the DVD_tray point? I will plug one in to try in the interim.

 

[srt4fun]

Here's a thread that's basically same problem as yours. http://team-xecuter.com/forums/showthread.php?t=71431&highlight=j2d2

Also, remember to select the Aud_clamp & DVD Tray option when building your FB image.

Hope that helps!

 

[Martin C]

How are you checking J2D2.1 and J2D2.2?

Turn off and unplug the console.

Put your meter on Ohms (max 2-10K should be fine).

Put the black probe on a ground point (copper collar on the board is fine).
Put the red probe on the J2D2.1 hole, not the diode etc.
Do the same with J2D2.2.

 

[mcornbill]

Hi Martin

I'm doing exactly that, red probe at pin header points, but putting my black probe onto the video port metal chassis at the rear of the motherboard.

 

[mcornbill]

Martin, here's my readouts, if they are of any help in diagnosing, from probing the various points with the multimeter on the diode setting, black probe to ground, console powered off (do these values look right).:

 

[srt4fun]

The readings for both J2D2.1 and J2D2.2 (at the header) should be 1.5k ohms for Falcons. You could try an alternate point for J2D2.2. I would suggest a reflow but, If it's been recently reflowed then I don't know.

You could also verify the connectivity of the trace for J2D2.2.
*Do this at your own risk and only if you're comfortable with exposing the copper trace.*

In the link you provided earlier, you're going to use the top pic posted by Xmods. Follow the white trace. At the end near the GPU, expose the copper of the round pad (I use an exacto knife and lightly scratch until I see shiny copper). Set your multimeter on ohms and probe from nand side of R2E4 to the pad near the GPU. You should get a reading of *0ohms. Anything above indicates a damaged trace.

Edit: *0ohms is slightly wrong....should be under 1ohm (due to the multimeter's own resistance and accuracy)

 

[Martin C]

Martin, here's my readouts, if they are of any help in diagnosing, from probing the various points with the multimeter on the diode setting, black probe to ground, console powered off (do these values look right).:

Link To Image

I'm guessing you meant ohms, not diode setting? The AUD_CLAMP/TRAY_OPEN points are not important, so ignore those.

J2D2.2 should be 1.5k as previously mentioned and it's not. If it's been reflowed then it's the GPU itself. I've been down this road with another console and can confirm once a new GPU was fitted all was well.

You're probably going to ask why it works ok with the normal NAND flashed to it? Well, it's because that part of the GPU is used for debug and we don't use it retail consoles.

Something to consider - Falcons Glitch REALLY well and whilst a standard JTAG here might be problematic, you may want to consider RGH instead. It would save you the trouble of getting the GPU replaced.

 

[mcornbill]

Hi Guys

srt4fun - Both J2D2.1 and J2D2.2 (at the header) show 1.56k ohms when the console is powered off. When the console is powered up both of these points go to 1.

I am comfortable working with traces, have the necessary fine guage wire for trace repair, so I will look at that as a last resort due to Martin's comments of possible GPU issue.

Martin C - Those values I'm giving you are from my multimeter on the diode setting. It is a cheap nasty meter, not a nice Fluke or anything like that! As I said to srt4fun, the points are showing 1.56k ohms resistance, but when powered up they both go to 1.

So are the points acting as they should now?

Cheers both

 

[keil423]

You did remember to change the SMC points on Jtag tool when you created your freeboot image correct?

 

[Martin C]

Yes, if the points are both at 1.5k then they should be fine.

If you're getting E79 still, check all wired points and ensure that if the above is the installation, you're choosing AUD_CLAMP and DVD_TRAY before writing Xellous.

 

[srt4fun]

If you're getting good readings from the header there's no need to check the trace for continuity. It's most likely either the wiring or how you're building the image.

 

[mcornbill]

keil423 - I am indeed selecting AUD_CLAMP & DVD_TRAY in Coolshrimps Jtag Tool.

Martin C - This is where I've never been entirely sure why there is a 'Write Xell' and a 'Write Xellous' on the Jtag Tool. I will give myself a load of face palms now :facepalm::facepalm::facepalm::facepalm:

So my normal routine, and this worked fine for the last Falcon jtag I did, is to just write Xell like I've been doing for Xenons. I did connect the console up last night and wrote Xellous as well to see if it would solve the problem, it didn't. However I didn't flash back to working nand beforehand, just wrote over the top of Xell.

I'm hoping now that you guys are going to point out a blindingly obvious mistake........:rolleyes2:

Cheers
Mark

 

[Martin C]

Xellous is more functional, but they both equate to the same. I use Xellous as I can hook the console up to my network and get CPU key that way.

Double check you wiring points and make sure you've not managed to lift the pad for AUD_CLAMP for example.

 

[keil423]

I'm hoping now that you guys are going to point out a blindingly obvious mistake........:rolleyes2:

What did you forget to change Jtag tool to Falcon or something? You useing HDMI cable maybe?

Seems like you may have figured it out if so what was up?

 

[mcornbill]

What did you forget to change Jtag tool to Falcon or something? You useing HDMI cable maybe?

Seems like you may have figured it out if so what was up?

No mate, I was assuming I had to write Xellous because of Martin's comments and thought that was going to be the issue, I was pre-empting a face palming basically! But it turns out that's not the case.

One question though, can you have Xell and Xellous installed alongside each other, or is it one or the other?

I'm going to give it the once over later tonight and re-try some fresh nand builds.

Cheers everyone.

 

[Martin C]

ok - make sure that your diodes are facing the right way - obvious I know.

Also, swap out the direct bridge between J2D2.4 - J2D2.7 and put a 330Ohm resistor there instead.