Xbox-Scene
Dec 5 2011, 04:23 AM
Xecuter CPU_RST PCB Solution For Slims - New SLIM POST QSB
Posted by XanTium | December 4 22:23 EST | News Category: Xbox360
|
| |
|
From team-xecuter.com: [QUOTE] Those that have fitted a CoolRunner to an Xbox Slim will be no stranger to the fact that it can take a great deal of trial and error to get the optimized boot times down to less than 5 seconds.
The main issue is the CPU_RST wire which has to be up to 50cm long and then coiled underneath the motherboard. In many cases the positioning of the coil is a factor due to signal interference. Then you have to try different lengths, 40cm,
We believe we have developed a simple yet elegant solution for this problem.
Using the process of serpentining, we have designed a QSB PCB for the 360 slim that fits neatly into place, giving you an optimized solution enabling you to select several different lengths without having to cut any wires and eliminates any guess work and possible signal interference issues.
Since the CoolRunner has been out in the wild, we have collected data from hundreds of testers and implemented the optimum lengths that were reported as giving the most consistently good results.
Simply cut the blue CPU_RST wire to 8cm and then you can select from 50cm, 47cm, 41cm, 38cn, 35cm, 32cm & 29cm.
We have also included all the POST points for the developers out there who wish to use that part of NANDPRO 3 that was implemented by Tiros.
To give you an idea of how the serpentining is used, I've adjusted some values in photoshop so you can get a better idea
We hope to have this on sale next week at only $3.95
We also suggest that you look at the instructions again as we have posted other troubleshooting solutions that may help you get the absolute best from your RGH install. [/QUOTE]
Official Site: http://team-xecuter.com Buy: CoolRunner / NAND-X / Phat QSB Kit / Slim QSB Kit
|
InvidiousDemise
Dec 5 2011, 06:31 AM
More shit to buy? Golly gee willakers I guess I'll have to get this when I decide to do a slim.
Blargharg
Dec 5 2011, 06:53 AM
I really don't understand why this can't be done with a few resistors. I mean seriously, what is the logic here? What's the science behind this? Or is it just trial and error, throw shit at the wall and see what sticks type of thing? Also, while I'm perfectly happy to pay 5$ for a QSB that saves me time on install & is reusable for future dumps/writes, I'd much rather stick with the 50cm wire than pay another 4 bucks for this.. this thing.
SNAAAKE
Dec 5 2011, 08:50 AM
shouldn't it already come with the tx coolrunner...
meh not buying. my slim loads fines..takes 5 something seconds maybe..I used keyner wrapping wire and not the wires come with tx coolrunner.
Exobex
Dec 5 2011, 12:08 PM
QUOTE(Blargharg @ Dec 5 2011, 05:53 AM)

I really don't understand why this can't be done with a few resistors. I mean seriously, what is the logic here? What's the science behind this? Or is it just trial and error, throw shit at the wall and see what sticks type of thing? Also, while I'm perfectly happy to pay 5$ for a QSB that saves me time on install & is reusable for future dumps/writes, I'd much rather stick with the 50cm wire than pay another 4 bucks for this.. this thing.
It's not down to resistance, it's down to timing, namely the time it takes for the signal to travel down half a metre of wire. Look at any modern motherboard and you'll see bus tracks wiggling, it's done to ensure all the tracks of the bus are the same length and the bits therefore arrive simultaneously.
Half a metre of wire will do the job just as well, but ideally will need to be tacked in place in a location where it's not going to interfere with or pick up interference from other tracks. The fact that the wire on this new PCB zigzags ought to help in that respect as well, coil it and it becomes an inductor. This is a neater way to pack in a 50cm wire that's going to stay put without needing to be glued in place.
QUOTE(SNAAAKE @ Dec 5 2011, 07:50 AM)

shouldn't it already come with the tx coolrunner...
Definitely.
col12
Dec 5 2011, 02:17 PM
tell you what executer everyone that bought a coolrunner send them one for free so the device ie coolrunner works as it should. starting to get like m$ greedy
the cool runner has been out in the wild for a while now we have had lots of feed back from testers NOT MEAN LOYAL CUSTOMERS .we have made a product that will make the product you bought from us work
BoNg420
Dec 5 2011, 02:49 PM
QUOTE(col12 @ Dec 5 2011, 08:17 AM)

