Home Page Forums MAME MAME Current status of the Commodore Amiga driver

Good job! There are many Amiga marked as not working. That needs to be all done so that it can changed to working. Also need catch up with WinUAE. I am currenting using WinUAE at this time.

Yes I'm full into shoot first, ask questions later.

Context should've been obvious but anyway: looking around the AGA entries, now that I have some way to run the interesting stuff.

Pinball Brain Damage (Amiga CD, WHDLoad available) is an odd one: table 2 ball gets stuck if it hits the top left reel, missing HW collision detection extra stuff?

CIA8520 memes (a.k.a. the I don't really comprehend this chip section)

- batman1 (Ocean Batman budget) writes a 0 to all TOD registers for even CIA (the one counting from hsync), wait for 1 vblank sequence then pretends that TOD is higher than > 0x115.
With current logic this can't possibly never get right (i.e. I tried several CPU speed combinations and never got a bit 8 high), TOD stay in latched state between these two events.

- cardiaxx / cardiaxxa keeps looping at a timer B check that never trigger ICR bit 1 (game makes sure to mask all irqs by then).
Specifically it writes 0x48 / 0x49 (TA with run mode) where m_count_b2 gets first set by m_ta_out then cleared by a mask if crb bit 0 is off.
Note that this definitely isn't protection: it does the exact same thing with WHDLoad version ...

I'd have thought you'd get 312 hblanks between vblank on pal and 262 on ntsc.

Which I presume is what it's trying to detect

Yeah, that's my guess too. It has been fixed in https://github.com/mamedev/mame/commit/361e11b3a7c0c5a581a3f30e2840fcb78875c7d8 by Duke: it uses an undocumented feature where latch is off with a CRB Alarm setup.

https://github.com/MiSTer-devel/Min...53e2193d30a657897e3/rtl/cia_timerd.v#L37

I wonder if it affects the 6526 as well.