Teensy 4 and the Gameduino 3X what pinouts? 5v?

[bitartrate]

In the latest email from James Bowman he shows the Teensy 4 driving the GD3X.  I have tried to hook it up but to no avail.  I did try an external 5v supply to the GD3 and did hook up both the 5v and Vin to 5v but the GD3 will not come on.    What are the proper pins to use?

Thanks!

[jamesbowman]

References:

excamera.com/sphinx/gameduino3/#hardware
forum.pjrc.com/teensy40_pinout1.png

The hookup is:

PIN	Teensy 4.0	Gameduino
SCK	13	13
MISO	12	12
MOSI	11	11
CS	8	8
GND	GND	GND
VCC	Vin	5V

The Gameduino doesn't start up at power-on. It needs a sketch loaded on the Teensy in order to start it. Best one to start with is the example "helloworld" - if you load it into the Teensy the Gameduino should start up.

[bitartrate]

Thank you for your reply James. It turns out that I did have the pins correct. But it still wont come on.
I am using a Teensy 4.0, with the newest TeensyDuino version, Arduino 1.8.9, and Gameduino2-v1.2.1.zip library.
My GD3 does work with an Arduino Uno so I do not believe that my GD3 is at fault.
Can you offer more advice?
Thank you.

[jamesbowman]

(I made a typo in the above table. The CS signal is pin is 8 on both boards.)


Here's what mine looks like:

[bitartrate]

Awesome! Thank you, that did the trick.

[Bennyturtle]

I wanted to ask, is there a way to use the gameduino3 sd card with the teensy 4.0 and (potentially) with a I2S sound chip
Was thinking of making a game for the gameduino but wanted speed, and the teensy is the best thing for that but with little support

[jamesbowman]

Yes, this definitely should work, but it's not been tried. I should have an opportunity this week to give it a try. When I do I will post the new hookup.

[darkfrost]

Hiya - using the GD3X along with a Teensy 4.1, but I'm having no luck - screen never lights up!

I've copied the pinout above - as far as I can tell, the pinout should be the same as the Teensy 4.0, just with extra pins?

Tried both the helloworld and logo samples, with no changes from the v1.2.2 release, no luck with either!

Any idea what I could be doing wrong, and what steps to take debugging this? I've triple checked my connections and I'm pretty sure I've got them hooked up as in your pinout / picture above!

[jamesbowman]

Hi darkfrost, that's odd. I'm running a Teensy 4.0 on my desk right now, with that pinout.

One quick thing to check first - there should be no microSD card in the slot.

[darkfrost]

Thanks for the speedy reply! No microsd card in either slot - on the teensy or on the GD

Is there anything about the 4.1 that might affect it differently than the 4.0?

[jamesbowman]

Well, it doesn't look like it from the docs. The GD library uses pin 8 and the SPI pins - not much to go wrong.

I've just ordered a 4.1 from PJRC for testing, it should be here next week.

[darkfrost]

That was my thinking too - looks the same as 4.0 but with extra stuff!

Thanks for much for ordering one to test with! That's really going above and beyond, hoping it's not just something wrong my end now!

[jamesbowman]

No problem at all!

OK, so it arrived and it seems to be working:




I'm using the SPI adapter board that's included in the SPIDriver expert pack

One thing to confirm is the 5V connection. The Gameduino uses the "5V" pin, not the "Vin" pin:

excamera.com/sphinx/_images/gameduino2_pinout.png

also shown here:

gameduino2.proboards.com/attachment/download/298

[darkfrost]

Thanks again for checking!

Darn, still no idea what's wrong then!

Was fairly sure my connections were right, but I wired it up again with some new header cables to double check, same result

Any idea for anything else I could try?

[darkfrost]

UPDATE: I think I might have a faulty gameduino?

Worked this out completely by accident, followed by some trial and error - if I plug in the teensy, nothing happens - if I plug in a teensy while applying some pressure to the left-ish side of the screen, the screen either comes on with just a backlight, or briefly runs the program (fizz), but with various errors / bars on the screen, then displays some form of "Coprocessor exception:" (the error message after varies)

Don't suppose there's an obvious fix for this, or should I contact where I bought it from? (coolcomponents)

Video of the issue: drive.google.com/file/d/1JPP7prjxxJ6VdsrLeQNFoHSsoe549nsU/view