tell you what executer everyone that bought a coolrunner send them one for free so the device ie coolrunner works as it should. starting to get like m$ greedy
the cool runner has been out in the wild for a while now we have had lots of feed back from testers NOT MEAN LOYAL CUSTOMERS .we have made a product that will make the product you bought from us work
Oh come on now, you paid $20 + sh to be a beta tester!
LordX
Dec 5 2011, 02:53 PM
Very lame PCB ,
many solder pads for deferent size , why not to use 1 pad for a wire and jumpers ?! even solder jumpers.
and why not to found away to fix the CPU_RST in the first place and make it more stable without all this lame tricks.
valkirie
Dec 5 2011, 03:16 PM
I personally do not care much for this device. My xbox slim has different boot time, but I honestly dont care for all the benefits it brings. So what I have to sometimes wait a minute for boot. I am just going to play with the wire to see if I find a sweet spot that will get the timing down to something lower.
Blackaddr
Dec 5 2011, 04:29 PM
This is getting out of hand with all these silly wire lengths and loops.
If you install your CPLD board right next to the CPU_RST point, and keep the wire under 1" there shouldn't be any interference on that signal. Why does everyone insist on putting it on top of the AVIP? Sure it's easy, but you're giving yourself bigger headaches.
If you try different timing values in the CPLD you can also optimize the timing for your particular console. Why spends days playing with wire lengths, spend an afternoon to learn to compile you own JED.
50 cm wires with loops? Come on, KISS.
ninja x
Dec 5 2011, 04:45 PM
not bad for people buying it now... not good for early adopters + damn right it should've come in the kit.
kinda pisses me off - but that's the name of the game with technology. everyone is in a hurry to be the first out to make a sell - then they take their time to improve the product progressively.
shtewps
Dec 5 2011, 06:28 PM
Jesus.. add a f*cking switch FFS. Not 50 pads to constantly move your wires to while testing.
You need this to improve your coolrunner, now come out with something to improve this BEFORE people buy it.
(agreed it should come bundled with kits -- resellers should be offering this item at cost for customers who have already purchased a CR)
xiaNaix
Dec 5 2011, 07:40 PM
QUOTE(SNAAAKE @ Dec 5 2011, 02:50 AM)

shouldn't it already come with the tx coolrunner...
meh not buying. my slim loads fines..takes 5 something seconds maybe..I used keyner wrapping wire and not the wires come with tx coolrunner.
if its included - what a complete waste of time and money for those that buy a coolrunner who are going to mod a phat
some of you need to think before typing

and if yours is booting in 5 seconds - then why would you even consider getting this ? You wouldn't.
Its also nothing to do with the wire you use. The impedance of that wire supplied with the coolrunner is the same as kynar
This seems like a great addon to make the job even easier than before. You dont want it ? keep your $3.95 and dont buy it. simple.
xiaNaix
Dec 5 2011, 08:33 PM
QUOTE(shtewps @ Dec 5 2011, 12:28 PM)

Jesus.. add a f*cking switch FFS. Not 50 pads to constantly move your wires to while testing.
You need this to improve your coolrunner, now come out with something to improve this BEFORE people buy it.
(agreed it should come bundled with kits -- resellers should be offering this item at cost for customers who have already purchased a CR)
A switch doesn't work - it plays with the impedance of the line - there was a big discussion about it on IRC. You dont think this stuff is tested while its being made ? So naive.....
And why should free ones be offered ? this is a tool to make a job easier - not to fix something that was broken
All you armchair complainers - why dont you make your own solutions instead of whining like little bitches ?
QUOTE(Blackaddr @ Dec 5 2011, 10:29 AM)

This is getting out of hand with all these silly wire lengths and loops.
If you install your CPLD board right next to the CPU_RST point, and keep the wire under 1" there shouldn't be any interference on that signal. Why does everyone insist on putting it on top of the AVIP? Sure it's easy, but you're giving yourself bigger headaches.
If you try different timing values in the CPLD you can also optimize the timing for your particular console. Why spends days playing with wire lengths, spend an afternoon to learn to compile you own JED.
50 cm wires with loops? Come on, KISS.
Your comment was useless and ill informed about why this is required in the first place
its nothing to do with resistance and everything to do with timing.
if you think its as easy as making your own CPLD code then go for it and share with everyone.......
You have to laugh at some of you - you post like you're technical in any way and that you know more than the engineers who work at places like Xecuter lol

