Project update 2 of 11
Yes, but with an adapter. Famicom games use a different board-edge connector that has 60 instead of 72 pins (and the pitch is very slightly different too). Otherwise, the games are compatible, since the internal hardware of the original Famicom and NES systems was remarkably similar. (For Famicom “expansion audio” support, see below.)
While we would love to have a dedicated Famicom cartridge slot on the TinyNES, this first hardware release doesn’t have one, primarily because of physical space. While it’s conceivable a Famicom slot could be squeezed into the same console form-factor, we’re not ready to do that right away. Perhaps a future (major) hardware revision will add a dedicated Famicom connector.
Famicom games had the capacity to generate and mix their own sound effects. Not many games took advantage of this, but a handful of them did. Famicom carts have audio in (45) and out (46) pins specifically for this purpose. However, NES games don’t have these pins. As a result, playing Famicom games using an adapter or from a flash cart on an NES means some of the original sound will be missing.
NES carts have an additional 10 expansion pins that are largely unused, so a de facto standard has emerged of using expansion pin 6 to carry this extra audio. Original front-loading NES systems have a hidden expansion port with an audio input pin, so it’s quite easy to add (via soldering) support for this additional audio. Instead of being mixed in the cart and then returned to the system for output, the additional audio is mixed in the console.
The answer in regards to TinyNES support is: yes, we are planning to support expansion audio! It’s technically quite simple, and the details are currently being worked on, so stay tuned. We are also considering the idea of bundling a Famicom to NES cart converter with built-in expansion audio support too.
No, not at this time. TinyNES outputs a composite (CVBS) analog NTSC video signal. This is because the primary PPU (picture processing unit) chips (RP2C02 and clones) produce this signal internally and output it on a pin. In this sense, this original video signal is “authentic” and is not being converted, sampled, or modified. Instead of the original single transistor amplifier circuit, the TinyNES uses a THS7314 for a cleaner signal.
There are various approaches to RGB support. One option is the use of different PPU chips, such as the RP2C03, RP2C04, or RP2C05, all of which output native RGB. These were designed and used primarily for arcade cabinets including the PlayChoice-10 and the VS. System, and they are harder to find and often expensive (over $100 each). They also have different color palettes, so some games will look significantly different, depending on the chip.
The other approach to RGB support is to intercept and modify the signals passing through the PPU, or to replace it entirely. The popular NESRGB product does the former. We haven’t tested it with the TinyNES, but in theory it should work, just don’t expect it to fit inside the TinyNES enclosure! We would love to create an RGB version of the TinyNES at some point, but this would involve developing an open-source implementation of an NESRGB-like intercept solution, or the use of a full PPU alternative (we are looking into the UnerversalPPU project). Hopefully this can happen in the future!
No, not at this time. Eventually, we would love to incorporate a high-quality HDMI output into the console itself, which would necessarily have to upconvert the native analog video signal. This is not completely trivial, but it is certainly possible. There are many standalone NTSC to HDMI converter boxes (of widely varying quality) on the market, including products by RetroTINK designed just for this purpose.
Sort of, but we don’t recommend it, because they’ll probably run at the wrong speed and could have other issues. PAL and NTSC use different clock frequencies, so just swapping in some PAL chips (RP2A07 and RP2C07) won’t be enough. However, since the changes required for a PAL system wouldn’t be extreme, the future release of a PAL TinyNES is definitely possible. Supporting both PAL and NTSC in the same system is awkward. In fact, clone systems that provided this support were known to have two pairs of chips!
Short answer: It could be any of them! We can’t guarantee any specific revisions with your order, but you can reach out to us if you have any concerns. Sourcing these chips is not a straightforward process. So, we’ve gathered whatever we could get our hands on. We have a whole assortment in our stock, including (but not necessarily limited to):
Some weird notes: We suspect that a small number of our RP2A03 chips might actually be re-marked UA6527s. This kind of forgery is unfortunately common. But, they do actually work, which is better than most counterfeits. Some of our UA6527 are certainly re-marked UA6527Ps, which is easy to determine because the clock multiplier is different. Any system that comes with a UA6527P (re-marked or not) will have the internal 1.25x CPU clock multiplier enabled so the processor runs at the correct (standard) speed.
Space! The TinyNES is really small and controller ports take up a lot of room! So only two controller ports are built-in, which is the same number as the original NES.
At the end of the Crowd Supply campaign, all the TinyNES source files will be publicly released on GitHub, not just for backers, but for everyone! The files will be released under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license, which allows you to reuse or adapt them however you like, as long as all derivative work is released under the same (or a compatible) license, and attribution (credit) is given to the original and any other contributing authors. The Tall Dog Electronics logo is excluded and should not be used in any derivative works, since those are your creations, not ours.
We don’t know yet. If you want to work on this issue, please let us know! The EverDrive N8 from Krikzz works great. We’re still waiting for our EverDrive N8 PRO to get here, so we’ll let you know once we test it.
Some NES cart PCBs have strange card-edge pads that stop some distance away from the edge of the board. We’re not sure exactly which games have contacts like this, or if all of the PCBs for any particular game are affected. Some anecdotal examples of this so far include certain John Elway’s Quarterback and Dragon Quest (Dragon Warrior) boards. These carts may not function properly in the TinyNES because their weird pads don’t reach far enough into the connector socket. We’re investigating this, and may or may not have a solution for the first hardware production run. If we can’t source a different socket, then these games won’t work without some modification (board edge trimming).