First R-JTAG - No Xell

[17481]

TX Product(s) used: Nand-X, JR-Programmer, R-JTAG
Console Type: Jasper
NAND size: 16
CB version: 6754
Screenshot of NAND details from J-Runner: https://www.dropbox.com/sh/vfnmyjkcgzp47se/0IqaYGKPGo
J-Runner log: https://www.dropbox.com/sh/vfnmyjkcgzp47se/0IqaYGKPGo
Image of Coolrunner: https://www.dropbox.com/sh/vfnmyjkcgzp47se/0IqaYGKPGo
Images of close-up soldering to motherboard: https://www.dropbox.com/sh/vfnmyjkcgzp47se/0IqaYGKPGo

Description of problem:
Typical R-JTAG install, read the install guild well but feel like i missed something stupid. Console Wont boot xell but DBG light shows the chip is fine (Normal Blinking Pattern). Tried with and without Aud_Clamp. Im not sure how long its suppose to take to boot into xell but i have waited 2-3 minutes each time iv tried it. Hopefully from images you can find something stupid i may have missed since this is first install. If you have any questions ask away! Thanks

Weird Behavior: On first try it glicthed and i got 3 quadrants that lit up green and stayed green (Chip was still glitching though). That has happened about 4 times total since my initial install. I have also gotten 2 red lights randomly on (Bottom Left and top right) (Diagnole from eachother) that blink, This has happend 2 times since initial install. There is also no secondary code so its not like a rrod.

Was the console working before you started: Yes

Do you get a green debug light appear on the RGH chip every 4-5 seconds: Yes

How long is the light on for each time: 1 Sec

DIPS: 5,7,8

 

[jsinger47]

POST output is very important here.

 

[17481]

POST output is very important here.

I can show you the rater stuff while its trying got boot xell. Added it to the Dropbox folder at "rater": https://www.dropbox.com/sh/vfnmyjkcgzp47se/0IqaYGKPGo

 

[jsinger47]

You haven't gotten a successful glitch at all in that POST log.

You have 6 dip settings to try, 3x voltage settings, 2x CPU_RST points. Have you tried them?

POST22 means the glitch was successful.

 

[17481]

You haven't gotten a successful glitch at all in that POST log.

You have 6 dip settings to try, 3x voltage settings, 2x CPU_RST points. Have you tried them?

POST22 means the glitch was successful.

I knew i havent gotten a succesfull glitch yet, thus no xell.
I have everything as Defualt/Standard, i would think the conosle would boot with "defualt" settings. The other stuff is there for fine tuning?...
Also do not want to tamper with dip settings, voltage settings, and CPU_RST settings when it could be something completely unrelated to them or something i missed.

I have tryed the alt CPU_RST and the green light stays solid and if i bump the wire it goes strobe. It seems very Unstable.

 

[17481]

Updated OP with the consoles strange behavior

 

[17481]

Have tested all possible CPU_RST no luck, Tested dips No luck

 

[Utmad]

You need to try the three voltage settings, done a jasper the other day that would only boot when the voltage was set to 1.2v and dip 2, the dip settings make a big difference between booting and not. It will not just boot on a default setting unless you are lucky.

 

[BL4K3Y]

Move CPU_RST to R8C2 (I cut it to fit and run it over the fan shroud) and set dip switches 4, 7 and 8 ON and test.

On a couple of recent R-JTAG installs, I have found that the 1V2 voltage option has helped, but you should treat the installs on a console-by-console basis because what works on one won't necessarily work on another.

 

[17481]

Move CPU_RST to R8C2 (I cut it to fit and run it over the fan shroud) and set dip switches 4, 7 and 8 ON and test.

On a couple of recent R-JTAG installs, I have found that the 1V2 voltage option has helped, but you should treat the installs on a console-by-console basis because what works on one won't necessarily work on another.

I tried that and utmad's method and nothing, I did the math and between the CPU_RST's, Voltage Settings, and DIPS there is 8 possible ways to do it per dip. So 1-6 dips times 8 equals 48 ways to do it between the CPU_RST's, Voltage Settings, and DIPS. Are you guys telling me i have to test all of them till i get one? Iv tested all the ones on the recommended section on the R-JTAG install guild and also your guess's nothing.

 

[Martin C]

Stick with topside CPU_RST point for now.