QUOTE(LordX @ Dec 5 2011, 08:53 AM)

Very lame PCB ,
many solder pads for deferent size , why not to use 1 pad for a wire and jumpers ?! even solder jumpers.
and why not to found away to fix the CPU_RST in the first place and make it more stable without all this lame tricks.
Jumpers were tested - as well as switches - they affected the impedance. if you had any clue you'd understand this. Same reason as to why a cable hardness wasn't used on the coolrunner. You don't think all this is tested first ? Similar conversations on IRC about it and you had to laugh at the kids who thought they knew more. the naivety is staggering - but its video games scene - what do you expect?
maybe you should fix the CPU_RST issue in the first place because you are obviously smarter than Tiros who spent over a year designing the hack......
cornnatron
Dec 5 2011, 09:05 PM
Im sorry to say xiaNaix but i think Blackaddr knows what he is talking about
he was also involved with first jtag i thought
and as far as i know he came up with the Transistor wiring with aud clamp for the first jtag
so more than enough technical knowhow
could you tell me where you helped with the scene or did you just read the irc.
becouse your comming over like a true Xecuter fanboy.
@blackaddr any tips on finding better timings for specific consoles?
X4life3
Dec 5 2011, 09:17 PM
Why are people complaining about this? If you dont want to spent the money dont and just wait 30+ seconds for it to boot, its not like you HAVE to use this its just a option. Ive tried everything to get my console booting in under 45 seconds, if they helps it I will use it.
warbeast
Dec 5 2011, 09:53 PM
QUOTE(X4life3 @ Dec 5 2011, 09:17 PM)

Why are people complaining about this? If you dont want to spent the money dont and just wait 30+ seconds for it to boot, its not like you HAVE to use this its just a option. Ive tried everything to get my console booting in under 45 seconds, if they helps it I will use it.
the same reason people complain about any other company that doesnt bring somthing new take the iphone 4s alot of people felt let down ask siri
everything done by tx for glitch has its diy roots witch can be done for half the price! i want to know when or even if tx will bring a dual nand chip? cygnos rev E sucks and theres a bigger market for it then this crap or do tx now stick to using simple easy to clone diy mods slapped onto pretty pcb's?
ruciz
Dec 5 2011, 11:03 PM
People do realize that this is aimed 100% at professional installers? People who are doing 5+ consoles a day?
the average joe end user can cut their 50cm wire back 3CM at a time and it will do the EXACT same thing! Against what the diagram says I guess the intentionally extra long wire isn't needed!
TX is admitting that their 50CM long slim wire IS a failure and this (which should really be included with the CoolRunners, esp now that they retail for $13/100) may help? The benefit of this is you quickly swap pads until you find the optimal length - no worries of board damage (then again if you are good at soldering there isn't either!)
If you want- get one of these, test the different lengths, find a suitable one and then remove and install a wire that long. Simple as that. Use the board on another slim to repeat.
Alternatively, cut and coil wires at 50, 47, 44, etc and keep trying until one is suitable.
I just tweaked a slim from usual 80-400 sec boots to under 20 sec every time by shortening their 50CM wire to a 32CM length as suggested by other teams/researchers. This is NOT measured, and is definitely shorter than 32CM but I cut off 3cm of wire at a time, 6 times, trialing between. Once you take into acct stripping, tinning, trimming Im likely at 31CM.. Its possible 29cm may work even better too, but Im satisfied.
I tested the unit 2 ways, which results seem to differ at other lengths.
1- cold boot (unplugged for 15 sec or longer)
2- warm boot (powered down orange light on PSU for 15 sec or longer)
Every time it boots in under 30 seconds now. Nominally 5-15 sec with favor to a 'warm' boot. The odd boot takes 20 sec. I have yet to hit over 30 seconds though with 15 boots. I have read some people get 5 sec 'cold' boots and really long 'warm' boots. If this is the case I suggest swapping from 3V3_STBY to 3V3 point. It will make every boot a cold boot...
Really wish TX would get it together tho. When these released they sucked with slims and jaspers.. After some trials, people figured out that the jaspers are stubborn need a cap. so TX include 68nF capacitor. Now they are admitting their 50CM wire isn't the best plan but rather than include the possible fix - they sell it separately at 20-33% of coolrunner cost.
To those who will shell out $16 to get it after shipping, I sincerely *hope* its worth it... compared to cutting back or getting 3.5M of wire to test all the lengths.
SNAAAKE
Dec 5 2011, 11:29 PM
QUOTE(xiaNaix @ Dec 5 2011, 01:40 PM)

if its included - what a complete waste of time and money for those that buy a coolrunner who are going to mod a phat
some of you need to think before typing

and if yours is booting in 5 seconds - then why would you even consider getting this ? You wouldn't.
Its also nothing to do with the wire you use. The impedance of that wire supplied with the coolrunner is the same as kynar
This seems like a great addon to make the job even easier than before. You dont want it ? keep your $3.95 and dont buy it. simple.
how much does a qsb cost? like 10 cents? time...mass produced in factory?
I dont need it for my own slim. but Id like it come with my $20 tx coolrunner package because I am a modder and doing this for people too. I dont wanna pay $20 for a half-assed product. thats why the qsb should come with with coolrunner so I have the FULL complete product so I can install it for my customer's xboxes.
doesnt matter for those of us already bought some tx coolrunner. I am not expecting these qsb for free because I bought some txc already. but for FUTURE orders I am expecting it to come with the qsb.
Exobex
Dec 5 2011, 11:42 PM
QUOTE(cornnatron @ Dec 5 2011, 08:05 PM)

Im sorry to say xiaNaix but i think Blackaddr knows what he is talking about
could you tell me where you helped with the scene or did you just read the irc.
becouse your comming over like a true Xecuter fanboy.
If you put xiaNaix into Google you'll find that he was responsible for the PSX-Scene and WiiNewz forums (before they were turned over to Caputo and WiiNewz turned to shit, but that's another story). He's not new to the scene, far from it.
Me, before you ask? Only a few bits and bobs made out of personal necessity and released to the public (Freelock, the 0.7 revision of raincoat, X360SAM).
You?
Ranger72
Dec 6 2011, 01:01 AM
This would have saved me about 10 hours of try and error on my first Slim. I would get the wire length just right and spooled around under the board just right to get it to boot under 5 seconds only to have it to all to shit when I put it back into the cage and have to mess with the wire length again.
There are some Slims out there that are much more picky than others. For those this device would come in handy.
pif001
Dec 6 2011, 01:29 AM
QUOTE(Blackaddr @ Dec 5 2011, 04:29 PM)

