Look at the motherboards, they are all zephyrs, the succesfull ones (notice the red circle) and the other one (the last one), no success... maybe the timing differ, can someone check this out ? thanks
Last edited:
Zephyr succesfull RGH
- Thread starter theboyfromthemoon
- Start date
Interesting find!
Hopefully you're on to something, as Zephyr boards not make much sense as to why they're a hit & miss.
never did a Zephyr yet, have one here, just looked & its the "bad" type.
Are you absolutely sure they're all zephyrs?
Hopefully you're on to something, as Zephyr boards not make much sense as to why they're a hit & miss.
never did a Zephyr yet, have one here, just looked & its the "bad" type.
Are you absolutely sure they're all zephyrs?
Last edited:
Hmm, very interesting. The last Zypher I did (which was successful) was a later model which had the smaller network chip.
Acton1
VIP Member
Statecowboy
BANNED
For what it's worth, I have a Xenon with that same longer chip in the last photo, can't glitch it for the worth of me. Tried multiple cap values, different shielded wire positions, etc. My photos of my setup are in the Xenon RGH thread.
Martin C
VIP Member
BL4K3Y
VIP Member
There are no "custom timings" for Zephyr consoles.
It will either glitch or it won't, all you can do is tweak with your wiring, maybe try adding a cap or even try using shielded coaxial cable on CPU_RST.
It will either glitch or it won't, all you can do is tweak with your wiring, maybe try adding a cap or even try using shielded coaxial cable on CPU_RST.
I did consider trying to get the 3 Zephyr's I've got to glitch... but I figured I'd just try and sell them as working, flashed consoles.
If I get one of the other's fixed (needs a reball and new GPU), then I might have a go at doing the RGH on it.
If I get one of the other's fixed (needs a reball and new GPU), then I might have a go at doing the RGH on it.
Well it was just a thought... inpired by this... quote:
`` As for changing the source code, Gligli posted all his source code to build your own JED on github. Try to compile his source code as-is using the free ISE Webpack tools (you can probably find general tutorials and guides on using ISE on the web, and ask around for help). Make sure you can compile the unaltered code, program the CPLD and it still works. This proves you're compiling correctly. Just learning this part will be the hardest, but it's worthwhile.
Then, find the following line in slim.vhd:
constant WIDTH_RESET_START : integer := 17357;
That's the one you will change.
Try changing the value from 17357 to 17358. See if it still works, does it work better? Try 17356, same thing, does it still work, is it any more reliable?
It probably sounds like a pain to have to change the code, recompile, reprogram and test. But If 17357 isn't already optimal for your console, then the best value will be very close, like, +/1 or +/- 2 at the most, so you really don't need to try many different values.``
`` As for changing the source code, Gligli posted all his source code to build your own JED on github. Try to compile his source code as-is using the free ISE Webpack tools (you can probably find general tutorials and guides on using ISE on the web, and ask around for help). Make sure you can compile the unaltered code, program the CPLD and it still works. This proves you're compiling correctly. Just learning this part will be the hardest, but it's worthwhile.
Then, find the following line in slim.vhd:
constant WIDTH_RESET_START : integer := 17357;
That's the one you will change.
Try changing the value from 17357 to 17358. See if it still works, does it work better? Try 17356, same thing, does it still work, is it any more reliable?
It probably sounds like a pain to have to change the code, recompile, reprogram and test. But If 17357 isn't already optimal for your console, then the best value will be very close, like, +/1 or +/- 2 at the most, so you really don't need to try many different values.``
reefz3ro
VIP Member
for what its worth here is a pic of my zypher and it glitches 1-3 seconds every time.
This may help and its goes for all phats...
Instead of routing the blue cpu wire from under the mobo, you can instead route the blue wire on top of the mobo.
The soulder point doesn't change for the blue wire, its just soulderd from the other side.
So just route the cpu wire on top of the board instead.
Works better and easier IMO.
Instead of routing the blue cpu wire from under the mobo, you can instead route the blue wire on top of the mobo.
The soulder point doesn't change for the blue wire, its just soulderd from the other side.
So just route the cpu wire on top of the board instead.
Works better and easier IMO.
Last edited:
I always use the alt stand by click its more easy to. 
---------- Post added at 10:08 ---------- Previous post was at 10:07 ----------
all my 3 Zephyr has big network chip.. 1 Zephyr glitches only once into xell, the others I can't test due to updated dash.
---------- Post added at 10:08 ---------- Previous post was at 10:07 ----------
all my 3 Zephyr has big network chip.. 1 Zephyr glitches only once into xell, the others I can't test due to updated dash.
I've got two zephyr with the small chip that glitch and one with the long chip that doesn't glitch.