Octal450 95 Posted May 29, 2021 Hi @ronsonol Glad you enjoy. All X360ACE files uses 150 MHz, but we can get 300 MHz by process on the rising and falling edges of the clock to get more precision. zephyr_150_E_1_L_1 = timing 27451 length 1 @ 150 MHz @ 300 MHz 54902 length 2 So if zephyr_150_E_1_L_1 works you should also have luck on ZE_L_0.6_T_68.7 or perhaps ZE_L_0.5_T_68.7 in my new release. (in J-Runner too) You can tune there a bit more precisely. The SMC+ for Falcon/Zephyr is not as fast as Jasper/Slim because those consoles take longer due to larger bootloaders. It will decrease the timeout from AF to 8A. Watch closely and you will notice. The reason the log is different as for SMC+, it builds in the SMC so the XeBuild does not need to patch it. But for without, the SMC from the nand is used and thus it must be patched for Glitch. Normal. Kind Regards, Josh Quote Share this post Link to post Share on other sites
ronsonol 1 Posted May 29, 2021 Thanks Josh, i appreciate the reply. Actually it was timing file zephyr_150_E_2_L_1.xsvf that I used successfully. Sorry I miss typed and just now corrected that in my last post. Also, thanks for looking at the smc+ info. I didn't know how to interpret the log differences, thought might be a bug or that the smc+ wasn't being applied. Quote Share this post Link to post Share on other sites
Octal450 95 Posted May 29, 2021 zephyr_150_E_2_L_1 = timing 27452 length 1 @ 150 MHz @ 300 MHz 54904 length 2 So if zephyr_150_E_2_L_1 works you should also have luck on ZE_L_0.6_T_69.3 or perhaps ZE_L_0.5_T_69.3 in my new release. (in J-Runner too) Kind Regards, Josh Quote Share this post Link to post Share on other sites
ronsonol 1 Posted May 29, 2021 Thanks again. I definitely tried those first as they were part of your recommendations. I tried them again and still not working. So not sure what's different about zephyr_150_E_2_L_1. While having, by far, the longest glitch times of all the consoles I've done, at least the Zehpyr is working, maybe 7 to 15 attempts and occasionally not at all. Quote Share this post Link to post Share on other sites
Octal450 95 Posted May 30, 2021 Hi @ronsonol INTERESTING... maybe for some reason your ace doesn't like 300mhz counting... (weird crystal?) If I go build you a file off the 150 MHz instead would you try it for me? Kind Regards, Josh Quote Share this post Link to post Share on other sites
ronsonol 1 Posted May 30, 2021 @Octal450 Absolutely, with the amount of testing you do for us it's the least I can do. Thanks! Quote Share this post Link to post Share on other sites
Bazatree 3 Posted June 1, 2021 On 5/23/2021 at 6:58 PM, Octal450 said: I don't think J-Runner knows what to do with 64MB small block images. I will look into this at some point in the future. Kind Regards, Josh Would be magnificent. If you want, I can donate 64mb XDK nand with CPU key. Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 1, 2021 @Bazatree No need, I can use from my XDK. But thanks! @ronsonol Thanks, I will have the file for you soon - just a bit busy rn. Kind Regards, Josh Quote Share this post Link to post Share on other sites
ronsonol 1 Posted June 2, 2021 @Octal450 No worries take your time, the zepyhr isn't going anywhere, will test when you are ready. I am also in the middle of a battle with a Jasper BB that might be glitching but not showing video. Fun times. Thanks. Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 8, 2021 @ronsonol Here: https://mega.nz/file/TQMl1QLI#kWMv2BRHFMI-ynnPjc4qFkwTNre1_O3tNIJDzB0AJYM Try this. Should work. If it does I'll make a few 150's to tune more. Kind Regards, Josh 1 Quote Share this post Link to post Share on other sites
ronsonol 1 Posted June 8, 2021 59 minutes ago, Octal450 said: @ronsonol Here: https://mega.nz/file/TQMl1QLI#kWMv2BRHFMI-ynnPjc4qFkwTNre1_O3tNIJDzB0AJYM Try this. Should work. If it does I'll make a few 150's to tune more. Kind Regards, Josh @Octal450 Awesome. It works! I think it might be working better than the one I was using before - but it's at least on par. Hard to tell with limited testing over my lunch hour. I only tried a few attempts so far; To the dash 12, 6 and 4. To Xell 4, and 3. So it seems my ace chip is only happy with the 150's. Thanks for the help. Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 8, 2021 @ronsonol Great! I will batch compile a bunch of 150s and add to the pack. Maybe you can better result. You get mostly short or long third blinks? Kind Regards, Josh Quote Share this post Link to post Share on other sites
ronsonol 1 Posted June 8, 2021 @Octal450 I think I mostly get short third blinks. When I see a long third blink, it tends to glitch successfully just after that one. Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 8, 2021 @ronsonol Try: https://drive.google.com/file/d/1o87_T6MZ5uyoQ8C1hy_tBdCOKHXbI3kx/view?usp=sharing Added 150s. Try the 0.5s. Sorry only those values can be made. Adjustment is only by integer in the code and cannot be inbetween, at lower freq less precision for adjustment. Kind Regards, Josh 1 Quote Share this post Link to post Share on other sites
ronsonol 1 Posted June 8, 2021 @Octal450 Thanks for the updated pack, it's nice to have some options in the 150s. I'll try them and settle on the one that works best. I really appreciate your help. Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 14, 2021 My pleasure @ronsonol! Btw, the OpenXenium programming should be available in one of the next updates. Kind Regards, Josh Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 27, 2021 Hello, This months' update 3.0.1 is now released to autoupdate. Changelog: V3.0.1: - Added: XeBuild and Dashlaunch version info - Added: F3 and F4 shortcut keys to open Program Timing File and Custom Nand Args - Added: Updater now shows changelog - Added: xFlasher can now handle Xenon/Zephyr/Falcon 64MB (Devkit) NANDs - Added: 0 Fuse DEVGL building options - Fixed: Cannot write ECCs via Custom Nand Args with xFlasher - Fixed: Glitch ECC made on 14699 and older NAND even if Glitch2 is selected - Fixed: Various bugs and usability issues - Fixed: Buggy and bad handling of hack type radio buttons - Fixed: Zephyr radio buttons didn't properly deselect other timing groups - Fixed: Patching or extracting NANDs doesn't save to working folder - Fixed: Name of XC2C64A showing as XC2C64 - Changed: Creating NAND from scratch does not require an SMC.bin if using Glitch2 CR4 or SMC+ SMCs - Changed: Made xFlasher detect motherboards faster - Changed: Huge improvements to COM Port Monitor - Changed: Cleanup some UI elements - Changed: Updates to some included timing files Noticeable change in behavior are: Timing File Programming menu opens to the selected console's page automatically, you can now use CR4 and SMC+ for Glitch2m images, and a totally new com monitor. A silent change is that we *should* be able to Program OpenXeniums via xFlasher (or squirt) now, but I can't test it quite yet. Kind Regards, Josh Quote Share this post Link to post Share on other sites
Bazatree 3 Posted June 27, 2021 Thanks for the update! 1 Quote Share this post Link to post Share on other sites
Octal450 95 Posted June 27, 2021 My pleasure! Kind Regards, Josh Quote Share this post Link to post Share on other sites
mafia4 0 Posted July 1, 2021 @Octal450 Hi Josh, Can you add blackcats Xell to the Jrunner ??? Its very useful for winbond super slims. Quote Share this post Link to post Share on other sites
Octal450 95 Posted July 1, 2021 Hi @mafia4 The included XeLL and ECCs already support winbond 2k E slims (I've done many of em). Reminder that the only thing the Winbond patches do is updated the CBB bootloader as the original one for RGH2 (13121), and doesn't know how to deal with 2k winbond ram (slim S winbond ram is knows how to do though). It updates to the 13182 CBB. However, the latest version of the XeLL ECCs support this and thus special XeLLs for Winbonds is no longer needed. I may recompile the Glitch2 ECCs though with the updated XeLL used in the XeBuilds though. Kind Regards, Josh Quote Share this post Link to post Share on other sites
grpracing 2 Posted July 8, 2021 I just wanted to add my thanks for all the hard work put into this. Due to the resurgence im gonna glitch some slims. Been using my bb jasper for 10 years on a coolrunner. 1 Quote Share this post Link to post Share on other sites
Octal450 95 Posted July 8, 2021 My pleasure. Hope you enjoy. Kind Regards, Josh Quote Share this post Link to post Share on other sites
Octal450 95 Posted July 15, 2021 July Update released to auto-update. V3.0.2: - Added: Totally redone xFlasher integration with custom SPI DLL - Added: xFlasher now shows blocks during read/write and proper progress - Added: xFlasher alerts user when trying to write a eMMC image in SPI mode - Added: xFlasher alerts user when trying to program a timing in eMMC mode - Added: Clean SMC building option for Retail and DEVGL - Added: Support for the final xFlasher product - Added: Support XDKbuild - Added: Improved updater - Added: Automatic detection of xFlasher dependencies - Fixed: Invalid hack types not greyed out after setting board type - Fixed: Zephyr timing info - Fixed: Buggy and bad handling of Winbond 2K radio buttons - Fixed: Various bugs and usability issues - Changed: Updater now shows download progress - Changed: Fixed dashlaunch XeBuild settings This release is out a little early in order to properly support the final xFlasher product. Shoutout Mena to who figured out how to get the SPI library to compile properly -> it was broken when we got it, as well as for finding the xFlasher speed boost! Shoutout Xvistaman2005 for XDKbuild. Shoutout Element18592 for the xFlasher, its great hardware! Kind Regards, Josh Quote Share this post Link to post Share on other sites
Bazatree 3 Posted July 15, 2021 Thanks for the update! 1 Quote Share this post Link to post Share on other sites