This is getting out of hand with all these silly wire lengths and loops.
If you install your CPLD board right next to the CPU_RST point, and keep the wire under 1" there shouldn't be any interference on that signal. Why does everyone insist on putting it on top of the AVIP? Sure it's easy, but you're giving yourself bigger headaches.
If you try different timing values in the CPLD you can also optimize the timing for your particular console. Why spends days playing with wire lengths, spend an afternoon to learn to compile you own JED.
50 cm wires with loops? Come on, KISS.
Please share a tutorial about optimizing our own JED files... and ignore that troll please!
shtewps
Dec 6 2011, 03:56 AM
You are sad, and 100% oblivious.
Were not talking about a test lab here you dumb sh*t (since you want to start name calling). Were talking about running a business and offering quality product to a consumer market.
You want to talk about testing, eh? Really? I bet your definition of 'testing' fits nicely with that of TX. Let's sell these "bitches" a product, let them do the leg work, and capitalize off their findings. Because it only took them an extra 3 months of "testing" to come out with a kit that wasn't complete. And this is not even mentioning BB jaspers that require a cap.
Oh f*ck yeah bud, so much "testing" going on here.
Please, do everyone a favour and don't associate yourself with the business world. Pathetic child.
QUOTE(xiaNaix @ Dec 5 2011, 03:33 PM)

You dont think this stuff is tested while its being made ? So naive.....
Blackaddr
Dec 6 2011, 04:03 AM
QUOTE(pif001 @ Dec 5 2011, 08:29 PM)

Please share a tutorial about optimizing our own JED files... and ignore that troll please!
Before you get into exotic ideas like long loops of cables, a ton of different cap values, give yourself the best chance at success first, then move on to more complex ideas. Put the CPLD board as close to the CPU_RST as you can reasonably get it, atleast for initial testing. You can always move it to a more convenient location later once you've established boot times with a very short wire. Then you know what the real impact is.
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.
shtewps
Dec 6 2011, 04:25 AM
Now if that wasn't constructive, I don't know what is. Thanks for the insight Blackaddr.
QUOTE(Blackaddr @ Dec 5 2011, 11:03 PM)

