I just took a brief look at your code and… Gah! No offense, but it looks like you need to learn arrays, man! All of that variable declaration at the beginning:
int xpos1=0, opos=0, circle1x=0, circle1y=0; int cross2x=0, cross2y=0, xpos2=0, xpos=0; int circle2x=0, circle2y=0, opos1=0, opos2=0; int cross3x=0, cross3y=0; int circle3x=0, circle3y=0, opos3=0, opos4=0; int cross4x=0, cross4y=0; int circle4x=0, circle4y=0, opos5=0; int cross5x=0, cross5y=0; int circle5x=0, circle5y=0;
…could be replaced with
int oPos[5], xPos[5]; int crossX[5], crossY[5]; int circleX[5], circleY[5];
If you’re struggling with C, I suggest the tutorials at cplusplus.com. C++ is basically C with additional features, but the language is mostly the same up to object oriented programming. Hope that helps!
By the way, is C your first language, or are you more familiar with another programming language?
Actually, since the design is completely open sourced, I built the adapter from scratch using through hole parts on stripboard. If you already have the tools, the parts cost is under $10. As far as flashing, if you don’t need anything fancy you can flash AVRs with a parallel port cable (called dapa), which is just a DB25 and some wire connected to the right pins. It’s not the safest thing, but when I first started using AVRs, I used a dapa cable. This is the instructable that got me started. Now I use a USBTinyISP that I bought off eBay for $15. (link) It’s a nice little programmer and works great with avrdude. Hope this helps!
Attachments:
Okay, I’m blowing the dust off of this topic.
While slowly working at getting Yoshi’s Cookie working, I’ve realized that unless I want to do some messy stuff with BGMaps, all the cookies are going to be constructed from objects. Reason: In Yoshi’s Cookie, the board seems to be made of a large grid of 8×8 tiles, with each cookie occupying 4 tiles (16×16). Unless I want to do some messy stuff with BGMaps, the easiest way to implement this seems to be to have a large grid of objects, and just modify their char references when necessary. I’ve already got that system working for the most part….
The problem is that the cursor (upper left corner) is doing some odd things. I have 2 object worlds, one for the cookie grid, and one for the cursor. This looks fine on the display, but when I check OBJ memory in Reality Boy Debug, one corner of the cursor always shows up in 2 banks of OBJ memory. What I mean by this, is that as my program is now, the lower right corner of the cursor is displayed not only in object set 2 (where it should be), but in object set 1 (not displayed) as well. I see this when I check objects in Reality Boy Debug. From what I know, It should be impossible for the same object to in 2 different object ranges (SPT2-SPT1 and SPT1-SPT0), so is this a glitch in my program, or in the emu?
