R-JTAG R-JTAG fails to boot into XELL (0x21 RATER error) on Jasper & Zephyr

[moddified360]

Hello all, I do hope this is the appropriate area for this thread. (Noob to TX forums / 5 years experience with console modding / fixing)

I recently purchased an R-JTAG 1.1 starter kit from ModChip Central and installed it to a Jasper (16MB) on dash 16202 using AUD-Clamp. I flashed over Xellous however the unit would not boot up. Although, the debugging light would appear consistently as all wiring is correct. I kept the dips at the default 7 & 8. (NOT using v3 QSB, all wired as shown in picture)

-After 2 hours of different variations of the CPU RSt / add & removing AUD_Clamp, Dip settings and so on, I kept receiving a 0x21 error under Rater no matter what:
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
Post 20 - CB entry point reached
Most Fails(cumulative): 0x21

I now have moved on to re-installing the entire R-JTAG to a Zephyr (don't hate

) console which does NOT have an RROD history. Zephyr is also on dash 16202 with a CB of 4569. I have switched the dips from 4,5, & 7-8
(NO AUD_Clamp) method

(I worked with the Zephyr most so all pictures below are on the Zephyr install not Japser)

This is my log of flashing Xellous to the NAND via JRunner:

Version: 10
Flash Config: 0x01198010
01198010
Xenon, Zephyr, Opus, Falcon
CB Version: 4569
Zephyr
Reading Nand to D:\J-Runner\output\nanddump1.bin
Reading Nand
Error: 250 reading block 3A3
Done!
in 3:21 min:sec


Reading Nand to D:\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Zephyr
Jtag Selected
Nand Initialization Finished
Reading Nand
Error: 250 reading block 3A3
Done!
in 3:21 min:sec


Comparing...
Bad Block ID 03A3 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 03A3 [Offset: 0xF00600]
Bad Blocks Remapped
Bad Block ID 03A3 Found @ 0x03FF [Offset: 0x107BE00]
Block ID 03FF [Offset: 0x107BE00] remapped to Block ID 03A3 [Offset: 0xF00600]
Bad Blocks Remapped
Nands are the same
R-Jtag Selected
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully zephyr.bin
Version: 10
Flash Config: 0x01198010
Writing Nand
zephyr.bin
Done!
in 0:18 min:sec



I also keep getting the same issue as I did with the Jasper shown below with Rater:

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 10 - Payload/1BL started
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
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 20 - CB entry point reached
Post 30 - VERIFY_OFFSET_4BL_CD
Post 20 - CB entry point reached
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 70 - INIT_VIDEO_DRIVER
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Most Fails(cumulative): 0x21
Shutdown



Possible defective R-JTAG board? ...

Any help or suggestions would be greatly appreciated-

 

[Martin C]

Yes - if you soldered CPU_RST to the same point on both this and the Jasper, you've answered the question as to why it's not booting.

It's the wrong point.

 

[moddified360]

Re: R-JTAG fails to boot into XELL (0x21 RATER error) on Jasper & Zephyr

Thanks Martin, I didn't even notice I was off on the point. Although I think this just made it worse, as I know have a "Most Fails(cumulative): 0xA0" error.

If I use CPU_RST under the board, I'll get an almost instant 0110 RROD error.

Rater Log:

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 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
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 30 - VERIFY_OFFSET_4BL_CD
Post 70 - INIT_VIDEO_DRIVER
Post 10 - Payload/1BL started
Post 12 - FSB_CONFIG_RX_STATE
Post 20 - CB entry point reached
Post 70 - INIT_VIDEO_DRIVER
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 20 - CB entry point reached
Post 30 - VERIFY_OFFSET_4BL_CD
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 20 - CB entry point reached
Post 30 - VERIFY_OFFSET_4BL_CD
Post 10 - Payload/1BL started
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
Most Fails(cumulative): 0xA0
Shutdown


Thanks again.

- - - Updated - - -

CORRECTION: I get a 0010 error

 

[BL4K3Y]

Keep the CPU_RST wire soldered to R8C2.

