<pclass="rvps2"><spanclass="rvts6"> All results were obtained by studying prior information available (from nestech 1.00, and postings on NESDev from miscellanious people), and through a series of experiments conducted by me. Results acquired by individuals prior to my reverse-engineering have been double checked, and final results have been confirmed. Credit is due to those individual(s) who contributed miscellanious information in regards to NES sound channel hardware. Such individuals are:</span></p>
<pclass="rvps2"><spanclass="rvts6"> Kentaro Ishihara (Ki) is responsible for posting (on the NESdev mailing list) differrences in the 2 square wave channels, including the operation of 2A03 hardware publically undocumented (until now) such as the frame IRQ counter, and it's ties with sound hardware. Goroh had originally discovered some of this information, and Ki confirmed it.</span></p>
<pclass="rvps2"><spanclass="rvts6"> A special thanks goes out to Matthew Conte, for his expertise on pseudo-random number generation (amoung other things), which allowed for the full reverse engineering of the NES's noise channel to take place. Without his help, I would still be trying to find a needle in a haystack, as far as the noise's method of pseudo-random number generation goes. Additionally, his previous findings / reverse engineering work on the NES's sound hardware really got the ball of NES sound emulation rolling. If it weren't for Matt's original work, this document wouldn't exist.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The 2A03 (NES's integrated CPU) has 4 internal channels to it that have the ability to generate semi-analog sound, for musical playback purposes. These channels are 2 square wave channels, one triangle wave channel, and a noise generation channel. This document will go into full detail on every aspect of the operation and timing of the mentioned sound channels.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The square channel(s) have the ability to generate a square wave frequency in the range of 54.6 Hz to 12.4 KHz. It's key features are frequency sweep abilities, and output duty cycle adjustment.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The triangle wave channel has the ability to generate an output triangle wave with a resolution of 4-bits (16 steps), in the range of 27.3 Hz to 55.9 KHz. The key features this channel has is it's analog triangle wave output, and it's linear counter, which can be set to automatically disable the channel's sound after a certain period of time has gone by.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The noise channel is used for producing random frequencys, which results in a "noisey" sounding output. Output frequencys can range anywhere from 29.3 Hz to 447 KHz. It's key feature is it's pseudo- random number generator, which generates the random output frequencys heard by the channel.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The 2A03 has an internal frame counter. The purpose of it is to generate the various low frequency signals (60, 120, 240 Hz, and 48, 96, 192 Hz) required to clock several of the sound hardware's counters. It also has the ability to generate IRQ's.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The smallest unit of timing the frame counter operates around is 240Hz; all other frequencies are generated by multiples of this base frequency. A clock divider of 14915 (clocked at twice the CPU speed) is used to get 240Hz (this was the actual measured ratio).</span></p>
<pclass="rvps2"><spanclass="rvts6"> - Any write to $4017 resets both the frame counter, and the clock divider. Sometimes, games will write to this register in order to synchronize the sound hardware's internal timing, to the sound routine's timing (usually tied into the NMI code). The frame IRQ is slightly longer than the PPU's, so you can see why games would desire this syncronization.</span></p>
<pclass="rvps2"><spanclass="rvts6"> - bit 7 of $4017 controls the frame counter's divide rate. Every time the counter cycles (reaches terminal count (0)), a frame IRQ will be generated, if enabled by clearing bit 6 of $4017. $4015.6 holds the status of the frame counter IRQ; it will be set if the frame counter is responsible for the interrupt.</span></p>
<pclass="rvps2"><spanclass="rvts6"> On 2A03 reset, both bits of $4017 (6 & 7) will be cleared, enabling frame IRQ's off the hop. The reason why the existence of frame IRQ's are generally unknown is because the 6502's maskable interrupt is disabled on reset, and this blocks out the frame IRQ's. Most games don't use any IRQ-generating hardware in general, therefore they don't bother enabling maskable interrupts.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Note that the IRQ line will be held down by the frame counter until it is acknowledged (by reading $4015). Before this, the 6502 will generate an IRQ *every* time interrupts are enabled (either by CLI or RTI), since the IRQ design on the 6502 is level-triggered, and not edge. If you've written a program that does not read $4015 in the IRQ handler, and you execute CLI, the processor will immediately go into a infinite IRQ call-return loop.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Depending on the status of $4017.7, the frame counter will follow 2 different count sequences. These sequences determine when sound hardware counters will be clocked. The sequences are initialized immediately following any write to $4017.</span></p>
<pclass="rvps2"><spanclass="rvts6"> During count sequences 0..3, the linear (triangle) and envelope decay (square & noise) counters recieve a clock for each count. This means that both these counters are clocked once immediately after $4017.7 is written with a value of 1.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Count sequences 1 & 3 clock (update) the frequency sweep (square), and length (all channels) counters. Even though the length counter's smallest unit of time counting is a frame, it seems that it is actually being clocked twice per frame. That said, you can consider the length counters to contain an extra stage to divide this clock signal by 2.</span></p>
<pclass="rvps2"><spanclass="rvts6"> No aforementioned sound hardware counters are clocked on count sequence #4. You should now see how this causes the 96, and 192 Hz signals to be generated when $4017.7=1.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The rest of the document will describe the operation of the sound channels using the $4017.7=0 frequencies (60, 120, and 240 Hz). For $4017.7=1 operation, replace those frequencies with 48, 96, and 192 Hz (respectively).</span></p>
<pclass="rvps2"><spanclass="rvts6"> After resetting the 2A03, the first time any sound channel(s) length counter contains a non-zero value (channel is enabled), there will be a 2048 CPU clock cycle delay before any of the sound hardware is clocked. After the 2K clock cycles go by, the NES sound hardware will be clocked normally. This phenomenon only occurs prior to a system reset, and only occurs during the first 2048 CPU clocks after the activation of any of the 4 basic sound channels.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The information in regards to this delay is only provided to keep this document accurate with all information that is currently known about the 2A03's sound hardware. I haven't done much tests on the behaviour of this delay (mainly because I don't care, as I view it as a inconvenience anyway), so this information should be taken with a grain of salt.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The sound hardware internal to the 2A03 has been designated these special memory addresses in the CPU's memory map.</span></p>
<pclass="rvps2"><spanclass="rvts6">$4004-$4007</span><spanclass="rvts6"> </span><spanclass="rvts6">Square wave 2 (identical to the first, except for upward frequency sweeps (see "sweep unit" section))</span></p>
<pclass="rvps2"><spanclass="rvts6"> Note that $4015 (and $4017, but is unrelated to sound hardware) are the only R/W registers. All others are write only (attempt to read them will most likely return the last byte on the bus (usually 040H), due to heavy capacitance on the NES's data bus). Reading a "write only" register, will have no effect on the specific register, or channel.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Every sound channel has 4 registers affiliated with it. The description of the register sets are as follows:</span></p>
<pclass="rvps2"><spanclass="rvts6">6-7</span><spanclass="rvts6"> </span><spanclass="rvts6">duty cycle type (unused on noise channel)</span></p>
<pclass="rvps2"><spanclass="rvts6">7</span><spanclass="rvts6"> </span><spanclass="rvts6">random number type generation</span></p>
<pclass="rvps2"><spanclass="rvts6">0-2</span><spanclass="rvts6"> </span><spanclass="rvts6">3 MS bits of wavelength (unused on noise channel)</span></p>
<pclass="rvps2"><spanclass="rvts6">4</span><spanclass="rvts6"> </span><spanclass="rvts6">DMC (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6">7</span><spanclass="rvts6"> </span><spanclass="rvts6">IRQ status of DMC (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6">4</span><spanclass="rvts6"> </span><spanclass="rvts6">DMC channel (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6"> This section will describe the internal components making up each individual channel. Each component will then be described in full detail.</span></p>
<pclass="rvps2"><spanclass="rvts56">volume/envelope decay unit</span><spanclass="rvts56"> </span><spanclass="rvts56"> </span><spanclass="rvts56"> </span><spanclass="rvts56"> X X</span></p>
<pclass="rvps2"><spanclass="rvts56">random number generator</span><spanclass="rvts56"> </span><spanclass="rvts56"> </span><spanclass="rvts56"> </span><spanclass="rvts56"> </span><spanclass="rvts56"> X</span></p>
<pclass="rvps2"><spanclass="rvts6"> This is a 5-bit, single direction counter, and it is only used in the triangle channel. Each of the 4 LSB outputs of the counter lead to one input on a corresponding mutually exclusive XNOR gate. The 4 XNOR gates have been strobed together, which results in the inverted representation of the 4 LSB of the counter appearing on the outputs of the gates when the strobe is 0, and a non-inverting action taking place when the strobe is 1. The strobe is naturally connected to the MSB of the counter, which effectively produces on the output of the XNOR gates a count sequence which reflects the scenario of a near- ideal triangle step generator (D,E,F,F,E,D,...,2,1,0,0,1,2,...). At this point, the outputs of the XNOR gates will be fed into the input of a 4-bit DAC.</span></p>
<pclass="rvps2"><spanclass="rvts6"> This 5-bit counter will be halted whenever the Triangle channel's length or linear counter contains a count of 0. This results in a "latching" behaviour; the counter will NOT be reset to any definite state.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The counter's clock input is connected directly to the terminal count output pin of the 11-bit programmable timer in the triangle channel. As a result of the 5-bit triangle step generator, the output triangle wave frequency will be 32 times less than the frequency of the triangle channel's programmable timer is set to generate.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The linear counter is only found in the triangle channel. It is a 7-bit presettable down counter, with a decoded output condition of 0 available (not exactly the same as terminal count). Here's the bit assignments:</span></p>
<pclass="rvps2"><spanclass="rvts6">0-6</span><spanclass="rvts6"> </span><spanclass="rvts6">bits 0-6 of the linear counter load register (NOT the linear counter itself)</span></p>
<pclass="rvps2"><spanclass="rvts6"> The counter is clocked at 240 Hz (1/4 framerate), and the calculated length in frames is 0.25*N, where N is the 7-bit loaded value. The counter is always being clocked, except when 0 appears on the output of the counter. At this point, the linear counter & triangle step counter clocks signals are disabled, which results in both counters latching their current state (the linear counter will stay at 0, and the triangle step counter will stop, and the channel will be silenced due to this).</span></p>
<pclass="rvps2"><spanclass="rvts6"> The linear counter has 2 modes: load, and count. When the linear counter is in load mode, it essentially becomes transparent (i.e. whatever value is currently in, or being written to $4008, will appear on the output of the counter). Because of this, no count action can occur in load mode. When the mode changes from load to count, the counter will now latch the value currently in it, and start counting down from there. In the count mode, the current value of $4008 is ignored by the counter (but still retained in $4008). Described below is how the mode of the linear counter is set:</span></p>
<pclass="rvps2"><spanclass="rvts6">0</span><spanclass="rvts6"> </span><spanclass="rvts6">load (on next linear counter clock), count</span></p>
<pclass="rvps2"><spanclass="rvts6">1</span><spanclass="rvts6"> </span><spanclass="rvts6">0</span><spanclass="rvts6"> </span><spanclass="rvts6">no change (during the CPU write cycle), count</span></p>
<pclass="rvps2"><spanclass="rvts6"> Old and new represent the state(s) of the MSB of $4008. Old is the value being replaced in the MSB of $4008 on the write, and new is the value replacing the old one.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Note that writes to $400B when $4008.7=0 only loads the linear counter with the value in $4008 on the next *linear* counter clock (and NOT at the end of the CPU write cycle). This is a correction from older versions of this doc.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The programmable timer is a 11-bit presettable down counter, and is found in the square, triangle, and noise channel(s). The bit assignments are as follows:</span></p>
<pclass="rvps2"><spanclass="rvts6">0-7</span><spanclass="rvts6"> </span><spanclass="rvts6">represent bits 0-7 of the 11-bit wavelength</span></p>
<pclass="rvps2"><spanclass="rvts6">0-2</span><spanclass="rvts6"> </span><spanclass="rvts6">represent bits 8-A of the 11-bit wavelength</span></p>
<pclass="rvps2"><spanclass="rvts6"> Note that on the noise channel, the 11 bits are not available directly. See the wavelength converter section, for more details.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The counter has automatic syncronous reloading upon terminal count (count=0), therefore the counter will count for N+1 (N is the 11-bit loaded value) clock cycles before arriving at terminal count, and reloading. This counter will typically be clocked at the 2A03's internal 6502 speed (1.79 MHz), and produces an output frequency of 1.79 MHz/(N+1). The terminal count's output spike length is typically no longer than half a CPU clock. The TC signal will then be fed to the appropriate device for the particular sound channel (for square, this terminal count spike will lead to the duty cycle generator. For the triangle, the spike will be fed to the triangle step generator. For noise, this signal will go to the random number generator unit).</span></p>
<pclass="rvps2"><spanclass="rvts6"> The length counter is found in all sound channels. It is essentially a 7-bit down counter, and is conditionally clocked at a frequency of 60 Hz.</span></p>
<pclass="rvps2"><spanclass="rvts6"> When the length counter arrives at a count of 0, the counter will be stopped (stay on 0), and the appropriate channel will be silenced.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The length counter clock disable bit, found in all the channels, can also be used to halt the count sequence of the length counter for the appropriate channel, by writing a 1 out to it. A 0 condition will permit counting (unless of course, the counter's current count = 0). Location(s) of the length counter clock disable bit:</span></p>
<pclass="rvps2"><spanclass="rvts6"> To load the length counter with a specified count, a write must be made out to the length register. Location(s) of the length register:</span></p>
<pclass="rvps2"><spanclass="rvts6"> The 5-bit length value written, determines what 7-bit value the length counter will start counting from. A conversion table here will show how the values are translated.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The length counter's real-time status for each channel can be attained. A 0 is returned for a zero count status in the length counter (channel's sound is disabled), and 1 for a non-zero status. Here's the bit description of the length counter status register:</span></p>
<pclass="rvps2"><spanclass="rvts6">0</span><spanclass="rvts6"> </span><spanclass="rvts6">length counter status of square wave channel 1</span></p>
<pclass="rvps2"><spanclass="rvts6">1</span><spanclass="rvts6"> </span><spanclass="rvts6">length counter status of square wave channel 2</span></p>
<pclass="rvps2"><spanclass="rvts6">2</span><spanclass="rvts6"> </span><spanclass="rvts6">length counter status of triangle wave channel</span></p>
<pclass="rvps2"><spanclass="rvts6">3</span><spanclass="rvts6"> </span><spanclass="rvts6">length counter status of noise channel</span></p>
<pclass="rvps2"><spanclass="rvts6">4</span><spanclass="rvts6"> </span><spanclass="rvts6">length counter status of DMC (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6">7</span><spanclass="rvts6"> </span><spanclass="rvts6">IRQ status of DMC (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6"> Writing a 0 to the channel enable register will force the length counters to always contain a count equal to 0, which renders that specific channel disabled (as if it doesn't exist). Writing a 1 to the channel enable register disables the forced length counter value of 0, but will not change the count itself (it will still be whatever it was prior to the writing of 1).</span></p>
<pclass="rvps2"><spanclass="rvts6">4</span><spanclass="rvts6"> </span><spanclass="rvts6">enable DMC channel (see "DMC.TXT" for details)</span></p>
<pclass="rvps2"><spanclass="rvts6"> This is just a standard 4-bit DAC with 16 steps of output voltage resolution, and is used by all 4 sound channels. On the 2A03, square wave 1 & 2 are mixed together, and are available via pin 1. Triangle & noise are available on pin 2.</span></p>
<pclass="rvps2"><spanclass="rvts6"> These analog outputs require a negative current source, to attain linear symmetry on the various output voltage levels generated by the channel(s) (moreover, to get the sound to be audible). Instead of current sources, the NES uses external 100 ohm pull-down resistors. This results in the output waveforms having some linear asymmetry (i.e., as the desired output voltage increases on a linear scale, the actual outputted voltage increases less and less each step).</span></p>
<pclass="rvps2"><spanclass="rvts6"> The side effect of this is that the DMC's 7-bit DAC port ($4011) is able to indirectly control the volume (somewhat) of both triangle & noise channels. While I have not measured the voltage asymmetery, others on the NESdev messageboards have posted their findings. The conclusion is that when $4011 is 0, triangle & noise volume outputs are at maximum. When $4011 = 7F, the triangle & noise channel outputs operate at only 57% total volume.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The odd thing is that a few games actually take advantage of this "volume" feature, and write values to $4011 in order to regulate the amplitude of the triangle wave channel's output.</span></p>
<pclass="rvps2"><spanclass="rvts6"> When the envelope decay disable bit (bit 4) is set (1), the current volume value (bits 0-3) is sent directly to the channel's DAC. However, depending on certain conditions, this 4-bit volume value will be ignored, and a value of 0 will be sent to the DAC instead. This means that while the channel is enabled (producing sound), the output of the channel (what you'll hear from the DAC) will either be the 4-bit volume value, or 0. This also means that a 4-bit volume value of 0 will result in no audible sound. These conditions are as follows:</span></p>
<pclass="rvps2"><spanclass="rvts6"> - When hardware in the channel wants to disable it's sound output (like the length counter, or sweep unit (square channels only)).</span></p>
<pclass="rvps2"><spanclass="rvts6"> - On the negative portion of the output frequency signal coming from the duty cycle / random number generator hardware (square wave channel / noise channel).</span></p>
<pclass="rvps2"><spanclass="rvts6"> When the envelope decay disable bit is cleared, bits 0-3 now control the envelope decay rate, and an internal 4-bit down counter (hereon the envelope decay counter) now controls the channel's volume level. "Envelope decay" is used to describe the action of the channel's audio output volume starting from a certain value, and decreasing by 1 at a fixed (linear) rate (which produces a "fade-out" sounding effect). This fixed decrement rate is controlled by the envelope decay rate (bits 0-3). The calculated decrement rate is 240Hz/(N+1), where N is any value between $0-$F.</span></p>
<pclass="rvps2"><spanclass="rvts6"> When the channel's envelope decay counter reaches a value of 0, depending on the status of the envelope decay looping enable bit (bit 5, which is shared with the length counter's clock disable bit), 2 different things will happen:</span></p>
<pclass="rvps2"><spanclass="rvts6">0</span><spanclass="rvts6"> </span><spanclass="rvts6">The envelope decay count will stay at 0 (channel silenced).</span></p>
<pclass="rvps2"><spanclass="rvts6">1</span><spanclass="rvts6"> </span><spanclass="rvts6">The envelope decay count will wrap-around to $F (upon the next clock cycle). The envelope decay counter will then continue to count down normally.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Only a write out to $4003/$4007/$400F will reset the current envelope decay counter to a known state (to $F, the maximum volume level) for the appropriate channel's envelope decay hardware. Otherwise, the envelope decay counter is always counting down (by 1) at the frequency currently contained in the volume / envelope decay rate bits (even when envelope decays are disabled (setting bit 4)), except when the envelope decay counter contains a value of 0, and envelope decay looping (bit 5) is disabled (0).</span></p>
<pclass="rvps2"><spanclass="rvts6"> The sweep unit is only found in the square wave channels. The controls for the sweep unit have been mapped in at $4001 for square 1, and $4005 for square 2.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Bit 7 </span><spanclass="rvts6"> </span><spanclass="rvts6">when this bit is set (1), sweeping is active. This results in real-time increasing or decreasing of the the current wavelength value (the audible frequency will decrease or increase, respectively). The wavelength value in $4002/3 ($4006/7) is constantly read & updated by the sweep. Modifying the contents of $4002/3 will be immediately audible, and will result in the sweep now starting from this new wavelength value.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Bits 6-4</span><spanclass="rvts6"> </span><spanclass="rvts6">These 3 bits represent the sweep refresh rate, or the frequency at which $4002/3 is updated with the new calculated wavelength. The refresh rate frequency is 120Hz/(N+1), where N is the value written, between 0 and 7.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Bit 3 </span><spanclass="rvts6"> </span><spanclass="rvts6">This bit controls the sweep mode. When this bit is set (1), sweeps will decrease the current wavelength value, as a 0 will increase the current wavelength.</span></p>
<pclass="rvps2"><spanclass="rvts6"> Bits 2-0</span><spanclass="rvts6"> </span><spanclass="rvts6">These bits control the right shift amount of the new calculated sweep update wavelength. Code that shows how the sweep unit calculates a new sweep wavelength is as follows:</span></p>
<pclass="rvps2"><spanclass="rvts6"> On each sweep refresh clock, the Wavelength register will be updated with the New value, but only if all 3 of these conditions are met:</span></p>
<pclass="rvps2"><spanclass="rvts6"> There are certain conditions that will cause the sweep unit to silence the channel, and halt the sweep refresh clock (which effectively stops sweep action, if any). Note that these conditions pertain regardless of any sweep refresh rate values, or if sweeping is enabled/disabled (via bit 7).</span></p>
<pclass="rvps2"><spanclass="rvts6"> - an 11-bit wavelength value less than $008 will cause this condition</span></p>
<pclass="rvps2"><spanclass="rvts6"> - if the sweep unit is currently set to increase mode, the New calculated wavelength value will always be tested to see if a carry (bit $B) was generated or not (if sweeping is enabled, this carry will be examined before the Wavelength register is updated) from the shift addition calculation. If carry equals 1, the channel is silenced, and sweep action is halted.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The duty cycle generator takes the fequency produced from the 11-bit programmable timer, and uses a 4 bit counter to produce 4 types of duty cycles. The output frequency is then 1/16 that of the programmable timer. The duty cycle hardware is only found in the square wave channels. The bit assignments are as follows:</span></p>
<pclass="rvps2"><spanclass="rvts6"> The wavelength converter is only used in the noise channel. It is used to convert a given 4-bit value to an 11-bit wavelength, which then is sent to the noise's own programmable timer. Here is the bit descriptions:</span></p>
<pclass="rvps2"><spanclass="rvts6">0-3</span><spanclass="rvts6"> </span><spanclass="rvts6">The 4-bit value to be converted</span></p>
<pclass="rvps2"><spanclass="rvts6"> Below is a conversion chart that shows what 4-bit value will represent the 11-bit wavelength to be fed to the channel's programmable timer:</span></p>
<pclass="rvps2"><spanclass="rvts6"> Octave and scale information is provided for the music enthusiast programmer who is more familiar with notes than clock cycles.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The noise channel has a 1-bit pseudo-random number generator. It's based on a 15-bit shift register, and an exclusive or gate. The generator can produce two types of random number sequences: long, and short. The long sequence generates 32,767-bit long number patterns. The short sequence generates 93-bit long number patterns. The 93-bit mode will generally produce higher sounding playback frequencys on the channel. Here is the bit that controls the mode:</span></p>
<pclass="rvps2"><spanclass="rvts6"> If mode=0, then 32,767-bit long number sequences will be produced (32K mode), otherwise 93-bit long number sequences will be produced (93-bit mode).</span></p>
<pclass="rvps2"><spanclass="rvts6"> The following diagram shows where the XOR taps are taken off the shift register to produce the 1-bit pseudo-random number sequences for each mode.</span></p>
<pclass="rvps2"><spanclass="rvts6"> The current result of the XOR will be transferred into bit position 0 of the SR, upon the next shift cycle. The 1-bit random number output is taken from pin E, is inverted, then is sent to the volume/envelope decay hardware for the noise channel. The shift register is shifted upon recieving 2 clock pulses from the programmable timer (the shift frequency will be half that of the frequency from the programmable timer (one octave lower)).</span></p>
<pclass="rvps2"><spanclass="rvts6"> I have been informed that revisions of the 2A03 before "F" actually lacked support for the 93-bit looped noise playback mode. While the Famicom's 2A03 went through 4 revisions (E..H), I think that only one was ever used for the front loading NES: "G". Other differences between 2A03 revisions are unknown.</span></p>
<pclass="rvps4"style="clear: both;"><spanclass="rvts18">Created with the Personal Edition of HelpNDoc: </span><aclass="rvts19"href="https://www.helpndoc.com/help-authoring-tool">Single source CHM, PDF, DOC and HTML Help creation</a></p>
