Coco 3 Plus for MiSTer
Coco 3 Plus extends CoCo3_MiSTer
with a configurable four-slot Multi-Pak, an original-firmware Sound & Speech
implementation, a reorganized menu, and clock/reset/memory timing repairs.
The original upstream Git history is retained; the Plus implementation is one
consolidated commit on main. Other original branches and tags remain available.
The Computer menu entry is Coco 3 Plus. Media lives in
/media/fat/games/coco3plus, independently of the stock CoCo3 core.
This targets a DE10-Nano MiSTer with the upstream-required 128 MB SDRAM module.
The separate original DE1 port is outside this repository.
Build and install on Windows
Install Git, Python 3.10+, and Quartus Prime Lite 17.0.2 Build 602 with Cyclone V device support. From this checkout in PowerShell:
.\windows\Setup-Tools.ps1
.\windows\Build-ROMs.ps1
.\windows\Build-FPGA.ps1 -QuartusSh C:\intelFPGA_lite\17.0\quartus\bin64\quartus_sh.exe
# Place your separately obtained SSC ROMs in roms\ssc first.
.\windows\Install-MiSTer.ps1 -Load
The installer prompts for an IP address or hostname and uses your existing passwordless SSH access. It preserves the stock core, existing games and saved Plus configuration, and backs up replaced files. Save/quit the running guest before installation: installation returns to the MiSTer menu.
The ROM build downloads pinned ToolShed assembly and uses native Windows LWASM; it does not depend on another emulator checkout, Bash, WSL or CMOC. SSC's two chip ROMs are separate inputs, ignored by Git and never downloaded by setup.
- Windows toolchain and reproducible builds
- Install, copy release files, first boot and rollback
- Features and hardware behavior
- Complete menu tree and operating notes
- Bug fixes: causes, implementation and checks
- Validation results and explicit limits
- Licenses and component provenance, attribution
- Required ROM inputs
- Standalone SD-image direction
Package-Release.ps1 produces a checked FAT-volume overlay for copying onto an
existing MiSTer card. The same payload is the basis for a future dedicated boot
image. An overlay alone is not a bootable image; MiSTer Linux and bootloader files
also reside on the SD card.
Timing results apply to the documented SDRAM/board-delay profile. Passing simulation and static timing does not establish electrical compatibility with every SDRAM module or validate every optional physical interface.