What determines glitch speed R-JTAG?

[jant90]

If I get a RROD (code 0010) with my Falcon R-JTAG a lot, is that:

• because glitching is going well and there is a problem with the JTAG part (e.g. the use of AUD_CLAMP or not, or the jumper at 470 or 330), or
• should I look at the R-JTAG chip (improve the glitch by messing with the DIP switch and CPU_RST wire)?

Please note, because of a defective JRP2 no way to use rater (see this thread why).

Also, can changing the actual JTAG part of the R-JTAG hack influence glitch speed? E.g. the use of AUD_CLAMP or not, or the jumper at 470 or 330? Or is glitch speed solely influenced by voltage, DIP setting, and CPU_RST wire and position?


Findings for my Falcon so far, with 1.2V I get no RROD's (as opposed to 50% RROD's with default voltage, and 100% RROD's with 1.8 voltage). Problem is glitching takes way longer with 1.2V and none of the DIP's seem to improve anything.

So therefore I'm wondering whether I should mess with CPU_RST and DIP's some more, or whether I should try AUD_CLAMP to solve the RROD and slow glitch combination.


Finally, I don't really read about anymore but I did in the past, does the AUD_CLAMP still disable 5.1 sound? As that's the reason I took the default JTAG and not the AUD_CLAMP.

 

[gazcoigne]

dude just buy a new JRPv2 and use the rater tool

its what its designed for to stop you wasting hours tweaking blind!!

the aud_clamp jtag method was also to improve boot times and solve error related issues but i dont think it has any bearing on the initial glitch to enable the JTAG exploit, so youll need the rater feature to see what your adjustments are doing

 

[Martin C]

The JTAG QSB settings have very little (IMHO nothing) to do with glitch times. By the time the boot process gets to the JTAG payload, the console will either boot or throw E79, depending on the wiring state. The R-JTAG is where it all happens, not forgetting that wiring placement also plays a big part.

 

[jant90]

The JTAG QSB settings have very little (IMHO nothing) to do with glitch times. By the time the boot process gets to the JTAG payload, the console will either boot or throw E79, depending on the wiring state. The R-JTAG is where it all happens, not forgetting that wiring placement also plays a big part.

Thanks, I'll try AUD_CLAMP then and see if using current settings that pop up a RROD / E79 after only a few glitches turn into boots.

Just my last question that's not answered though: I don't really read about anymore but I did in the past, does the AUD_CLAMP still disable 5.1 sound?

 

[Martin C]

What do you mean, still? I've never had an issue with AUD_CLAMP.

 

[jant90]

Yeah I never found sound confirmation, but it was something bugging in my head because some places on the internet mention that 5.1 over optical is disabled. But it seems like bullshit then. Will def use the AUD CLAMP as default from now on then.

 

[Ubergeek]

dude just buy a new JRPv2 and use the rater tool

its what its designed for to stop you wasting hours tweaking blind!!

the aud_clamp jtag method was also to improve boot times and solve error related issues but i dont think it has any bearing on the initial glitch to enable the JTAG exploit, so youll need the rater feature to see what your adjustments are doing

WHAT HE SAID !