#define TFT_DC 44
#define TFT_RST 46
#define TFT_CS 47 // any pin will work not hardware
ILI9488_t3 tft = ILI9488_t3(&SPI2, TFT_CS, TFT_DC, TFT_RST);
@mjs513 - Good morning again...
I thought for quick test to see if SPI2 is defined properly for T4.1 beta at least looks like it outputs something to the memory pins, I started to hack up the continuous update test...
And ran into issues with the ILI9488_t3 constructor (or my laziness). Which I can get around. But wondering what you think if I make the constructors work work more consistent with some of our other libraries.
That is my test, is to first make sure works with SDIO pin.
So I tried the shorthand version, and it failed as it still defaults to MOSI=11, SCK=13... Which are not valid for SPI2...Code:#define TFT_DC 44 #define TFT_RST 46 #define TFT_CS 47 // any pin will work not hardware ILI9488_t3 tft = ILI9488_t3(&SPI2, TFT_CS, TFT_DC, TFT_RST);
So possible fix #1 is when using shorthand constructor, then use default SPI pins for that port...
Also Wondering about adding new constructor like: ILI9488_t3 tft = ILI9488_t3(TFT_CS, TFT_DC, TFT_RST, TFT_MOSI, TFT_SCK, TFT_MISO)
And have it deduce which SPI port if the MOSI/SCK/MISO are all valid for a port than use that port...
Make sense?
For this test will probably just do full constructor with all of the pins... But what fun is that
Yep - But turns out bad test case for this T4.1 as I was using the one using EXTRAM... And this one does not have this.
I also think we need/should figure out best ways to handle cases like this on libraries. That is right now #define option to use external memory or not. But again I can imagine wanting some programs/T4.1s use external ram and others not... Wondering if it needs/should be some compile option or maybe sub-class?
…
#elif __has_include(<RA8876_t3.h>)
#include "Ra8876_Lite.h"
#include "RA8876_t3.h"
#define RA8876 1
#else
#if __has_include(<optional>)
# include <optional>
# define have_optional 1
#elif __has_include(<experimental/optional>)
Hello everybody,
do you see a chance to get the RPI display running with the Teensy 4.0?
https://www.waveshare.com/wiki/4inch_RPi_LCD_(C)
Unfortunately I don't find a suitable 4 inch display.
Thank you!
Hi,
I got the delivery today. After a lot of trying it works now.
I use the init commands from https://github.com/996refuse/waveshare4c/blob/master/const.py and had to set the SPI frequency to 19Mhz. With 20Mhz there are errors and it crashes. With 18Mhz it stays white.
Does anyone have any idea why it is so sensitive? I run the ILI9341 with t3n lib with 115Mhz without problems.
I also transferred the init commands to the ILI9341_t3n lib. So far without function. But I will keep trying.