What's new

Tools J-Runner with Extras (Latest Dashboard) - Built in Timings, Bugfixes, and New Features!

  • Thread starter Octal450
  • Start date
  • Views 32,960
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Hi,

Based on there being some interest I decide to post my J-Runner with Extras here to provide for y'all.
This is just the op post, make sure to read my replies for updates once they come!

So what has it?
- Fully working in Windows Vista, 7, 8.x, 10, and 11! No more crashing!
- 17559 Dashboard, 3.21 Dashlaunch, and 1.21 XeBuild support
- Native FTDI Support (xFlasher and squirt)
- SMC+ Support (Super fast glitch cycles without false success resets)
- RGH3 Support
- Added 6717 and 9199 Dash Support for JTAG, GLITCH, GLITCH2, R-JTAG (THX SGCSam SGCSam !) (Supported motherboards only)
- RGH1.2, S-RGH, R-JTOP timings added to Program Timing File menu (see picture)
- Timing Assistant
- Easy Donor Nand Creator
- Tweaked XeLL RELOADED:
----- Displays Console LDV
----- Displays Motherboard type
----- Displays serial number for console and board
----- Fixed USB refresh bug
- Cleanup the UI in general, loads of usability and quality of life improvements
- Loads of various bugfixes all over the place, rewritten code for a more stable experience
- DEVGL Build Support (doesn't include any keys, find them yourself)
- Bigffs Build Support
- AND LOTS MORE!

image.png.9d99aae7b798fa7f2600ca45a43d781a.png
image.png.1f2dc7d23e2a9803ba3ed19197eef255.png


Download Release: [Click here to view this link]
More Details/Screenshots: https://www.realmodscene.com/index....l-built-in-timings-bugfixes-and-new-features/

Kind Regards,
Josh
 
Last edited:
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Hi

Now J-Runner V3.0.0d is available to auto-update. Original links in OP are still the latest
:)


V3.0.0d:
- Added: FTDI support for Xilinx XC2C64A-FG48 for Matrix "small-IC"
- Added: FTDI can now detect and check flash configs and motherboards
- Added: FTDI automatic board type detection on reading/writing
- Added: Query console button works with FTDI now
- Fixed: Cannot write JTAG XeLL bins with FTDI
- Fixed: Bug with timing programming of Zephyr timings
- Fixed: Various bugs and usability issues
- Fixed: Scan IP for console bug
- Changed: Tweaks to included timing files

Kind Regards,
Josh
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
June update 3.0.1 is 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
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
I'm going to give this a go tomorrow and see what happens... Have a jasper I'm taking apart to rgh1.2 for a friend.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Best of luck on your mod! Remember the timing files are built into the Program Timing File menu :smile:
if you run into any issues, let me know so that I can fix them!

Kind Regards,
Josh
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
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
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
Ive been having an issue getting timing files loaded onto my coolrunner chips.
I mean it’s not so much of an issue rather than a process I wasn’t expecting.

Open JRunner, plug in programmer and plus coolrunner into jrunner.
Switch both to program mode using the built in switches.
Write timing files to glitch chip.
Success.
Close the program files from the program itself, flip switches back to normal position, unhook JRP from glitch board. Would try to boot without success (my own fault see below)

But, then trying to do a different timing file the program must be fully closed and restarted otherwise it will put the programmer into a program loop (red AND green lights on) without sending out packets to the coolrunner.

I was having issues with timing files on a falcon mobo last night, was trying to figure out why. Little did I know my ftu trace was cold soldered and wound up messing up the Hana pad during troubleshooting which were my own faults. I’m buying defective consoles (fats with bad disc drives) so it’s been a learning process for me. Just thought I’d share this little bit of info with you, maybe it can be an update in the future to refresh the connection in the tool though I doubt this happens often to those who have successfully glitched consoles in the past.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
But, then trying to do a different timing file the program must be fully closed and restarted otherwise it will put the programmer into a program loop (red AND green lights on) without sending out packets to the coolrunner.
Sorry, I cannot reproduce this. Please make sure any anti-viruses or such exclude J-Runner, there may be a false positive.

I tested a JRP, NAND-X, and xFlasher and everything programs repeatedly. So I'm not sure why you have this issue. (and it hasn't been reported by others either)

Kind Regards,
Josh
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
Sorry, I cannot reproduce this. Please make sure any anti-viruses or such exclude J-Runner, there may be a false positive.

I tested a JRP, NAND-X, and xFlasher and everything programs repeatedly. So I'm not sure why you have this issue. (and it hasn't been reported by others either)

