Home Page Forums MAME MAME Triumph-Adler alphatronic P3 (+ P1, P2 and P4)

Adding 1kb of separate ram at 0x1800 that is implied by the memmap on the first page (there's also 2 512 byte sram chips on the cpu board) fixes the above problem. The main problems now is the keyboard missing shift key and doubling key presses.

Thanks!
We've put a call out for help for more dumps of the keyboard controller, since one of mine is obviously flaky, the 8041 gives inconsistent dumps all the way, so we're stuck with the 8278 dump for the moment.

I'll post a table helwie sent me that might help demystify the keyboard addresses.

Robert

This is helwie44's comparison chart between the ITT3030's and the Alphatronic's keyboard

https://mega.nz/#!OBg3SKhK!qdSM_MxRl6ml5buVcI9xvU9f2Jb-zBewILcv6EZw_1c

I grabbed the head of your tree and pushed it. It was just diverging too much making it hard to work on.

Robert, do the "inconsistent dumps" of the 8041 all have bad readings on D2? If not, it should be possible to make a good dump out of them by piecing a couple together (and using the 8278 dump as a reference).

I've put a set of the bad dumps of the 8041 from both TeamE and myself on the FTP.

Thank you for many changes so that the driver goes ahead. In this source version - the translation is aborted with an error.
therefore, I have locally exchanged two source lines back with me. This is the translation has been done.


The SHIFT function is obviously visible via the 0xCy function code via the Excel table. Thanks for good work!

The main problem with the double character (with a keystroke) is opaque. In 8085 debug mode, the MAME of the 8278 chip on port 0x11 will always return the first read from the 0x10 dataport (1st character is ok), but then the status port 0x11 will already supply a character as ready. And the data port 0x10 provides an identical character.
Could it possibly be a wrong timing in the 8278 chip emulation? From the documentation of the 8278, the internal scan time is about 10 ms !!?
Does anyone have deeper information - about this error behavior?

Using the BP-1400 programmer LN procured for me, I dumped the 8041 that was yielding iffy reads for both TeamE and me, and they're turning out identical every time now, plus they're identical with the 8278 from the other machine.

https://mega.nz/#!uZ4VzJaL!NuFOf8xXVbWZA_jpE1kpudqupRkViXz6aIIiy3Bckk0

After examining the various dumps, I reconsidered my earlier judgment. Of course it wasn't just D2 that would be bad in the first dump; bytes were getting swapped across A2, too. I don't think it really helps to include two identical dumps as separate BIOS versions, though...

If you can add the second chargen in a way that allows easy switching (and therefore switching between the two machines that differ in their card sets, even though they share the same BIOS and keyboard ROMs) it would be great.