GENERAL Falcon RGH

srt4fun

Senior Member
Sep 8, 2011
133
0
California
So, I found this issue with Falcons and the RGH (with the Diligent C-MOD at least). While the CPU_PLL_Bypass wire is taped to the board it freezes when xell loads. Usually never gets past the "Xell Reloaded" ascii text. Now when I take the tape off and let it hang down a bit it goes straight through and loads up linux from my usb drive. I flash the stock image back on with the C-MOD fully disconnected, and wires still in place; taped=0022 hanging=boot. Tried different gauges of wire, routed it differently, and shortened the wire. All to no effect. Also verified this on 2 separate Falcons. My Zephyr and Jasper didn't do this.....weird, eh? :confused:
 

baguette

Noob Account
Nov 2, 2011
3
0
i seem to be having the exact same problem.
wires taped to board: freezes or 0022.
not taped: console working fine.
did you manage to find a workaround for this?
 

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Last edited:
  • Like
Reactions: voldemrd

seanr28

VIP Member
Mar 7, 2004
1,203
0
Yeah, I found a solution. Credit goes to Podger, he gave me the idea. The trick is to route CPU_PLL_BYPASS away from CPU_RST and POST_OUT1 as much as possible. My Falcon will boot 95% of the time in 10 seconds or less. It never takes more than 30 seconds at it's worst. Used 30AWG wire for signal and 24AWG for Power/Ground

Here are a couple pics of my install.

http://img844.imageshack.us/img844/7881/img0492ud.jpg
http://img197.imageshack.us/img197/4532/img0496te.jpg

Thats useful to know:) You seem to have an extra resistor across 2 pins??
 
Last edited:

baguette

Noob Account
Nov 2, 2011
3
0
Yeah, I found a solution. Credit goes to Podger, he gave me the idea. The trick is to route CPU_PLL_BYPASS away from CPU_RST and POST_OUT1 as much as possible. My Falcon will boot 95% of the time in 10 seconds or less. It never takes more than 30 seconds at it's worst. Used 30AWG wire for signal and 24AWG for Power/Ground
ah... i tried routing the cables differently, which didn't work, and came up with a more 'ghetto' workaround, using foam blocks as spacers to keep the cables at a slight distance from the board.
http://i.imgur.com/5dq4l.jpg
seems to work fine so far, got fsd up and running reliably.
 

srt4fun

Senior Member
Sep 8, 2011
133
0
California
Thats useful to know:) You seem to have an extra resistor across 2 pins??
Nope, the only thing extra is the debug LED. Didn't have any larger 3.3v LEDs around so I used a 603, Pain in the arse to solder it, haha.


ah... i tried routing the cables differently, which didn't work, and came up with a more 'ghetto' workaround, using foam blocks as spacers to keep the cables at a slight distance from the board.
http://i.imgur.com/5dq4l.jpg
seems to work fine so far, got fsd up and running reliably.
Nice, doesn't look ghetto to me...
 
Last edited:

esbmaepo

VIP Member
Oct 2, 2011
461
48
Esbjerg - Denmark
Yeah, I found a solution. Credit goes to Podger, he gave me the idea. The trick is to route CPU_PLL_BYPASS away from CPU_RST and POST_OUT1 as much as possible. My Falcon will boot 95% of the time in 10 seconds or less. It never takes more than 30 seconds at it's worst. Used 30AWG wire for signal and 24AWG for Power/Ground

Here are a couple pics of my install.

http://img844.imageshack.us/img844/7881/img0492ud.jpg
http://img197.imageshack.us/img197/4532/img0496te.jpg
Yes I had the same problem with a Falcon.

I then routed each wire away from each other. Chose to make cpu_pll_bypass wire as short as possible, so I routed it directly underneath the cooling fan. The cpu_rst I routed on top of the board. I then insulated each wire with shinkable wire tubing.

It now works really well. Boots into dash 13604 within 5-10 secs every time. Only slight problem is that it wont boot via controller, but only via power button. But I can live with that...

So thanks to Podger and srt4fun.
 
  • Like
Reactions: voldemrd