Before you get into exotic ideas like long loops of cables, a ton of different cap values, give yourself the best chance at success first, then move on to more complex ideas. Put the CPLD board as close to the CPU_RST as you can reasonably get it, atleast for initial testing. You can always move it to a more convenient location later once you've established boot times with a very short wire. Then you know what the real impact is.
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.
ruciz
Dec 6 2011, 05:25 AM
QUOTE(Ranger72 @ Dec 6 2011, 01:01 AM)

This would have saved me about 10 hours of try and error on my first Slim. I would get the wire length just right and spooled around under the board just right to get it to boot under 5 seconds only to have it to all to shit when I put it back into the cage and have to mess with the wire length again.
There are some Slims out there that are much more picky than others. For those this device would come in handy.
Serious? 10 hours to tape wire?
Totally not worth it. save 10 sec on a boot, be 10 years before I would notice that amount of time saving.
QUOTE(Blackaddr @ Dec 6 2011, 04:03 AM)

Before you get into exotic ideas like long loops of cables, a ton of different cap values, give yourself the best chance at success first, then move on to more complex ideas. Put the CPLD board as close to the CPU_RST as you can reasonably get it, atleast for initial testing. You can always move it to a more convenient location later once you've established boot times with a very short wire. Then you know what the real impact is.
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.
kudos for this tidbit of information. Its greatly appreciated.
pif001
Dec 6 2011, 10:53 AM
Thnx Blackaddr. You explained it well....
Tag234
Dec 6 2011, 11:00 AM
'xiaNaix' - you sir, are either seriously misinformed or are just working for TX.
Thanks for that info Blackaddr
Exobex
Dec 6 2011, 11:18 AM
QUOTE(Blackaddr @ Dec 6 2011, 03:03 AM)

Before you get into exotic ideas like long loops of cables, a ton of different cap values, give yourself the best chance at success first, then move on to more complex ideas. Put the CPLD board as close to the CPU_RST as you can reasonably get it, atleast for initial testing. You can always move it to a more convenient location later once you've established boot times with a very short wire. Then you know what the real impact is.
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.
I've not meddled with CPLD programming at all, but does this mean that a DIY-even-for-newbies version would be possible? I'm thinking a 4-gang DIP switch on the PCB, which would, for example, allow a range from 17350 to 17365 to be selected, or 17354 to 17341 with a spare switch for something else? Obviously this depends on how the code uses the WIDTH_RESET_START constant gets used wirhin the code, and if there are spare I/O pins available to read the switches.
cornnatron
Dec 7 2011, 12:32 PM
Tnx for the explaination of the timming blackaddr will have a look at ISE tonight .
dop3snation
Dec 7 2011, 09:54 PM
Why are so many people complaining? this is ridiculous.
Is the coolrunner perfected for all consoles? no maybe not but it is still a hell of alot easier to use than any other glitch chip out there
before the coolrunner i bought the matrix glitcher because i was impatient and it was a piece of shit + i paid 30 for it.
The coolrunner is only 20 bucks, this is cheap considering it changes a standard xbox into a homebrew enabled xbox, have you guys seen some of the prices on things in the ps3 scene? 20 bucks is cheap
I have installed the coolrunner in multiple slims and have always had success multiple falcons all with boot times of about 3 seconds a zephyr with good times. I know jaspers seem to be a bit of a bitch, but i have seen many jaspers be glitched without problems, who cares if you have to wait 30 seconds - 1 min for boot?!?! go make a sandwich, have a smoke, call your mother, check your email...
This product is 3-4 bucks, it isnt necessary and is only for those who have been unable to to get the slims to glitch in a reasonable time, the coolrunner works fine this is just an attempt to optimize. An slim costs roughly 200 usd new and your complaining about a 3-4 dollar pcb??? really???
I do not work for team x and am in no way shape or form affiliated with them, but every product i have boughten from them has worked flawlessly, we are lucky we have so many options, the xbox scene has always been a very active one and this rgh is a blessing, we should be happy for any and all progression not putting it down
We are all on the same team, so get over yourselfs, get off your high horse, if you want to make something better by all means be my quest i support homemade sollutions 100% i built my own probe instead of buying team x if you can do it yourself then great! but if you are not good at soldering or are lazy, or are doing customer installs this pcb is great, dont jump to bullshit conclusions before you know the facts
also, team x said they are not interested in making a dual nand solution because they dont think it will be undetectable permanently, was this bs? maybe but that is what i have been told. So for now we have the cygnos which in my opinion is a great piece of equipment, so please if you are bitching get off your lazy asses and do something, complainers dont do anyone any good
rastiemon
Dec 8 2011, 01:56 AM
I don't know what to think of this wire and coil length stuff. I have glitched about 30 slims to this point and never really had a issue with extreme boot times nothing over 45 seconds or so. Then I worked on a slim this week that just didnt want to glitch constantly at all. Tried every combo of coil shape, wire length etc. It would boot 1 min, 6, never, 4min, 6min, and once every 20 boots or so it would boot under 20 seconds. I even tried a different coolrunner.
So I can understand peoples frustration if their only box has issues like that one. But so far the coolrunner has given me great boot times on most slims so far. Im hoping the last batch I ordered wasn't an issue also. I am gonna try to glitch another box with the same 2 chips I used on the last and see how that goes.
ruciz
Dec 8 2011, 02:01 AM
QUOTE(Exobex @ Dec 6 2011, 11:18 AM)

