Corona V2 CR4 XL boots to xell but not Xebuild image

mcudogs

Noob Account
Nov 14, 2019
3
1
Australia
  • Console Type:Corona v2
  • Programmer Used: Corona 4gb nand reader
  • NAND Size: 4GB
  • Dashboard version: 16756
  • CB Version: ?
  • Screenshot of NAND details from J-Runner:
  • J-Runner log
  • updflash.bin log
  • Image of the CR4 XL
  • Images of close-up soldering to motherboard
  • Detailed Description of the Problem
  • Was the console working before you started: Y
  • Do you get a green debug light appear on the CR4 XL chip every 4-5 seconds: one flash then nothing
  • How long is the light on for each time 0.5 secs

Hi all,

This is my 2nd CR4 XL install, first was a trinity and all went well no issues. This one is a corona v2 4GB nand board and it won't boot the final image.

The nand read went well using a 4gb sd reader and the ecc image was written and the CR4 wired and installed. I used the standard dip setting (3 & 8 on) and when I booted the box it glitched twice then loaded xell with no issues. Got the CPU key entered it into jrunner created the xebuild image dash 17150, connected the nand reader and wrote the nand which completed successfully. Disconnected the sd reader and tried booting the box. The green debug light flashes once only and not again and the console does not boot.

I tried this about 5 times with different dashes and all jumper and dip settings. I reflashed the original nanddump and the console booted into retail normally.

Pics are attached. Any suggestions?



log
https://i1250.photobucket.com/albums/hh526/mcudogs1/jrunner_zps21r3n3hz.jpg
https://i1250.photobucket.com/albums/hh526/mcudogs1/20191213_194447_zpsme9aov17.jpg
https://i1250.photobucket.com/albums/hh526/mcudogs1/20191213_194456_zpsd8vdxi2r.jpg
https://i1250.photobucket.com/albums/hh526/mcudogs1/20191213_194506_zpscle8uvcb.jpg
https://i1250.photobucket.com/albums/hh526/mcudogs1/20191213_194553_zpsohhjyp1w.jpg
https://i1250.photobucket.com/albums/hh526/mcudogs1/20191213_194634_zpsxicgey3v.jpg
 
Last edited:

mcudogs

Noob Account
Nov 14, 2019
3
1
Australia
use the alternative cpu_rst point
Thanks for the quick reply. I tried connecting the blue wire cpu_rst to the alternative point and still get the same result. Any idea why it boots into xell ok with 2 flashes but not the final build? I thought that if the cr4 booted into xell all connections would be correct. Is that not so?
 

mcudogs

Noob Account
Nov 14, 2019
3
1
Australia
u could have a bad flash. create ur freeboot and flash it to console again. also select CR4 on jrunner before creating the freeboot img.
Okay I finally got it to boot freeboot. I reflashed the nand again and got exactly the same problem so I decided to get the cro out to check some signals, As part of that I accidentally unplugged the hdmi connection to my tv. It booted after 2 flashes. I then tried connecting the tv via composite video and the console still boot after 2 ok. I then tried a different tv connected via hdmi and it also booted ok. This pointed to the tv in my workshop being the problem. Sure enough if I boot the console with the tv turned off it boots ok, I can then turn the tv on and everything works ok. The tv in question is an old lcd tv, one of the first with hdmi. Not sure why this is a problem but I think it must have been introducing noise into the xbox system enough to disrupt the glitch signal. This also explains why I had to redo the timing on the first console I rgh'd as it was set up on the same tv with a 3-4 glitch startup and when connected to a different tv it took about 8 glitches to boot.

Thanks for the help in fixing this problem Playingmax, it's good to know there are experts available to help when needed.