/[projet1]/public/pc/tools/osdk/main/Osdk/_final_/Oricutron/ReadMe.txt
Defence Force logotype

Contents of /public/pc/tools/osdk/main/Osdk/_final_/Oricutron/ReadMe.txt

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1118 - (show annotations)
Mon Feb 24 19:28:30 2014 UTC (5 years, 6 months ago) by dbug
File MIME type: text/plain
File size: 7413 byte(s)
Osdk 1.1 
- Updated Oricutron to version 1.1
1 Oricutron 1.1
2 -------------
3
4 (c)2009-2013 Peter Gordon (pete@petergordon.org.uk)
5
6 This is a work in progress.
7
8
9 Current status
10 ==============
11
12 6502: 100% done (apart from any unknown bugs :)
13 VIA: 95% done.
14 AY: 99% done.
15 Video: 100% done
16 Tape: 99% done (.TAP, .ORT and .WAV supported)
17 Disk: Reading/Writing sectors works. No track read/write.
18
19
20
21 Credits
22 =======
23
24 Programming
25 -----------
26
27 Peter Gordon
28
29
30 Additional Programming
31 ----------------------
32
33 Francois Revol
34 Alexandre Devert
35 Stefan Haubenthal
36 Ibisum
37 Kamel Biskri
38 Iss
39
40
41 Amiga & Windows ports
42 ---------------------
43
44 Peter Gordon
45
46
47 MacOS X port
48 ------------
49
50 Francois Revol
51 Kamel Biskri
52
53
54 MorphOS & AROS ports
55 --------------------
56
57 Stefan Haubenthal
58
59
60 Linux port
61 ----------
62
63 Francois Revol
64 Ibisum
65 Alexandre Devert
66
67
68 Pandora port
69 ------------
70
71 Ibisum
72
73
74 Pravetz disk support
75 --------------------
76
77 Iss
78
79
80
81
82 Thanks
83 ======
84
85 Thanks to DBug and Twilighte for letting me distribute their demos and
86 games with Oricutron.
87
88 Thanks to DBug, Twilighte, Chema, kamelito, Yicker, JamesD, Algarbi, ibisum,
89 jede, thrust26 and everyone else for their help and feedback!
90
91
92
93 AVI export notes
94 ================
95
96 The AVI export uses the MRLE codec. Your favourite player might not support
97 it, but MPlayer plays it, ffmpeg converts it and you can upload it directly
98 to youtube.
99
100 Note that the MRLE codec shows up some endian-issues on the Amiga OS4 port
101 of MPlayer, so it will sound crappy and have wrong colours until those bugs
102 are fixed :-(
103
104
105 Command line
106 ============
107
108 You can specify certain options on the command line. All options have
109 both short and long versions. For example:
110
111 -mblah
112
113 or
114
115 --machine blah
116
117 Is the same thing. Note that the short version doesn't have a space, but
118 the long version does.
119
120 Here are all the options:
121
122
123 -m / --machine = Specify machine type. Valid types are:
124
125 "atmos" or "a" for Oric atmos
126 "oric1" or "1" for Oric-1
127 "o16k" for Oric-1 16k
128 "telestrat" or "t" for Telestrat
129 "pravetz", "pravetz8d" or "p" for Pravetz 8D
130
131 -d / --disk = Specify a disk image to use in drive 0
132 -t / --tape = Specify a tape image to use
133 -k / --drive = Specify a disk drive controller. Valid types are:
134
135 "microdisc" or "m" for Microdisc
136 "jasmin" or "j" for Jasmin
137
138 -s / --symbols = Load symbols from a file
139 -f / --fullscreen = Run oricutron fullscreen
140 -w / --window = Run oricutron in a window
141 -R / --rendermode = Render mode. Valid modes are:
142
143 "soft" for software rendering
144 "opengl" for OpenGL
145
146 -b / --debug = Start oricutron in the debugger
147 -r / --breakpoint = Set a breakpoint
148 -h / --help = Print command line help and quit
149
150 --turbotape on|off = Enable or disable turbotape
151 --lightpen on|off = Enable or disable lightpen
152 --vsynchack on|off = Enable or disable VSync hack
153 --scanlines on|off = Enable or disable scanline simulation
154
155 NOTE: If you are not sure what machine or drive type is required for a disk or
156 tape image, just pass the filename without any options and Oricutron will
157 try and autodetect for you.
158
159
160 Examples:
161
162 oricutron tapes/tape_image.tap
163 oricutron disks/disk_image.dsk
164 oricutron --machine atmos --tape "tape files/foo.tap" --symbols "my files/symbols"
165 oricutron -m1 -tBUILD/foo.tap -sBUILD/symbols -b
166 oricutron --drive microdisc --disk demos/barbitoric.dsk --fullscreen
167 oricutron -ddemos/barbitoric.dsk -f
168 oricutron --turbotape off tapes/hobbit.tap
169
170
171
172 Keys
173 ====
174
175 In emulator
176 -----------
177
178 F1 - Bring up the menu
179 F2 - Go to debugger/monitor
180 F3 - Reset button (NMI)
181 F4 - Hard reset
182 Shift+F4 - Jasmin reset
183 F5 - Toggle FPS
184 F6 - Toggle warp speed
185 F7 - Save all modified disks
186 Shift+F7 - Save all modified disks to new disk images
187 F9 - Save tape output
188 F10 - Start/Stop AVI capture
189 Help - Show guide
190
191
192 In menus
193 --------
194
195 Cursors - Navigate
196 Enter - Perform option
197 Backspace - Go back
198 Escape - Exit menus
199 (or use the mouse)
200
201
202 In Debugger/Monitor
203 -------------------
204
205 F2 - Return to the emulator
206 F3 - Toggle console/debug output/memwatch
207 F4 - Toggle VIA/AY/disk information
208 F9 - Reset cycle count
209 F10 - Step over code
210 F11 - Step over code without tracing into
211 subroutines.
212 F12 - Skip instruction
213
214
215 In the console:
216 ---------------
217
218 Up/Down - Command history
219
220
221 In memwatch:
222 ------------
223
224 Up/Down - Scroll (+shift for page up/down)
225 Page Up/Page Down - Page up/down
226 Hex digits - Enter address
227 S - Toggle split mode
228 Tab - Switch windows in split mode
229
230
231 Monitor instructions
232 ====================
233
234 In the monitor, number arguments are decimal by default, or prefixed with $ for
235 hex or % for binary. Pretty much everything is output in hex.
236
237 In most places where you can enter a number or address, you can pass a CPU or
238 VIA register. (VIA registers are prefixed with V, e.g. VDDRA). Anywhere you can
239 pass an address, you can also use a symbol.
240
241 Commands:
242
243 ? - Help
244 a <addr> - Assemble
245 bc <bp id> - Clear breakpoint
246 bcm <bp id> - Clear mem breakpoint
247 bl - List breakpoints
248 blm - List mem breakpoints
249 bs <addr> - Set breakpoint
250 bsm <addr> [rwc] - Set mem breakpoint
251 bz - Zap breakpoints
252 bzm - Zap mem breakpoints
253 d <addr> - Disassemble
254 df <addr> <end> <file>- Disassemble to file
255 m <addr> - Dump memory
256 mm <addr> <value> - Modify memory
257 mw <addr> - Memory watch at addr
258 nl <file> - Load snapshot
259 ns <file> - Save snapshot
260 r <reg> <val> - Set <reg> to <val>
261 q, x or qm - Quit monitor
262 qe - Quit emulator
263 sa <name> <addr> - Add or move user symbol
264 sk <name> - Kill user symbol
265 sc - Symbols not case-sensitive
266 sC - Symbols case-sensitive
267 sl <file> - Load user symbols
268 sx <file> - Export user symbols
269 sz - Zap user symbols
270 wm <addr> <len> <file>- Write mem to disk
271
272
273
274 Breakpoints
275 ===========
276
277 There are two types of breakpoints. "Normal" breakpoints trigger when the CPU
278 is about to execute an instruction at the breakpoint address. "Memory" breakpoints
279 trigger when the breakpoint address is accessed or modified.
280
281 There are three ways a memory breakpoint can be triggered; when the CPU is about
282 to read the address (r), and the CPU is about to write the address (w), or after the
283 value at the address changes for any reason (c).
284
285 You specify which ways you'd like the breakpoint to trigger when you set the memory
286 breakpoint:
287
288 bsm r $0c00 <-- Break when the CPU is about to read from $0c00
289 bsm rw $0c00 <-- Break when the CPU is about to access $0c00
290 bsm c $0c00 <-- Break after then contents of $0c00 change
291 bsm rwc $0c00 <-- Break just before the CPU accesses $0c00, or just after it
292 changes for any reason.

  ViewVC Help
Powered by ViewVC 1.1.26