I thought I'd post this as it might help others troubleshoot their RGH without causing any permanent damage.
Issue: boot times were VERY erratic. I fitted the 100nF cap between GND and A which made it glitch fine once, but wouldn't glitch afterwards. I know from experience that the CPU_RST wire can be the cause, especially if there's interference. I tested the theory by wiring it topside but leaving it loose but nowhere near any other components. It did glitch, but was still quite erratic and only seemed to go when I pinched the wire between thumb and forefinger.
I've seen others use coax (I take no credit in this whatsoever), so I picked up 10m of RG-174 from ebay and cut to length (Xecuter recommends LMR-100A - but I couldn't find any locally so went for RG-174 which seems to work well too). I didn't bother about earthing the screen, so just cut back cleanly leaving a multi-strand core (Although Xecuter does recommend soldering the shield to GND and solid core is also preferred to multi-strand core). I used insulating tape to protect where it was cut (so that no stray earth strands were visible). You can use heat-shrink to similar effect.
I initially soldered it between CPU_RST and D topside to test. Booted up every time between 5-15 secs. I therefore went ahead and installed it properly (see attached image). Same result.
So, if you have a stubborn Jasper, do things in THIS order:
1. Check ALL solder points. This goes without saying. If your soldering is no good then no amount of wire positioning etc will help.
2. Use the preferred wire routing as posted in the tutorials. Keep the CPU_RST wire loose for now and away from any other components.
3. Either solder a 100nF cap between GND and A (rev. A CR) or bridge the cap point (rev. B / rev. C CoolRunner).
If it's not glitching at this point, try pinching the CPU_RST wire between thumb and forefinger as previously mentioned. Your body provides a natural insulation by doing this. If this helps, look at using LMR-100A / RG-174 instead as advised.
If it's STILL not booting, make sure your ECC file is good etc. as at this point, it's going to be something more obvious.
Issue: boot times were VERY erratic. I fitted the 100nF cap between GND and A which made it glitch fine once, but wouldn't glitch afterwards. I know from experience that the CPU_RST wire can be the cause, especially if there's interference. I tested the theory by wiring it topside but leaving it loose but nowhere near any other components. It did glitch, but was still quite erratic and only seemed to go when I pinched the wire between thumb and forefinger.
I've seen others use coax (I take no credit in this whatsoever), so I picked up 10m of RG-174 from ebay and cut to length (Xecuter recommends LMR-100A - but I couldn't find any locally so went for RG-174 which seems to work well too). I didn't bother about earthing the screen, so just cut back cleanly leaving a multi-strand core (Although Xecuter does recommend soldering the shield to GND and solid core is also preferred to multi-strand core). I used insulating tape to protect where it was cut (so that no stray earth strands were visible). You can use heat-shrink to similar effect.
I initially soldered it between CPU_RST and D topside to test. Booted up every time between 5-15 secs. I therefore went ahead and installed it properly (see attached image). Same result.
So, if you have a stubborn Jasper, do things in THIS order:
1. Check ALL solder points. This goes without saying. If your soldering is no good then no amount of wire positioning etc will help.
2. Use the preferred wire routing as posted in the tutorials. Keep the CPU_RST wire loose for now and away from any other components.
3. Either solder a 100nF cap between GND and A (rev. A CR) or bridge the cap point (rev. B / rev. C CoolRunner).
If it's not glitching at this point, try pinching the CPU_RST wire between thumb and forefinger as previously mentioned. Your body provides a natural insulation by doing this. If this helps, look at using LMR-100A / RG-174 instead as advised.
If it's STILL not booting, make sure your ECC file is good etc. as at this point, it's going to be something more obvious.
