CORONA Corona V3 CR4 XL issue

T

tr4ckerz

VIP Member
Aug 20, 2010
497
33
I soldered everything as usual, made three identical dumps of NAND (no bad blocks), wrote ECC and got Xell within a minute. After writing a freeboot the console is not booting as it should.

It starts booting very occasionally and randomly like after every fifth or more tries after powering up. When it boots, it boots great like within 1-2 glitches. But usually it won't boot at all - the green debug LED just stops blinking (randomly after 1-3 glitches) and nothing, no boot and no video output. I have to power off the console and repeat the process several times until I get successful boot. Does not matter what DIP settings and postbit jumper I use.

Pic4.jpg Pic1.jpg Pic2.jpg Pic3.jpg Pic7.jpg Pic5.jpg Pic8.jpg Pic6.jpg Pic10.jpg Pic9.jpg

Remark: The yellow wire to FT3T10 is just temporary when I tried alternative CPU_RST (one end of the blue CPU_RST to C5R11 is unsoldered at this time).

J-RUNNER LOG:
Code: 
===================================================
J-Runner v0.3 Beta (7) Started

Checking Files
Finished Checking Files
Version: 03
Flash Config: 0x00043000
00043000
Corona
CB Version: 13182
Corona
Reading Nand to G:\%Private%\J-Runner v03 Beta (7)\output\nanddump1.bin
Reading Nand
Done!
in 2:03 min:sec

Reading Nand to G:\%Private%\J-Runner v03 Beta (7)\output\nanddump2.bin
Initializing nanddump1.bin..
Corona
Reading Nand
Glitch2 Selected
Nand Initialization Finished
Done!
in 2:02 min:sec

Reading Nand to G:\%Private%\J-Runner v03 Beta (7)\output\nanddump3.bin
Comparing...
Reading Nand
Nands are the same
Done!
in 2:02 min:sec

Comparing...
Nands are the same
CR4 Selected
ECC created
Version: 03
Flash Config: 0x00043000
Writing Nand
image_00000000.ecc
Done!
in 0:09 min:sec

Getting info from ip ********
LockDownValue is 7
Initializing nanddump1.bin..
CpuKey is Correct
Added Key to Database
Corona
Nand Initialization Finished
Moving All files from output folder to G:\%Private%\J-Runner v03 Beta (7)\************
Load Files Initiliazation Finished
17150
Started Creation of the 17150 xebuild image
KV Info saved to file
---------------------------------------------------------------
     xeBuild v1.14.693
---------------------------------------------------------------
base path changed to G:\Private\J-Runner v03 Beta (7)\xeBuild
---- { Image Build Mode } ----
building glitch2 image

---------------------------------------------------------------
G:\Private\J-Runner v03 Beta (7)\************\updflash.bin image built, info:
---------------------------------------------------------------
Kernel    : 2.0.17150.0
Console   : Corona
NAND size : 16MiB
Build     : Glitch (v2)
Xell      : power on console with console eject button
Serial    : ************
ConsoleId : 438990826571
MoboSerial: 7501237200823105
Mfg Date  : 03/06/2013
CPU Key   : *****************************
1BL Key   : *****************************
DVD Key   : *****************************
CF LDV    : 7
KV type   : type2 (hashed - unchecked, master key not available)
---------------------------------------------------------------
    xeBuild Finished. Have a nice day.
