Differences between dragon and coco detectable from the cart slot
Posted: Sat Feb 22, 2025 8:37 am
Hello Everyone
This is my first post here, so pardon me if i have incorrect etiquette.
I am looking for tips and ideas for how to tell the difference between a dragon and a coco that are detectible from the cart slot.
We are working on a cart that has a raspberry pi pico on it emulating a ROM, and would like to not require a jumper to select coco or dragon compatibility. Or worse yet, a separate software load per platform!
There is an obvious solution where we monitor bus transaction and look for sequences from known boot code per platform, but this seems like it would possibly be problematic for implementation.
Are there any known, easily detectible from simple sampling of a few signals, ways that people have discovered?
Any ideas appreciated!
Thanks,
Bill Athing
This is my first post here, so pardon me if i have incorrect etiquette.
I am looking for tips and ideas for how to tell the difference between a dragon and a coco that are detectible from the cart slot.
We are working on a cart that has a raspberry pi pico on it emulating a ROM, and would like to not require a jumper to select coco or dragon compatibility. Or worse yet, a separate software load per platform!
There is an obvious solution where we monitor bus transaction and look for sequences from known boot code per platform, but this seems like it would possibly be problematic for implementation.
Are there any known, easily detectible from simple sampling of a few signals, ways that people have discovered?
Any ideas appreciated!
Thanks,
Bill Athing