Tutankham sound

GretarJ

New member
Joined
Jun 20, 2012
Messages
10
Reaction score
0
Location
Kopavogur, Hofudborgarsvaedid, Iceland
I have this tutankham board and the sound didn't work. I soon found that the 2732 eprom chips were placed backwards.. I took them out and placed them right. Now the speaker beeps and I can hear a muffled sound when I die (the explosion).

Does it mean that the chips are fried?
If they are, what can I do?

Cheers!
 
If the chip has been damaged, you can't read from it. Which is probably why you don't get sounds now...the board can't read from the chip.

We can use the files from MAME to make new eprom chips.
 
Thanks for the info so far!

I found a eprom writer I can borrow, I would like to do it myself to learn and be able to fix other chips later in life.

But that raises another question. I downloaded the Tutank ROM from http://www.romnation.net/srv/roms/25798/mame/Tutankham.html

That gave me 17 .bin files.

Now how do I find out what is what and how do I know what to put on the 2732 eprom chip marked S1 and the other one marked S2?

Thanks!
 
Thanks, I have downloaded and studied the schematics.

On page 11, there you can see the two 2732 sound proms, in A7 and A8. On page 17 there is the schematics for the soundboard, the chips are located near the bottom right corner, marked 2732 across and A7 and A8 in each side, on top there is also marked CS1 for A7 and CS2 for A8.

So what's the next step for me?
 
Thanks for the info so far!

I found a eprom writer I can borrow, I would like to do it myself to learn and be able to fix other chips later in life.

But that raises another question. I downloaded the Tutank ROM from http://www.romnation.net/srv/roms/25798/mame/Tutankham.html

That gave me 17 .bin files.

Now how do I find out what is what and how do I know what to put on the 2732 eprom chip marked S1 and the other one marked S2?

Thanks!

If you look at the ROM names for that game, you'll see one called S1.7A.

The first part of the file name appears to be the Chip Label, and the second part is probably the chip location. So S1 at Location 7A on the board.

Not all MAME ROMS are named that nicely, but most should give you a good idea of what they are.
 
If you look at the ROM names for that game, you'll see one called S1.7A.

The first part of the file name appears to be the Chip Label, and the second part is probably the chip location. So S1 at Location 7A on the board.

Not all MAME ROMS are named that nicely, but most should give you a good idea of what they are.

Where do you see S1.7A ? Did you extract the .bin files? I've got a bin file called 11-7a.bin.
 
If you look at the ROM names for that game, you'll see one called S1.7A.

The first part of the file name appears to be the Chip Label, and the second part is probably the chip location. So S1 at Location 7A on the board.

Not all MAME ROMS are named that nicely, but most should give you a good idea of what they are.

Where do you see S1.7A ? Did you extract the .bin files? I've got a bin file called 11-7a.bin.

I've been google'ing for hours! Can someone please elaborate? How does Arcadenut see a file called "S1.7A" from the ROM download but all I see are .bin files?

Thanks!
 
I've been google'ing for hours! Can someone please elaborate? How does Arcadenut see a file called "S1.7A" from the ROM download but all I see are .bin files?

Thanks!

He may have another archive where they were named differently. The point is, the sound ROMs are at 7A and 8A. Use the ROM images named "11-7a.bin" and "10-8a.bin".
 
