Nintendo 64 Homebrew General Guide

(Rough Draft) – V0.0.4

If you wish to contribute to the guide, PM Rocky on Discord

Chapter 1: Introduction

The following guide was created by Rocky, with the intent to provide users with a simple to follow quick start guide to help those find the resources, knowledge and information they would require to get started on the path to developing for the Nintendo 64. Below you will find many useful links and resources to help you get started. Should you not find what you are looking for here, please feel free to join the growing community of other Nintendo 64 enthusiasts over at the N64brew Channel on Discord, or the N64Dev IRC Channel, located here: #n64dev.

1.1 Table of Contents

    • 1.1 Table of Contents 2
    • 1.2 Using this Manual 2
    • 1.3 Useful links 2
    • 2.1 Requirements 3
    • 2.2 Installation 3
    • 2.3 Setting up your Windows 98 VM 3
    • 2.4 Installing software (Inside VM) 4
    • 2.5 Testing your N64 development environment 4
    • 3.1 Our intro to n64 programming 5
    • 3.2 Getting started with n64 development 5
  • CHAPTER 4: FAQ 6

1.2 Using this Manual

This manual covers a large selection of Nintendo 64 Development topics. You can use the table of contents in section 1.1 to help you navigate your way around. There are some important topics that can prove to be more valuable than others, we recommend users beginning with chapters 2 and 3.

1.3 Useful links

  • – Official Nintendo 64 documentations and downloads.
  • – Official Nintendo documents about n64 programming.
  • – Has lots of useful information about n64 programming in c with the official SDK.
  • – Lots of SDK downloads and docs (there are some dead links).

Chapter 2: Setting up your first N64 Development Environment.

2.1 Requirements

  • • Win98 SE
  • • VMware player (VirtualBox doesn’t fully support DOS based operating systems)
  • • Nintendo 64 SDK 5.0 installer

2.2 Installation

Install VMware player and install win98SE in an VM. After that you can install the VMware tools, for more interaction between the host OS and the guest OS. One of the functions this will add is the possibility to run win98 at native screen resolution. To do this, you have to change the graphics driver. This can be done by right clicking at the windows desktop and selecting “properties”. In the top of the upcoming window, click at “settings” and then at “advanced”. In the upcoming window, go to the “adapter” tab and click “change”.

In the update device driver wizard, click “next” and then the second radio button. There should be shown up 1 compatible screen driver from VMware, select that one and click “next”.

2.3 Setting up your Windows 98 VM

Download the following programs/files inside your VM

  • • Opera 9.64 or Firefox 2 (to download with Internet Explorer)
  • • A program to unpack files (example WinRAR 3.xx)
  • • N64sdk.7z
  • • (optional) A text editor / IDEM

I recommend to download some software from because you can filter on win98 by lots of downloads.

2.4 Installing software (Inside VM)

The first thing to download and install is a new browser, because Internet Explorer 5 is rather difficult to work with. After that install the unpack program and optionally a text editor or IDE. To install the SDK, “insert” the Nintendo 64 SDK 5.0 installer and run it. This should install all tools, except for the sound tools and the allman50 manuals. Allman50 does include the samples that are referred to in the documentation.

You can install the n64 sound tools from:


To get the compiler working, you have to extract N64sdk.7z and copy the ultra folder to the root of your virtual hard drive. You only have to copy the missing files.

Optionally, you can copy and/or extract the manuals from: <drive>:\man\allman50.tgz to a folder where you can find it fast and easy (on the Host or guest OS, depend on preference).

After this, you are ready to learn programming for the n64. The allman50 web documentation should help you to learn the ins and outs of the n64.

2.5 Testing your N64 development environment

There are lots of demo programs to learn from included with the installation. To get fast to your development environment after starting the dos command prompt, we are going to make a folder for that contains the source code and a bat file. In our example below, you have to replace <..> with the source code dir and move save the file as c:\windows\setup.bat


cd c:\ultra

call setup.bat


So when you want to use the compiler tools, you only have to type “setup” (without quotes) to make the terminal ready for usage with the n64 compiler tools. You have to do this each time starting up the terminal

To really test your setup, move the source code of one of the example programs to your source code folder and run the setup file for setting up the compiler tools. This makes you able to use make (the compiler tools are an fork of the gnu c 3.xx modified to make n64 roms).

Chapter 3: Getting started

3.1 Our intro to n64 programming

Lots of people are saying that the n64 is (too) difficult to program. But it’s just that the programmers have to learn some new aspect before he begins with coding for n64. Reading lots about the hardware details should be a required part of the road to an homebrew ROM. End even the way the system boots can be managed by the programmer. It’s not really difficult, but it’s a fun challenge.

3.2 Getting started with n64 development

The N64 isn’t an easy platform to program for, because of the usage of two processors, the CPU and the Reality CoProcessor (RCP). The RCP is a combination of the I/O + Reality Display Processor (RDP) + Reality Signal Processor (RSP). All these chips have to be initialized before the system can give video output. Because of the complexity of the system, and cut off c libraries you’re required to learn the basics of n64 before programming anything. Unfortunately, there is no studio.h in the SDK.

To help you with learning the N64, here is the way I am learning it.

Open the n64 SDK docs (allman50 folder, or and go to the “intro to n64 & tutorial” section and start with reading the intro to the n64 and then the n64 tutorial, all example code in the manual can be found in the allman50 folder. The best solution to test your homebrew is buying real hardware, because existing emulators co only support official Roms and can crash by using other Roms, this is because the n64 is really hard to emulate perfect because of the two asynchronous operating processors. We recommend the 64drive because it’s the only homebrew cartridge that is made for homebrew development.

Chapter 4: FAQ