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

## writeword

Syntax
writeword id vaddr data

Explanation
It writes data to a target system location. Specifically, it sends a request to write a word into the memory space of the target system by using the dbgif tool. The id is the thread number. Even though all threads share the same address space, you must still specify a thread. This command is shared with other debuggers in which threads may have different address spaces. The virtual address vaddr is the location to write, and it must be on a word boundary. The 32-bit data is the value to be written. Before execution of this command, the dbgif program must be running and the METHOD environment variable must be set to indicate whether this is a request for the R4300 CPU or the coprocessor. The value zero represents the CPU and the number one represents the RCP. In csh, this is accomplished by specifying:

    setenv METHOD 0

If METHOD is set to 1 and the co-processor is running, the request will probably fail (as it should). It is generally unwise to use METHOD 1 for this command anyway; all addresses may be accessed from the CPU.
Bugs
In the event of a communications failure, the program will dump core. If that happens, you will need to remove the core file manually.
See Also
dbgif
listthreads
readmem

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