ROM_START( tutankhm )
/* ROMS located on the KT-3203-1B board. */
ROM_REGION( 0x20000, "maincpu", 0 ) /* 64k for M6809 CPU code + 64k for ROM banks */
ROM_LOAD( "m1.1h", 0x0a000, 0x1000, CRC(da18679f) SHA1(8d2a3665db937d0e1d19300ae22277d9db61fcbc) ) /* program ROMs */
ROM_LOAD( "m2.2h", 0x0b000, 0x1000, CRC(a0f02c85) SHA1(29a78b3ffd6b597772953543b02dd59acf5af38c) )
ROM_LOAD( "3j.3h", 0x0c000, 0x1000, CRC(ea03a1ab) SHA1(27a3cca0595bac642caaf9ee2f276814442c8721) ) /* Name guessed */
ROM_LOAD( "m4.4h", 0x0d000, 0x1000, CRC(bd06fad0) SHA1(bd10bbb413d8dd362072522e902575d819fa8336) )
ROM_LOAD( "m5.5h", 0x0e000, 0x1000, CRC(bf9fd9b0) SHA1(458ea2ff5eedaaa02e32444dd6004d2eaadbdeab) )
ROM_LOAD( "j6.6h", 0x0f000, 0x1000, CRC(fe079c5b) SHA1(0757490aaa1cea4f4bbe1230d811a0d917f59e52) ) /* Name guessed */
ROM_LOAD( "c1.1i", 0x10000, 0x1000, CRC(7eb59b21) SHA1(664d3e08df0f3d6690838810b6fe273eec3b7821) ) /* graphic ROMs (banked) -- only 9 of 12 are filled */
ROM_LOAD( "c2.2i", 0x11000, 0x1000, CRC(6615eff3) SHA1(e8455eab03f66642880595cfa0e9be285bf9fad0) )
ROM_LOAD( "c3.3i", 0x12000, 0x1000, CRC(a10d4444) SHA1(683899e1014ee075b16d9d2610c3c5b5c4efedb6) )
ROM_LOAD( "c4.4i", 0x13000, 0x1000, CRC(58cd143c) SHA1(e4ab27c09858cede478f4ed3ac6d7392e383a470) )
ROM_LOAD( "c5.5i", 0x14000, 0x1000, CRC(d7e7ae95) SHA1(7068797770a6c42dc733b253bf6b7376eb6e071e) )
ROM_LOAD( "c6.6i", 0x15000, 0x1000, CRC(91f62b82) SHA1(2a78039ee63226978544142727d00d1ccc6d2ab4) )
ROM_LOAD( "c7.7i", 0x16000, 0x1000, CRC(afd0a81f) SHA1(cf10308a0fa4ffabd0deeb186b5602468028ff92) )
ROM_LOAD( "c8.8i", 0x17000, 0x1000, CRC(dabb609b) SHA1(773b99b670db41a9de58d14b51f81ce0c446ca84) )
ROM_LOAD( "c9.9i", 0x18000, 0x1000, CRC(8ea9c6a6) SHA1(fe1b299f8760fc5418179d3569932ee2c4dff461) )
/* the other banks (1900-1fff) are empty */

/* ROMS located on the KT-5112-2B board. */
ROM_REGION( 0x10000 , "tpsound", 0 ) /* 64k for Z80 sound CPU code */
ROM_LOAD( "s1.7a", 0x0000, 0x1000, CRC(b52d01fa) SHA1(9b6cf9ea51d3a87c174f34d42a4b1b5f38b48723) )
ROM_LOAD( "s2.8a", 0x1000, 0x1000, CRC(9db5c0ce) SHA1(b5bc1d89a7f7d7a0baae64390c37ee11f69a0e76) )
ROM_END
 
Last edited:
....

/* ROMS located on the KT-5112-2B board. */
ROM_REGION( 0x10000 , "tpsound", 0 ) /* 64k for Z80 sound CPU code */
ROM_LOAD( "s1.7a", 0x0000, 0x1000, CRC(b52d01fa) SHA1(9b6cf9ea51d3a87c174f34d42a4b1b5f38b48723) )
ROM_LOAD( "s2.8a", 0x1000, 0x1000, CRC(9db5c0ce) SHA1(b5bc1d89a7f7d7a0baae64390c37ee11f69a0e76) )
ROM_END

Hey, looks like that's from the latest driver: http://mamedev.org/source/src/mame/drivers/tutankhm.c
So that tells you who's actually got the old stuff.... :D

Funny thing I noticed in the latest driver is this comment:
"I include here the document based on Rob Jarrett's research because it's really exaustive."
Yet all of Rob's documentation has been stripped from the driver! :001_smad:
 
you guys need to take documentation like that and store it either on a website or paste it here.

i've done that with sean riddle's work on williams source. otherwise it gets lost. the entries at mamedev or in the source are just short phrases that totally miss the mark on the true detail.
 
Code:
Tutankham Emu Info
------------------

By Rob Jarrett
[email protected] (until June 20, 1997)
or [email protected]

