GD2 With FT813 on Arduino Zero

[kira076]

Hello,

I recently switched from an FT80x capacitive screen to an FT813 screen from Riverdi. I'm using the Riverdi Arduino shield on an Arduino (Genuino) Zero with the latest GD2 library downloaded straight from the Github and modified to add an Arduino Zero definition alongside Due definitions for compatibility.

This setup worked fine with my old screen. However with  the new one, whenever I upload a sketch (just the examples such as HelloWorld or Blobs) the screen does not turn on and the "L" LED on my Zero is lit up constantly.

I've attempted to debug with AtmelStudio but the sketch doesn't even seem to compile. From a bit of searching, it seems it may be a problem with a fuse? But I don't know enough about the hardware side of Arduino to know.

I've also attempted to use the Riverdi example library/project... And it works just fine. However it makes use of FTDI's code which is extremely technical and difficult to parse through. 

Does anyone know how I could get the GD2 library going with both a Riverdi FT813 screen (with Riverdi Arduino shield) -and- an Arduino Zero?

Thanks!

[kira076]

Small update:

I've attempted to use the "GD3" library from this thread: forum.arduino.cc/index.php?topic=429381.0 (Again modified to add definitions for Arduino Zero alongside Due ones).

When the "MCU_Teensy" definition in GD3.h, line 43 is set to 1 and I attempt the FT8XX_helloworld example sketch... The screen will flicker on for a moment before turning to black once again and the LED on my Zero board coming on. When that same definition is 0, the screen doesn't even flicker.

[kira076]

Aha! I seem to have solved the problem - When modifying to add definitions for the Zero, I went back and only added definitions where it came up with errors when compiling (Which meant -not- adding Zero definitions for the alternate SPI stuff for the Due)... The GD3 library linked above now seems to work!

[kira076]

It just occured to me that I'm removing mention of the SPI clock without implementing the custom SPI that I assume negates the need for that... Is that an issue?

i.e. I'm modifying a couple places as follows:



#if !defined(__DUE__) && !defined(__ZERO__)
   SPI.setClockDivider(SPI_CLOCK_DIV2);
   SPSR = (1 << SPI2X);
#endif
Does the clock divider need to be changed when using the Zero?

Edit:

The touch detection also seems to be non-functioning. Not sure why? Other than it's a capacitive screen.