Kind Regards,
Josh
I can try again tonight and send my logs or something, maybe my coolrunner chip is toasted? If there’s any way to tell that by metering out the points or what not.
The issue was trying to program the glitch timing back to back without closing JRunner fully… it would get stuck without sending the packets out to my coolrunner - but it’s easy to work around as I just needed to unplug everything and relaunch JRunner then plug it all back in.
 
S

scottD1503

Enthusiast
Messages
57
Solutions
2
Reaction score
17
Points
100
Ive been having an issue getting timing files loaded onto my coolrunner chips.
I mean it’s not so much of an issue rather than a process I wasn’t expecting.

Open JRunner, plug in programmer and plus coolrunner into jrunner.
Switch both to program mode using the built in switches.
Write timing files to glitch chip.
Success.
Close the program files from the program itself, flip switches back to normal position, unhook JRP from glitch board. Would try to boot without success (my own fault see below)

But, then trying to do a different timing file the program must be fully closed and restarted otherwise it will put the programmer into a program loop (red AND green lights on) without sending out packets to the coolrunner.

I was having issues with timing files on a falcon mobo last night, was trying to figure out why. Little did I know my ftu trace was cold soldered and wound up messing up the Hana pad during troubleshooting which were my own faults. I’m buying defective consoles (fats with bad disc drives) so it’s been a learning process for me. Just thought I’d share this little bit of info with you, maybe it can be an update in the future to refresh the connection in the tool though I doubt this happens often to those who have successfully glitched consoles in the past.
iv had the this issue before, normally unplugging the jrp before trying to program fixes the issue.
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
iv had the this issue before, normally unplugging the jrp before trying to program fixes the issue.
I have a habit of leaving it plugged in though, but yeah that works as a work around - a great work around actually.
My smooth brain sometimes forgets though, then I fear I may have corrupted something in the coolrunner.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Strange, I don't have that problem. I can program over and over and over in my JRP without fault.

Kind Regards,
Josh
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
Strange, I don't have that problem. I can program over and over and over in my JRP without fault.

Kind Regards,
Josh
Judging off my experience in my thread with a potentially faulty coolrunner, I want to say the issue is my end entirely.
As long as I cycle power on the JRP (using the button built in) it seemed to work tonight flawlessly.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Please let me know if it happens again and I will investigate further.

Thanks!

Kind Regards,
Josh
 
Lucky

Lucky

Classique is best
Super Moderators
Premium
Scaling the Mountain Beginning of An Odyssey Bright Idea
Messages
4,492
Solutions
13
Reaction score
1,599
Points
1,585
Please let me know if it happens again and I will investigate further.

Thanks!

Kind Regards,
Josh
Sure thing, I’ll include my logs as well. Maybe even a video showing it, should it happen again. Fingers crossed I won’t need to do more than one timing file on a new coolrunner.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Hello,

Sorry for so quick update again. But, many fixes to the xFlasher implementation post release of the tool!

V3.0.2b:
- Added: xFlasher support for Xilinx XC2C64A-VQ100 for Matrix "Super-Big-IC"
- Added: Better grabbing of CPLD type for xFlasher
- Added: Ability to abort xFlasher SPI read/write via Esc key
- Fixed: Incorrect display of xFlasher initializing
- Fixed: Post-release bugs with xFlasher implementation
- Fixed: 32-bit xFlasher dependancy detection
- Fixed: Crashing issue with xFlasher and some antivirus software
- Fixed: Various bugs and usability issues

FYI: xFlasher does not support Windows XP due to driver problems. Please use Windows Vista SP2 or later.

Kind Regards,
Josh
 
XeX Sinister

XeX Sinister

Newbie
Messages
9
Reaction score
0
Points
35
NI9lIF0.png


The image is from V3.0.2b, checked permission and ownership, nothing and there is no log since the program has yet to actually execute it's own code.

I can still run an older version V3.0.0c without any issue whatsoever.
 
Octal450

Octal450

Specialist
Specialist
Messages
220
Solutions
6
Reaction score
140
Points
165
Sound like you antivirus detect it falsely. Microsoft thinks J-Runner is a KeyGen for some reason.

Please exclude it from your AntiVirus Defender and try again.

Kind Regards,
Josh
 
XeX Sinister

XeX Sinister

Newbie
Messages
9
Reaction score
0
Points
35
Yep, it seems that it was windows anti virus slapping me with a false positive.
 
Top Bottom
Login
Register