R-JTAG Falcon Trouble

[kloneoner]

hey guys im having trouble running xell for the first time and getting my cpu key

the system power button blinks fast green and the rjtag board blinks green slowly

im sure i messed something up

phat falcon
16537 dash 5774 CB
aud clamp with the 1&3 connected on 470 and middle switch
1.2V 5&7bin ON


this is what im getting in rater

Post 8E - Panic - VPU_UNAVAILABLE
Post 10 - Payload/1BL started
Post 11 - FSB_CONFIG_PHY_CONTROL
Post 12 - FSB_CONFIG_RX_STATE
Post 13 - FSB_CONFIG_TX_STATE
Post 15 - FETCH_OFFSET
Post 18 - FETCH_CONTENTS
Post 19 - HMACSHA_COMPUTE
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



i want to try this but i dont know exactly where these points are


1. 1.5k resistance between J2D2.1 and GND.
2. 1.5k resistance between J2D2.2 and GND.
3. AUD_CLAMP wiring in place.
4. aud_clamp xell written.
5. continuity from J2D2.1 goes to the diode and then onto DB1F1.
6. J2D2.2 goes to the diode and onto Q2N1.
7. J2D2.4 bridged to J2D2.7.
8. NO continuity from J2D2.2 to J2D2.4.



sorry for the bad picture and the horrible soldering


thanks alot for your help guys i appreciate it

joe:facepalm:

 

[chronic1553]

First thing i'd try is retouch the points on the post qsb, and have you tried the default cpu_rst point?

 

[kloneoner]

yes i first tryed the point on the underside of the board

 

[chronic1553]

ok, retouch the points on the post qsb, make sure your using enough flux

 

[kloneoner]

touched them up. my phone is taking horrible pictures

they all look pretty good even though the pictures dont

 

[jsinger47]

ok, retouch the points on the post qsb, make sure your using enough flux

Why? His POST looks fine to me.

 

[kloneoner]

i appreciate everyones help its fine i tryed to touched up anything that didnt look really good to me im gonna try it again now

 

[kloneoner]

Phat Selected
Version: 10
Power Up
Waiting for POST to change
Post 83 - Panic - DATA_SEGMENT 
Post C3 - LZX_EXPAND_3 
Post 83 - Panic - DATA_SEGMENT 
Post C3 - LZX_EXPAND_3 
Post 83 - Panic - DATA_SEGMENT 
Post C3 - LZX_EXPAND_3 
Post D3 - FETCH_HEADER_CB_B 
Post DB - BRANCH_CB_B 
Post D9 - SHA_COMPUTE_CB_B 
Post DD 
Post 89 - Panic - FPU_UNAVAILABLE 
Post 8D - Panic - TRACE 
Post 89 - Panic - FPU_UNAVAILABLE 
Post 89 - Panic - FPU_UNAVAILABLE 
Post 89 - Panic - FPU_UNAVAILABLE 
Post 89 - Panic - FPU_UNAVAILABLE 
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 06 
Post FE 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post FE 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 10 - Payload/1BL started 
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 86 - Panic - EXTERNAL 
Post FE 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 8E - Panic - VPU_UNAVAILABLE 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 12 - FSB_CONFIG_RX_STATE 
Post 15 - FETCH_OFFSET 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
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 06 
Post 06 
Post 06 
Post 0E 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 10 - Payload/1BL started 
Post 11 - FSB_CONFIG_PHY_CONTROL 
Post 12 - FSB_CONFIG_RX_STATE 
Post 15 - FETCH_OFFSET 
Post 16 - FETCH_HEADER 
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 06 
Post 86 - Panic - EXTERNAL 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 8E - Panic - VPU_UNAVAILABLE 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 18 - FETCH_CONTENTS 
Post 19 - HMACSHA_COMPUTE 
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 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 8E - Panic - VPU_UNAVAILABLE 
Post 8E - Panic - VPU_UNAVAILABLE 
Post FE 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post FE 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 86 - Panic - EXTERNAL 
Post 06 
Post 06 
Post 10 - Payload/1BL started 
Post 19 - HMACSHA_COMPUTE 
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

well it deff got longer for each glitch...

 

[jsinger47]

Now your POST is messy and the QSB needs to be resoldered.

 

[kloneoner]

is this better or worse lol

 

[jsinger47]

It doesn't matter what your soldering looks like, it matters what POST you get.

In the case of a spelling error, I blame Tapatalk.

 

[kloneoner]

wait so im confused... what am i doing wrong?

 

[jsinger47]

Well, let's see your POST output. It was fine until you redid it the first time due to bad advice.

In the case of a spelling error, I blame Tapatalk.

 

[kloneoner]

 

[kloneoner]

i Read the Nand with the black connector marked TMS,TDI,TDO etc connected to the RJTAG board.

would that have messed things up?

can i read again?

 

[XMonsterModsX]

if your talking about the cr program cable then no do not plug it in

 

[Martin C]

i Read the Nand with the black connector marked TMS,TDI,TDO etc connected to the RJTAG board.

would that have messed things up?

can i read again?

No you don't - that doesn't read your NAND. That does stuff to your R-JTAG board via J-RP that you never need to do.

The problem here is another noob with more posts to his name than he should do started to throw random ideas at you. You're advised to read before posting and this is exactly why. You POST soldering *was* ok.

You have a choice of 6 DIPs and 3 power settings, making 18 configuration options in all. Did you try all 18 before asking for help?

 

[kloneoner]

if your talking about the cr program cable then no do not plug it in

yeah i was i had it plugged in when i read the nand and created the xell

 

[kloneoner]

No you don't - that doesn't read your NAND. That does stuff to your R-JTAG board via J-RP that you never need to do.

The problem here is another noob with more posts to his name than he should do started to throw random ideas at you. You're advised to read before posting and this is exactly why. You POST soldering *was* ok.

You have a choice of 6 DIPs and 3 power settings, making 18 configuration options in all. Did you try all 18 before asking for help?

thanks alot for your help

 

[kloneoner]

No you don't - that doesn't read your NAND. That does stuff to your R-JTAG board via J-RP that you never need to do.

The problem here is another noob with more posts to his name than he should do started to throw random ideas at you. You're advised to read before posting and this is exactly why. You POST soldering *was* ok.

You have a choice of 6 DIPs and 3 power settings, making 18 configuration options in all. Did you try all 18 before asking for help?

with your amazing help i was able to get it to boot but jrunner is not letting me add a dash


SOLVED