IeXdi2ClientNotifyMemChg::NotifyMemoryChange (Windows Embedded CE 6.0)
1/5/2010
This method notifies client applications of a change in memory such as virtual memory, physical memory, peripheral I/O, or CPU register context.
Syntax
HRESULT NotifyMemoryChange(
MEM_TYPE2 mt2Changed,
ADDRESS_TYPE Address,
BYTE bAddressSpace,
DWORD dwNbElemChanged,
BYTE bAccessWidthInBytes
);
Parameters
mt2Changed
[in] Memory change type. Indicates one of the following types of change:- Virtual memory
- Physical memory
- Peripheral I/O
- CPU register context
- Address
[in] Starting address of the data buffer to be accessed on the target.
bAddressSpace
[in] Address space to be accessed for virtual memory changes or for CPU register context changes (mtChanged is not mtPhysicalOrPeriIO).By convention, the following values are used.
- 0 = Physical memory
- 1 = Peripheral I/O if not memory mapped
- 2...255 = free for custom use
- dwNbElemChanged
[in] Number of elements of bAccessWidthInBytes to be accessed.
- bAccessWidthInBytes
[in] Data width in bytes, such as byte=1, word=2, dword=4, and so on.
Return Value
The following table shows return values for this method.
| Value | Description |
|---|---|
S_OK |
Indicates the function was successful. |
E_FAIL |
Indicates an unspecified failure. |
Remarks
The debugger can use this function to invalidate its internal cache.
The driver calls this function only when the target is halted. When the target is running, all memory cache should be invalidated.
Requirements
| Header | eXDI2.h |
| Library | ole32.lib, oleaut32.lib |
| Windows Embedded CE | Windows CE 5.0 and later |