Special thanks go to Pete Custerson for the schematics!!


I've recently been working on an emulator for Tutankham. Unfortunately,
time and resources are not on my side so I'd like to provide anyone with
the technical information I've gathered so far, that way someone can
finish the project.

First of all, I'd like to say that I've had no prior experience in
writing an emulator, and my hardware knowledge is weak. I've managed to
find out a fair amount by looking at the schematics of the game and the
disassembled ROMs. Using the USim C++ 6809 core I have the game sort of
up and running, albeit in a pathetic state. It's not playable, and
crashes after a short amount of time. I don't feel the source code is
worth releasing because of the bad design; I was using it as a testing
bed and anticipated rewriting everything in the future.

Here's all the info I know about Tutankham:

Processor: 6809
Sound: Z80 slave w/2 AY3910 sound chips
Graphics: Bitmapped display, no sprites (!)
Memory Map:

Address        R/W    Bits        Function
------------------------------------------------------------------------------------------------------
$0000-$7fff                Video RAM
                    - Screen is stored sideways, 256x256 pixels
                    - 1 byte=2 pixels
        R/W    aaaaxxxx    - leftmost pixel palette index
        R/W    xxxxbbbb    - rightmost pixel palette index
                    - **** not correct **** Looks like some of this memory is for I/O state, (I think < $0100)
                      so you might want to blit from $0100-$7fff

$8000-$800f    R/W     aaaaaaaa    Palette colors
                    - Don't know how to decode them into RGB values

$8100        W            Not sure
                    - Video chip function of some sort
                    ( split screen y pan position -- TT )

$8120        R            Not sure
                    - Read from quite frequently
                    - Some sort of video or interrupt thing?
                    - Or a random number seed?
                    ( watchdog reset -- NS )

$8160                    Dip Switch 2
                    - Inverted bits (ie. 1=off)
        R    xxxxxxxa    DSWI1
        R
        R            .
        R            .
        R            .
        R
        R
        R    axxxxxxx    DSWI8

$8180                    I/O: Coin slots, service, 1P/2P buttons
        R

$81a0                    Player 1 I/O
        R

$81c0                    Player 2 I/O
        R

$81e0                    Dip Switch 1
                    - Inverted bits
        R    xxxxxxxa    DSWI1
        R
        R            .
        R            .
        R            .
        R
        R
        R    axxxxxxx    DSWI8

$8200                    IST on schematics
                    - Enable/disable IRQ
        R/W    xxxxxxxa    - a=1 IRQ can be fired, a=0 IRQ can't be fired

$8202                    OUT2 (Coin counter)
        W    xxxxxxxa    - Increment coin counter

$8203                    OUT1 (Coin counter)
        W    xxxxxxxa    - Increment coin counter

$8204                    Not sure - 401 on schematics
        W

$8205                    MUT on schematics
        R/W    xxxxxxxa    - Sound amplification on/off?

$8206                    HFF on schematics
        W            - Don't know what it does
                    ( horizontal screen flip -- NS )

$8207                    Not sure - can't resolve on schematics
        W
                    ( vertical screen flip -- NS )

$8300                    Graphics bank select
        W    xxxxxaaa    - Selects graphics ROM 0-11 that appears at $9000-9fff
                    - But wait! There's only 9 ROMs not 12! I think the PCB allows 12
                      ROMs for patches/mods to the game. Just make 9-11 return 0's

$8600        W            SON on schematics
                    ( trigger interrupt on audio CPU -- NS )
$8608        R/W            SON on schematics
                    - Sound on/off? i.e. Run/halt Z80 sound CPU?

$8700        W    aaaaaaaa    SDA on schematics
                    - Sound data? Maybe Z80 polls here and plays the appropriate sound?
                    - If so, easy to trigger samples here

$8800-$8fff                RAM
        R/W            - Memory for the program ROMs

$9000-$9fff                Graphics ROMs ra1_1i.cpu - ra1_9i.cpu
        R    aaaaaaaa    - See address $8300 for usage

$a000-$afff                ROM ra1_1h.cpu
        R    aaaaaaaa    - 6809 Code

$b000-$bfff                ROM ra1_2h.cpu
        R    aaaaaaaa    - 6809 Code

