Why Most MiSTer Guides Are Written for the Wrong Country
The first time I powered on a MiSTer, I’d spent three weeks sourcing parts, two evenings soldering headers, and roughly forty-five minutes convincing myself the DE10-Nano wasn’t going to explode. It booted fine. Then I loaded Sonic the Hedgehog on the MegaDrive core, and something was immediately, unmistakably wrong. The music was running fast. Not slightly fast — noticeably fast, like someone had nudged the pitch up a semitone and trimmed the tempo. I sat there for a good ten minutes assuming I’d assembled something incorrectly before realising what had actually happened: I’d followed an American guide, configured the system for 60Hz NTSC output by default, and the PAL-native audio timing in the core was fighting it.
That’s the thing nobody tells you when you’re starting out with MiSTer in the UK. The platform’s documentation, the most popular video guides on YouTube, the Reddit posts everyone links to — they’re almost all written from a North American perspective, aimed at NTSC televisions, 60Hz displays, and a set of assumptions about what “correct” looks like that simply don’t apply to us. We grew up with PAL. Our Mega Drives ran at 50Hz. Our SNES titles had borders and slower music and, yes, sometimes that was worse — but for a lot of us, that’s what authentic means. And even if you want to run everything at 60Hz on a modern display, you still need to understand PAL timing to make informed choices about which cores to use and how to configure them.
This guide is written specifically for UK builders. Every price is in pounds, every supplier recommendation is UK-accessible, and every configuration note is written with PAL behaviour in mind. I’m going to walk you through the complete build from bare board to fully configured system, warn you about every mistake I made along the way, and give you a setup that genuinely works — for under £200. Let’s get into it.
What You Actually Need: The Full Requirements List
Before anything else, let’s be completely clear about what MiSTer is and isn’t. It’s not a Raspberry Pi emulator. It’s a collection of FPGA cores running on a Terasic DE10-Nano development board, each core being a hardware-level recreation of a specific piece of silicon. The distinction matters because it affects everything from how you source parts to what you can realistically expect in terms of compatibility and output accuracy. When the MiSTer MegaDrive core runs Sonic, it’s not emulating a Mega Drive — it’s being one, at the gate level. That’s why timing, including PAL timing, can be so precise.
Essential Hardware
- Terasic DE10-Nano FPGA board — The heart of the whole system. There is no substitute. Approximately £120–£140 from UK distributors including Mouser, RS Components, and occasionally Amazon Marketplace. Do not buy clones — I’ll explain why shortly.
- MiSTer FPGA USB Hub add-on board — Gives you proper USB connectivity plus the I/O header your add-ons need. Around £20–£30 from MiSTer Addons, MiSTer FPGA UK, or the Misterfpga.co.uk store. You can run MiSTer without this, but you’ll be frustrated within a week.
- SanDisk 32GB (minimum) MicroSD card — This is where your cores and ROMs live. Use a reputable brand. I’ve had two cheap cards corrupt mid-write and it is genuinely miserable. SanDisk Ultra or Extreme, 32GB gets you going, 64GB is better. Around £8–£12.
- 5V 3A USB-C power supply — The DE10-Nano is power-hungry. A phone charger isn’t enough. The official Raspberry Pi 5V 3A supply works brilliantly and costs about £8 from most UK electronics retailers.
- HDMI cable — Any decent one will do. You almost certainly already own one.
Optional but Strongly Recommended Hardware
- MiSTer FPGA RAM add-on (128MB SDRAM board) — Required for several cores including the SNES and PlayStation. Without this, roughly a third of the available cores simply won’t load. Around £20–£25. Buy it now; you’ll want it within the first hour.
- RTC (Real-Time Clock) module — Needed for accurate in-game saves on cores that rely on battery-backed RAM, like the MegaDrive. About £5. Small, easy to fit, annoying to realise you needed it after the fact.
- A case — Not strictly required, but the bare DE10-Nano is a magnet for accidental shorts if you’ve got it sitting on a desk with other metal things nearby. The SYNCHRO or Pixel Cases 3D-printed shells are excellent. Budget £15–£25.
- 8BitDo Pro 2 controller — My go-to recommendation for MiSTer. USB or Bluetooth, works natively, button layout suits both SNES-style and six-button Mega Drive mapping. Around £35–£40. If you already own a decent USB pad, start with that.
For PAL Display Output (If You’re Going CRT)
- HDMI to analogue converter with SCART RGB output — If you’re outputting to a CRT via SCART, you’ll need an adapter that can handle the MiSTer’s 15kHz signal. The RetroTINK-2X or OSSC aren’t necessary for a basic build, but a decent SCART adapter is. Roughly £25–£40 depending on quality. More on this in the display section.
Total Cost Breakdown
- DE10-Nano: ~£130
- USB Hub add-on: ~£25
- 128MB SDRAM board: ~£22
- MicroSD (64GB SanDisk): ~£10
- Power supply: ~£8
- Case: ~£20 (optional but recommended)
- Total: approximately £215 fully loaded, or £163 bare minimum
Yes, that scrapes over £200 with everything included. But you can absolutely hit under £200 by skipping the case initially and using a controller you already own. I’ll note where you can save money versus where cutting costs will genuinely cause you pain.
Step 1: Sourcing Your DE10-Nano in the UK Without Overpaying
1. Go to Mouser Electronics (mouser.co.uk) or RS Components (rs-online.com) and search for “DE10-Nano”. These are legitimate UK distributors with stock. At time of writing, Mouser lists the DE10-Nano at £136 including VAT with UK shipping. RS Components is occasionally slightly cheaper. Both are reliable.
2. Check the MiSTer FPGA UK community (misterfpga.co.uk) — they sometimes bundle the DE10-Nano with add-on boards at a modest discount, which makes sense if you’re buying everything at once. The UK-based MiSTer resellers have improved enormously over the past couple of years; you no longer need to import from the US and pay customs duty, which used to add £30–£50 to the cost and several weeks of waiting.
3. Do not buy a “MiSTer FPGA clone” or “compatible board” from AliExpress or Temu. I know they look tempting at £40–£60. I know someone in a Facebook group will tell you they work fine. They do not work reliably, the Cyclone V FPGA on the genuine DE10-Nano has specific characteristics that the cores are compiled against, and you will spend more time debugging than playing. I tried one. It lasted three weeks before random cores started hanging at load. The genuine board is the correct answer here.
4. While you’re waiting for the board to arrive (usually 2–5 working days from Mouser UK), order your add-ons. The MiSTer Addons store and misterfpga.co.uk are both UK operations. Order the USB Hub board, the 128MB SDRAM board, and the RTC module as a bundle if possible — the shipping savings add up.
Pro Tip: The SDRAM board comes in two versions: 32MB and 128MB. Always buy 128MB. The 32MB version used to be fine for most cores, but PlayStation and several arcade cores now require 128MB. The price difference is about £5 and the regret difference is enormous.
Step 2: Physical Assembly — Stacking the Add-On Boards
5. Before you handle the DE10-Nano, touch something earthed. The FPGA is not as ESD-sensitive as bare RAM chips, but it’s still a £130 piece of electronics sitting on your desk. I keep an anti-static mat at my soldering station, but even touching the metal chassis of a plugged-in (but switched off) appliance is sufficient discharge for casual assembly work.
6. Lay out all three boards: the DE10-Nano, the USB Hub add-on, and the SDRAM module. Check that you have the GPIO headers on the add-on boards. Most pre-built add-on boards from reputable UK suppliers come with headers already soldered. If yours don’t, you’ll need to solder 2×20 pin headers — this is straightforward work, but requires a fine-tip iron and a steady hand. Don’t rush it. Cold joints on FPGA GPIO headers cause maddening intermittent faults.
7. The SDRAM module connects to GPIO0 (the left 40-pin header on the DE10-Nano when the board is oriented with the FPGA chip facing you and the USB ports to your right). The USB Hub board connects underneath the DE10-Nano via the GPIO1 header and stacks below it. Line up the pins carefully. There’s only one correct orientation — the PCB silkscreen usually has an arrow or “UP” indicator. Check it before pressing anything together.
8. Press the SDRAM module onto GPIO0 firmly and evenly. You want all pins seated simultaneously, not one side going in first. If you feel uneven resistance, stop and realign. Bent GPIO pins are a nightmare to straighten and the DE10-Nano is too expensive to force.
9. Attach the USB Hub board to GPIO1 in the same manner. This board also powers from the USB-C port on the DE10-Nano, so there’s no separate power connection required.
10. If you have an RTC module, it connects to a small header on the USB Hub board itself — check the silkscreen labelling, it’ll say “RTC” clearly. The module is keyed, so it only goes in one way. Press it gently until it’s fully seated.
11. Install the assembled board stack into your case if you have one. Pixel Cases and SYNCHRO cases both use the standard DE10-Nano mounting hole layout, so the board drops in and you secure it with the provided M3 screws. Don’t overtighten — the DE10-Nano’s mounting holes are not reinforced and cracking the PCB here is heartbreaking and expensive.
⚠️ Warning: The USB Hub board has a small fan connector header. Some versions ship with a 5V fan already included; others don’t. The DE10-Nano does generate heat during intensive use — particularly when running the PlayStation or SNES core for extended periods. If your case doesn’t have passive ventilation, add a small 5V fan. I didn’t bother on my first build and after a three-hour session of Castlevania: Symphony of the Night the board throttled and started glitching. Five-volt 30mm fans are about £3 from Amazon and clip straight onto the hub board header.
Step 3: Preparing Your MicroSD Card — The MiSTer Script Method
12. Download the MiSTer update script from the official MiSTer FPGA GitHub repository (github.com/MiSTer-devel/mr-fusion). At time of writing, the recommended starting point for new UK builders is the MR Fusion image — a minimal bootable image that, when written to your SD card, automatically downloads and installs everything it needs on first boot via your network connection. This is far easier than manually managing files, and it means your core versions are immediately current.
13. Download Balena Etcher (free, available for Windows and macOS) or use Raspberry Pi Imager if you already have it. Both work identically for this purpose. Do not use Windows’ built-in “format” tool on your SD card — it will not create a bootable image correctly.
14. Insert your MicroSD card into your computer using a proper USB card reader. The built-in SD slots on some laptops write slowly and occasionally cause subtle card corruption. A £5 USB reader from Amazon is your friend here.
15. Open Balena Etcher, select the MR Fusion .img.gz file you downloaded (you don’t need to decompress it first — Etcher handles that), select your SD card as the target, and click Flash. The process takes about 5–8 minutes. Do not interrupt it.
16. Once flashing completes, Etcher will verify the write automatically. If verification fails, try a different SD card. I’ve had two SanDisk Ultra cards (the cheaper range) fail verification; I’ve never had a SanDisk Extreme or Samsung EVO fail. The extra £3 is genuinely worth it.
17. After verification, your computer will likely try to prompt you to format the card because it can’t read the Linux partition. Dismiss this without formatting. Eject the card normally.
Pro Tip: Label your SD card with a small piece of masking tape and a marker pen. If you’re anything like me, you’ll eventually have multiple SD cards for different MiSTer configurations and testing different core versions. “Main build – v2024” beats “which one is this” panic every time.
Step 4: First Boot and Network Configuration
18. Connect your DE10-Nano assembly to your television or monitor via HDMI. Connect a keyboard via the USB hub (you’ll need it to navigate the initial setup). Connect an Ethernet cable from the hub board’s network port to your router — do not skip this step for first boot, even if you plan to use the system offline afterwards. The MR Fusion script needs internet access to complete the initial setup.
19. Insert the MicroSD card into the DE10-Nano’s card slot. It’s on the underside of the board, which can be fiddly if you’ve already put it in a case — another reason to complete SD card setup before final assembly.
20. Connect the 5V 3A USB-C power supply. The DE10-Nano powers on immediately without a separate power button. You’ll see the FPGA’s configuration LEDs blink, then a Linux boot sequence on your HDMI output. If your display says “No Signal”, check that the HDMI cable is firmly seated at both ends. The DE10-Nano’s HDMI port is slightly recessed on some revisions and can feel seated when it isn’t.
21. The MR Fusion script runs automatically on first boot. It expands the filesystem, connects to the internet, downloads the latest MiSTer menu system and a base set of cores, and then reboots. This takes between 5 and 20 minutes depending on your connection speed. Do not power off during this process. I know it looks like it’s hung. It hasn’t. Go make a brew.
22. After the automatic reboot, you’ll be dropped into the MiSTer main menu. This is a simple text-based interface that lists your available cores. At this point, you’ll have the menu system and a handful of basic cores. You’ll update and expand this in the next steps.
23. Navigate to the Scripts section of the MiSTer menu (scroll down, it’s near the bottom of the menu list) and run the update script. This connects to GitHub and downloads the latest versions of all available cores. Depending on how many cores you want, this can take 10–30 minutes. Let it run completely. When it finishes, it’ll return you to the menu.
⚠️ Warning: If your network connection drops mid-update, the script may leave partial core files on your card. Run the update script again if you suspect interruption — it’s idempotent, meaning it can safely be run multiple times and will simply download what’s missing.
Step 5: PAL Configuration — This Is Where It Gets Interesting
This is the section most guides skip entirely, and it’s the most important part for UK users. Let me explain the situation clearly before we get into the specific steps.
MiSTer cores can output video in multiple ways. The most common is HDMI at 1080p, scaled up from the original resolution using integer scaling. By default, many cores output at 60Hz because that’s what NTSC consoles ran at, and it’s what most modern displays prefer. For UK users who want PAL-authentic behaviour — 50Hz timing, correct audio pitch, the original screen borders on PAL-specific conversions — you need to configure things explicitly. Even if you’re outputting to a modern 4K television and don’t care about CRT output, getting the timing right affects audio pitch and game speed in ways that matter enormously to anyone who grew up playing these games on PAL hardware.
Configuring the MiSTer.ini File for PAL Output
24. The MiSTer system configuration lives in a file called MiSTer.ini on the root of your SD card. You can edit this via SSH from your computer (the MiSTer’s IP address is visible in the System menu), or by removing the SD card and editing it on your PC. I prefer SSH — it’s faster and you don’t have to keep pulling the card out. On Windows, use PuTTY. On Mac or Linux, just use Terminal. The default SSH credentials are username: root, password: 1. Change this once you’re in — yes, really.
25. Open MiSTer.ini in a text editor (nano works fine via SSH: type nano /media/fat/MiSTer.ini). You’ll see a large file with many commented-out options. We’re interested in a specific set of video settings. Find or add the following lines:
video_mode=8— This sets the HDMI output to 1280×1024 at 60Hz as a fallback. Don’t worry, individual core video modes override this.vsync_adjust=1— This tells MiSTer to adjust the HDMI output’s vertical sync to match the core’s native refresh rate. Set this to 1 (adaptive sync). This is crucial for PAL cores running at 50Hz — without it, you’ll get judder or frame drops on displays that don’t natively support 50Hz input.hdmi_limited=0— Ensures full RGB range output. Some televisions interpret the HDMI signal incorrectly if this is set wrong, resulting in washed-out or crushed colours.vscale_mode=1— Integer scaling. Keeps pixels sharp without introducing filtering artefacts. Leave this at 1 unless you specifically want smoothing.
26. Save the file (Ctrl+O in nano, then Enter, then Ctrl+X to exit). These are global settings. Core-specific settings override them on a per-core basis, which we’ll cover next.
Per-Core PAL Configuration
27. Load the MegaDrive core. In the MiSTer menu, it’s listed under “Console” cores. Once it loads, press F12 to open the core’s OSD (on-screen display) menu. This is different from the main MiSTer menu — it’s the core’s own configuration interface.
28. In the MegaDrive core OSD, navigate to the System settings. You’ll see a Region option. Set this to EU. This does several things simultaneously: it tells the core to run at PAL timing (50Hz), sets the VDP to PAL mode (which affects the display area and blanking timings), and switches the system region flags that games read to determine whether to run in PAL or NTSC mode. For authentically PAL behaviour — including the slightly lower audio pitch and the wider top/bottom borders — EU region is what you want.
29. Still in the MegaDrive OSD, look for the Video settings. Ensure PAL is selected under video output mode. You’ll also see an option for HSync width — leave this at default unless you’re outputting to a CRT and experiencing sync issues.
30. Exit the OSD and load a game. I always test with Sonic the Hedgehog (1991) because I know exactly what it should sound like at PAL speed. Green Hill Zone music at PAL timing has a specific, slightly more relaxed feel compared to the NTSC version. If it sounds right, your PAL configuration is working.
31. Repeat the region-setting process for other PAL-relevant cores. The SNES core (look for “SNES” or “Super Nintendo” in the menu) has a similar region setting. The NES core does as well, though PAL NES games are rarer. The Amiga core (MiSTer’s Amiga implementation is extraordinary, by the way — it’s called “ao486” for PC and “Minimig” for Amiga specifically) defaults to PAL automatically because the Amiga was predominantly a PAL platform, particularly in the UK. Check it anyway.
Pro Tip: MiSTer saves core configurations per-core in individual .cfg files. Once you’ve set a core up correctly, those settings persist. You don’t have to redo this every time you load the core. However, when you update a core via the update script, always check that your settings weren’t reset to defaults — this has happened to me after major core version jumps.
Step 6: Display Output Options for UK Builders
This is genuinely one of the best things about MiSTer compared to other solutions like the Analogue Mega Sg or Super Nt — the display output flexibility is extraordinary. You have three main paths, and which you choose depends entirely on your setup.
Option A: Modern HDMI Display (The Easy Route)
32. If you’re outputting to a modern flatscreen — a 4K TV, a 1080p monitor, anything with HDMI — MiSTer just works. The vsync_adjust=1 setting we configured earlier tells the display to adapt to the core’s native refresh rate. On a good modern display with HDMI 2.0 input, this means your 50Hz PAL cores output at a genuine 50Hz signal and your display accepts it cleanly. Most Samsung and LG televisions from 2018 onwards handle this without complaint. My current monitor is an LG 27GP850 and it accepts 50Hz HDMI without any manual configuration whatsoever.
33. The potential issue with modern displays and 50Hz input is input lag. Some televisions add processing lag to 50Hz signals that they don’t add to 60Hz. Always enable “Game Mode” on your television for MiSTer output — this bypasses most of the processing pipeline and dramatically reduces input lag. On a Samsung QLED with Game Mode off, I measured roughly 80ms lag on a 50Hz input. With Game Mode on, it dropped to under 10ms. That’s the difference between playable and unplayable for a platformer.
Option B: CRT via SCART RGB (The Purist Route)
I won’t pretend this isn’t my preferred setup for certain cores. Running a PAL Mega Drive core through SCART RGB into a 1990s Sony Trinitron is genuinely stunning. The scanlines are real, the phosphor bloom is real, the geometry is authentic. For games like Streets of Rage 2 (1992) or Sensible Soccer (1992), it’s transformative.
34. MiSTer outputs a 15kHz analogue RGB signal through its GPIO header when configured correctly. The most straightforward way to get this to a SCART television is to use the MiSTer’s dedicated analogue IO board (not the same as the USB Hub board — this is a separate add-on that costs around £25–£35 from misterfpga.co.uk). This board provides direct SCART output.
35. Alternatively, for HDMI-to-SCART conversion, you can use an OSSC (Open Source Scan Converter) — roughly £100 new, though I’ve seen them go for £60–£70 on eBay — or a RetroTINK 2X at around £50. Both devices take the HDMI output from MiSTer and convert it to analogue signals suitable for a CRT. The OSSC is the better choice here because it supports line doubling and various passthrough modes that preserve the 15kHz signal characteristics your CRT expects.
36. If you go the CRT route, add the following to MiSTer.ini:
direct_video=1
This enables direct 15kHz video output from the GPIO header, bypassing the HDMI scaler entirely when using cores that support it. The result is the cleanest possible analogue signal from the FPGA.
Option C: Hybrid — HDMI for Modern Cores, CRT for Retro
37. This is actually how I run my setup day-to-day. My MiSTer sits between a 27-inch IPS monitor (for arcade cores, Neo Geo, PlayStation) and a 14-inch Sony PVM (for NES, SNES, Mega Drive, Master System). I switch between them using an HDMI switch for the modern output and the analogue IO board’s SCART output feeding directly to the PVM’s RGB BNC inputs via a SCART-to-BNC breakout cable. Yes, it looks ridiculous. No, I have no regrets.
Step 7: Adding ROMs and Games
I’m going to be straightforward here: the legal situation around ROMs is what it is, and I’ll leave the specifics of where to source them to your own research and conscience. What I will cover is exactly how the MiSTer file structure works, because getting this wrong results in cores that refuse to find games and an afternoon of frustration.
38. MiSTer expects ROMs in specific folders on the SD card. The root of the card has a folder called /media/fat/games/. Inside this, each core has its own subfolder. The exact folder name matters — it’s case-sensitive on the Linux filesystem. The MegaDrive core expects its ROMs in /media/fat/games/MegaDrive/. The SNES core wants /media/fat/games/SNES/. The NES core wants /media/fat/games/NES/.
39. You can transfer files to MiSTer via the network using any SMB-compatible file manager. On Windows, type \\MISTER in File Explorer’s address bar (or use the IP address). On Mac, Finder’s “Connect to Server” with smb://MISTER works identically. The shares are visible as named folders. Drag your ROM files in.
40. File formats: MegaDrive ROMs should be .md or .bin format. SNES ROMs should be .sfc or .smc. NES ROMs should be .nes. Zipped ROMs (.zip) work for many cores — the MiSTer can unzip on the fly — but I recommend unzipped files where possible for faster loading. Some cores are fussy about zip files with unusual internal structures.
41. BIOS files are required for some cores. The PlayStation core needs the PlayStation BIOS (SCPH1002.BIN for the European version, which is the PAL-correct one for UK builds). The Neo Geo core needs neo-geo.rom. The Mega CD core needs several BIOS files. These go in /media/fat/games/[CoreName]/ alongside your game files, or in /media/fat/ for system-wide BIOSes like the Neo Geo. The MiSTer wiki has the exact filenames required — search “MiSTer FPGA BIOS” and you’ll find the official documentation.
Pro Tip: For PAL-correct PlayStation emulation, you specifically want the European BIOS (SCPH1002). The Japanese BIOS (SCPH1000) and North American BIOS (SCPH1001) will work but won’t give you the correct PAL boot animation and region handling. If you want to replicate playing a PAL PlayStation in 1995 Britain, the SCPH1002 is what you grew up with.
Step 8: Controller Setup and Mapping
42. Plug your controller into one of the USB ports on the hub board. MiSTer will prompt you to define your buttons the first time it sees a new controller. This mapping is global — it applies across all cores — which is both convenient and occasionally annoying when a core expects a different button layout.
43. The button-mapping screen asks you to press each function in sequence: D-pad directions, face buttons, shoulder buttons, start, select, and so on. Take your time here. Press each button deliberately. If you rush and press the wrong button, you can redo the mapping by going to the main MiSTer menu and selecting “Define joystick buttons” under the controllers section.
44. For the 8BitDo Pro 2 specifically: connect it via USB-C cable first to do the initial mapping. The Bluetooth connection works, but for first-time setup the wired connection is more reliable. Once mapped via USB, the Bluetooth profile retains the same mapping — no need to re-map when switching to wireless.
45. Core-specific button remapping is available in each core’s OSD menu. For the MegaDrive core, you can remap to a six-button layout — critical for games like Mortal Kombat II (1994) and Street Fighter II: Special Champion Edition (1993), both of which were designed for the six-button Mega Drive controller. Press F12 while a game is running, navigate to “Input”, and you’ll find the per-core mapping options.
46. If you’re using a Bluetooth controller and it occasionally disconnects or has input lag: go back to the USB connection. Bluetooth on MiSTer is functional but not flawless — it depends heavily on the USB Bluetooth dongle you’re using. The only adapter I’ve had consistent luck with is the 8BitDo USB Bluetooth Adapter 2 (the one designed for the Switch). It’s about £12 and pairs with 8BitDo controllers without any fuss.
Step 9: Keeping Everything Updated
47. Run the update script monthly at minimum. The MiSTer project is extraordinarily active — cores receive meaningful improvements regularly, and the menu system itself gets updated too. Significant updates to the MegaDrive core in 2023 improved PAL border rendering noticeably; the SNES core has had multiple accuracy improvements in the last year that affect specific games I was testing at the time. Staying current matters.
48. The update script is accessible from the MiSTer main menu under Scripts. It connects to GitHub directly, downloads the latest core binaries, and overwrites your existing ones. Your game files and configurations are not touched. Run it, wait for it to complete, and restart the system.
49. Back up your SD card periodically. Use Win32DiskImager (Windows) or dd (Mac/Linux) to create a full image of the card. Store it somewhere safe. I do this every two months and it’s saved me twice — once when a card started showing read errors, and once when I accidentally ran a command as root that I shouldn’t have.
Troubleshooting: The Problems I’ve Actually Had
“No Signal” on HDMI After Boot
This one got me the first time. The DE10-Nano defaults to a resolution that some displays won’t accept. Boot MiSTer, wait 30 seconds (it’s definitely booted even if you can’t see it), then press F12 to open the OSD — the display may or may not show something. If your display then shows a signal, great; your resolution was wrong. SSH in (you can do this even without a display) and change the video_mode setting in MiSTer.ini. Mode 0 is 1280x720p 60Hz and works on virtually everything.
Audio Running at Wrong Speed (PAL/NTSC Mismatch)
Exactly what happened to me on day one. Go into the core’s OSD (F12), find Region settings, set to EU. If the audio is faster than expected, you’re running an NTSC core at 60Hz. If it’s slower than expected and you want 60Hz output, set Region to US and accept that you’re running the NTSC version of the game. There’s no shame in that for certain titles — Castlevania Bloodlines, for instance, has no PAL-specific gameplay advantages worth preserving.
SDRAM Module Not Detected
The SNES core (and others) will display a message about missing SDRAM. This almost always means the SDRAM board isn’t properly seated. Power off, remove the SDRAM board, check the pins for any that are bent (use a magnifying glass under good light), and reseat. Press evenly and firmly. The pins on the DE10-Nano GPIO headers are more delicate than they look. I bent three of them on my second build and had to straighten them with a fine dental pick under a loupe. Agonising work. Seat the board carefully.
Games Loading but Immediately Resetting or Corrupting
This almost always means your MicroSD card is at fault, either failing or formatted incorrectly. Try a different card. Use Balena Etcher to rewrite the MR Fusion image and start fresh. If the problem persists with multiple cards, check your power supply — an inadequate 5V supply causes SD card write errors that look exactly like card failures. The 5V rail on the DE10-Nano is sensitive; use a quality supply.
Controller Not Responding in a Specific Core
Two possible causes. First: the controller mapping for that core is wrong. Open the core OSD (F12), find Input settings, and remap. Second: some cores require a specific USB port — the primary game port is usually the first USB port on the hub board (the one nearest the board edge, not the UART port). Try plugging your controller into a different port on the hub.
CRT Output Has No Sync or a Rolling Picture
If you’re using direct video output to a CRT and getting sync issues, the first thing to check is whether the core you’re running supports direct_video mode. Not all cores do. Check the MiSTer wiki for the specific core. If the core supports it and you’re still getting sync problems, check your SCART cable — many cheap SCART cables omit the sync-on-luma pin. A proper RGB SCART cable (like those from Retro Access or HD Retrovision UK) uses genuine composite sync and makes a significant difference.
SSH Not Connecting
If you can’t SSH into your MiSTer, check that it’s connected to your network (the hub board’s Ethernet LEDs should show activity), then find its IP address. The easiest way to do this is to log into your router’s admin page and look at connected devices — it’ll appear as “MiSTer” or as a Linux device. Use that IP address directly rather than the hostname if DNS isn’t resolving it.
Where This Build Sits Compared to the Alternatives
I get asked regularly whether MiSTer is worth it compared to a Raspberry Pi 5 running Batocera or EmulationStation. My honest answer: they’re doing different things, and the difference matters most on the platforms where accuracy is critical. A Raspberry Pi 5 running SNES emulation via Retroarch with Bsnes-accuracy core is genuinely excellent — I’ve run both side by side on a modern display and in that context the differences are subtle for most games. But fire up a PAL Mega Drive game on MiSTer’s MegaDrive core and then on a Pi running Genesis Plus GX, output both to the same CRT, and the timing and audio are measurably different. MiSTer is being the hardware; the Pi is approximating it.
Compared to Analogue’s hardware — the Mega Sg, the Super Nt, the Pocket — MiSTer’s advantage is breadth and price. The Analogue Mega Sg is a superb piece of kit at around £200 on its own, but it only does Mega Drive. My MiSTer runs NES, SNES, Mega Drive, Master System, Neo Geo, Amiga, Atari ST, arcade boards from the late 1970s through to the late 1990s, and a PlayStation core that, at the time of writing, handles the vast majority of the PAL library without issues. For under £200 total, nothing comes close to that breadth.
The tradeoff is setup complexity. An Analogue device comes out of the box working. MiSTer requires the setup process I’ve described above, and occasional troubleshooting when things don’t behave. If that appeals to you — if you’re the sort of person who reads RetroInHand and finds the process half the fun — MiSTer is extraordinary. If you want plug-and-play, buy an Analogue Pocket or a MegaSg and enjoy it. Both answers are correct.
My Final Verdict
Two years into daily MiSTer use, I’ve built four of these things — two for myself (I kept iterating on the setup), one for my brother, one for a friend who’d never soldered anything before and followed this exact process with me on a video call. All four work. All four are configured for PAL output. All four have given people hours of genuine joy playing games they grew up with, the way those games actually ran on the hardware they actually had.
The under-£200 target is real and achievable, though I’d encourage you not to skimp on the SDRAM board or the MicroSD card — those are the two places where saving £5 costs you hours of frustration. Everything else has flexibility. The case is cosmetic. The controller you can substitute. The power supply you might already own. But the core components need to be correct.
What makes this build specifically worth doing as a UK builder is the PAL configuration. Most people running MiSTer are running it in NTSC mode on NTSC displays, which is completely fine for them — but it means they’ve never heard Sonic the Hedgehog’s Green Hill Zone at the correct speed, never seen the PAL border on a Mega Drive game rendered accurately, never experienced the specific timing of European games on European hardware. Set up the way I’ve described in this guide, that’s exactly what you get. Hardware-accurate, timing-correct, PAL-native retro gaming from a single board that fits in your hand and cost less than two tanks of petrol.
It’s one of the best things in this hobby. Build one.