nesdev.org

So I noticed that microchip now has the PIC18F66J60 microcontroller that has a built-in 10base-t mac/phy. There is also a reference implementation for a full TCP/IP stack that runs on the chip that is available for free. I think this presents the best opportunity for getting the NES connected to eth...

I've read over all of the NES hardware docs I've been able to find on the web and I've found a conflict on what pin 4 of the expansion port is for. the NES hardware development guide says that it is /NMI showing the 2C02's vblank status and the 2A03's /NMI status. Then in another document, pin 4 is ...

Try again. I'm not having any trouble with my servers but if it persists, I'll consider switching to github or sourceforge.

I actually have a GP2X with the base that provides USB host support. I don't think that would be very hard to get running since the GP2X runs embedded Linux. I also happen to have a Dreamcast and a coder's cable and all of the tools necessary to create bootable CD-R's for it. Since there is a Linux ...

I'm going to test out the portability of my library soon. I've got an intel Mac and a PPC Mac to test this on. I can also test this on Windows with Cygwin but I don't see the point of that. If anybody has tested libcopynes and bcn on any platform other than i386 Linux, please let me know. I'm most c...

I just posted a major update to libcopynes . I switched the library over to using all async I/O on the serial port plus I finally figured out how to properly configure the serial port so that I get the raw, 8-bit data being dumped over the wire by the CopyNES. I just ran a few tests where I was able...

oops, sorry. I meant to include that. Try the link again, I updated the tarball to include the source. On my system I have to run the following commands to compile bcn: $ gcc -c bcn.c $ gcc -o bcn bcn.o -lcopynes -L/usr/local/include/copynes This assumes that when you installed libcopynes you did th...

The bcn application is on the same page as libcopynes. Here's a direct link though. It'd be cool if you could make your code for creating .nes and .unf files a library too. That way we're building up a set of libraries for all of these common functions. As I move forward with libcopynes, I'm realizi...

I found a solution to the connector problem. I just sliced my 48 pin connectors down the middle splitting the two rows of pins in two. It turns out that each side is just the right thickness to fit snugly between the expansion connector and its shell, so the two halves of the female socket don't hav...

New version (0.2) here . I added support for loading and running plugins on the CopyNES and reading the mirroring byte and the return packets. I have updated the bcn command line tool to use the new features in libcopynes. It now has a "dump" function that takes the name of the plugin rom ...

alright, I fixed a few bugs. get the first release here . I also added an example command line app that uses the library. I'll be adding features to this library as time permits. It currently supports getting the version string and playing the cart in the NES. The next feature I'm going to implement...

here's the first release...it just supports open/close, reset, version for now... I spent all my time trying to figure out autotools... http://www.linuxprogrammer.org/ I use dreamhost which allows me to have my own subversion server. You can get the latest code from: svn co http://code.linuxprogramm...

Yep, you're right about the complexity. You've written a ton of code. I'm thinking that we should start over from scratch. I've only written a hundred lines of code or so and I almost have full control over the CopyNES. This doesn't mean what you've written is useless. I'm thinking that a simple lib...

I'm most interested in getting this to work because I hate how all of these hacker tools are windows only. Also because I'm working on an ethernet adapter that plugs into the NES expansion port and I need a tool like this to explore the expansion port stuff. I'm 99% sure I have a workable ethernet a...

I'll see what I can do. I think the simplest solution is to just use FD sets to implement async communication. That way, the code that I've been publishing here doesn't change all that much. The read loops are transformed into signal callbacks and FD set tests to see which fd woke up the application...