I think the FLP (rather than original FDK) version ignores the jumpers?jobdone wrote: Mon Jun 03, 2024 6:15 pm I too tried the 8k one in q-emulator which seemed fine with minerva 1.98. I wonder if the jumper for the mdv over-ride makes any difference?
MicroP Controller with Minerva Issue
Re: MicroP Controller with Minerva Issue
Re: MicroP Controller with Minerva Issue
On a slightly different note, if you have the manual for the FLP version, Dilwyn shows that as MIA on his site.
Re: MicroP Controller with Minerva Issue
I also just did a quick look into the 5.3E rom on Dilwyn's site, and this one shows FDK in the rom
Re: MicroP Controller with Minerva Issue
I have the QFLP manual (don't know how original it is) for the v1.19 QFLP ROM that's installed, but no manual for the card itselfjobdone wrote: Mon Jun 03, 2024 6:23 pm On a slightly different note, if you have the manual for the FLP version, Dilwyn shows that as MIA on his site.
Re: MicroP Controller with Minerva Issue
I would say that is the manual he's after, most likely an add on part or similar?
Re: MicroP Controller with Minerva Issue
Just checked and the one I have is on his sitejobdone wrote: Mon Jun 03, 2024 6:35 pm I would say that is the manual he's after, most likely an add on part or similar?
https://dilwyn.theqlforum.com/qlrom/QFLP ... Manual.pdf
Re: MicroP Controller with Minerva Issue
I must've missed that. dunno where I got the idea it was MIA.
Re: MicroP Controller with Minerva Issue
Have replaced the JM ROM's in the spare QL with Minerva ROM and have the same issues with the MicroP Controller that I had in my main QL
I guess the issue could be with the MicroP Controller, but it seems fine with JM ROM's. Strange.
I guess the issue could be with the MicroP Controller, but it seems fine with JM ROM's. Strange.
-
- Aurora
- Posts: 964
- Joined: Tue Dec 17, 2013 1:17 pm
Re: MicroP Controller with Minerva Issue
One thing I don't think anyone has mentioned, Minerva checks more addresses in memory for ROM's than the Sinclair ROM's.
Maybe there is some kind of address problem on your MicroP interface. So that the ROM appears twice, or at some odd addresses.
So the Sinclair ROM's just see the first instance of the ROM, But Minerva sees it twice, or multiple times. And the MicroP ROM tries to initialize itself multiple times and screws up the system in the process.
Maybe there is some kind of address problem on your MicroP interface. So that the ROM appears twice, or at some odd addresses.
So the Sinclair ROM's just see the first instance of the ROM, But Minerva sees it twice, or multiple times. And the MicroP ROM tries to initialize itself multiple times and screws up the system in the process.
- XorA
- Site Admin
- Posts: 1609
- Joined: Thu Jun 02, 2011 11:31 am
- Location: Shotts, North Lanarkshire, Scotland, UK
Re: MicroP Controller with Minerva Issue
Minerva actually has a check for that, it compares the first few bytes to see if the rom has already been seen! Needed for Trump cards!Martin_Head wrote: Tue Jun 18, 2024 10:12 am One thing I don't think anyone has mentioned, Minerva checks more addresses in memory for ROM's than the Sinclair ROM's.
Maybe there is some kind of address problem on your MicroP interface. So that the ROM appears twice, or at some odd addresses.
So the Sinclair ROM's just see the first instance of the ROM, But Minerva sees it twice, or multiple times. And the MicroP ROM tries to initialize itself multiple times and screws up the system in the process.
G