MiSTer FPGA Forum

FPGA64 wrote: ↑Tue Jan 25, 2022 10:37 am Scumm Vm on the Mister is purely running on the Arm. It doesnt touch the FPGA at all.

Isn't the FPGA doing video + scaler?

So I ran the uaearm binary I posted before (i.e. emulation of cpu AND chipset - no core stuff except fbdev). This is running with MiSTer still in the background. This is with JIT enabled. So, sysinfo looks much better, particularly FPU. Real dhrystones is pretty close to qemu. Anyway seems worth trying (again!) to rip out the emulation side of it a...

Good question, I have no idea...

Edit: Digs out M68020 book and looks at section 7: COPROCESSOR INTERFACE DESCRIPTION!

OK, this one should all be in sync with the original Minimig core. You need to update the MiSTer and the MinimigHybrid.rbf. https://github.com/scrameta/MiSTer_Hybrid_Support I've not tested it yet myself, but should be ok. I have been testing this and it seems to have some bugs. The FastRAM option now shows "---" instead of... I think I ...

Which rbf file do we need for Linux, to provide fbdev video via the scalar?

I'm going to give this a go, to get real Debian installed... Wish me luck!
https://forum.digikey.com/t/debian-gett ... -kit/12435

Does anyone want to try out uae4arm? I mean a plain compile, not a hybrid patched jit. This is a static build for mister. I'm not sure which core has fbdev support, the menu one? I'm curious how it performs on that amiga-dhrystone binary...
http://www.64kib.com/mister_hybrid_files/uae4arm

Ooops: that isn't static!

OK, this one should all be in sync with the original Minimig core. You need to update the MiSTer and the MinimigHybrid.rbf.
https://github.com/scrameta/MiSTer_Hybrid_Support
I've not tested it yet myself, but should be ok.

Small update on ARAnyM... Again, finding this painful. Going to start from uae4arm instead first. I guess we should try just compiling it natively first, to see how it does without the FPGA side. i.e. 100% arm. It should only be faster than that, though not necessarily better! Since the emulator can freeze hardware during JIT to reduce relative lat...

Look if this is a big problem I can change the order... I just thought it was an opportunity to clean it up! True, but I would favor compatibility though, and then hopefully this change could be made in the official core first. At any rate its a minor detail. Its not especially important to me, I just noticed it and figured it might make sense to ...

raparici wrote: ↑Wed Jan 19, 2022 3:02 am I got a 5MB HDF to work at a time, but not always. Hard Disk issues seem the most blocking to me after a quick review. Floppies work perfect.

The hdf's work fine for me if I turn off the fast IDE stuff. Are you seeing issues with that disabled?

Look if this is a big problem I can change the order... I just thought it was an opportunity to clean it up!

Regarding connecting a pi: 36 pins/header on the DE10 nano https://rocketboards.org/foswiki/pub/Documentation/DE10NanoDevelopmentBoard/20-pin_header_pin-out.png?t=1486406248 With 36 pins, say 32 bits data at 100MHz: 400MB/s shouldn't be an issues from the DE10 side, or 800MB/s if using both edges. This might be little trickier to achieve on the pi ...

It only launches the software when 68Arm is selected and stops it when another CPU is selected. I forget if I stopped it when choosing another core though, that will be needed! Also it could be more generic in its implementation, but the same could be said for the whole of mister main! Yes I changed the cpu mapping since the mapping was: 0:68000, 1...

Turns out the configure doc page explains all these modes: direct, fixed and real.
https://github.com/aranym/aranym/wiki/a ... onfigure_2

I figured out why I was struggling to find the memory stuff in the aranym uat jit... Because it doesn't have an access layer like in musashi, it simply mmaps everything into the right place. i.e. the binary is set to load at 0x10000000 (virtual address), leaving the entire virtual space to mmap in like the target system. Then page faults can be use...

So I forked aranym and stripped out almost all the Falcon hardware. I need to figure out their memory access system now and strip out the Falcon memory layout, so I can provide my own. Then figure out the interrupts. Seems there is some helpful description here, so I'd better dig through that... https://raw.githubusercontent.com/scrameta/aranym_MiS...

Great:-) Turn on data cache and you'll be the same pretty much but with 5x chip speed.

I'm going to have another bash at stripping down aranym to just the jit. 3rd time lucky:-) Wish me luck!

OK, dhrystones drop with rtg on. From 160->130k on mine (pal highres vs 1280x720x8). Depends on the mode of course, if you have higher bpp might be more. As for app versions, they match what I included: 01e9f684ff929a186af52bf888023087 allocp < from c: bd16359c630b07356c669e5ac1e83b95 stackattack < from c: bd16359c630b07356c669e5ac1e83b95 ../StackA...

I think sdram timings are fixed for all boards. Fast ram is ddr3, ie on the de10 nano itself.

USB polling: could be I guess. It’s also possible I posted the wrong version of the stack and alloc patches. I’ll check.

Oh I might have said that last week. I had the cache turned off by accident and it took me a while to realise.

For Doom I used ADoom with -fps. I’m using rtg otherwise it’s probably chip ram bound anyway.

I guess memory access from the scalar could impact fast ram latency. Early in the thread I had 70k+ "dhrystones" in sysinfo, not sure how! Now I get 53K consistently I think.

I added some developer docs here. https://github.com/scrameta/Minimig-AGA_MiSTer_Hybrid/tree/MiSTer/doc/hybrid. ***** Emu 68 and ARAnyM devs read this please and help us :-) *** While 125000 is low, its better than the 4000 I was getting without these patches! Perhaps its related to a different memory layout of a different amiga os? Why do you thin...

Yes about 20fps on doom vs 10fps on tg68k. Not as much as I'd expect, probably some bottlenecks remain. With stackattack and the memory patch you should see ~150-200k dhrystones if you run the app I included. Its the real thing, unlike sysinfo. I wonder if the quake memory layout suffers from the sharing code and data stuff somehow else. Or if it h...

ron wrote: ↑Sat Jan 15, 2022 11:06 am

foft wrote: ↑Sat Jan 15, 2022 11:02 am The core needs to be started before starting the emulation. Normally it runs 'start' for you. Are you running it like that?

Yes, from ssh I try to launch the emulators first, but emus don't work, I get a Segmentation Fault. The core loads but without emulation nothing to do.

Are you using the 20220114 version of the tar?

The core needs to be started before starting the emulation. Normally it runs 'start' for you. Are you running it directly from the menu like normal?

Tidying up a bit... Put these onto my github: https://github.com/scrameta/MiSTer_Hybrid_Support (release scripts and binaries) https://github.com/scrameta/Minimig-AGA_MiSTer_Hybrid (core) https://github.com/scrameta/Main_MiSTer_Hybrid (modifications to start hybrid emulation) https://github.com/scrameta/qemu_MiSTer_Hybrid https://github.com/scramet...

I mean look how simple this is to use:
https://github.com/kstenerud/Musashi
Qemu is much more complex but at least has docs:
https://qemu.readthedocs.io/en/latest/devel/index.html

I’ll post docs on the kernel interface and memory map. So that any other software dev can try porting emu68 and anarym. The _interfaces_ for those are not well designed (in my opinion!) so they need a dev with experience of those code bases - or at least more patience than me:)

Did you put stackattack and the patched allocp in the startup sequence? For disk games not sure how we can do that. Perhaps a patched rom will be needed.

I always faster in sysinfo, perhaps a version.

Yes workbench and boot is slow. Not sure if it is the memory use patterns or something else…

ADoom has 2x fps of 020.