ChanServ changed the topic of ##yamahasynths to: Channel dedicated to questions and discussion of Yamaha FM Synthesizer internals and corresponding REing. Discussion of synthesis methods similar to the Yamaha line of chips, Sound Blasters + clones, PCM chips like RF5C68, and CD theory of operation are also on-topic. Channel logs: https://freenode.irclog.whitequark.org/~h~yamahasynths
andlabs has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
andlabs has joined ##yamahasynths
andlabs has quit [Ping timeout: 265 seconds]
<KitsuWhooa>
ValleyBell: neat! What are the hacks? Curious
<cr1901_modern>
So I stopped following closely after the ROMs were dumped- which projects are using/intend to use the CM32P ROMs?
<KitsuWhooa>
no idea
<KitsuWhooa>
but would be nice to have a munt-equivalent
<KitsuWhooa>
VB is writing a mame driver for it
<cr1901_modern>
The hell is munt?
<KitsuWhooa>
MT-32 emulator
<cr1901_modern>
ahhh
<KitsuWhooa>
it's what I used to record the CM-64 music :p
<ValleyBell>
KitsuWhooa: There is a function in the ROM that writes the text to a 32-byte buffer under some conditions manually raises the interrupt for writing from that buffer to the LCD.
<ValleyBell>
Interestingly there is a "data buffer" in the MAME driver for D-110 and MT-32 that caches all LCD "data" writes and flushes them at the next "control" write.
<ValleyBell>
However that code doesn't seem to work with the 32P firmware.
<ValleyBell>
just doing direct (unbuffered) writes works just fine instead
<ValleyBell>
Now I can even switch between certain test modes using the keyboard :)
<ValleyBell>
(it crashes after switching 2 times though)
<cr1901_modern>
Wait, ValleyBell you have the actual unit now?
<ValleyBell>
I'm not sure how far I want to go with the MAME driver, but I would like to get it so far that it boots "normally" and processes some MIDI commands so I can have a look at what it does.
<ValleyBell>
I also still have to figure out how the sample table works. (IC18, offset 0x100, 0x0A bytes per entry)
<KitsuWhooa>
shouldn't be too difficult in theory
<ValleyBell>
There are 2 tables in the IC18 ROM, btw: a tone/instrument table (offset 0x1000, 128 entries I think, 85 valid ones) and a sample table (offset 0x0100, 0xA8 entries)
<ValleyBell>
The tone table contains the instrument name and various parameters. ("tone type", a few note numbers, sample IDs, some stuff I haven't figured out yet)
<ValleyBell>
I haven't yet figured out how the sample table works.
<Sarayan>
since it's a rompler it shouldn't be too hard to reach basic sample playing
<Sarayan>
I can help if you need some
<ValleyBell>
Thanks! I'm sure I'll take your offer sooner or later.
l_oliveira has joined ##yamahasynths
andlabs has joined ##yamahasynths
andlabs has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<KitsuWhooa>
I'm not sure what about those pages is fake :p
<cr1901_modern>
The "equivalence tables"
<ValleyBell>
Okay, now that I've figured out how to properly boot the CM-32P via emulation (and where the test mode "SW A/B" are connected), I can actually see some diagnostic message:
<ValleyBell>
"ERROR 2 3 "
<ValleyBell>
2 = MIDI IN/OUT, 3 = PCM ROM
<Lord_Nightmare>
pcm ROM must not be mapped right, or fail its ROM test i guess
<Lord_Nightmare>
midi in/out means maybe the int/clock source for the midi clock is wrong, i think the mt-32 that clock is divided down by an asic and fed to one of the 8095 int pins?
<Lord_Nightmare>
i suspect it works the same way on the cm-32p
<ValleyBell>
It might fail the PCM card test, actually.
<ValleyBell>
(that's also 3)
<ValleyBell>
The MIDI clock should be right, as I took the MT-32 driver as a reference.
<ValleyBell>
and something is probably not connected properly
<KitsuWhooa>
Maybe EXINT?
<KitsuWhooa>
It's the only line I can see that'd be of interest between the 8098 and the IC that has the 32.768 crystal