openmsx debugger - memory layout

Expert (77)

19-10-2022, 13:05

Suddenly the memory layout is no longer displaying the memory segments (it shows a hyphen instead). Cannot seem to get it working again. Does anybody know how to solve this?

!login ou Inscrivez-vous pour poster

Par Manuel

Ascended (19330)

19-10-2022, 14:53

Question is: what changed to cause the changed behaviour? Think deeply before you say 'nothing', because that can't be true

Par inchl

Expert (77)

19-10-2022, 16:04

A lot of things, I just noticed it suddenly.
However... the "debugger hex view: 4mb external ram regs" does display the segments (*), so I was wondering why the memory layout view does not.

(*) it displays 5 items ????

Par Manuel

Ascended (19330)

20-10-2022, 07:52

What mapper type are you using? Also, posting a screenshot might help to better understand.

Par SjaaQ

Champion (372)

20-10-2022, 08:54

The debugger (development build from github) shows this:

Now when I implement this tcl script:

proc debug_memmapper { } {
  set result ""
  for { set page 0 } { $page < 4 } { incr page } {
    set tmp [get_selected_slot $page]
    append result [lindex $tmp 0] "-" [lindex $tmp 1]
    if { [lsearch [debug list] "MapperIO"] != -1} {
      append result " segment " [debug read "MapperIO" $page]
    } else {
      append result "?"
    }
	append result "\n"
  } 
  return $result
}

And run "debug_memmapper" in the console I do get results:

The machine has a MFRSD+ and the default Turbo-R GT memory mappers configured.

set auto_enable_reverse off
machine "Panasonic_FS-A1GT2_int"
set power off
ext "MegaFlashROM_SCC+_SD"
ext "moonsound"
ext "video9000"
hda insert N:/app/MSX/Disk/SUNRISE_IDE_A.dsk
hdb insert N:/app/MSX/Disk/SD.dsk

debug set_watchpoint write_io 0x2D
debug set_watchpoint write_io 0x00 {} {set throttle $::wp_last_value}

set scale_algorithm simple
set scanline 15
set blur 0
plug joyporta mouse
set too_fast_vram_access real
set VDP.too_fast_vram_access_callback debug_too_fast_vram_access
set power on
set fullspeedwhenloading on
set throttle off
after time 30 "set throttle on"

I used this build:

Par Manuel

Ascended (19330)

20-10-2022, 13:36

So, you think it worked with an earlier build? Can you check which one? That helps a lot in finding out what change caused this.

Par SjaaQ

Champion (372)

20-10-2022, 19:21

Well I don't know what build worked, but none of these do:
openMSX_Debugger_x64_20180220.zip
openMSX_Debugger_x64_20201008.zip

I don't have any older ones. The blendsplitter one does not work either.

Maybe it is some setting in OpenMSX itself?

Par Manuel

Ascended (19330)

20-10-2022, 21:54

I don't know really. It seems to work fine here, using the latest code... if we could find how to reproduce this issue, I could investigate...

Par Manuel

Ascended (19330)

21-10-2022, 07:58

If you want to check whether it's an openMSX setting, you could rename settings.XML to reset them to defaults.