JTAG Falcon Jtag e79

[Xexea]

TX Product(s) used: JR Programmer
Console Type: Falcon
NAND size: 16.5 MB
Dashboard version: 1688
CB version:
Screenshot of NAND details from J-Runner: Down Below.
J-Runner log: isn't a problem with the nands and what not.
updflash.bin log (if applicable):
Images of close-up soldering to motherboard: Down Below
Description of problem: Down Below

Was the console working before you started: Yes



Nands are the same : ===================================================
Monday, February 17, 2014 1:49:01 AM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Downloaded *J-Runner_UserGuide.pdf
Finished Checking Files
Initializing nanddump1.bin..
Falcon/Opus
Comparing...
Jtag Selected
Nand Initialization Finished
Nands are the same






So, I am having a bit of a problem. I have a Falcon that was on a pre-nxe dash, so I decided to Jtag it. I read the nand, created/wrote the ECC to the console, and installed the actually jtag wiring and diodes. I turn on the console to try and get XeLL to come up to grab my CPU Key, and I get e79 error. So I wait for around 30 minutes and try booting it up again. Still e79. So then I try and boot it numerous times (Thinking maybe it will boot eventually), and still e79. So then I Flashed the OG nand back to the console, and it works fine. Wrote the ECC back to the console, and installed the jtag wiring, and boom e79. I bought this Falcon off a friend, and the DB1F1 Point is a bit burned, so I Used the bottom point (FT1U2). I also tried the point right beside (FT2R2). Nothing worked. Any help would be well appreciated. I also just ordered some 10K 1/4Watt resistors and some 2N3904 Transistors to AUD_Clamp it. I would really like to fix this problem so I don't have to AUD_Clamp it, but if I have to then I will. Thank you for asnwering. PICS BELOW.



I know the soldering looks a bit messy, but that is because I am dead tired, from messing with this console.


http://gyazo.com/3a0bfa57283f2090d64f79898c29352a
http://gyazo.com/627a13ee84422e59c6f3de776cb5dc13
http://gyazo.com/cb85dc499bdd69ba99b87d439fc7f899

 

[gavin_darkglide]

Check the values of tms/tdi with a multimeter, I think they should both be around 1.5kohms(dont quote me, I could be wrong), if not, then the GPU could be faulty, or need reballed.

 

[Xexea]

Check the values of tms/tdi with a multimeter, I think they should both be around 1.5kohms(dont quote me, I could be wrong), if not, then the GPU could be faulty, or need reballed.

Did you not read the post at all?? I said it works PERFECT when I reflash the OG nand to the console. Also I did that with the multimeter...

 

[gavin_darkglide]

Those points arent used by the console, unless it is jtaged, so just because your OG nand works, doesnt mean it might not need to be reballed, or there isnt an issue with the gpu. Since it works normally with og nand, I think we can rule out the southbridge as the culprit.

 

[Xexea]

Those points arent used by the console, unless it is jtaged, so just because your OG nand works, doesnt mean it might not need to be reballed, or there isnt an issue with the gpu. Since it works normally with og nand, I think we can rule out the southbridge as the culprit.

From what I've heard on the internet, people are saying this is a common problem with all HDMI consoles. People are all over forums saying that I just need to do the AUD_Clamp. I guess I will just have to try the AUD_Clamp when the Resistors and Transistors get here, but if anyone knows a couple troubleshooting steps to take, then that would be awesome.


I would also like to add that this console is brand new. Just took it out the OG Sealed Box it originally came in. Plus, it has literally no dust at all.

 

[Martin C]

From what I've heard on the internet, people are saying this is a common problem with all HDMI consoles. People are all over forums saying that I just need to do the AUD_Clamp. I guess I will just have to try the AUD_Clamp when the Resistors and Transistors get here, but if anyone knows a couple troubleshooting steps to take, then that would be awesome.


I would also like to add that this console is brand new. Just took it out the OG Sealed Box it originally came in. Plus, it has literally no dust at all.

Your post is incomplete. Make sure you fill out the template if you want help. There are more images we need to see plus what steps you did in J-Runner.

gavin_darkglide was spot on about checking TMS and TDI (J2D2.1 and J2D2.2) against GND. Yes, even brand new consoles can have these points reading incorrectly. If you want help on something you know nothing about, it's extremely rude to dismiss suggestions like this.

AUD_CLAMP can be used with diodes too - no idea who told you otherwise.

 

[Xexea]

Mind linking me to a post of a Jtag AUD_Clamp install using Diodes? I looked on Se7ensins and saw where someone used Transistors and resistors. Also where is the Forum to fill out???

 

