6502 EMULATOR T CODE
6502 EMULATOR T WINDOWS

That makes it hard to detect what goes in RAM and what goes in EEPROM. Zero page and stack can be in Arduino RAM, the program could be in EEPROM, but where are the BASIC variables stored? On most interpreted BASICs they start at the top of RAM and work down towards where the program is. I assume you can't put everything in EEPROM or it will be hellishly slow. It's just a first test any as I plan to run CBM-basic on it for Vic-20/C64 emulation. That should keep it relative safe even though the basic variables gets written in EEPROM when the basicprogram runs. To be safe I mapped the first 768bytes to Arduino RAM and the rest is EEPROM space. It can take 1000000 writes before going bad. I used a 24LC256 32Kb EEPROM for memorystorage. I hacked around abit with your emulator and patched Read/Write6502. I'm looking into getting a 32 KB SPI chip for more memory. I wouldn't want to use EEPROM because it can only be written to so many times before it goes bad.

6502 EMULATOR T CODE

The 767 bytes is just what EhBASIC reports as the remaining storage for BASIC code and variables. The emulator has access to 1536 bytes of RAM, but the first 512 bytes make up the 6502's zero page and stack page, then the next 256 are used by the BASIC interpreter itself. The program (as in the EhBASIC ROM image) is stored in the flash memory along with the code.

6502 EMULATOR T WINDOWS

I wrote an Apple emu for Windows a while back with cassette support (via WAV files), and the interface is unbelievably simple. There isn't enough program storage on an Uno to link in the SD card functions and still have the BIOS embedded with it, I tried.Д¬assette should also be reasonably easy to add. You would need something like the Mega 2560 for that, though. You could also use a microSD shield to store Apple disk images on. Or maybe even go one step further: Reading programs from a cassette tape scnr Just think about printer integration, maybe even floppy. :)ДЄlso: Have you thought about mapping a whole arduino I/O Port to the memory? That would enable for a HELL OF A LOT of mega cool features. If you were to get at least 48 KB of SPI memory you could emulate the Apple ][. Those are the only two functions you need to worry about. If I'm reading your code correctly, to enable the use of external - say SPI memory you would only need to write read6502() and write6502() for your SPI flash, right? Very cool :) Map the analog ports to memory addresses so if you peek() them you read the analog value (only 8 bits, but heyвЂ¦the bottom 2 bits are usually just noise anyway) That way you could program it in BASIC and deploy it in real projects. More ideas: Make it so that if you connect a special pin to GND it automatically runs the BASIC program (stored in EEPROM) on boot-up. You could probably spend a lifetime writing BASIC and not wear it out (how long would it take you to make 100,000 edits to a program?)

I wouldnвЂ™t want to use EEPROM because it can only be written to so many times before it goes bad. I meant store the BASIC program in EEPROM (and variables in RAM). The emulator has access to 1536 bytes of RAM, but the first 512 bytes make up the 6502вЂ™s zero page and stack page, then the next 256 are used by the BASIC interpreter itself.

6502 emulator t