ST-121-041594 Sega Enterprises, Ltd. Saturn Boot ROM ver.08 | Floppy Disk Information Doc. # ST-121-041594 | SEGA ` @ , < A © Copyright 1994 Sega. All rights reserved. ST-121-041594 Sega Enterprises, Ltd. NOTICE When using this document, keep the following in mind: 1. 2. This document may, wholly or partially, be subject to change without notice. All rights are reserved: No one is permitted to reproduce or duplicate, in any form, the whole or part of this document without SEGA’s permission. SEGA will not be held responsible for any damage to the user that may result from accidents or any other reasons during operation of the user’s equipment, or programs according to this document. Software, circuitry, and other examples described herein are meant merely to indicate the characteristics and performance of SEGA’s products. SEGA assumes no responsibility for any intellectual property claims or other problems that may result from applications based on the examples describe herein. No license is granted by implication or otherwise under any patents or other rights of any third party or SEGA Enterprises, Ltd. This document is confidential. By accepting this document you acknowledge that you are bounded by the terms set forth in the non-disclosure and confidentiality agreement signed separately and/in the possession of SEGA. If you have not signed such a non-disclosure agreement, please contact SEGA immediately and return this document to SEGA. (4/20/94 - 001) ST-121-041594 Sega Enterprises, Ltd. . . i Ha n 03/23/1994 06 | Sn CS Hardware/Suzuki /ontents ¥ BOOTIP --- Sample for initial program (IP) creation. — BOOTO080 --- Source for BOOT ROM Version 0.80 (V0.80) FUJITA # Services design tool from SCSI. MASANORI * Loads arid runs CD-ROM file IP from SCSI or SIMM. SUZU * Initializes hardware; loads and runs IP from cartridge or MAP. Development Environment These files were created with the Sun workstation versioniof the SH development software. MAKEFILE must be rewritten before creating on a PC. When reinstalling on the Sun workstation, change the file names to lower case except for the following file where uppercase is partially used, and then restore: boot080/fujita/MB89352A. h On the Sun workstation, create the object files in the following order. Enter the MAKE command under the BOOT080 directory to create the BOOT ROM (vo. 80 for BIG OX Release 1) object. To create files that will be written into the ROM chip, a Sun workstation Md a LAN-connected E7000 emulator are needed. “he IP sample can be created with the Sun workstation version of the SH development software. Enter the MAKE command to create all necessary object files under the BOOTIP directory. Change and use the following files to match the application: sys_id.src and smp_sys.src Reference BOOT ROM V0.80 checks the following items in sys_id.src: offset H'00 Presence or absence of "SEGA" characters offset H'EO IP size (minimum H'1000, maximum H'8000) offset H'E4 Start address (Must be in range of H'6010000 + IP size.) Using E7000 in BOOT ROM Creation First connect the FTP to the Sun, and then switch to the BOOT080 directory. Note the following E7000 commands: FTP> ASC FTP> LTR LD.COM;R:LD.COM | FTP> BIN 7 FTP> CC LD.COM Ås a result, the necessary load modules are automatically downloaded to the E7000. After the modules are downloaded, the BOOTROM.MOT file is created in the BOOTO080 directory. This file - (comes the source file for the data that is written into the 2 Mbit ROM chip. (DY, 4/21/94) ST-121-041594 Sega Enterprises, Ltd. @°20ing the BOOT ROM (V0.80) Initial Program (IP) ”urrently, the BOOT ROM IP is loaded into memory at the following fixed address. (The address ay be changed in the future.) H'6010000 (Beginning of work RAM + 64 KB offset) Cartridge IP Load If ID (object of sys_id.src) is at one of the following memory addresses, the load program begins to load IP before displaying the logo screen display. - H'2000000 (ROM board connected to the A-bus connector) Priority H' 1000000 (E7000 MAP memory) Before loading the IP, the load program checks the following: Offset H'00 "SEGA" characters are present . 4 If the "SEGA" characters are absent , the load program will not load the IP. After loading the IP, the load program checks the following ranges in the work RAM: Offset H'EO IP size (minimum H'1000, maximum H'8000) Offset H'E4 Start address (Must be in range of H'6010000 + IP size.) If the ranges are appropriate, the program jumps to: H'6010100 sys sec.obj ... Dummy security code (After passing through that address, the program jumps to the start address of sys_id H'E4.) Both sys_id and sys_sec are therefore necessary to load and run the IP. G JG from a CD-ROM (Emulation) . the IP.BIN file is in the SIMM memory, the load program begins to load the file to the work RAM immediately after the logo screen display is started. H'4000000 (The file is in SIMM memory. However, the header is the IP.BIN file header instead of "SEGA. A) After IP loading from the SIMM memory fails, the load program begins to load the ‘IP from the SCSI if the DIP switch settings for SCSI usage on the Saturn main unit are correct and if the IP.BIN file is in the hard disk of the CD emulator host machine. After loading the IP, the load program checks the following items in the work RAM: Offset H'00 Presence or absence of "SEGA" characters Offset H'EO IP size (minimum H'1000, maximum H'8000) Offset H'E4 Start address (Must be in range of H'6010000 + IP size.) — If the ranges are appropriate, the program jumps to: H'6010100 sys sec.obj ... Dummy security code The subsequent steps are the same as for IP loading from a cartridge. Remarks . Although the IP.BIN source file does not differ from the cartridge IP, some tools are necessary to convert the program. For information on CD-ROM emulation, refer to the other materials. eo Loading Fails Tne logo screen display becomes still, and depending on the DIP switch settings of "he Saturn main unit, the system enters operation mode as a SCSI design tool, or it vreaks from the E7000 and loads and runs the application. 2 (DY, 4/21/94) ST-121-041594 Sega Enterprises, Ltd. er Initialization by the BOOT ROM (1) 03/08/1994 (2) 03/23/1994 CPU Initialization CPU type Initialization by BOOT ROM Initialization during V0.80 V0.90 and above user-defined usage Master SH2 cache 1 KB, 4-way Same as for V0.80 Can be changed (2-way + 2KB bank) For MID For SMALL For BIG BOX Not necessary. Or, can be used for same initialization Bus control Vector numbers can be changed if no constraints are imposed by high-level software, such as the library. Priority must be changed before installed modules can be used. Cannot be changed Defines vector numbers | Same as for V0.80 of installed modules. Priority is 0. (No actual use in verification initialization. Interrupt control Assigns FRT input capture interrupt to , communication with’ slave SH2. Vector table, VBR Regulates use of initial | Same as for V0.80 work RAM area. ' Occupies about 8 KB in work RAM. Same as for V0.80 Can be changed No processing Same as for V0.80 Arbitrary or restricted by regulations Can be changed (2-way + 2KB bank) lave SH2 cache (Currently, no hardware) | Same as for V0.80 1 KB, 4-way For BIG BOX For MID For SMALL Not necessary. Or, can be used for same initialization Bus control Priority must be changed before installed modules can be used. No processing. Undefined Interrupt control Assigns FRT input capture interrupt to communication with master SH2. Slave has only this interrupt, no SCU interrupt. Initializes initial work Undefined Vector table, VBR . RAM area. +H'800 SP Occupies about 2 KB in | Undefined Can be changed work RAM. , Other No processing Undefined Arbitrary or restricted by regulations No processing regulations 68000 No processing during Can be used as a Arbitrary or restricted by erratic run. Cannotbe | demonstration? regulations controlled. PC | (No hardware) SMPC operates without | Arbitrary or restricted by initialization. Used for regulations clock setup, backup RAM management. (DY, 4/21/94) 6 Board Initialization Work RAM SCU interrupt contro! A-bus setup VDP1 register VDP2 register (DY, 4/21/94) Initialization by BOOT ROM V0.80 Writes vectors to first 64 KB. No data is written to other areas. Allows VBI, VBO, and end code fetch interrupts. Also, allows A-BUS interrupt when SCSI is enabled. Stopped (Currently, no hardware) Sets SCSI1 and SIMM memory refresh. 1/60 auto draw Transparent illustration Terminate command only 320 mode VRAM allocation AO-NBGO Character A1-NBGO Name ' BO-NBG1 Character B1-NBG1 Name 16x16 cells 16 million colors 24-bit name Logo (NBG1) Background (NBGO) V0.90 and above Same as for V0.80 (Size may be reduced) Processing changes depending on graphic tool Same as for V0.80 Same as for V0.80 Processing changes depending on graphic tool Processing changes depending on graphic tool Processing changes depending on graphic tool Processing changes depending on graphic tool ST-121-041594 Sega Enterprises, Ltd. user-defined usage Arbitrary except for first 64 KB Arbitrary or restricted by regulations. Note that A-bus needs CD or SCSI. ' Arbitrary use or may require regulations if constrained by high- level software Cannot be changed Arbitrary | Arbitrary Arbitrary Arbitrary | ST-121-041594 Sega Enterprises, Ltd. Work RAM Initialization "nit type Initialization by BOOT ROM initialization during V0.80 V0.90 and above user-defined usage Vector table Already set up in Same as for V0.80 Cannot be changed due beginning of work RAM. to regulations. Hook area +H'280 Overall modification Not disclosed IP check scheduled for security (Not disclosed) reasons +H'300 Scheduled addition of | Forced usage to user Interrupt handler. disclosed routines, such 4 registration references | as SCU interrupt mask setup + Specifications being - studied. i ` Scheduled addition of | Not disclosed multipiayer-related routine, resolution change routine Debugging monitor +H'700 Deleted. Status monitoring of SCU interrupt normal C functions Counter i registered to interrupts by user. For V0.80 only; therefore not disclosed. | Sérvice routines Resident interrupt Resident interrupt Can be used through handler (Includes handler. Hook services. | hook area. Cannot be monitor function) used directly. Used for graphic tool. Deleted in product Can be used as a version development tool Continued in development version (DY, 4/21/94)