cmonex was one of the big folks from that period, so I'd trust it, yeah
-
So far I've worked out that there seems to be some list of tasks that need to be completed in order to bring up the system, which is sensible enough. Once the kernel is brought up, there's a function with a check at 13E2C (virtual) of R3, then at 13E30 it loops back if it's > 0.
R3 starts at 0x12 on entry to the function and gradually decrements as various bring-up tasks are completed (based on observing kernel calls and reads/writes to hardware registers). R1 increments, but at a strangely different rate. R3==3, R1==0x10 seems to be the failure point.
-
-
Interestingly, if I set MAME's debugger to break on that condition (R15==0x13E2C, R3==3, R1==0x10), then force R3 to be 0, it continues starting up, though I have to figure it's doing so in an unstable state.
Kiitos. Käytämme tätä aikajanasi parantamiseen. KumoaKumoa
-
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.