1.8
1.8
Nintendo 64 Developers Newsletters will be published periodically, as needed. These feature software and hardware system anomalies, which have been discovered, and their solutions and/or work-arounds. Development tips will also be included.
s32 osAfterPreNMI(void);
Initializes the RSP program counter (PC).
Explanation:
When the application receives a pre-NMI event, halt all RSP tasks and then call this function.
If the function call is successful, 0 is returned. If the RSP is active, the call fails and -1 is returned. In this case, wait for the executing RSP task to end and then call the function again.
When a pre-NMI event arrives, the application must halt GFX tasks and audio tasks. At the time that a pre-NMI event is received, confirm that the executing RSP task has ended and that no new RSP task has begun, and then call the osAfterPreNMI() function.
Please call the osAfterPreNMI() function whenever a pre-NMI event is received, even if you are using some mode other than MPAL (NTSC etc.).
This is an N64 hardware problem. When more than around 0.5 second elapses between the time that the power is turned on to N64 and the time that the osAiSetFrequency() function is called, then this noise will be produced when the function is called.
To avoid this noise, please call osAiSetFrequency() right after startup. However, note that osAiSetFrequency() must not be called until after the osInitialize() function has been called. In general, osInitialize() is the first function called in an N64 application. Therefore, we strongly recommend that you call osAiSetFrequency() immediately after calling the osInitialize() function.
Even if you can not follow the above recommendation, please make sure to call the osAiSetFrequency() function within 0.5 second after calling osInitialize().