Zephyr No Green light but sounds like its glitching

Furiiious

Senior Member
Aug 9, 2013
105
0
TX Product(s) used: CR Rev C
Console Type:Zephyr
NAND size: 16/
Dashboard version: e.g 2.0.13**
CB version: 4578
Screenshot of NAND details from J-Runner:
(attach an image to your post)
J-Runner log:
Code:
===================================================

09 April 2014 17:08:44



J-Runner v0.3 Beta (4) Started







Checking Files

Finished Checking Files

Checking Console..

Version: 10

Flash Config: 0x00000000

Can not Continue

Can not continue

Checking Console..

Version: 10

Flash Config: 0x01198010

01198010

Xenon, Zephyr, Opus, Falcon

CB Version: 4578

Zephyr

Version: 10

Flash Config: 0x01198010

01198010

Xenon, Zephyr, Opus, Falcon

CB Version: 4578

Zephyr

Reading Nand to G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\output\nanddump1.bin

Reading Nand

Done!

in 3:41 min:sec



Reading Nand to G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\output\nanddump2.bin

Initializing nanddump1.bin..

Zephyr

RGH Selected

Nand Initialization Finished

Reading Nand

Done!

in 3:30 min:sec



Comparing...

Nands are the same

* unpacking flash image, ....

Spare Data found, will remove.

Removed

* found decrypted CD

* found XeLL binary, must be linked to 0x1c000000

 * we found the following parts: 

SMC: 1.10

CB_A: 4578

CB_B: missing

CD (image): 8453

CD (decrypted): 8453

 * this image will be valid *only* for: zephyr

 * patching SMC...

Patching Zephyr version 1.10 SMC at offset 0x1257

 * zero-pairing...

 * constructing new image...

 * encrypting CB...

 * encrypting CD...

 * base size: 6C000

 * No separate recovery Xell available!

 * Flash Layout:

0x0..0x1FF (0x200 bytes) Header

0x200..0xFFF (0xE00 bytes) Padding

0x1000..0x3FFF (0x3000 bytes) SMC

0x4000..0x7FFF (0x4000 bytes) Keyvault

0x8000..0xFF1F (0x7F20 bytes) CB_A 4578

0xFF20..0x15F1F (0x6000 bytes) CD 8453

0x15F20..0xBFFFF (0xAA0E0 bytes) Padding

0xC0000..0xFFFFF (0x40000 bytes) Xell (backup)

0x100000..0x13FFFF (0x40000 bytes) Xell (main)

 * Encoding ECC...Done!

------------- Written into output\image_00000000.ecc


Version: 10

Flash Config: 0x01198010

Writing Nand

image_00000000.ecc

Done!

in 0:18 min:sec



Programming Coolrunner

G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\common\xsvf\zephyr.xsvf

Version: 03

Flashing G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\common\xsvf\zephyr.xsvf to CoolRunner

Input Filesize: 593E

Output Filesize: 28C6

Done!


Programming Coolrunner

G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\common\xsvf\zephyr.xsvf

Version: 03

Flashing G:\Alll\RGH\J-Runner v02 Beta (288) Core Pack\J-Runner v02 Beta (288) Core Pack\common\xsvf\zephyr.xsvf to CoolRunner

Input Filesize: 593E

Output Filesize: 28C6

Done!
updflash.bin log (if applicable):
Image of Coolrunner:
20140409_180559.jpg

Images of close-up soldering to motherboard:
(attach images to your post)

Description of problem: Zephyr wont glitch no green light

Was the console working before you started: Yes

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

How long is the light on for each time:

(be aware that if you're trying to work on a faulty console, this is not a T-X product issue!!).
 

Attachments

Furiiious

Senior Member
Aug 9, 2013
105
0
I tried it when the resistor was on and no luck shall i still bridge with solder to see if that sorts it?
 

Furiiious

Senior Member
Aug 9, 2013
105
0
Nope i just prefer to use that as ive messed it up before as BL4KEY knows as i had to send the console to him for repair -.- so have used the alt ever since
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Nope i just prefer to use that as ive messed it up before as BL4KEY knows as i had to send the console to him for repair -.- so have used the alt ever since
Was that the Trinity STBY_CLK repair I did for you?

Leave the CPU_RST wire loose for the time being (hold it in mid-air) and see what happens.

If it is picking up any interference, you need to place it somewhere else.
 

Furiiious

Senior Member
Aug 9, 2013
105
0
Yes mate and ever since i haven't been near that point haha and what so hold it in mid air boot the console and see if it flashes green?


I always have the blue wire going over the fan shield surely it cant be that?
 

BL4K3Y

VIP Member
Jul 7, 2010
13,721
118
Colne, Lancashire (UK)
Yes mate and ever since i haven't been near that point haha and what so hold it in mid air boot the console and see if it flashes green?


I always have the blue wire going over the fan shield surely it cant be that?
Points A and D (CPU_PLL_BYPASS and CPU_RST) are very sensitive to interference.

It's worth doing what I suggested to see if the DBG LED blinks.

If either of those two wires pick up any interference, the console won't even attempt to glitch.
 

Furiiious

Senior Member
Aug 9, 2013
105
0
Flashed original nand boots instantly :(

Could the chip be dodgy never had one dodgy before but is it a possibility?
 

Menethoran

VIP Member
Sep 1, 2012
339
0
Reading, PA
can you show pics of point B to mobo (orange wire), and... i cant be sure, but looks like your PLL_BYPASS might be grounding on the resistor just south of the solder point... I would recommend redoing it (and clipping the exposed end to about half)
 

Furiiious

Senior Member
Aug 9, 2013
105
0
Im using the alternate for point B which is FT2R2 i have provided that picture mate, i thought that to and have redone this since :( any more ideas?

Will cut snip the wire and see if that does the trick :)
 
Last edited: