falcon glitches immediately or not at all
Ok everyone time to wrap-up on this, and if there are no other viable lead to resolve then I must come to the conclusion that this specific unit is a difficult one for the coolrunner to glitch.
It is a falcon (cb 5771) and it is glitching only one out of five attempts. When it is glitching then it does so immediately, if not (the 5 other attempts) then it does not glitch at all.
At this point I am left with trying to see if there are any ways to adjust the timing by which the CR glitches the x360.
I feel to have excluded most of the other factors , but any suggestion on what might have been overlooked is welcomed
Coolrunner (note they both work fine in my slim, reprogrammed obviously!!!)
1) Tried two different coolrunner (revB) , so excluded the CR itself
2) tried cap activated/deactivated and switch to phat or slim
3) programmed to falcon
- with Jtagtools,
-also did with nandpro (NandPro xsvf: falcon.xsvf)
Thus excluded the programming of the CR
Electrical level (all soldering done with good equipment, flux, and experience)
1) Wiring
-tried the 2 sets of phat wires included in the two CR
-tried cat 5 wire
-Tried shielded thin coax on blue and green wire (with shield grounded)
-for the R4b24 point, I desoldered the QSB and went to alternate point FT2R2 (no bridging to C3B2)
So excluded the wiring
2) routing
-Blue wire usual below the coils pins, and also tried above the coils pins (running beside the green)
and to the alternate near the the front of the board running the cale under the shroud (as per pic)
-Green usual above the coil pins, and also just under the x-clips, and under the Xclips,
and going the other way behing the fan opening
-Yellow staying near the memory chip, or as much left and as high as possible
So excluded the routing
Image flashed
1) ECC
-prepared one with jtagtools, another with PythonCryto, and another with multiBuilder
-flashed with jtagtools, and also tried with nandpro usb: +w16 image_00000000.ecc
2) Freeboot.bin image ( dash 13604) note that I had excluded this since the ecc was already not glitching
as it should for a falcon. But just to be sure…
-prepared an image with Xebuild, jtagtools, and multibuild
-flashed with both jtagtools, and also rawflash v4
Thus excluded the image
also returned to original nand.bin and disconnected the coolrunner and all is fin so the x360 itself is OK!!!
As mentioned, I am left with what I consider a difficult x360 and trying to see if there are any adjustment to the timing possible to improve this (like the cable length on slim or the +/- adjustment on some other chip)??? or other changes to timing files...
any leads are welcomed, tia, soso
