This debuggable is always 128kB in size, even if the actual amount of VRAM is different: More...

Inheritance diagram for openmsx::LogicalVRAMDebuggable:

Collaboration diagram for openmsx::LogicalVRAMDebuggable:

Public Member Functions
	LogicalVRAMDebuggable (VDP &vdp)

byte	read (unsigned address, EmuTime::param time) override

void	write (unsigned address, byte value, EmuTime::param time) override

Public Member Functions inherited from openmsx::SimpleDebuggable
unsigned	getSize () const finaloverride

const std::string &	getDescription () const finaloverride

byte	read (unsigned address) override

void	write (unsigned address, byte value) override

const std::string &	getName () const

MSXMotherBoard &	getMotherBoard () const

Additional Inherited Members
Protected Member Functions inherited from openmsx::SimpleDebuggable
	SimpleDebuggable (MSXMotherBoard &motherBoard, const std::string &name, const std::string &description, unsigned size)

	~SimpleDebuggable ()

Protected Member Functions inherited from openmsx::Debuggable
	Debuggable ()

	~Debuggable ()

Detailed Description

This debuggable is always 128kB in size, even if the actual amount of VRAM is different:

If there is less actual VRAM (e.g. 64kB), the upper regions of this debuggable act in the same way as if the CPU would read/write those addresses (mirroring or return fixed value / ignore write).
If there is more VRAM (128kB + 64kB extended VRAM), the extended VRAM part is not accessible via this debuggable (it is via the 'physical VRAM' debuggable). We might change this in the future, but the interaction between interleaving and extended VRAM can be tricky, for example the size of this debuggable would have to be 256kB to be able to access the complete extended VRAM in interleaved mode.

Definition at line 44 of file VDPVRAM.cc.