1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
# Callback on read from uninitialized memory (UMR). Not enabled by default.
set_help_text umrcallback \
{This is an example of a UMR callback function. You can set the "umr_callback"
setting in openMSX to "umrcallback" and this function will be called whenever
openMSX detects a read from uninitialized memory. It might be a good idea to
go into 'debug break' mode in this callback, so that you can easily examine
what is going on which has caused the UMR.
@param addr The absolute address in the RAM device.
@param name The name of the RAM device.
}
proc umrcallback {addr name} {
puts stderr [format "UMR detected in RAM device \"$name\", offset: 0x%04X, PC: 0x%04X" $addr [reg PC]]
}
#set umr_callback umrcallback
# Callback on changing the VDP command registers while a command is still in
# progress. Not enabled by default.
set_help_text vdpcmdinprogresscallback \
{This is an example of a vdpcmdinprogress callback function. To use it execute
set vdpcmdinprogress_callback vdpcmdinprogresscallback
After changing that setting this proc will be called whenever openMSX detects a
write to a VDP command engine register while there's still a VDP command in
progress. Often this is an indication of a bug in the MSX program. This example
callback proc only prints the register number, the value that was being written
and the program counter. Feel free to write your own callback procs. For
example it might be a good idea to enter 'debug break' mode in your callback,
so that you can easily examine what is going on.
@param reg The VDP command engine register number that was being written
This is in range 0..14. Note that it's OK to write register 12
while a command is in progress. So this callback will not be
triggered for writes to register 12.
@param val The value that was being written.
}
proc vdpcmdinprogresscallback {reg val} {
puts stderr [format "Write to VDP command engine detected while there's still a command in progress: reg = %d, val = %d, PC = 0x%04X" [expr {$reg + 32}] $val [reg PC]]
}
#set vdpcmdinprogress_callback vdpcmdinprogresscallback
# Callback on setting invalid PSG port directions.
set psg_directions_warning_printed false
proc psgdirectioncallback {} {
if {$::psg_directions_warning_printed} return
set ::psg_directions_warning_printed true
message {The running MSX software has set unsafe PSG port directions.
Real (older) MSX machines can get damaged by this.} warning
}
interp alias {} default_invalid_psg_directions_callback {} psgdirectioncallback
# Callback on setting an invalid PPI mode.
set ppi_mode_warning_printed false
proc ppimodecallback {} {
if {$::ppi_mode_warning_printed} return
set ::ppi_mode_warning_printed true
message {Invalid PPI mode selected. This is not yet correctly emulated. On a real MSX this will most likely hang.} warning
}
interp alias {} default_invalid_ppi_mode_callback {} ppimodecallback
# Callback on DI;HALT.
proc dihaltcallback {} {
set machine [machine_info type]
if {[string match "MSX*" $machine] || $machine eq "SVI"} { # These machines do not use NMI.
message "DI; HALT detected, which means a hang. You can just as well reset the machine now..." warning
}
}
interp alias {} default_di_halt_callback {} dihaltcallback
# Callback on too fast VRAM read/write, not enabled by default
proc warn_too_fast_vram_access {} {
message [format "Too fast VRAM access PC=0x%04x Y-pos=%d" [reg PC] [machine_info VDP_msx_y_pos]] warning
}
proc debug_too_fast_vram_access {} {
warn_too_fast_vram_access
debug break
}
#set VDP.too_fast_vram_access_callback debug_too_fast_vram_access
#set VDP.too_fast_vram_access_callback warn_too_fast_vram_access
proc default_dot_clock_direction_callback {} {
message "The running MSX software has set bit 0 of VDP register 9 (dot clock direction) to one. In an ordinary MSX, the screen would go black and the CPU would stop running." warning
}
#set VDP.dot_clock_direction_callback default_dot_clock_direction_callback
proc sensorkidportstatuscallback {port value} {
message "Sensor Kid port $port has been [expr {$value ? "enabled" : "disabled"}]" info
}
proc sensorkidacquirecallback {port} {
set time [machine_info time]
switch $port {
0 { # Sine
return [expr {int(sin($time * 0.1) * 127.0) + 128}]
}
1 { # Sawtooth
return [expr {int($time * 10.0) % 256}]
}
2 { # Triangle
set t [expr {int($time * 4.0) % 512}]
return [expr {($t > 255) ? (511 - $t) : $t}]
}
default {
return 255
}
}
}
set sensor_kid_port_status_callback sensorkidportstatuscallback
set sensor_kid_acquire_callback sensorkidacquirecallback
proc default_V9990_invalid_register_read_callback {reg} {
message [format "Reading from V9990 write-only register 0x%x" $reg] warning
}
proc default_V9990_invalid_register_write_callback {reg value} {
message [format "Writing 0x%x to V9990 read-only register %i" $value $reg] warning
}
#set v9990_invalid_register_read_callback default_V9990_invalid_register_read_callback
#set v9990_invalid_register_write_callback default_V9990_invalid_register_write_callback
|
