foft wrote: ↑Wed Apr 20, 2022 10:09 pm
I didn't yet implement interrupts plumbing, so perhaps that is needed for the diagnostic to work. I was figuring it wasn't since a lack of interrupts would be a fault that I'd expect the diagnostic cart to handle.
Hi foft,
Sorry -- I've haven't had both my Falcon and my scope (or logic analyser) in the same place since I promised to have a look at your register's decoding timing. Do you still need to know that?
I'm not sure about which interrupts are needed for the diag cart. I remember in my early days of expansion development SPURIOUS INTERRUPT was an issue I saw a lot if AVEC wasn't properly handled.
I've a sneaking feeling you may need to support the autovectored VBL (and/or) HBL for the diag cart to be completely happy. Does Musashi support AVEC/VPA? I've never managed to get a build working.
The cart shouldn't really be filling the screen with nonsense unless you've run a RAM test, so something's gone awry early on, I'm afraid.
Just to be completely sure: it is the Falcon's diag cart you're using? Screen initialisation gibberish would likely happen with an STE cart, for example.
BW
DFB1 Open source 50MHz 030 and TT-RAM accelerator for the Falcon
DSTB1 Open source 16Mhz 68k and AltRAM accelerator for the ST
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark