![os-9 68k emulator -mac os-9 68k emulator -mac](http://www.reischke.de/dtr/imgs/d2316fd0.gif)
I also noticed a bug in the ROM: it always uses the first sector buffer because it takes the current buffer bit from the wrong memory location. The ROM even has compensation for shifts of between 1 and 7 bits in the incoming subcode Q data, probably because of some hardware timing issue. It turns out that the 601 ROM performs CRC validation on the subcode Q data from the lead-in area (which is where the TOC is stored), and CD-i Emulator didn’t provide a valid CRC (no other ROMs I’ve seen so far validate this in software). Having done that, I did some more digging into the TOC read issue.
![os-9 68k emulator -mac os-9 68k emulator -mac](http://i0.wp.com/www.toughdev.com/content/wp-content/uploads/2017/04/Screenshot-from-2017-04-11-15-38-30.png)
For now I’ve assumed that version 2.x also uses the older CDIC chip, but that may be wrong (the 602 or 604 might be interesting test cases). The 180 has no such chip, the 601 has version 1.x where the 605 has version 3.x.
OS 9 68K EMULATOR MAC SOFTWARE
I have yet to find a way to get chip version information from the CDIC chip itself, so for the time being I’ve keyed the differences on the SLAVE software version. I noticed the JNMS / Maxi-MMC link from the CD-i player type table in the July 1996 issue of The Interactive Engineer (it’s on the ICDIA site) turns out I had misinterpreted the Board column on page 4 (there’s also an error there: the 601/602 certainly do not have the 180 board!).Īfter noticing this I did some testing and it turns out that the CDIC modifications needed for the 180 also work for the 601, including the TOC reading problem. The link between the JNMS and Maxi-MMC boards is the CDIC chip: both turn out to have the same older CDIC chip version that differs in a few details from the version used on the Mini-MMC and Mono-I boards players (I described these differences in the earlier “CD-i 180 disc playing” post). From the emulation point of view it is virtually identical to the Mini-MMC board used by the CDI 605 player, but it has a different CDIC chip version. The Maxi-MMC board is the one in the CDI 601 and 602 players. It is not used in any other player and contains a CDIC (CD Interface Controller) chip but no SLAVE processor. The JNMS board is the one in the CDI 180 player (also called the JNMS player). I had previously erroneously identified these two boards but they are different. This weekend I fixed some disc emulation issues for the JNMS and Maxi-MMC boards. System that enabled word processing, spreadsheets and various programming The MC6809 was an 8-bit CPU with some 16-bit features from Motorola
![os-9 68k emulator -mac os-9 68k emulator -mac](https://i.ytimg.com/vi/8KkB4Bmc9xY/hqdefault.jpg)
Systems can easily be configured to take advantage of these devices.Įach device has a corresponding OS-9 device driver. PIA6821 emulates a Motorola 6821 Peripheral Interface Adapterīecause of their modularity, the Microware OS-9 or NitroOS9 operating.VirtualDisk interfaces a DSK image to the emulator as a floppy or harddisk.
![os-9 68k emulator -mac os-9 68k emulator -mac](https://m.gjcdn.net/fireside-post-image/900/5611266-ppah3ajw-v4.jpg)
HWClock makes it possible to get the date and time from the host of the emulator.IRQBeat sends an IRQ interrupt every 20 milliseconds to the CPU.AciaGraphicalUI uses Java Swing to create a simple terminal and AciaTelnetUI opens a socket on port 2323, which the user can telnet to. Both Acias can be configured with 3 different user interfaces: AciaConsoleUI writes to Java's System.out and reads from System.in.Acia6850 emulates a Motorola 6850 UART.The other called mo5 emulates a Thomson MO-5 That runs OS-9 Level 1 in multi-user mode with two terminals, two diskĭrives and a printer. You can allocate RAM, load data into the memory and set up devices. The purpose of this project is to create an 6809 emulator that canīe configured at runtime with a range of memory mapped devices. Retrocomputing: A Java-based 6809 emulator