Then try DIPs 1-6 on standard voltage.

Then again on 1v2 and again on 1v8.

One of these should get you past 22 (on to 2E and beyond).

If not, you need to check continuity to all soldering.

 

[17481]

I get alot of panics while my 1.2 V is soldiered...
You can clearly see i unsoiled the 1.2 v at the end of the code and the panics go away.

Phat SelectedVersion: 10
Power Up
Waiting for POST to change
Post 04 
Post 05 
Post 25 - LOCATE_3BL_CC 
Post 35 - RC4_INITIALIZE_4BL_CD 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post 65 - INIT_STACKS 
Post 75 - INIT_DUMP_SYSTEM 
Post 65 - INIT_STACKS 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post F5 
Post 75 - INIT_DUMP_SYSTEM 
Post 65 - INIT_STACKS 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 60 - INIT_KERNEL 
Post 70 - INIT_VIDEO_DRIVER 
Post 50 - LOAD_UPDATE_1 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post 12 - FSB_CONFIG_RX_STATE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 60 - INIT_KERNEL 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post 40 - Entrypoint of CD reached 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post 15 - FETCH_OFFSET 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 50 - LOAD_UPDATE_1 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F4 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F2 - Panic - SHA_VERIFY_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 70 - INIT_VIDEO_DRIVER 
Post F0 - Panic - VERIFY_OFFSET_CB_B 
Post 18 - FETCH_CONTENTS 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 60 - INIT_KERNEL 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Post 80 
Post A0 - Panic - VERIFY_SECOTP_6 
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 14 - FSB_CONFIG_TX_CREDITS 
Post 15 - FETCH_OFFSET 
Post 16 - FETCH_HEADER 
Post 17 - VERIFY_HEADER 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
Post 1A - RC4_INITIALIZE 
Post 1B - RC4_DECRYPT 
Post 1C - SHA_COMPUTE 
Post 1D - SIG_VERIFY 
Post 1E - BRANCH 
Post 20 - CB entry point reached 
Post 21 - INIT_SECOTP 
Post A0 - Panic - VERIFY_SECOTP_6 
Most Fails(cumulative): 0xA0
Shutdown

 

[17481]

No luck, tried all the dips and both voltage settings. Is there a way to test the chip? I soldered everything and nothing. Did i do something wrong with the JTAG QSB?

 

[17481]

Length of my green E wire is too long?
Would wire positioning be a caused. Gone over soldiering multiple times, everything i self troubleshoot dosent fix it, it honestly feels like im missing something. Any pictures needed of anything?

 

[Martin C]

wire positioning could be a factor. Are you using the topside CPU_RST point?

 

[17481]

wire positioning could be a factor. Are you using the topside CPU_RST point?

Yes, i know when i use the topside it is very sensitive, if i move the wire sometimes it will make the dbg light stobe or go solid, its very unique.

Also, I just wrote original nand to console. Put JTAG QSB to off, and unsoildered the 5v point from the glitch chip and no boot/light/turn on. Normal? How would i see if original nand boots fine? Cant believe i didnt try og nand before as this may be the problem...

 

[Martin C]

With the original NAND written back, you only need to remove the POST ribbon to test the console. Don't desolder anything and don't feck around with switches on the JTAG QSB.

If it doesn't boot at all, then it should at least RRoD after a maxiumum of 30 secs.

 

[17481]

With the original NAND written back, you only need to remove the POST ribbon to test the console. Don't desolder anything and don't feck around with switches on the JTAG QSB.

If it doesn't boot at all, then it should at least RRoD after a maxiumum of 30 secs.

Ya, console wont turn on at all with OG nand written. Bad?
I put everything back to normal also

 

[Martin C]

Yes, very bad. As at the very least it should RRoD.

Are you sure you've written a retail NAND to it? Does it sound like it's constantly trying to boot (reset) ?

 

[17481]

Yes, very bad. As at the very least it should RRoD.

Are you sure you've written a retail NAND to it? Does it sound like it's constantly trying to boot (reset) ?

OG Nand : http://gyazo.com/4c39cff81c82c5b9c0e5e425e440212e
I cant hear anything, its like the console is completely dead/not getting power (It is because i can write nand), went over soldiering and its all clean. Nothing touching eachother for sure. I can repost pictures if it would help. Ideas?