MiSTer FPGA Forum

kolla wrote: ↑Thu Apr 29, 2021 5:44 am What I find really strange is how all benchmarks say everything is much faster than tg68, while in reality it is so much slower, heh...

Could that be because benchmarks can execute from the cache on the arm side, and the challenge in performance is in the fpga to arm bridge?

Just a thought bas, is there an input queue from the arm side to the core? If that fills and isn’t emptied it would suggest the core isn’t running…. Either way, checking with sorg or other maintainer that we’re not reinventing the wheel sounds wise

Good luck!

That’s inspiringly awesome! Would love to get started with fpga stuff...

It’s not fpga, but rgbtohdmi makes use of a raspberry pi and cpld to capture digital signals inside a machine before the d2a stage, and it works with up to 12 bit colour (4096 colours, as in the Amiga)

That project is on GitHub and might give some good hints too?

I can’t see anyone saying “this is a bad idea”, but I can see people pointing out that this isn’t trivial: either implementing a high performance processor core, or offloading processor duties to the arm for emulation, is hard. There is a fantastic 68k processor core, it’s been designed and implemented by the vampire team. It’s not available it see...

That looks to be a very good way forward: thanks for the info!

What did happen to Gunnar’s offer of 060 level performance to any project with the option to unlock the 080 performance at a price? I only saw reference to it on a1k.org a while ago

Other than that, there are no better 68k cores than the one we have.

Intrigued as to what the Easter egg is now!

That is excellent work! I was going to ask whether you'd created an API between the Amiga and core, but using share: is a really elegant way to achieve this with no core changes. Nice work everyone involved!

I too have patched the SCSI rom - there's a process that could do with a script, too...

Makes a lot of sense to have that icon for ks2+ - one thing I should do to the install script is use "join" rather than just copying things over: will sort that.

The only thing I have found that doesn't work is that info under 1.3 returns "not a dos disk" for share, and I can't quite see why...!

The code for misterfilesystem in MisterFPGA github is being linked to KS2+ startup code - using the 1.3SDK and linking the associated startup sorted it. I built it using the Docker environment from Niklas Ekstrom's original Pi314 build environment... the only issue I had compiling was needing to deference a pointer to the name in the source. I also...

The only thing I really used the MMU for was for Enforcer. A faster CPU in the core would be awesome, however I'm not aware of other 68k implementations in FPGA that could give a better result - apart from the vampire 68080, and that's not likely to be coming any time soon I guess! Of course, I could just be parading my ignorance around implementat...

Thinking aloud, would it be possible to use this work as the basis for improving the disk activity light to reflect MOTOR_ON as it does in the Amiga - rather than DMA_ON which is what it does now if I understand correctly - and secondly to pass more signals back up to the ARM side with a view to adding in floppy sounds? (Or is that not possible due...

uigiflip wrote: ↑Sat Feb 20, 2021 10:55 pm has uart mode disappeared for pi midi?

No, it's still there, it's in the SYSTEM page of the OSD (push right arrow when on the CORE page). It's definitely working and you've got the choice of None, PPP, Console, MIDI or Modem

The placement on the screen, as many above have said, was programmable... The fun of DIWSTRT, DDFSTRT, DIWSTOP and DDFSTOP - the horror. It's a non-trivial thing to solve given programmers can and do shift them around: the joy of CRTs on a real Amiga is that once you've got it perfect for one screenmode, you can guarantee it'll be nearly unusable f...

I had a dig through the code and could see nothing 3.x specific at all in there, so guessed it may be to do with the build environment linking to 3.x startup code... It looks like that's the problem! If anyone else is daft enough to want MiSTer running on 1.3 with access to the Share: directory, I've managed to build the MiSTerFileSystem using kick...

Is there any reason why the Share driver - specifically misterfilesystem.c - would not work on System 1.3? (ks1.3/wb1.3). I've tried this, and when trying to access Share:, for example by attempting "list share:", I get the error "file is not an object module" From checking Library documentation, I can't see any reason why it wo...

Lisko wrote: ↑Tue Feb 09, 2021 6:51 pm You could pull latest picasso96 version from individual computer technically but I don't know if it's permitted by their license

It'd be a very easy change as there's a list of files to download for the disks which gets pulled from GitHub, however as robinsonb5 notes, the new package is commercial software that needs a licence.

I've had a bit of a play with Bash scripting after discovering that the Linux kernel natively supports mounting ADFs, and have created a script that pulls lha and Picasso96 from Aminet, the necessary files from Minimig Extras on GitHub, and assembles them into an ADF ready for mounting on the Amiga side. I've also written a quick amiga script to ex...

I had exactly this problem after a recent update - it seemed that 1942, Commando and a few others simply produced corrupted output.
Turns out I had no mister.ini, so running the ini_settings script created one, and the problem was solved.

Odd...

That looks awesome! I've just received my board and add-ons, and am wanting something interesting as a case - that looks like it does the job very well!