Now it's time to experiment with different dip switch settings and voltage options as per the R-JTAG guide.

There are 18 combinations to try (6 dip switches with each voltage option - OPEN/1V2/1V8).

 

[moddified360]

Alright I'll give that a try- Thanks

 

[moddified360]

Alright guys, I followed up on all procedures on troubleshooting the DIP & voltage settings on the R-JTAG & keep getting 0x21 error now on three consoles. I tried installing the R-JTAG (same chip) on my personal Jasper (16MB) (latest 16547 dash) and no anvil.

Here is what I get in Rater: (See pictures for new install to this Jasper board)

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 20 - CB entry point reached
Post 28 - FETCH_CONTENTS_3BL_CC
Post 08
Post 20 - CB entry point reached
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 22 - INIT_SECENG
Post 1B - RC4_DECRYPT
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
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 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 13 - FSB_CONFIG_TX_STATE
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 1B - RC4_DECRYPT
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
Post 1A - RC4_INITIALIZE
Post 20 - CB entry point reached
Post 21 - INIT_SECOTP
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 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL


Here is my JRunner log:

Reading Nand to D:\J-Runner\output\nanddump2.bin
Initializing nanddump1.bin..
Jasper 16MB
Jtag Selected
Nand Initialization Finished
Reading Nand
Done!
in 3:21 min:sec


Comparing...
Nands are the same
Aud_Clamp Selected
R-Jtag Selected
Patching Jasper version 2.3 SMC at offset 0x12BA
XeLL file created Successfully jasper_hack_aud_clamp.bin
Version: 10
Flash Config: 0x00023010
Writing Nand
jasper_hack_aud_clamp.bin
Done!
in 0:18 min:sec

Is there a possibility that I received a "bad R-JTAG board" ? I mean come on, this is frustrating as hell. I just wish I knew the issue because I have never had this big of a problem with any other R_JTAG nor RGH... even some RGH2 console have been less problematic.

Thanks again.

-moddified360

 

[Martin C]

So you screw up in the installation initially by soldering to the wrong CPU_RST point. I'm seeing garbage in your POST output and yet your assumption is the R-JTAG is faulty?

You'll have to explain this logic to me.

Sort out POST. Check all points for resistance against GND and ensure you have no bad solder connections (or unwanted bridges).

 

[moddified360]

I did re-check all solder points and there are no bridges although I cleaned excess flux. I checked resistance & changed out the CPU_RST wire with kynar wire. End result on 2nd 16MB Jasper w/ AUD_Clamp: cumulative error 0x21.

..Here is my theory, you see, initially I installed the CPU_RST properly on the first SM Jasper as well as all other configurations. I tried just about every voltage / DIP / AUD_Clamp combo I could think of.

As I mentioned prior to "screwing up in the installation" on R8C2 on the Zephyr, I did have the CPU_RST wire attached to C7R112 however the infamous 0010 error would occur when using any other voltage than default. I don't consider this a "mess up" rather than a misplaced wire simply because I never work with Zephyrs on R-JTAG installs (Not worth it) and am not used to the point being so close to the cap. So my bad I guess..

Basically the logic here is that no matter what alteration I apply to this R-JTAG board, I wind up with the same 0x21 error on all three motherboards as I stated.

I suppose I could rip this R-JTAG off and yet again, and attempt an install on a Falcon Rev1 I have laying around.. but I'm telling you, this chip is faulty. Either that, some impedance issue, or possibly a faulty QSB

 

[Martin C]

Since cleaning up the install, post new pics and POST output. Just because you can't get it to boot, doesn't mean it's faulty.

Personally I would have installed back on the Jasper. We know some Zephyrs are troublesome, even with the new 1.1 code.

 

[moddified360]

Since your last post I have already removed the the R-JTAG and QSBs (The POST QSB was a **** to remove without ripping the traces / points) and will re-install soon to my personal SB Jasper or the Falcon I mentioned prior. Best luck is probably with the Jasper as you mentioned.

I don't want to waste you're time so I'll look over those tips and come back once I have fully re installed the R-JTAG to either board and post the outcome.

-moddified360