#Syncterm on wondows crashes c64 mode generator
#Syncterm on wondows crashes c64 mode serial
#Syncterm on wondows crashes c64 mode code

c64_win_gdi - implements GUI and connects everything together (C64 board, 1541-II drive and environment)Įverything in the system is synchronized by the CPU clock.c64_environment - definition of interfaces used by emulator to interact with external world (like outputting graphic and audio, reading files.).c64_system - C64 board that connects all emulated hardware as well as keyboard/joystick emulation.c64_io - CIA chip and IEC (serial) bus emulation.c64_av - VIC-II and SID chips emulation.c64_common - clock, memory, IO port and interrupt line emulation.

#Syncterm on wondows crashes c64 mode code

All these techniques provide better compatibility with different software, but they come with a performance costs.Ĭommodore 64 Block Diagram Project StructureĮmulation code is separated in several assemblies so some things, like CPU, memory and IO port emulation, can be reused for other projects like VIC, PET or NES emulators. It also implements real-drive emulation of 1541-II drive.

With appropriate tools it should be possible to convert games that are available in T64 format to D64 (disk) format, so those games should be playable too.Įmulator is cycle-based, which allows perfect emulation of chip timings and synchronization among different chips in the system. REU and tape emulation is also not available. The one major thing that is missing is SID chip emulation. The implementation covers the most of the hardware needed to run games.

#Syncterm on wondows crashes c64 mode generator

3xROM chips - storing Basic interpreter, OS (KERNAL) and character generator used by VIC-II chip.RAM chips - 64 kilobytes available to program.Color RAM - 4-bit memory used by VIC-II chip to generate colors of displayed graphic.

#Syncterm on wondows crashes c64 mode serial

2xCIA chips - responsible for timers and IO (like serial bus, keyboard, joystick.).

6510 chip - the CPU (same as 6502 chip but with one additional IO port).

Parts of Commodore 64 that are visible and can be used by the programmer are: Instead I will focus my attention on emulation - what should be done and how it was done in this implementation.īefore you try to build the solution or run the emulator you should read section about ROM files. There is a huge amount of great resources that cover these subjects better that I could do. In this article I will not try to explain how the actual hardware works. Unfortunately there are stuffs that will remain incomplete, missing or implemented correctly, but it is still a good base to explain the basic concept of emulation. Since it would be a waste time and effort not to use the code available in some way, I decide to write an article about the subject. In the wake of these results I abandoned the C# implementation. I re-implemented the emulator in C++ for other purposes and the implementation yielded a great increase of performance.

The performances are not that great, because of several reasons, like cycle-based and real drive emulation as well as the way some things are implemented in source code. This article describes details about implementation of Commodore 64 emulator written in C#.

Download Commodore 64 source Code - 102.3 KB.

Download Commodore 64 Emulator Binaries - 65.6 KB.