N64® Functions Menu

al - Audio Library Functions
gDP - DP GBI Macros
gdSP - General GBI Macros
gSP - SP GBI Macros
gt - Turbo Microcode RDP
gu - Graphics Utilities
Math - Math Functions
nuSys - NuSystem
os - N64 Operating System
sp - Sprite Library Functions
uh - Host to Target IO
64DD - N64 Disk Drive

Nintendo® Confidential

## gload

Syntax

    gload [-a "appstring"] [-f log format file]
    [-o rom offset] [-n] [-V] [-v] [-s] [romImage filename]

Explanation
It is a utility that loads games for the N64 development system. Specifically, it downloads a prepared ROM image into the "Game Pak memory" on the Nintendo 64 development board. We refer to this as RAMROM memory because it is RAM memory that occupies 16MB of space where a Game Pak's ROM would ordinarily reside on the real game hardware.
Command Line Options

- -a <"application-argument-string"> The ASCII contents of the quoted text string following the -a argument are loaded into RAMROM memory at the standard offset location RAMROM_APP_WRITE_ADDR, which is defined when <ultra64.h> is loaded by the #include directive.
- -f <log format file> Is an alternate file for specifying the format of strings corresponding to logging events (see below). If this option is not specified, gload looks for the log.fmt file in the current directory.
- -o <rom offset> Overrides the default ROM load location of zero (this is intended for SGI internal debugging, not for the general user).
- -s Causes gload to exit immediately after loading and starting the game.
- -n Prevents loading or using a ROM image; it starts the print server.
- -V Turns on verify mode; all downloaded RAMROM memories are read back and verified.
- -v Sets a verbose flag, which will print out any errors detected when the RAMROM memory is read back and verified.

By default, gload does not exit after loading the game image but acts as a server for error, print, and logging requests by the application. The gload program reads the log format file (by default, log.fmt) to determine how to expand event log codes and their arguments into formatted strings. The log format file consists of a number of lines of this form:
<code> <printf-like format string>
The format string is printf-like because it does not support 64-bit formats such as "%ll" and interprets the floating point formats as single precision, not double precision. See osLogEvent for more details.
The default error handler for the debug version of the library also uses this mechanism for formatting of error strings; it uses the global format file /usr/lib/PR/error.fmt for this purpose.
Notes
After each memory image is loaded (ROM and application arguments), gload reads back the memory and verifies the contents. Once both memory images have been individually loaded, gload goes back and verifies the integrity of each section one more time to make sure that none of the memory images overlapped each another.
All writes and reads to and from RAMROM memory are made through the N64 device driver, which must be installed and configured into your kernel; also, the /dev/u64 and /dev/u64_print special device files must exist with proper read/write permissions.
Files
/dev/u64
/dev/u64_print
/dev/u64_logging
/dev/u64_fault
/usr/lib/PR/error.fmt
See Also
makerom (Irix 5.3)
makerom (Irix 6.x)
osLogEvent
osSyncPrintf

Nintendo® Confidential Warning: all information in this document is confidential and covered by a non-disclosure agreement. You are responsible for keeping this information confidential and protected. Nintendo will vigorously enforce this responsibility.
Copyright © 1998
Nintendo of America Inc. All rights reserved
Nintendo and N64 are registered trademarks of Nintendo
Last updated March 1998