and then in the config file adjust these lines for your display:#define ST77XX_ON_SPI_SPI1
#else
//CS DC MOSI SCK RST WINK ROT INIT
{0, 2, 26, 27, 3, -1, 0, INITR_144GREENTAB }, // RIGHT EYE display-select and wink pins, no rotation
{10, 9, 11, 13, 8, -1, 0, INITR_144GREENTAB }, // LEFT EYE display-select and wink pins, no rotation
#endif
I've been using these:https://www.aliexpress.com/item/329...rchweb0_0,searchweb201602_,searchweb201603_52
I've gotten them to work with a raspberry pi before, although this is my first time trying them on other hardware. I don't have anything wired to 5v, except the USB cable powering the teensy. I'll see if I can get a good picture of my wiring shortly.
Display - Pin Desc - T4 (what you have) - T4 what should be
1,2,5,6,12 - Ground - Black - no problem
3,4 - 3.3v - Red - no problem
7 - D/C - White - Pin 9 --- ok this can be any digital pin
8 - CS - Blue - Pin 10 ---- ok this is typical for CS pin
9 [COLOR="#FF0000"]- SCL - Green - Pin 14 ---- SPI CLOCK IS ON PIN 13 not pin 14[/COLOR]
10 - SDA - Yellow - Pin 11 - Pin 11 so this is ok.
11 - Reset - Orange - Pin 8 - Pin 8 typical and what I am using
the only bridges i have were for connecting the multiple grounds and the led to the 3v input. is there a separate folder for the graphics test? the only one i seen was for the ILI screen, not the ST ones. though the scroll test did seem to work flawlessly from what i could tell
Teensy 3.2, MK20DX256VLH7, M4, cpu 96Mhz, spi 24Mhz, TFT, 128x128, ST7735, 2 eyes: 85fps
Teensy 3.2, MK20DX256VLH7, M4, cpu 96Mhz, spi 24Mhz, TFT, 128x128, ST7735, 1 eye: 85fps
Teensy 3.5, MK64FX512, M4, cpu 120Mhz, spi 18Mhz, OLED, 128x128, SSD1351, 2 eyes: 56fps
Teensy 3.5, MK64FX512, M4, cpu 120Mhz, spi 18Mhz, OLED, 128x128, SSD1351, 1 eye: 56fps
Teensy 4.0, i.MX RT 1062, M7, cpu 600Mhz, spi 48Mhz, TFT, 240x240, ST7789, 2 eyes: 30-32fps
Teensy 4.0, i.MX RT 1062, M7, cpu 600Mhz, spi 48Mhz, TFT, 240x240, ST7789, 1 eye: 15-16fps
Hallowing M0, ATSAMD21G18, M0, cpu 48Mhz, spi 12Mhz, TFT, 128x128, ST7735, 1 eye: 22fps
Hallowing M4, ATSAMD51G18, M4, cpu 120Mhz, spi 50Mhz, TFT, 240x240, ST7789, 1 eye: 27-31fps
Monster M4SK, ATSAMD51G19, M4, cpu 120Mhz, spi 50Mhz, TFT, 240x240, ST7789, 2 eyes: 20-29fps
#if defined(__MK66FX1M0__)
DMASetting ST7735_t3::_dmasettings[3][4];
#endif
#if defined(__IMXRT1062__) // Teensy 4.x
// On T4 Setup the buffers to be used one per SPI buss...
// This way we make sure it is hopefully in uncached memory
ST7735DMA_Data ST7735_t3::_dma_data[3]; // one structure for each SPI buss...
#endif
d:
cd d:\GitHub\Cores
git fetch upstream
git checkout master
git reset --hard upstream/master
git push origin master --force
cd %home%
c:
Yep - think the sledgehammer will be the way to go for me - to be honest think its cleaner (or easier for me to understand whats going on. That will be the project for when I get back from my errands.KurtE said:My typical REBASE is again the sledgehammer. I copy away my new stuff to some save folder (example on my desktop).
I use the first sledge hammer above.
After that completes, I create a new branch, which I copy in my changed stuff, and then check the changes, push that one up.... And delete my previous working version... But I know there should be a cleaner way...