[Martin C]

It's right there in the sticky section of this forum:

[h=3]TEMPLATE: RGH/JTAG help[/h]

 

[Xexea]

Just put up the template, can you link me to a post of the AUD_Clamp Diode method? Thanks Martin!

 

[chronixx]

Just put up the template, can you link me to a post of the AUD_Clamp Diode method? Thanks Martin!

thanks but first post the pictures of installation including the r-jtag chip, rater readings. e79 can also be caused by the poor soldering of the jtag qsb. so what is it going to be? are going to fill out all the template?

 

[Xexea]

It's a JTAG not a R-jtag.. Also im not using Jtag QSBs.

 

[chase]

You can use diodes but I would stick to the transistor method as it is better with E79

 

[Xexea]

You can use diodes but I would stick to the transistor method as it is better with E79

Can you give me a link to the diode AUD_Clamp method? It would be gladly appreciated.

 

[Martin C]

You can use diodes but I would stick to the transistor method as it is better with E79

No it doesn't - it's the SAME method.

OP - we need full images of all soldering to ensure you have everything connected properly. There's also no mention in your template of what you wrote to the console. Start again - write the original NAND back, then create and write xell, then try it. If it's still not working, post the J-Runner output of the above.

 

[chase]

No it doesn't - it's the SAME method.

So why is there a transistor method when there was the diode method before that?

Also, the transistor method has fixed a few diode jtag installs for me in the past so im just saying from what i've experienced

 

[Martin C]

So why is there a transistor method when there was the diode method before that?

Also, the transistor method has fixed a few diode jtag installs for me in the past so im just saying from what i've experienced

The diode method was thought to be unsafe as TMS/TDI were high after boot. The transistor method was released to combat this.

I've never had to use the transistor in place of diodes. Ever.

If a console boots on transistor but didn't on diodes, then it was either a sh*tty install or faulty diode(s).

 

[Xexea]

No it doesn't - it's the SAME method.

OP - we need full images of all soldering to ensure you have everything connected properly. There's also no mention in your template of what you wrote to the console. Start again - write the original NAND back, then create and write xell, then try it. If it's still not working, post the J-Runner output of the above.

Doing this now. Getting the reading the nand now.

 

[Xexea]

Flashed the OG nand back to the console, reread the nand, created Xell, and wrote Xell to the console. Still e79 error. I have done plenty of Jtags/RGHs in the past, but this one just seems to give me fits. Also, I can going to try using different diodes.


===================================================

Monday, February 17, 2014 4:15:30 AM


J-Runner v0.3 Beta (4) Started




WARNING! - Your selected working directory already contains files!
You can view these files by using 'Show Working Folder' Button




Checking Files
Finished Checking Files
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 00
Wrong Version.
Falcon Manually Selected
Version: 00
Wrong Version.
Version: 00
Wrong Version.
Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 5770
Falcon/Opus
Reading Nand to C:\Users\Blake\Downloads\output\nanddump1.bin
Reading Nand
Done!
in 3:25 min:sec


Initializing nanddump1.bin..
Reading Nand to C:\Users\Blake\Downloads\output\nanddump2.bin
Falcon/Opus
Jtag Selected
Reading Nand
Nand Initialization Finished
Done!
in 3:29 min:sec


Comparing...
Nands are the same
XeLL file created Successfully falcon.bin
Version: 10
Flash Config: 0x00000000
Can not Continue
Version: 10
Flash Config: 0x01198010
Writing Nand
falcon.bin
Done!
in 0:18 min:sec

 

[Martin C]

Test your diodes first. Also report back on what values you get on TMS/TDI.

TBH you should be using AUD_CLAMP anyway. You only need to move the RoL wire to the leg on Q2N1 and build/write xell with aud_clamp selected.

 

[Xexea]

Ok, so I changed the wiring, because I seen someone who had a similar problem here : http://team-xecuter.com/forums/showthread.php?t=66754

I used his wiring. Also, I still have the orange wire on the jumper on the top of the board. Also, I Created/Wrote Xell with AUD_CLAMP checked. I would also like to say that the yellow wire has a diode on the end of it, the black line facing the DVD drive point. Also, I soldered the wire that is suppose to be on the ROL to the AUD_CLAMP. I think the only thing left I have to do is try different diodes. Also Martin, may I ask what a TMS/TDI is? I may know what it is, just don't know the ''slang'' for it.


Pics:


http://gyazo.com/c784ef5b1b715c36e2f234a125ed5ef2
http://gyazo.com/cd9b8fc47597911a45544fc7da631581
http://gyazo.com/cebe6775c76cbf3ba3100766a9eabc8a