---------------------------------------------------------------
Saved to G:\%Private%\J-Runner v03 Beta (7)\************
Image is Ready
Initializing updflash.bin..
Corona
Nand Initialization Finished
Version: 03
Flash Config: 0x00043000
Writing Nand
updflash.bin
Done!
in 1:55 min:sec
POST LOG:
Code: 
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 0E - CB_B ENTRY REACHED 
Post 0F - GLITCH SUCCESSFUL 
[B]Shutdown[/B] [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
[B]Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE
[B]Shutdown [/B][COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
[B]Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
[B]Shutdown [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
[B]Shutdown [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 0E - CB_B ENTRY REACHED 
Post 0F - GLITCH SUCCESSFUL 
Post 10 - ...... 
Post 11 - ....... 
Post 12 - ........ 
Post 13 - ......... 
Post 15 - CONTINUING 
Post 16 - . 
Post 17 - .. 
Post 18 - ... 
Post 19 - .... 
Post 1A - ..... 
Post 1B - ...... 
Post 1D - ........ 
Post 1E - . 
Post 1F - .. 
Post 20 - ... 
Post 21 - .... 
Post 22 - . 
Post 23 - .. 
Post 24 - Entrypoint reached 
Post 25 - ... 
Post 26 - .... 
Post 27 - ..... 
Post 28 - ...... 
Post 29 - ....... 
Post 2A - ........ 
Post 2B - ......... 
Post 2C - ........... 
Post 2D - ............ 
Post 2E - LOAD XAM 
Post 2F - ............. 
Post 30 - .............. 
[B]Shutdown [COLOR=#008000][B](REMARK: SUCCESSFUL BOOT AFTER 5 TRIES)[/B][/COLOR][/B]

Things that I already tried with no change to behaviour of the console:

- soldering CPU_RST to alternative FT3T10
- soldering POST_OUT to PAD50 on postfix adapter
- different DIP settings with combination of different postbit jumper settings
- 22 and 47pF caps on CPU_RST
- repeated the process of building freeboot image and writting back to NAND (this time using 360 Simple NAND Flasher)
- replaced CR4 XL chip for another one

Everything with no change, I got successful boot very occasionaly, mostly the debug LED just stops blinking and no boot.

I don't know if that helps. but what I noticed is that I can hear a silent sound from power brick while console is glitching, in the same frequency as the debug LED is blinking (like every 5 seconds). During unsuccessful boot when the green debug LED stops blinking, the frequency of sound from power brick is like 5x faster (reminds me old good times with DGX when we needed to find a hot spot by changing lengths of wires where we had similar sound from fan after unsuccessful glitch pointing to halt of CPU or something like that).

Any ideas?
 
Last edited:
Orangeprofessor

Orangeprofessor

VIP Member
Oct 27, 2013
171
23
The Third Dimension
Try building your Xebuild image on an earlier dash (worked for me in some cases). Do you have a JR-programmer? If you do, what do the post logs look like? This also sounds like the the kinda of problem with phats where the cr4 glitches again before the console can hit the dash. I'm not sure how to slow it down on slims tho. Does xell still boot when you hit the eject key? Does it still boot stock?
 
Last edited:
Oggy

Oggy

Staff member
Troll Eating Dogs
Mar 1, 2010
3,346
128
Can you get a post log of it?
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
nice soldering mate , check your pin on the post fix , could be wrong but it looks slightly bent to the left
 
T

tr4ckerz

VIP Member
Aug 20, 2010
497
33
Thank you all for your replies. Apologies for late reply guys. I was away on IIHF Ice Hockey Championship.

Orangeprofessor said:
Try building your Xebuild image on an earlier dash (worked for me in some cases). Do you have a JR-programmer? If you do, what do the post logs look like? This also sounds like the the kinda of problem with phats where the cr4 glitches again before the console can hit the dash. I'm not sure how to slow it down on slims tho. Does xell still boot when you hit the eject key? Does it still boot stock?
Click to expand...
I just tried on DB 16767, same result. What worse, not even Xell is booting every time I press EJECT button. I also tried to write back the ECC with still the same result - sometimes it boots up but usually it stops like mentioned in the OP. Could it mean something specific?

I also have JR-P V2 so I will hook it up and post RATER result later today (I think I will also have to solder "K" point and R2C4 bridge to get RATER working).

I haven't tried yet to write back original NAND to make sure that retail is still working without issues. Should I also try this?

Oggy said:
Can you get a post log of it?
Click to expand...
Yes, as mentioned above, I will hook it up for RATER.

briggs01 said:
nice soldering mate , check your pin on the post fix , could be wrong but it looks slightly bent to the left
Click to expand...
Thanks mate. Rather than nice soldering I would want it working, you know ;)

I believe that it is just the angle from which it was acquired. Here is a closer picture. Is it worth to desolder the anchors and try to reposition the postfix adapter? Would it be working as described in the OP if the pin would have touched wrong ball or bridge two of them together under XCGPU?

Pic12.jpg


john mathews said:
if u have a jrp v2 then hook it up for rater , that will tell us alot
Click to expand...
Same as above, I will do it.

ablegepu said:
doubtful seeing as he is getting debug.

OP do you have another CR4XL you could try. Oh sorry you already have.
Click to expand...
Yes I tried two different pieces of CR4 XL with the same result as mentioned in the OP.

Dadko said:
What ram memory does this board has?
Click to expand...
Samsung memory.
 
B

briggs01

VIP Member
Feb 17, 2013
1,324
0
tr4ckerz said:
Thank you all for your replies. Apologies for late reply guys. I was away on IIHF Ice Hockey Championship.


I just tried on DB 16767, same result. What worse, not even Xell is booting every time I press EJECT button. I also tried to write back the ECC with still the same result - sometimes it boots up but usually it stops like mentioned in the OP. Could it mean something specific?

I also have JR-P V2 so I will hook it up and post RATER result later today (I think I will also have to solder "K" point and R2C4 bridge to get RATER working).

I haven't tried yet to write back original NAND to make sure that retail is still working without issues. Should I also try this?


Yes, as mentioned above, I will hook it up for RATER.


Thanks mate. Rather than nice soldering I would want it working, you know ;)

I believe that it is just the angle from which it was acquired. Here is a closer picture. Is it worth to desolder the anchors and try to reposition the postfix adapter? Would it be working as described in the OP if the pin would have touched wrong ball or bridge two of them together under XCGPU?

View attachment 32361



Same as above, I will do it.


Yes I tried two different pieces of CR4 XL with the same result as mentioned in the OP.


Samsung memory.
Click to expand...
i don't think you would get debug if it was wrong budy , it a long shot but you could try putting it in the cage and soldering the ground wire as per tut , also try it with the hd in etc
 
A

ablegepu

VIP Member
Jan 3, 2014
925
0
Alabama U.S
don't see any better suggestions so have you tried another power supply? Don't see where it would make a difference but if you got a spare you could rule out the possibility.
 
T

tr4ckerz

VIP Member
Aug 20, 2010
497
33
briggs01 said:
i don't think you would get debug if it was wrong budy , it a long shot but you could try putting it in the cage and soldering the ground wire as per tut , also try it with the hd in etc
Click to expand...
I already had it inside the cage with all the accessories (DVD, HDD, Wifi Adapter) connected with no change to behaviour of the console.

ablegepu said:
don't see any better suggestions so have you tried another power supply? Don't see where it would make a difference but if you got a spare you could rule out the possibility.
Click to expand...
I already tried different power supply but unfortunatelly it didn't help.

john mathews said:
I would try different spot on postfix adapter and solder the ground to where it suppose to be grounded at which I don't think that matter because a ground is a ground
Click to expand...
I already tried PAD50 on Postfix Adapter, didn't help.

I can try to solder GND somewhere else, but where did it go? I can't see that end of wire in the tutorial. Is it going to A/V connector shell?
 
A

ablegepu

VIP Member
Jan 3, 2014
925
0
Alabama U.S
yes it always has been the a/v housing. But I also use the closest header gnd when doing an install and I have never had a problem, I highly doubt gnd is the problem but I dont really have any better suggestions.
 
A

ablegepu

VIP Member
Jan 3, 2014
925
0
Alabama U.S
maybe you could try post monitoring to see if maybe someone can see what is causing it to stop or where it is stopping the glitch? I don't know much about post monitoring but seems like it could be a good diagnostic tool for the problem you are experiencing.

Sorry i noticed this was already suggested but still worth a try.
 
Last edited:
T

tr4ckerz

VIP Member
Aug 20, 2010
497
33
OK here is a POST log (a bit of pain to bridge R2C4 if you have NAND QSB V3 already fitted). Also added to the OP.

If someone could point out the problem I would really appreciate it because I spent tens of hours with this stubborn Corona.

Code: 
CR4 Selected
Version: 10
Power Up
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 0E - CB_B ENTRY REACHED 
Post 0F - GLITCH SUCCESSFUL 
[B]Shutdown[/B] [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
[B]Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE
[B]Shutdown [/B][COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
[B]Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
[B]Shutdown [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
[B]Shutdown [COLOR=#ff0000][B](REMARK: NO BOOT)[/B][/COLOR]
Power Up[/B]
Waiting for POST to change
Post 03 - ... 
Post 04 - BOOT SEQUENCE STARTING 
Post 05 - ... 
Post 06 - .... 
Post 07 - ..... 
Post 08 - ...... 
Post 09 - ....... 
Post 0A - ........ 
Post 0B - ......... 
Post 0C - .......... 
Post 0D - GLITCH CHECK COMMENCE 
Post 0E - CB_B ENTRY REACHED 
Post 0F - GLITCH SUCCESSFUL 
Post 10 - ...... 
Post 11 - ....... 
Post 12 - ........ 
Post 13 - ......... 
Post 15 - CONTINUING 
Post 16 - . 
Post 17 - .. 
Post 18 - ... 
Post 19 - .... 
Post 1A - ..... 
Post 1B - ...... 
Post 1D - ........ 
Post 1E - . 
Post 1F - .. 
Post 20 - ... 
Post 21 - .... 
Post 22 - . 
Post 23 - .. 
Post 24 - Entrypoint reached 
Post 25 - ... 
Post 26 - .... 
Post 27 - ..... 
Post 28 - ...... 
Post 29 - ....... 
Post 2A - ........ 
Post 2B - ......... 
Post 2C - ........... 
Post 2D - ............ 
Post 2E - LOAD XAM 
Post 2F - ............. 
Post 30 - .............. 
[B]Shutdown [COLOR=#008000][B](REMARK: SUCCESSFUL BOOT AFTER 5 TRIES)[/B][/COLOR][/B]
 
john mathews

john mathews

VIP Member
Jan 3, 2014
2,551
88
peoria illinois
I hate to say this but its coming down to your setup / I did a v3 last week boot from instant to 2 cycle and everything is default and no caps and I know every console is different but slims are the easyiest to glitch:cool2:/ u can try another program to write your glitch image but jrunner I never had any issues, I wish u the best sir(clearly soldering isn't your issue) great job by the way
 
Last edited:
S

stucknvegas

VIP Member
Oct 25, 2012
656
0
Cypress CA. USA
I have had a couple of Coronas stop the debug light during the glitch cycle !! But not as often as that.
Maybe 1-out of 10 ..at the most ..I always include a ROL indicate mod on those consoles that just stop glitching
2-k-ram not a option on 16/MB nand
Usually Corona 250 the easy one to tune for me on any 5-V chip
How about remove the yellow wire from post fix and check the resistance to ground do you get something around 60..k
also I would consider Low Loss cable and lower QSB
I am curios to see what Oggy thinks about your post codes
 
Last edited:
T

tr4ckerz

VIP Member
Aug 20, 2010
497
33
john mathews said:
I hate to say this but its coming down to your setup / I did a v3 last week boot from instant to 2 cycle and everything is default and no caps and I know every console is different but slims are the easyiest to glitch:cool2:/ u can try another program to write your glitch image but jrunner I never had any issues, I wish u the best sir(clearly soldering isn't your issue) great job by the way
Click to expand...
I know that Slims are easy to glitch. I did hundreds of them including dozens of Corona V3 and during the whole period I experienced several issues that has been sooner or later resolved, but none like this (except that with DGX that I mentioned in the OP, when we had to use DGX setup on 15xxx dashboards and where I experienced very similar issue quite often when the debug LED just stopped blinking without boot and accompanied with fast ticking sound from the FAN).

But never experienced this with CR4 until now.
 
S

stucknvegas

VIP Member
Oct 25, 2012
656
0
Cypress CA. USA
Your work is clean and sounds like you know what you are doing so no punt intended
I have had my ass kicked by a couple of Jaspers and Slim V-6 and V-6 super slim
Every console is different I have learned that much
 
You must log in or register to reply here.