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.
![Name: Pic4.jpg
Views: 69
Size: 1.24 MB]()
![Name: Pic1.jpg
Views: 64
Size: 1.24 MB]()
![Name: Pic2.jpg
Views: 62
Size: 1.24 MB]()
![Name: Pic3.jpg
Views: 59
Size: 1.22 MB]()
![Name: Pic7.jpg
Views: 65
Size: 1.25 MB]()
![Name: Pic5.jpg
Views: 61
Size: 1.25 MB]()
![Name: Pic8.jpg
Views: 60
Size: 1.23 MB]()
![Name: Pic6.jpg
Views: 55
Size: 1.25 MB]()
![Name: Pic10.jpg
Views: 57
Size: 1.27 MB]()
![Name: Pic9.jpg
Views: 58
Size: 1.25 MB]()
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).
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
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?