I've not meddled with CPLD programming at all, but does this mean that a DIY-even-for-newbies version would be possible? I'm thinking a 4-gang DIP switch on the PCB, which would, for example, allow a range from 17350 to 17365 to be selected, or 17354 to 17341 with a spare switch for something else? Obviously this depends on how the code uses the WIDTH_RESET_START constant gets used wirhin the code, and if there are spare I/O pins available to read the switches.
Possible yes by putting it out to different pins.
You would then need to solder the center of your switch to the corresponding pin and cut then 'bridge' it to your reset timing pad.
It would be much easier and cheaper to just try the different code. the chips take 5 seconds to program max and can be done while its in the console (least for the TX coolrunner they can)
rastiemon
Dec 8 2011, 03:02 AM
Im gonna have a go messing around with the programming also. I would rather do that then sit and play with wire lengths all night.
BerT69
Dec 8 2011, 05:09 AM
Wow....people can hate all they want...I cant wait to try this
I am currently doing my first slim and it boots with erratic times...but still boots. UNTIL I try to put the machine back together... then nothing, but as soon as I pull the wire away from the board it boots fine. However like i say, boot times are a bit erratic (but acceptable). I have tried playing with wire lengths till I'm blue in the face. I dying to try another option. So far this has proven (for me) not to be stable enough mod to sell to customers yet. I hope this option will change my opinion.
Julets
Dec 8 2011, 11:22 PM
QUOTE(Blackaddr @ Dec 5 2011, 04:29 PM)

This is getting out of hand with all these silly wire lengths and loops.
If you install your CPLD board right next to the CPU_RST point, and keep the wire under 1" there shouldn't be any interference on that signal. Why does everyone insist on putting it on top of the AVIP? Sure it's easy, but you're giving yourself bigger headaches.
If you try different timing values in the CPLD you can also optimize the timing for your particular console. Why spends days playing with wire lengths, spend an afternoon to learn to compile you own JED.
50 cm wires with loops? Come on, KISS.
I believe at this point, you mean Ki$$, or KiMM (Keep it making money). I'm just saying...
BerT69
Dec 10 2011, 05:30 PM
Is the topic now dead??..when and where is release for the item. I have found nothing on the hardware sites.
jayboy86
Dec 11 2011, 05:12 AM
QUOTE(BerT69 @ Dec 10 2011, 05:30 PM)

