BMCoCo-Pi 0.1.0rc3 · Windows setup, Linux console and model downloads.
Troubleshooting
Start by recording your Pi model, running build/date if visible, display/cable, power supply, whether local OSD works, and the exact error. Keep Windows/Linux card-preparation errors separate from a problem after the card is in the Pi. No end-user setup utility is released yet; missing executable/download links are the current project status, not a fault on your computer.
| Symptom | First checks |
|---|---|
| No expected Windows/Linux download | Read availability; source ZIPs are not installers |
| Card not listed by the future utility | Check reader/card connection and identity; never select a system disk instead |
| Administrator access refused | Stop safely; do not bypass device safeguards or format through a second tool |
| ROM missing/wrong size/checksum | Check exact names and paths, extensions and ROM version; renaming is not conversion |
| No picture after power-on | Check power, correct HDMI input/port, display sync and exact-model boot bundle |
| Guest shows corruption or does not boot | Record the screen; verify ROMs, guest selection and bundle before assuming a TV fault |
| TV picture blank after idling | Press/release one key to wake, then type normally; check System's blanking timeout |
| Image stretched/cropped | Compare TV aspect/overscan and guest screenshot; a screenshot does not capture the TV's scaling |
| F12 appears not to work | If blanked, first key only wakes; release/repress. Check keyboard, ownership and OSD state |
| Web page does not load | Use Ethernet, wait for delayed startup/DHCP, find actual router/OSD IP; current build has no Wi-Fi |
| Web controls report busy/unavailable | Exit local OSD; check other controller clients and unfinished file/kernel jobs |
| SD upload exists but software did not start | Upload stores a file; attach supported media under Media, then use its guest load procedure |
| MCX128 chosen but RAM says 20K | Correct base-RAM setting: 128K is separate cartridge RAM |
| MOOH chosen but RAM says 64K | Correct CoCo2 base-RAM setting: MOOH adds separate 512K expansion |
| Gamepad not controlling MC-10 guest | MC-10 controller support is currently OSD navigation only |
| Gamepad stopped after reconnect | Device discovery may renumber; check mappings and release to neutral before retrying |
| Saved profile not used after reboot | Saving and selecting next startup are separate; missing/invalid media can cause baseline fallback |
| New kernel file present but old build shown | Upload, Apply and reboot are separate; inspect the running identity after reboot |
Do not repeatedly power-cycle during SD writes or run a new update over an unknown transaction outcome. Recovery instructions explain the distinction between a lost reply and a verified failed operation.
A useful support report
Provide exact model, release/build identity, PC OS if relevant, the steps that caused the issue, expected/actual behavior and a non-private screenshot/photo. Specify whether the picture is a guest capture, browser screenshot or TV photo. The guest screenshot function does not capture OSD or the whole HDMI output. Never include ROM/media payloads, credentials, private full-card images or unnecessary personal/router details. A public issue tracker is not available yet.
Guide edition: November 2, 2026.