+CyranoJ Posted September 20, 2014 Share Posted September 20, 2014 Hi Just wondering if anyone (Tursi?) has modified JCP to allow multiple skunkboards connected to a single PC? I should get my second skunk shortly, and it would be nice to have two build scripts, one to target my K-model jaguar, and one to target my M-model jaguar. On that note, anywhere cheap(ish) to get a Jaguar powerpack (that won't blow a skunkboard up) mailed international? 1 Quote Link to comment Share on other sites More sharing options...
Zerosquare Posted September 21, 2014 Share Posted September 21, 2014 I've looked at the source code for jcp. It looks like there's no explicit support for multiple Skunkboards connected for the same PC; it will use whichever happens to be first in the USB devices list. But improving that appears to be pretty simple. The relevant code is in the findEZ() function. It enumerates all USB devices until it finds one whose Vendor ID/Product ID couple matches the Skunkboard's, then opens the device. To support multiple Skunkboards, I would add a command-line parameter to specify the serial number of the board you want to use, and insert an additional condition in findEZ() (after the device had been opened) to check that the serial number is the correct one, by reusing code from DoSerialInfo(). If so, it would proceed as usual; if not, it would close the device using usb_close(udev), and resume the scan. 4 Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted September 21, 2014 Author Share Posted September 21, 2014 It looks like there's no explicit support for multiple Skunkboards connected for the same PC; it will use whichever happens to be first in the USB devices list. But improving that appears to be pretty simple. That might be good enough - I guess only one Jag will be powered up at a time and in receive mode. Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted September 21, 2014 Share Posted September 21, 2014 Hi, Maybe jcp can be started with a parameter which usb port to use. Then launching jcp in two seperate sessions This would allow to run it I guess. This way you could launch each jcp for each jaguar when you want no need to turn on/off one of those. Quote Link to comment Share on other sites More sharing options...
Goochman Posted September 22, 2014 Share Posted September 22, 2014 Maybe while your in there add a command to display 'available skunks' with the respective ID you'd need to pass to program. Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted September 22, 2014 Share Posted September 22, 2014 yes you can scan ID (serial) and USB port, but not everytime you start jcp because if one is transfering and then the second jcp is started it could interfere. so your solution only would work if you use one skunk at a time but the idea was not to turn both jaguars off, then you must do it with another approach. So better do it this way. Option in JCP to scan skunk serial and usb port nr. The use a config file The make 2 batchfiles. In the batchfile type: START JCP <config file> normal parameters for JCP <skunkfile> The second batchfile aswell, both will launch as seperate thread so they will not interfere. In the config file - serial nr skunkboard - usbport nr. That's all I think. Quote Link to comment Share on other sites More sharing options...
Zerosquare Posted September 22, 2014 Share Posted September 22, 2014 yes you can scan ID (serial) and USB port, but not everytime you start jcp because if one is transfering and then the second jcp is started it could interfere.I don't know the inner workings of libusb, but there's probably a way to know that a device has already been opened by another process, and exclude it from the list. Using USB port numbers is less reliable than using the Skunkboard's serial number, because they're arbitrary and can change if you plug/unplug devices. Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted September 22, 2014 Share Posted September 22, 2014 But connecting them on one pc why would you want to change ports ? Connected = connected... Quote Link to comment Share on other sites More sharing options...
Zerosquare Posted September 22, 2014 Share Posted September 22, 2014 I'm not sure libusb guarantees the port numbers it reports are consistent if you plug/unplug other devices (USB keys, etc.) Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted September 23, 2014 Share Posted September 23, 2014 Ah ok thats what you mean sorry didnot understood correctly. Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted September 23, 2014 Share Posted September 23, 2014 (edited) I would love to see a patched jcp if someone get it to work great idea... Edited September 23, 2014 by TXG/MNX Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted October 3, 2014 Share Posted October 3, 2014 Anyone looked if this could be done i would be very interested in it Quote Link to comment Share on other sites More sharing options...
JagChris Posted October 4, 2014 Share Posted October 4, 2014 Hi Just wondering if anyone (Tursi?) has modified JCP to allow multiple skunkboards connected to a single PC? I should get my second skunk shortly, and it would be nice to have two build scripts, one to target my K-model jaguar, and one to target my M-model jaguar. On that note, anywhere cheap(ish) to get a Jaguar powerpack (that won't blow a skunkboard up) mailed international? What are the concerns between these two models of Jaguars that you need two build scripts? Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted October 4, 2014 Author Share Posted October 4, 2014 What are the concerns between these two models of Jaguars that you need two build scripts? The GPUs have different bugs. 1 Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted October 4, 2014 Share Posted October 4, 2014 Indeed so this would be very usefull... Otherwise you need to swap the skunkboard everytime or plug/unplug usb everytime Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted January 30, 2015 Share Posted January 30, 2015 The GPUs have different bugs. Any documentation of these bugs for each type of console? Quote Link to comment Share on other sites More sharing options...
ggn Posted January 30, 2015 Share Posted January 30, 2015 Yes. Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted January 31, 2015 Share Posted January 31, 2015 (edited) Could you point me to the documentation please where the difference between gpu bugs in the K and M consoles are written. Edited January 31, 2015 by TXG/MNX Quote Link to comment Share on other sites More sharing options...
+CyranoJ Posted January 31, 2015 Author Share Posted January 31, 2015 Could you point me to the documentation please where the difference between gpu bugs in the K and M consoles are written. I have to ask... why? Have you written anything.... .....that has a bug due to hardware? 1 Quote Link to comment Share on other sites More sharing options...
sh3-rg Posted January 31, 2015 Share Posted January 31, 2015 (edited) Could you point me to the documentation please where the difference between gpu bugs in the K and M consoles are written. Differences were posted on jagware.org or here in the past, searching jagware might be the best bet I recall one instance when I gave a modded Jaguar to CJ. We found Project One would black screen on it, I kind of half remember something about that massive gpu object on the title screen. All I really remember was CJ complaining that I must have hurt the Jaguar when I modded it I just can't remember, it was so long ago while working on only the second thing we attempted, dark days when using the force was the only way Edited January 31, 2015 by sh3-rg 2 Quote Link to comment Share on other sites More sharing options...
TXG/MNX Posted January 31, 2015 Share Posted January 31, 2015 I asked because that info about diff between m & k was not mentioned in the dev docs i got. Quote Link to comment Share on other sites More sharing options...
sh3-rg Posted January 31, 2015 Share Posted January 31, 2015 I asked because that info about diff between m & k was not mentioned in the dev docs i got. IIRC the differences were not documented, hardly surprising given what people say regarding the tech ref etc. Maybe Atari covered themselves with a few Thou Shalt Nots or maybe some things just never became a problem until someone tried to do a little tinkering in less-explored corners of the Jaguar... or maybe CJ just imagined it all thanks to the power of rum. 4 Quote Link to comment Share on other sites More sharing options...
dilinger Posted March 12, 2015 Share Posted March 12, 2015 Hello, Just wish to know if one of you have checked this jcp (Win32 or x64) update I did some weeks ago and available at: http://3do.cdinteractive.co.uk/viewtopic.php?f=35&t=3606 You have to enter your USB port (0, 1, etc.) to select the Jaguar. At that time, I didn't think about the use of the Skunkboard serial (but I may add it in the future). Thanks, 5 Quote Link to comment Share on other sites More sharing options...
sh3-rg Posted March 12, 2015 Share Posted March 12, 2015 (edited) Hello, Just wish to know if one of you have checked this jcp (Win32 or x64) update I did some weeks ago and available at: http://3do.cdinteractive.co.uk/viewtopic.php?f=35&t=3606 You have to enter your USB port (0, 1, etc.) to select the Jaguar. At that time, I didn't think about the use of the Skunkboard serial (but I may add it in the future). Thanks, Probably not the best place to post releases, looks like you have an audience of one (I noticed only one download of the 32-bit version before I took a copy of the 64-bit one, that would be the one other person posting in the thread I assume). Thanks for the release. Edited March 12, 2015 by sh3-rg 2 Quote Link to comment Share on other sites More sharing options...
dilinger Posted March 12, 2015 Share Posted March 12, 2015 Probably not the best place to post releases, looks like you have an audience of one (I noticed only one download of the 32-bit version before I took a copy of the 64-bit one, that would be the one other person posting in the thread I assume). Thanks for the release. I think I have an explanation about the number of downloads. When I updated / edited the message in my original thread, it did reset the download number to 0. I updated my original message to avoid to stack pile versions in the thread. This jcp version is not the 1st one I did; the 1st one took more downloads but it had a Windows XP compatibility problem (which was solved in the current release). If you find an issue, please let me know, and I will look at it. In the web site, there is a also a discussion about M68K debugging (Code::Blocks, GDB, jserve & Skunkboard) and an updated jserve version (a new one is in progress but I need time to test it more, and I may include the Skunkboard detection version - which may be more user friendly that to give an usb port). Regards, 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.