I've made some small changes to my version.

A change to the way the overall timing is done means faster execution on slow machines and a lower CPU load on fast machines.

Lee.

Thanks for checking that Lee!
Simply doing a hex search for the opcode values $D8 (CLD) and $F8 (SED) will not suffice, as I found out quickly.
One has to observe the hex values within the code simultaneously, requiring extra effort...

_________________
65Org16:https://github.com/ElEctric-EyE/verilog-6502

When I have a good month I will certainly try make an effort (this happens alot as I'm not feeling too good in periods of my life because of sickness).

Wiill upload latest versions to its webpage later on as fits (For example Peter's version and mine is screen compact version for visually impaired). Similiar to the one you got to see one version of.

I see many ppl already starts making use of the tiny emulator, doing online versions etc. Very nice.
This was the very intention, very happy about the results.

Got some ideas how to push the envelope further, but right now I really have to stay laidback to not get worse. Will post here when further progress happens for sure.

I want to personally want to say thankyou one would not know how much work I put down into that little emu.
My sickness is literally worse because of it. Stupid move of me trying to hard.

For the ones who loves the Commodore or just retro and want a breeze of nostalgia
you may check these out, very nice reading.

http://www.commodore128.org/Library/ind ... +64+Books/

Best wishes!
/Jay

Updated.

Cycle timings for opcodes are now almost all correct. Still some work to do on indexed address modes.

Lee.

Another updare.

This is much faster, it no longer maxes out the CPU in my crappy laptop in debug mode. Well, 98% isn't quite maxed out.

I was going to include a compiled version for download but no matter how I try I can't get it to run on any other machine but the one I compiled it on. It gives up with a "Memory access violation!" error. I spent a couple of hours chasing that but even after trying many 'fixes' for this error it still didn't work.

Anyone else tried and got it to work?

Writing to the C64 screen is still a huge time sink as it writes 64*2 pixels for every character written to the screen RAM. Is there no way to use the character bitmap data directly?

This actually looks like a viable 6502 emulator, even on my crappy old laptop it now executes the 6502 code more than 20 times faster than the original C64 did, just don't write to the screen.

Is anyone else apart from JayPanda trying this out?

Lee.

Not yet, although I am a 'serious' C-64 fan... And JayPanda's last link is much appreciated!
Your guys' work will not go un-noticed...

_________________
65Org16:https://github.com/ElEctric-EyE/verilog-6502

I downloaded the Blitz3D demo, your modified code, and the 3 rom files.

It would not run under the demo version as it reports the source file is too large for demo mode.

I spent 10 minutes stripping out all the comments and extra lines and just barely got it to fit within the apparent 16k limit.

It did run after that. I'm not sure I want to spend $100 for the Blitz3D full version. However, this does look like a decent platform for those who want to pursue it.

Daryl

Yet another update replaces pixel by pixel screen drawing with character tiles. No more stripey screen, unless you want it, and much faster screen updates.

Enjoy.

Lee.

Just for giggles I made a VIC 20 version as well.

Lee.

JayPanda

I see from the Blitz forum that you have made some optimizations to my 0.53 version of the code.

I've looked through your code a few times but can't work out where your optimizations are. Could you point them out to me?

Cheers,
Lee.

Both the C64 and Vic emulators have been updated.

Cycle timings completed, alternate character sets available and more keys mapped to CBM keycodes.

If I ever implement a storage device you can LOAD from and SAVE to these would then be almost usefull.

Lee.