MiSTer FPGA Forum

First time trying to bring a new (read: git tip) build up off the ground - using boot0.rom from git dev branch and boot1.rom both from git dev and from the ET4000, in all cases I get the following (from an otherwise-working vhd and unchanged config from the latest official ao486 release): - Proper video BIOS ID string (either 2MB from Tseng Labs or...

Thanks for the pointer!

About the only real issue I had with the Mac Plus (ah - my high school Turbo Pascal days!) was the keyboard input repeat problem...which is an awful shame, because every other bit of the experience was SO spot-on. Knocks vMac into a cocked hat!

Sure enough, a second compile attempt let the fitter work...but I still think the LU fill is pretty close to the breaking point now for this core. Caveat emptor!

One thing I learned the hard way (and still haven't worked out in my head why this is) - the vertical scale must be at least 3x for (custom filter) scanlines to work. 2x is *not* enough.

Core size - or more correctly LUs, the basic unit of operation in an FPGA. Quartus tries to arrange the gates such that they have minimal overlap and thus waste the least number of LUs in a process called 'fitting' at compile time...and after the fitter is done, it says there's too many LUs required (active + waste) to fit in the constraints of the...

Might be because the part of AO486 that required more than Lite is now being replaced with an open source alternative, it sounds like. I'm aware, I'm the one that told Sorgelig about it. The problem is that the fitter - at least in Lite 17.0.2 (which is the recommended build platform) - can't make ao486 fit in the available units on the Cyclone V....

tontonkaloun wrote: ↑Fri Jul 31, 2020 10:59 pm

rhester72 wrote: ↑Fri Jul 31, 2020 10:09 pm Anyone able to compile the (very latest) dev branch? I get "can't fit design in device" against the Cyclone V target in Quartus Prime Lite 17.0.2.

Yes !!!!!

i just did it !

OK..._how_ did you do it (with Lite)?

Anyone able to compile the (very latest) dev branch? I get "can't fit design in device" against the Cyclone V target in Quartus Prime Lite 17.0.2. I haven't used the software, at all, yet, is there more than one device? maybe you have the wrong one selected? There are lots of compile targets, but given the Cyclone V is the FPGA on the DE...

Anyone able to compile the (very latest) dev branch? I get "can't fit design in device" against the Cyclone V target in Quartus Prime Lite 17.0.2.

IAmParadox wrote: ↑Fri Jul 31, 2020 8:06 pm Sorgelig has implemented an opensource uart, that means it no longer costs a couple thousand dollars to compile the core....

Also, RobertPeip increased the size of L2 cache, by double.

Where did you see this?

EDIT: Never mind, wasn't following the dev branch

This is the one I was referring to, specifically:

https://opencores.org/projects/a_vhd_16550_uart

I didn't perceive any issues with parity locking or FIFOs as affecting any normal functionality of ao486, but perhaps I was mistaken.

Are you consistently using the same input device?

Honestly, a MiSTer portable would be physically huge and rather pointless, not to mention issues with heat dissipation. There's about zero chance of any homebrew project like MiSTer (running mostly off-the-shelf hardware) being a useful portable device.

There is no "stock 32MB". "Stock" is the RAM built into the DE10-Nano on-die (and it's a LOT more than 32MB). The 32MB (and 128MB) SDRAM module is separate, and required now for _most_ cores (Genesis is a notable exception).

Auto Region defaults to File Ext, which is not what is desired in nearly all cases.

Set Auto Region to Header, Priority to US>JP>EU and Region to US, then Save settings. Alternatively, set Auto Region to Disabled and Region to US, then Save settings.

I'm trying to get scanlines on the ZX Spectrum, with the following MiSTer.ini settings: [Spectrum] video_mode=7 vscale_mode=1 vsync_adjust=2 This should give me 76 blank rows on top and bottom of a 1080p display (and it does), and the 284 displayed lines should be doubled (they are). However, turning on Scale Filter - Custom and selecting Scanlines...

Upon further testing, I've also noticed that the declared internal resolution for Mega CD PAL appears to be wrong (set to the same as NTSC), so I'm not sure the Mega CD core was fully built for PAL...it looks like it tries to run PAL titles with NTSC framing and internal clocks but PAL refresh.

Good call - that's it exactly, thank you!

Unfortunately the 2.4g can only do X-Input when wired, so I've now ordered the Bluetooth model.

With the following combination: - Mega CD 2 V2.00W BIOS - EU region - 50.2Hz refresh with vsync_adjust=2 I get very consistent stuttering in the introductory FMV on Syndicate for Mega CD. I've confirmed the dump matches the hashes on redump.org. I don't see this with other FMV-heavy games (e.g. intro to Microcosm with US 2.11 BIOS and US region/60H...

My setup is pretty basic - I'm either playing with a wired SN30 Pro (mostly) or a wired M30 (Genesis/Mega CD). When I flip between them (by unplugging one and plugging the other into the same USB port, in case that matters), I lose the dpad mappings and have to remap the controller from scratch on the MiSTer main menu every time. Is this normal beh...

3 wireless USB devices on an unpowered hub = no bueno.

@ExCyber - that shouldn't affect MiSTer at all. Storage services are running on the Linux side of the house, and the FPGA shouldn't be subject to that at all.

If a hardware pointer wasn't affected on a real Amiga, it shouldn't be on MiSTer, either.

No, CRC32 isn't affected by compression (assuming you're looking at the calculated CRC32 inside the ZIP) - it's very likely yours is just different.

Going to PM you.

OK, I apologize - I couldn't find anywhere on the site to add just the case to the cart.

I'm not sure that's the problem either. Mine works fine, and:

rickdangerous wrote: ↑Fri Jul 17, 2020 1:32 pm

• Official Case for Digital I/O.

Still looking very forward to seeing photos (or even a site listing) for this

Does it still happen after a hard reboot of MiSTer? It's been black-screening for me lately as well (and nothing changed!).

I knew about 'squishing' with respect to density (again, referring to Amiga), but had no idea it had any effect on C64 (because I just hadn't thought through the fact that 200px mapped to a 256px box is going to be distorted LOL). I've literally never seen a PAL C64 or TV in my life, so I was asking very much out of ignorance - but thank you very m...

Ohhhhhh...interesting. On the Amiga (where I could display PAL), you get 256 lines of uninterlaced non-overscan, so I assumed the same held true on the C64. Wow...yeah, they must have looked quite different. The AR on C64 PAL (normal display area without borders) looks almost widescreen to me.

Thanks for the clarification!