| [hatari-devel] 030 MMU table dumping |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: Hatari Development <hatari-devel@xxxxxxxxxxxxxxxxxxx>
- Subject: [hatari-devel] 030 MMU table dumping
- From: Eero Tamminen <oak@xxxxxxxxxxxxxx>
- Date: Wed, 22 Oct 2025 23:27:48 +0300
- Dkim-filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi 130E32113E18
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=helsinkinet.fi; s=2025-03; t=1761164869; bh=rPV1A1X/qwSPeYxoi4PVrpn6cBx4GlPyoAOnccKZVjA=; h=Date:To:From:Subject:From; b=BY5ncmkVUiqYqIeS1p6mzkZwY+BkelKXj5UCg69BKwiFcdUWf1wH6d9nRqrztLjkq 9NSpSkoDqXkC4s0e2A45aPheExdUq890/5wF3UndUkZxORuF/fgUQ2fqi1wRFtwLDI nzYe31aNqzpmxKenezR0ChRkKoGfHWvFVnH77uj9nEpQTj+xAJhKTlGZhHJ4Puk1pE JgzewWr+Zt4VEG7nGEiXqJ5ATplSgLdC+wLkAuXmcSq5L3neabDrMMSdGJOoOYHHLS GcQaTgzX4TSSdNn9nCJMK6RfKzhHstxcbkkFZPSyS00XCci/QeekME8cys9f9EPocJ pb3dKiQjqH2Dw==
Hi,
With CPU core just getting mmu030_dump_tables() functionality, would it
help MMU debugging for "info mmu" to call that when FC value is provided?
(Patch attached.)
- Eero
From ebb28601123be847c78b999ead627df0a43e1fa7 Mon Sep 17 00:00:00 2001
From: Eero Tamminen <oak@xxxxxxxxxxxxxx>
Date: Wed, 22 Oct 2025 23:24:25 +0300
Subject: [PATCH] Debugger: with <FC>, "info mmu" shows 030 MMU tables
---
src/debug/debugInfo.c | 2 +-
src/m68000.c | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/debug/debugInfo.c b/src/debug/debugInfo.c
index 22b0a805..9aabb887 100644
--- a/src/debug/debugInfo.c
+++ b/src/debug/debugInfo.c
@@ -674,7 +674,7 @@ static const struct {
{ false,"ikbd", IKBD_Info, NULL, "Show IKBD (SCI) register contents" },
{ true, "memdump", DebugInfo_CpuMemDump, NULL, "Dump CPU memory from given <address>" },
{ false,"mfp", MFP_Info, NULL, "Show MFP register contents" },
- { false,"mmu", M68000_MMU_Info, NULL, "Show MMU register contents" },
+ { false,"mmu", M68000_MMU_Info, NULL, "Show MMU register contents (with <FC>, dump 030 MMU tables)" },
{ false,"nvram", NvRam_Info, NULL, "Show (TT/Falcon) NVRAM contents" },
{ false,"osheader", DebugInfo_OSHeader, NULL, "Show TOS OS header contents" },
{ true, "regaddr", DebugInfo_RegAddr, DebugInfo_RegAddrArgs, "Show <disasm|memdump> from CPU/DSP address pointed by <register>" },
diff --git a/src/m68000.c b/src/m68000.c
index 3eafa62a..327b79a9 100644
--- a/src/m68000.c
+++ b/src/m68000.c
@@ -1032,6 +1032,8 @@ void M68000_MMU_Info(FILE *fp, uint32_t flags)
fprintf(fp, "TC:\t0x%08x\n", tc_030);
fprintf(fp, "TT0:\t0x%08x\n", tt0_030);
fprintf(fp, "TT1:\t0x%08x\n", tt1_030);
+ if (flags)
+ mmu030_dump_tables(flags);
}
else /* 68040 / 68060 mode */
{
--
2.39.5