El 15/06/2022 a las 20:05, smf escribió: > Right, it's fine for some things, but if your code requires accurate > timing (which is very common with c64 code) then not being able to stop > the vic2/sid/cia etc chips will make it pretty much worthless. > > Even dma'ing memory is going to be problematic as the cpu will have to > stop. But it would make a killer downloader. > > A new motherboard with dual port ram would be cool Of course that there is no way to freeze the complete computer but only the CPU as the VIC-II does. But DMA'ing would make testing almost instant. Imagine an IDE that once compiled, instead of creating files to be burnt in a ROM, or files to be copied to a image disk, would "transfer to C64 memory" directly so changes would be see on the fly. > > On 15/06/2022 17:49, Bill Degnan wrote: >> >> I'd like to clarify my use of an in-circuit emulator, which is not an >> "emulator" of a C64. It's just a CPU emulator. You literally plug the >> in-circuit emulator into the 6502 slot and run the cable into the >> hardware unit. The hardware unit has a serial interface that allows >> you to step machine instructions, load programs, move/inject/change >> values within a block of RAM, take snapshots of RAM and save the log >> session as a text file, etc. >> Bill >Received on 2022-06-15 22:00:43
Archive generated by hypermail 2.3.0.