joeyaage Posted November 25, 2022 Share Posted November 25, 2022 My JagGD is Firmware V1.10 Menu V1.07 ASIC V1.07 Stub V1.03 This time I plugged in the GD, windows searches for drivers and finds them so windows thinks the device is installed and working. Jaggd.exe -r returns with "Jaguar Gamedrive not connected). Here is what is installed... when I run zadig, I get this... If I list all devices in options, then I can select 'Interface 1' and it is already installed but not with WCID (odd..). I tried to install this as well. After a long wait it is seconds from aborting and says 'successfully installed driver' but it shows "Driver (NONE)". Tried a reboot but makes no difference. All I get is 'Jaguar Gamedrive not connected" from jaggd.exe. 1 Quote Link to comment Share on other sites More sharing options...
42bs Posted November 25, 2022 Share Posted November 25, 2022 Interface 0 is the "command" interface, here you should install WinUSB driver. Interface 1 is a serial port and the driver should be "usbser". 2 Quote Link to comment Share on other sites More sharing options...
Ericde45 Posted November 30, 2022 Share Posted November 30, 2022 On 11/18/2022 at 5:57 PM, SainT said: I've used Tera Term in the past, but any terminal will do. The JagGD just presents itself as a USB serial port. working fine, i added nice strings printing on my PC , coming from GD, for debug purpose. a debugger would be the final master piece of this great product ! 2 Quote Link to comment Share on other sites More sharing options...
42bs Posted December 19, 2022 Share Posted December 19, 2022 @SainT did you consider a MacOS (preferably M?) version? Quote Link to comment Share on other sites More sharing options...
42bs Posted December 19, 2022 Share Posted December 19, 2022 @SainT ha, not needed, just run jaggd via Parallels+win11 on my M1 Mac 🙂 1 Quote Link to comment Share on other sites More sharing options...
SainT Posted December 19, 2022 Author Share Posted December 19, 2022 I don't use a Mac, so it's not something I'd do myself. The source is available, though, if anyone wanted a Mac version -- https://github.com/RetroHQ/JagGDCmd Quote Link to comment Share on other sites More sharing options...
42bs Posted January 16 Share Posted January 16 Could compile open_jaggd on my M1 MacBook. Works like charm 🙂 Thanks @cubanismo ! 2 1 Quote Link to comment Share on other sites More sharing options...
42bs Posted January 20 Share Posted January 20 Update: Added "-rr" and "-uxr" flag to open_jaggd: https://github.com/42Bastian/open_jaggd 3 1 Quote Link to comment Share on other sites More sharing options...
+cubanismo Posted January 21 Share Posted January 21 Glad it's working. I'll take a look at the patches. OT, but curious if you've tried my Mac Skunkboard/JCP installer package on your M1. They're built with ARM support, but I've no way to test it. Quote Link to comment Share on other sites More sharing options...
42bs Posted January 21 Share Posted January 21 9 hours ago, cubanismo said: Glad it's working. I'll take a look at the patches. OT, but curious if you've tried my Mac Skunkboard/JCP installer package on your M1. They're built with ARM support, but I've no way to test it. Not yet, but now that I know I will. Quote Link to comment Share on other sites More sharing options...
+cubanismo Posted February 2 Share Posted February 2 I'm having some trouble testing the '-e' option, and '-uxr'. I had assumed usage like this would allow me to run T2K with an EEPROM where I'd previously saved game data: jaggd -rd -e "Tempest 2000.e2p" -uxr "Tempest 2000.j64" but the above always just reboots to a red screen of death. "Tempest 2000.e2p" is a file in the root directory of the SD card, and "Tempest 2000.j64" is a local file on my computer. If I break it out like this: jaggd -rd jaggd -e "Tempest 2000.e2p" jaggd -uxr "Tempest 2000.j64" Or this: jaggd -rd jaggd -u "Tempest 2000.j64" jaggd -e "Tempest 2000.e2p" jaggd -xr The game usually starts (Not always, still red screens quite often), but I don't see my EEPROM data (No high scores, no "keys" to start from). The same .e2p file works fine if I launch from the GD's menu. Am I misunderstanding how the EEPROM option works? In general, running multi-part commands like: jaggd -rd -uxr <romname> fails very frequently, as in more often than it works. The upload appears to succeed, but it just launches to a red screen of death. This is similar to the experience I had with my work-around "reboot" ROM posted earlier. Is there some instability in the file transfers or a race somewhere between finishing a transfer and executing the next command or something? I see a "Sleep(1500)" was added in the main program after a reset-to-stub operation, and a "Sleep(500)" after an upload command, but things still seem generally unstable unless I manually space commands out, and even that doesn't always help, so I'm concerned there's a general issue with the transfer robustness, some buffer being unflushed, or something of that nature lurking somewhere deeper, like in the firmware. As-is, the "execute via reboot" functionality isn't usable for me, and I can't figure out how the EEPROM stuff is supposed to work. Note launching ROMs from the SD card using the menu works 100% of the time, so the card in general seems reliable. The issues seem specific to the command line tools/USB path, which unfortunately is my main use case for the GD (rapid iterations while developing). 1 Quote Link to comment Share on other sites More sharing options...
SainT Posted February 2 Author Share Posted February 2 I know CJ has had some issues with red screening -- this will be due to some data corruption somewhere on the upload. And, yes, you are right there is some instability somewhere which I've not been able to sort yet. I think there is still some issues with eeprom as well. This is an area I need to look at again once the 7800GD is finished. It will be nice to have a break and get back to this. 2 1 Quote Link to comment Share on other sites More sharing options...
+cubanismo Posted February 26 Share Posted February 26 I still experience the stability issues, but in the meantime I've finished porting the new functionality in the RetroHQ jaggd.exe v1.0.1 release to Open JagGD and released an equivalent v1.0.1 for Linux and MacOS users (@42bs mostly): https://github.com/cubanismo/open_jaggd/releases/tag/v1.0.1 4 1 Quote Link to comment Share on other sites More sharing options...
42bs Posted February 26 Share Posted February 26 Works nice and easy. Thanks for adding -wf, no more switching to DOS 🙂 1 Quote Link to comment Share on other sites More sharing options...
+BitJag Posted February 26 Share Posted February 26 14 hours ago, cubanismo said: I still experience the stability issues, but in the meantime I've finished porting the new functionality in the RetroHQ jaggd.exe v1.0.1 release to Open JagGD and released an equivalent v1.0.1 for Linux and MacOS users (@42bs mostly): https://github.com/cubanismo/open_jaggd/releases/tag/v1.0.1 Thank you! I may actually start using my GD over my skunkboard now. 2 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.