read_memory_physical
Read bypassing cache
How to use it
Project documentation lists read_memory_physical for the Debugforge MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), then check which tools your installed version makes available. Tool availability can depend on configuration and credentials. A server handshake does not verify this tool’s behavior. See the full listing for setup details.
Install Debugforge
pip install debugforgeOther tools in Debugforge (39)
Delete all breakpoints at once
Connect to a TRACE32 PowerView instance
Delete a breakpoint
Disconnect from TRACE32
Evaluate a TRACE32 expression or function
Execute any TRACE32 PRACTICE command
Get call stack with function names
Get name of currently executing function
Get call stack with all local variables per frame
Get the loaded project configuration (paths, scripts, settings)
Combined run/halt statistics
Get current source file and line
Get current CPU execution state
Start/continue program execution
Stop program execution
List all active breakpoints
Read target memory (hex dump format)
Read through CPU data cache
Read a single CPU register
Read multiple registers at once
Read a C/C++ variable by symbol name
Reset the target CPU
Run a PRACTICE (.cmm) script with timeout
Execute a TRACE32 command on hit
Set a program/read/write/readwrite breakpoint
Breakpoint with HLL condition (e.g., i > 100)
Stop after N-th hit (loop debugging)
Trigger on memory access with optional value match
Trigger only for a specific OS task/thread
Auto-deletes after first hit
Get connection status, TRACE32 version, and system state
Single-step execution (into, over, or out)
Look up symbol name by address
Look up symbol address by name
Enable/disable a breakpoint without deleting
View a variable/struct/array with full expansion
Write data to target memory
Write a value to a CPU register
Write a value to a C/C++ variable