How does want NES puts up go?
There is at want before me, Seek NES IC, Its IP at goes use procedure DUMP out,
Does not know he IC is what, Too has no DUMP procedure, Can someone help I?
Sorry, My English not very good, This is use translate software turn over become English
When I'll have finished my studies in electronics engineering I could definitely do something like that. Now that the pattent have expired for the NES I guess this is legal (even if the official patents are inacurade, which is cheat from Nintendo).Gonna make your own Famiclone and make millions? Wink
Anyway Kevin Horton was the first to sucessfully did something like that.
The NES architecture assumes 240p output. I can see a few advantages of 480p or bigger output:kyuusaku wrote:One can dream But there is still a lot of $$$ to be made from Famiclones, I'm guessing especially ones with 720p/1080p output or other trendy features.
- emulating more than one NES at once,
- a hint screen displayed above the game window like in PlayChoice,
- less lag from typical entry-level flat TVs' upscalers, and
- the possibility of Scale#x or hq#x output.
It will be VERY hard for me to get that accurate, at least for a long time. The clones actually are clones afterall, they just have a few sloppy parts probably from mistakes viewing the mask.MottZilla wrote:Any Famiclone that actually does sound and video and many other things right that all the Famiclones FAIL at would be nice. It's a shame the market is stuffed full of shitty NES clones as many average users will think there is nothing wrong when there is so much wrong.
Right now my clone doesn't really even have a CPU yet, just someone else's HDL core I haven't tested as a placeholder. Currently I'm working on the PPU so I can hit the ground running. I've got a prototype for all the components designed except for sprite evaluation, I just need to put it all together and design a basic upscanner to see some results..
I think also if things work out I can use my design to write a visual tech document, like a more accurate update to Brad Taylor's and integrate newer info from the forum.
Code: Select all
Scanline: Odd Even Odd Frames: 0 180 Even Frames: 180 0
Also, it should have the luminance and chrominance signals filtered before they are combined to form the composite output.
If you don't understand what I'm getting at, let me know.
That's actually the point of 20th scanline being short by one pixel. (I'd point you at the wiki but it's down for me).CartCollector wrote:The S-Video/composite board should have the color carrier rotate 180 degrees every scanline and switch off every frame
It doesn't always look good, though -- especially with scrolling content. (The last time I played with a modern ATI card's composite/s-video out, it included a bunch of different color modulation options because different pictures look better with different characteristics).
I recently started working on it again. I'm trying to pipeline the PPU, and implement audio.
kyuusaku: I am also using someone else's CPU. I got mine from www.birdcomputer.ca. After through testing, I only found one small bug involving the RTI instruction. I've been meaning to e-mail them to get it fixed and just haven't gotten around to it yet.
I like your idea about creating a new tech document. All of the documents I've found have been incomplete and a few even contradict each other.
Actually, being short by one pixel only rotates the phase by 240 degrees, not 180, since the CPU and the color carrier oscillate at a ratio of 2 color carrier cycles to 3 PPU cycles. 3.58/5.37 = 2/3. (2/3)*360 = 240. Visually:That's actually the point of 20th scanline being short by one pixel. (I'd point you at the wiki but it's down for me).The S-Video/composite board should have the color carrier rotate 180 degrees every scanline and switch off every frame
Code: Select all
Original color carrier: --- --- --- --- ___ ___ ___ ___ CPU clock: -- -- -- -- -- -- __ __ __ __ __ __ Color carrier -1 CPU cycle: (4 dashes) - --- --- --- -- ___ ___ ___ ___ Original color carrier: (again) --- --- --- --- ___ ___ ___ ___
Look at Nestopia with the NTSC filter on and you'll notice that color and luminance decoding errors are still noticeable on still images, which they wouldn't be if the phase rotated by 180 degrees. For instance, if one white pixel surrounded by black pixels created interference in the chroma bandwidth that caused it to be yellow tinted, it would be blue tinted in the next frame if the color carrier shifted 180 degrees. Since yellow and blue are exactly opposite each other, when averaged out by flickering, the pixel looks colorless (white). However, if the color carrier shifts 240 degrees, the pixel would be cyan tinted in the next frame, and would look light green tinted when averaged out.
Good to hear because that's the one I'm going to test my PPU with! ;)Stief21774 wrote:I got mine from www.birdcomputer.ca. After through testing, I only found one small bug involving the RTI instruction. I've been meaning to e-mail them to get it fixed and just haven't gotten around to it yet.
BTW, I'm using a Digilent Nexys 2 + breadboard for I/O.