Is the topic now dead??..when and where is release for the item. I have found nothing on the hardware sites.
I second that question
kipper2k
Dec 11 2011, 06:57 PM
I've seen a lot of pictures that peopple show with their wires all over the place, heres a nice simple solution, a piece of cardboard, some scotch tape and wire that is zigzagged to make up the desired length, you could even shield it if you want by putting some tin foil on the top side of the cardboard and then lay the wires.
Heres a pic of a cheap, tidy and simple solution that will save you buying the board
kipper2k
Dec 11 2011, 08:32 PM
QUOTE(Blackaddr @ Dec 6 2011, 04:03 AM)

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.
Is anyone willing to share and post a jed file (or 3) for the slim that has already been recompiled with the different values
thanks
cornnatron
Dec 11 2011, 10:59 PM
very much tnx for the tip blackaddr now booting 5sec constantly still sometimes takes 15 sec but no longer.
had to use +1 on mine with 1 inch cable and 270uf on matrix glitcher
here for the people who cant compile
trinity timing files cpldexplanation inside
kipper2k
Dec 11 2011, 11:21 PM
QUOTE(cornnatron @ Dec 11 2011, 10:59 PM)

very much tnx for the tip blackaddr now booting 5sec constantly still sometimes takes 15 sec but no longer.
had to use +1 on mine with 1 inch cable and 270uf on matrix glitcher
here for the people who cant compile
trinity timing files cpldexplanation inside
Many thanx, A gentleman and a scholar
cornnatron
Dec 11 2011, 11:39 PM
QUOTE(kipper2k @ Dec 11 2011, 11:21 PM)

Many thanx, A gentleman and a scholar

me is just a simple plumber certenly no scholar , but no probs
took me all day to get my jtag cable working ,
becouse of unknown device in impact.
in the end made a new cable and works a treat now .
learning compiling in ise only took up several hours.
DrZeus
Dec 12 2011, 10:01 AM
QUOTE(cornnatron @ Dec 11 2011, 09:59 PM)

very much tnx for the tip blackaddr now booting 5sec constantly still sometimes takes 15 sec but no longer.
had to use +1 on mine with 1 inch cable and 270uf on matrix glitcher
here for the people who cant compile
trinity timing files cpldexplanation inside
Wow very interesting. I would like to try different timings on some Zephyr's that just wont glitch no matter what I do. I wonder if it might help. Is there any chance you can do the same and compile for Zephyr's. maybe go +5 either way, I'd really appreciate it as I don't have ISE
Cheers
cornnatron
Dec 12 2011, 12:07 PM
QUOTE(DrZeus @ Dec 12 2011, 10:01 AM)

Wow very interesting. I would like to try different timings on some Zephyr's that just wont glitch no matter what I do. I wonder if it might help. Is there any chance you can do the same and compile for Zephyr's. maybe go +5 either way, I'd really appreciate it as I don't have ISE
Cheers
Ill see what i can do tonight ,at work at the moment
And also i aint got no way to test So thats some thing you have to
Do yourself
cornnatron
Dec 12 2011, 12:26 PM
QUOTE(DrZeus @ Dec 12 2011, 10:01 AM)

Wow very interesting. I would like to try different timings on some Zephyr's that just wont glitch no matter what I do. I wonder if it might help. Is there any chance you can do the same and compile for Zephyr's. maybe go +5 either way, I'd really appreciate it as I don't have ISE
Cheers
Ill see what i can do tonight ,at work at the moment .
And also i aint got no way to test zephyrs .
So thats some thing you have to do yourself.
One last thing wich file do you use normaly on the zephyr?
cornnatron
Dec 12 2011, 10:52 PM
allright as requested
diff zephyr timming files
zephyr cpld files
dokworm
Dec 13 2011, 01:27 AM
QUOTE(cornnatron @ Dec 12 2011, 12:26 PM)

Ill see what i can do tonight ,at work at the moment .
And also i aint got no way to test zephyrs .
So thats some thing you have to do yourself.
One last thing wich file do you use normaly on the zephyr?
Wow, thanks, you should really start a new thread for this, everyone would be better off doing this rather than messing with unreliable coils of wire or add-on boards.
DrZeus
Dec 13 2011, 05:21 AM
QUOTE(cornnatron @ Dec 12 2011, 09:52 PM)

allright as requested
diff zephyr timming files
zephyr cpld filesThanks heaps mate, very helpful!
I can't test tonight cause i'm off to see the Foo Fighters!
Will report back once I get some time to test.
cheers
cornnatron
Dec 13 2011, 03:05 PM
No probs Drzeus
as to the new topic ill have a look after i get some reports
Back on how the files work for. People but
Then again i do think ill get more reports on it in its own topic
But i have to compile jasper and falcon files first
Havent made those jet
Cheers corn.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.