Re: [cc65] VICE/NESICIDE integration

From: Gábor Lénárt <lgb1lgb.hu>
Date: 2012-03-28 11:27:20
On Wed, Mar 28, 2012 at 11:17:23AM +0200, Uffe Jakobsen wrote:
> 
> 
> On 2012-03-27 23:53, Christopher Pow wrote:
> >
> >Right now I'm doing it all with blocking QTcpSocket calls in a worker
> >thread, which is annoying because I have to block for about 1 second
> >in order to keep up.  Once I get the commands down that I need to use
> >to support the IDE functionality, I'll spend more time working on the
> >asynchronous QTcpSocket implementation, which should be much faster.
> >But, having said that, I did notice that it takes quite a long time to
> >get results for "m $0 $ffff"  =].  Perhaps I'll have to make the
> >memory dump smarter somehow.
> >
> 
> Shared memory ? a bit like the MITSHM framebuffer sharing option in VICE ?
> 
> Some years ago I started extending VICE with a shared memory mapping
> option that would enable external applications to peek (and poke)
> into the emulated memory map - but never finished the job...

Well yes, much easier that way, however a bit hard to do it well. For
example you must also know if ROM/RAM is seen for a given address. Though I
am not familiar with VICE internals at all, I can imagine that C64's RAM is
stored as a 64K long memory area. However from the view point of the
(emulated) C64 an address may be different, it can be ROM, I/O area etc
depending on the memory banking state. The external "debugger" (or whatever
we want to name it as) must know this too (also what happens with some
"exotic" stuffs like cartridge emulation with custom ROM, etc).

Afaik, VICE would be able to "export" all the memory (as shared memory) for
the emulated hardware (including ROMs, RAMs) maybe a monitor command can be
developed which tell VICE to do it, then the response of the command would
tell how some can interact with.  Also there can be a monitor command which
gives an overview of the current memory configuration of the emulated
machine, so the external debugger can know which exported shared memory
segments should read/write etc for a given address?

----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.
Received on Wed Mar 28 11:27:42 2012

This archive was generated by hypermail 2.1.8 : 2012-03-28 11:27:46 CEST