Gameduino Reference Manual v0!

On page 13, there's a ; missing in Sketch 3.

Also on page 13, might want to note that if you access the SPI within an interrupt, when you're also accessing SPI in your main loop, and the interrupt occurs in the middle of an ongoing SPI transaction, things will start failing (have not tested this on actual hardware yet, but I assume this to be the case, because it makes sense).

On page 18, ATmaga168 should be ATmega168 in the text, and in the table under Processor there's an ATmaga2560 that should be ATmega2560.

On page 28, it says SCROLL_R instead of SAMPLE_R in the table.

On page 43, there's an 'are' missing in 'They the most complex part'.

On page 51, it should be voices '33-63' instead of '33-64'.

On page 52, it says SCROLL_R instead of SAMPLE_R in the table (again).

Thanks for starting this--esp. for the J1 section. I'm a Forth n00b and this was very helpful.

Here is some feedback after my first pass through...

• p 5 Sketch 2 has delay(2500), but mentions a delay of 250ms. Shouldn't it be delay(250)?

• p 51 Audio: how are all the Sound Synth volumes added up to produce the final output volume? As in, do we have to scale/clamp ourselves or does the gameduino do that for us?

• p 51 Audio: "RING_MOD" is not the name used in GD.h It defines "MODULATOR"

Thanks, that is an awesome resource! It's very helpful to see advice on how to handle things like double buffering with the Gameduino.

Awesome start! I'm printing a copy which I'll be reading at the airport this evening, and hopefully I'll have some additions and comments soon. Documentation and examples are what made the Arduino successful, hopefully the same will be true of the Gameduino.

Hi,

The link for the manual just goes straight to apple icloud log in screen

? :/

I thought the poster is the documentation! Nice work derek. The 80 pages so far are an excellent reference.

A suggestion: I was trying to design my first character set background for a test I was doing, and it wasn't entirely obvious to me how the characters should be designed. My intuition tells me that the lowest 2 bits of the least significant byte would be the left most pixel, but that doesn't seem to be the case. I turned to the table on page 31 for the RAM_CHR organization, and the notation actually obscured what the answer was more than it revealed. Perhaps we could figure out a better way to explain the rule... James? Any suggestions?