Support using a ModRetro Chromatic as a dumper - #128
Conversation
Requires https://github.com/fredemmott/chromatic_dumper firmware loaded into FPGA RAM, but not ROM.
The official way to get this on Windows is to use msys2 + pacman... not really viable IMO. On the other hand, if i extract modretro's updater and grab ... that works |
|
Oh thanks! I do not own this device and cannot test anything, so I am not comfortable adding it to the main repo for now. But great job nonetheless! |
|
Thanks; for me to continue on this a bit more, is there any documentation on the commands and variables? For example:
|
|
my notes on |
|
My firmware module is planned to be released under GPL soon |
af4372b to
3cf83f3
Compare
|
Not sure how much it helps but have tested and confirmed the following work as expected with this fork:
|
|
I'm leaving this open for visibility that there is an option here, but this specific approach is now a dead end that won't get further development or testing. I have a work-in-progress new approach, building on https://github.com/Lesserkuma/FlashGBX_LK_Firmware/ , and allowing playing + FlashGBX from the same firmware image. |
6446726 to
0272d8e
Compare
Requires https://github.com/fredemmott/chromatic_dumper firmware loaded into FPGA RAM, but not ROM.
If you're interested in taking this, the next step would be to automatically load the firmware with
openfpgaloader. For now, I'm using the gowin IDE to load it before starting FlashGBX.Given that changing cartridges requires turning off the chromatic, turning it on, and loading the firmware again every time, it would probably be best to automatically load it on connect if needed, rather than going through the current firmware update process.
This is a modified copy of
hw_JoeyJr.py