the possession of SEGA. If you have not signed such a non-disclosure agreement, please contact
SEGA immediately and return this document to SEGA.
document. SEGA may make improvements and/or changes in the product(s) and/or the
program(s) described in this document at any time.
information about SEGA products must be made to your authorized SEGA Technical Services
representative.
party.
property claims or other problems that may result from applications based on the examples
describe herein.
Such references/information must not be construed to mean that SEGA intends to provide such
SEGA products or services in countries other than Japan. Any reference of a SEGA licensed prod-
uct/program in this document is not intended to state or simply that you can use only SEGA's
licensed products/programs. Any functionally equivalent hardware/software can be used instead.
document. Please address comments to :
150 Shoreline Drive, Redwood City, CA 94065
SEGA may use or distribute whatever information you supply in any way
it believes appropriate without incurring any obligation to you.
document, or come up with any questions or comments, please let us know so that we can make the
required changes in subsequent revisions. Simply fill out all information below and return this form to
the Developer Technical Support Manager at the address below. Please make more copies of this form if
more space is needed. Thank you.
Attn: Manager,
Developer Technical Support
Attn: Manager,
Developer Technical Support
275 Shoreline Dr. Ste 500
Redwood City, CA 94065
board settings
section 6.1 was changed to 21800000H.
1.2 Communication by FRT Input Capture Signal ....... 1
2.2 EVA Board Settings ............................................... 2
4.2 Stack Variables and Static and Global Variables ... 3
4.3 Slave CPU Initialization ......................................... 3
4.4 Initialization (Vector, Stack) by the Boot ROM ....... 3
5.2 Polling of the FRT Input Capture Flag ................... 4
6.2 Polling of the FRT Input Capture Flag ................... 5
7.2 Cache Invalidate .................................................... 5
The programs executed by the slave CPU and the reset vector obtained during reset
are exactly the same as those of the master CPU. However, identification of the
master and slave CPUs is performed in the boot ROM because each CPU must be
initialized separately.
forced to wait for access and execution speed decreases.
module can be used to implement communication between the master and slave
CPUs. Specifically, to input the FRT Input Capture signal to the slave CPU, write
16-bit data to address 21000000
MODE command.
E7000 MODE(MD5-0)=xx? 2E [Return]
MODE SET (C:CONFIGURATION/U:USER/M:MASTER-SLAVE)=X? C [Return]
CONFIGURATION WRITE OK?(Y/N)? Y [Return]
2010001f xx
operated until the slave CPU reset is released.
slave CPU must therefore be restarted by the SMPC command (SSH_ON = 02
ecute an execution file from any location. (If the cache is used as internal RAM,
programs placed in internal RAM are not shared.)
because a stack area is allocated separately for each CPU (boot ROM setting). How-
ever, if both CPUs execute programs that rewrite static or global variables, special
attention must be paid to the execution sequence and to concurrent execution in
each CPU.
entry (SYS_SETSINT(164
master and slave CPUs. For communication from the master CPU to the slave CPU,
the Sega Saturn provides the methods described in the following sections.
CPU. To set interrupt processing from the master CPU, use the application initial-
ization routine to register the interrupt processing routine to interrupt vector 64
PCU, the interrupt vector is 164
register in the FRT unit. The SH CPU then monitors change in the flag during pro-
cessing wait state (or synchronous wait state). This method is especially effective
when there are many synchronous or processing waits because it has a shorter
reception time than the interrupt processing method. When using this method, be
sure to disable the FRT Input Capture interrupt in the application initialization
routine. (Set 01
CPU, the Sega Saturn also provides all of the same communication methods for
communication from the slave CPU to the master CPU.
ter CPU. To set interrupt processing from the slave CPU, set up the application
initialization routine to register the interrupt processing routine to interrupt vector
64
register in the FRT unit. The SH CPU then monitors change in the flag during pro-
cessing wait state (or synchronous wait state). This method is especially effective
when there are many synchronous or processing waits because it has a shorter
reception time than the interrupt processing method. When using this method, be
sure to disable the FRT Input Capture interrupt in the application initialization
routine.
when data is transferred between the master and slave CPUs, the CPU reading the
data must either perform a cache-through read or read the data after the cache of the
target area is invalidated.
20000000
when 40000000
(when the FRT Input Capture Flag is polled.)
tion entry function of the slave CPU.
replaced with version 3.2. Also note that the script syntax changed when the
VCDPRE.EXE was upgraded from version 1.xx to version 2.xx.
being played in multi-player mode.
real-time emulation mode.
access.
board to version 3.2.
· The directory record is always located at the beginning of a sector when the
The total number of files that are currently operating is only a little more than 500. Although the
specification allows up to 1300 files to be executed as options when XMS is used, this specifica-
tion has not been announced due to a bug that was found.
1.xx. Users of version 1.xx must change the script file. For details, refer to the syntax in
item 7, EXSAMPLE.SCR.
5. VCDMKTOC.EXE (version 1.20)
6. SWAP.EXE (version 1.00)
to this example during script modification.