|
Post by dshadoff on Apr 22, 2022 22:32:00 GMT
Due to one of the threads in this forum, I decided to look into the USB download capability of the Turbo Everdrive (v2.x boards) today. For anybody familiar with sending ROMs to their Everdrive via USB, you will know that there is a single executable file "turbo-usb2.exe" on the krikzz forums: krikzz.com/pub/support/turbo-everdrive/v2/usb-tool/Today, I decided to look into the protocol in use for that file transfer program, and it turned out to be really easy... so I wrote a python program which should be able to do the same thing, but across multiple platforms. For now, I've only tested it on Windows, and I haven't tested the special "sliced" 3 megabit files specifically, but it seems to be working for the files I have tested with. Please check out the GitHub repository I've made here: github.com/dshadoff/PCE_TurboEverdrive_USBAlso, since USB-enabled Turbo Everdrive carts are not particularly common, I've given an overview of what needs to happen in order to USB-enable them.
|
|
|
Post by gredler on Apr 22, 2022 22:45:06 GMT
That's awesome thanks! I use turbo-usb2.exe all the time, and cherish my ted2 with usb, but having the ability to create another is a great possibility I hope to follow up on so I can stop shifting my ted between systems to test across varying hardware configs. Am I understanding you correctly when you say that this is now a native python application rather than cmd executable? I might switch to this anyways because my windows deployments are different between my desktop and laptop and have to keep a uncomitted git script on either one or the other to accomodate; staying within python and not relying on cmd would be a good workflow efficiency improvement
|
|
|
Post by dshadoff on Apr 22, 2022 22:59:24 GMT
Yes, this is native python which means: - you may need to ‘pip’ to get the serial driver, but it’ll be fine - you’ll still need the FTDI drivers, but you have these installed for dozens of other devices - since I don’t try to autodetect the port, you will need to put it in the command line; the port naming system is different on linux than Windows, and the numbering will vary from machine to machine - you will need to type ‘python ‘ at the beginning of the line unless you do python-to-Exe on it
oh, and I guess if you have multiple everdrives you can send different files to each one because you can specify which port… but I suspect nobody will use this feature.
|
|
|
Post by gredler on Apr 22, 2022 23:23:10 GMT
Wow multiple everdrives is something I hadn't considered, but I do test builds across a express pce stock pce duo r rgb modded, so hypothetically I could set that up but would have to buy and mod two more teds which seems unlikely given the chip climate at the moment. Thanks for this, I'll definitely try to integrate this into my build commands as I try to transition away from cmd for those right now I compile huc then pipe the rom into turbo2usb and launch in emulator when I run my build hotkey
|
|