$c000-$cfff                ROM ra1_3h.cpu
        R    aaaaaaaa    - 6809 Code

$d000-$dfff                ROM ra1_4h.cpu
        R    aaaaaaaa    - 6809 Code

$e000-$efff                ROM ra1_5h.cpu
        R    aaaaaaaa    - 6809 Code

$f000-$ffff                ROM ra1_6h.cpu
        R    aaaaaaaa    - 6809 Code

Programming notes:

I found that generating an IRQ every 4096 instructions seemed to kinda work. Again, I know
little about emu writing and I think some fooling with this number might be needed.

Sorry I didn't supply the DSW and I/O bits, this info is available elsewhere on the net, I
think at tant or something. I just couldn't remember what they were at this writing!!

If there are any questions at all, please feel free to email me at [email protected] (until
June 20, 1997) or [email protected].


BTW, this information is completely free - do as you wish with it. I'm not even sure if it's
correct! (Most of it seems to be). Giving me some credit if credit is due would be nice,
and please let me know about your emulator if you release it.


Sound board: uses the same board as Pooyan.
 
That's an interesting historical doc, but most (all?) of that info can be found in the memory map of the current MAME driver.
Code:
	AM_RANGE(0x0000, 0x7fff) AM_RAM AM_SHARE("videoram")
	AM_RANGE(0x8000, 0x800f) AM_MIRROR(0x00f0) AM_RAM AM_SHARE("paletteram")
	AM_RANGE(0x8100, 0x8100) AM_MIRROR(0x000f) AM_RAM AM_SHARE("scroll")
	AM_RANGE(0x8120, 0x8120) AM_MIRROR(0x000f) AM_READ(watchdog_reset_r)
	AM_RANGE(0x8160, 0x8160) AM_MIRROR(0x000f) AM_READ_PORT("DSW2")	/* DSW2 (inverted bits) */
	AM_RANGE(0x8180, 0x8180) AM_MIRROR(0x000f) AM_READ_PORT("IN0")	/* IN0 I/O: Coin slots, service, 1P/2P buttons */
	AM_RANGE(0x81a0, 0x81a0) AM_MIRROR(0x000f) AM_READ_PORT("IN1")	/* IN1: Player 1 I/O */
	AM_RANGE(0x81c0, 0x81c0) AM_MIRROR(0x000f) AM_READ_PORT("IN2")	/* IN2: Player 2 I/O */
	AM_RANGE(0x81e0, 0x81e0) AM_MIRROR(0x000f) AM_READ_PORT("DSW1")	/* DSW1 (inverted bits) */
	AM_RANGE(0x8200, 0x8200) AM_MIRROR(0x00f8) AM_READNOP AM_WRITE(irq_enable_w)
	AM_RANGE(0x8202, 0x8203) AM_MIRROR(0x00f8) AM_WRITE(tutankhm_coin_counter_w)
	AM_RANGE(0x8204, 0x8204) AM_MIRROR(0x00f8) AM_WRITENOP // starfield?
	AM_RANGE(0x8205, 0x8205) AM_MIRROR(0x00f8) AM_WRITE(sound_mute_w)
	AM_RANGE(0x8206, 0x8206) AM_MIRROR(0x00f8) AM_WRITE(tutankhm_flip_screen_x_w)
	AM_RANGE(0x8207, 0x8207) AM_MIRROR(0x00f8) AM_WRITE(tutankhm_flip_screen_y_w)
	AM_RANGE(0x8300, 0x8300) AM_MIRROR(0x00ff) AM_WRITE(tutankhm_bankselect_w)
	AM_RANGE(0x8600, 0x8600) AM_MIRROR(0x00ff) AM_WRITE_LEGACY(timeplt_sh_irqtrigger_w)
	AM_RANGE(0x8700, 0x8700) AM_MIRROR(0x00ff) AM_WRITE(soundlatch_byte_w)
	AM_RANGE(0x8800, 0x8fff) AM_RAM
	AM_RANGE(0x9000, 0x9fff) AM_ROMBANK("bank1")
	AM_RANGE(0xa000, 0xffff) AM_ROM
 
Back
Top Bottom