N64 tool that loads games for the N64 development system
gload [-a "appstring"] [-f log format file] [-o rom offset] [-n] [-V] [-v] [-s] [romImage filename]
gload is a utility that 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
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 to output to the console. 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.
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.
makerom, osLogEvent, and osSyncPrintf
/dev/u64, /dev/u64_print, /dev/u64_logging, /dev/u64_fault, /usr/lib/PR/error.fmt
1999/04/30 Changed Format