Home Page Forums MAME MAME Labtam 3000

Nothing really, the manual is very comprehensive.

Actually there is one question that I'm a bit unclear on: The manual states pretty clearly that the ROM space for the 8086 board is from 0x70000 to 0x7FFFF, with the upper half of the memory space being reserved for a Multibus window.

Have I overlooked some spot in the manual where it makes it clear how the 8086 is able to fetch its boot vectors, since those invariably come from the upper 16 bytes of the overall address space?

I've started in on writing the driver, hoping that the Z80 would be a more reasonable thing to bring up first.

Annoyingly, there seems to be some strangeness in terms of the Z80 ROMs, right from the beginning.

It's not entirely clear whether "labtam3000-z80-boot-abs-0.bin" or "labtam3000-z80-boot-abs-1.bin" is what's located at address 0 from the Z80's perspective, but I'm betting it's the first one.

That said, the first few addresses it probes are fairly weird.

According to the technical manual, the default would be for memory accesses to default to the "System Map", which has the first 16K for the boot EPROMs, the next 2K at offset 0x4000 for local RAM, then 2K for the "intermap window" (whatever that is) at 0x4800, and then 0x8000 through 0xBFFF mapped to 0xF8000 through 0xFBFFF as an "I/O Buffer Window", mapped to 0xF8000 through 0xFBFFF as Multibus addresses.

These are the first few things the Z80 does. I'm always a bit suspicious when the first thing a CPU does is read things, rather than write things. Does anyone have any suggestions as to what's going on?

For Z80, check if the IRQ (0x38) and NMI (0x66) default vectors make sense in either of the ROMs. The one where they do will be the correct one at 0 in most cases.

Agree to look strange for initial rom Z80..

Neither of them make a whole lot of sense as far as initial programs go.

The -1 ROM doesn't seem to have anything valid at 0x38, and the NMI vector is itself a bit weird, though if you shave the byte off of the previous instruction, it produces somewhat sensible instructions:



The -0 ROM, as you've indicated, also doesn't seem to make too much sense for mapping at address 0.

try to see if the code functions in the ROMS line up with any of the absolute address jumps / calls you can see.

I suspect neither maps at 0, maybe half size dumps or something

Could also be the upper address line inverted or similar, check the middle of the ROM for the startup code etc.

We have another board with z80 installed in a working labtam. I will read ROM dumps from this machine, maybe they will be different.

It's not necessarily a given that Z80 code will have an interrupt handler at 0x38, since that's only necessarily the vector in IM 1 (though most arcade games do use that). Anyway, neither of those listings looks much like any sort of boot code to me either.

The -0 rom comes first, and set the PC to 1800 at start. Then it starts to make sense.

There's no handler for NMI or IM1.