> I ran it at 44100 but it didn't sound any different, even comparing recordings with
> both frequencies.
>
> I'm having a bit of trouble with this though:
>
> attotime timer_period = attotime::from_hz(device->clock() /3);
>
> This should work fine but it's hanging before emulation starts. Any idea why?
1. The current K056800 implementation doesn't take a clock parameter so it defaults to 0. This is easily fixed with:
Code:
#define MCFG_K056800_ADD(_tag, _interface, _clock) \
MCFG_DEVICE_ADD(_tag, K056800, _clock) \
Unfortunately the K056800 clock isn't documented. It could be 16MHz, 16.934MHz or something else entirely (though unlikely).
2. For a 16.934MHz clock, attotime::from_hz(device->clock() /3) produces a 5.3MHz timer, which is far too high  Ideally we want something like:
Code:
attotime::from_hz(device->clock()) * 16384 * 3
This would give a frequency of 344.5Hz (period 2.9ms - NOT usec!). This of course is MAME's current timer value so some experimentation is in order.
Ideally we need somebody with a boardset and frequency counter to measure the actual values.
|
Index 
Flat 
Re: GTIClub
Reply
Ideally we want something like:
Re: GTIClub
