You shouldn't worry about a ticket.not sure how fast is legal?
Moved my T4 reset to 8 from 23 to match github, it works w/graphicstest.
Slow without the post #2221 ILI9488_SPICLOCK edit … not sure how fast is legal?
The graphicstest Sum time was not added
Not sure what the INO pics above come from?
@KurtE
Not sure what else I can do with combining libraries, what is left:
1. sizeofFifo for T3x
2. framebuffer
3. DMA?
void ILI9488_t3::begin(void)
{
// verify SPI pins are valid;
#ifdef KINETISK
#if defined(__MK64FX512__) || defined(__MK66FX1M0__)
// Allow to work with mimimum of MOSI and SCK
if ((_mosi == 255 || _mosi == 11 || _mosi == 7 || _mosi == 28) && (_sclk == 255 || _sclk == 13 || _sclk == 14 || _sclk == 27))
#else
if ((_mosi == 255 || _mosi == 11 || _mosi == 7) && (_sclk == 255 || _sclk == 13 || _sclk == 14))
#endif
{
if (_mosi != 255) SPI.setMOSI(_mosi);
if (_sclk != 255) SPI.setSCK(_sclk);
// Now see if valid MISO
#if defined(__MK64FX512__) || defined(__MK66FX1M0__)
if (_miso == 12 || _miso == 8 || _miso == 39)
#else
if (_miso == 12 || _miso == 8)
#endif
{
SPI.setMISO(_miso);
} else {
_miso = 0xff; // set miso to 255 as flag it is bad
}
} else {
return; // not valid pins...
}
SPI.begin();
void ILI9488_t3::begin(void)
{
if (SPI.pinIsMOSI(_mosi) && ((_miso == 255) || SPI.pinIsMISO(_miso) && pinIsSCK(_sclk))
...
//=============================================================================
//=============================================================================
#include <ILI9488_t3.h>
#include <ILI9488_t3_font_Arial.h>
#define TFT_RST 8
#define TFT_DC 10
#define TFT_CS 9
ILI9488_t3 tft = ILI9488_t3(TFT_CS, TFT_DC, TFT_RST);
//=============================================================================
// Setup
//=============================================================================
void setup()
{
tft.begin();
tft.setRotation(3); // 180
delay(100);
tft.fillScreen(ILI9488_BLACK);
delay(250);
tft.fillScreen(ILI9488_RED);
delay(250);
tft.fillScreen(ILI9488_BLUE);
delay(250);
tft.fillScreen(ILI9488_GREEN);
delay(250);
tft.fillScreen(ILI9488_BLACK);
drawColor(0, 0, "Red", ILI9488_RED);
drawColor(0, 80, "Green", ILI9488_GREEN);
drawColor(0, 160, "Blue", ILI9488_BLUE);
drawColor(0, 240, "White", ILI9488_WHITE);
drawColor(240, 0, "Yellow", ILI9488_YELLOW);
drawColor(240, 80, "Orange", ILI9488_ORANGE);
drawColor(240, 160, "Cyan", ILI9488_CYAN);
drawColor(240, 240, "Pink", ILI9488_PINK);
}
void drawColor(uint16_t x, uint16_t y, const char *psz, uint16_t color)
{
tft.setFontAdafruit();
tft.setTextColor(color);
tft.setTextSize(2);
tft.setCursor(x,y);
tft.print(psz);
tft.drawRect(x+100, y, 50, 50, color);
tft.fillRect(x+110, y+10, 30, 30, color);
tft.drawLine(x+100, y+70,x+200, y+70, color);
tft.drawLine(x+220, y, x+220, y+70, color);
tft.drawLine(x+100, y+70, x+220, y, color);
tft.drawCircle(x+50, y+50, 30, color);
tft.fillCircle(x+50, y+50, 20, color);
tft.setFont(Arial_12);
tft.setCursor(x+160, y+50);
tft.print(psz);
}
//=============================================================================
// Loop
//=============================================================================
void loop()
{
}
hardware().queue_size
Pretty sure wrong thread? Unless you have one of the few T4 beta boards. Support for 1.8.9 Arduino requires Beta 10FYI
1.46-beta9 + regular installer 1.8.9
"Checking Arduino 1.8.8:
version: "lib/version.txt" wrong version: 1.8.9 Does not match Arduino 1.8.8
"
Pretty sure wrong thread? Unless you have one of the few T4 beta boards. Support for 1.8.9 Arduino requires Beta 10
Which you will find in the thread: https://forum.pjrc.com/threads/55471-Teensyduino-1-46-Beta-10
You shouldn't worry about a ticket.
Will the Teensy 4.0 support an end-user writing new firmware into it via USB and the Teensy Loader https://www.pjrc.com/teensy/loader.html or similar?
I am interested in the Teensy 4.0 for audio work. Looking at IMXRT1060RM.pdf I see the SAI1 to SAI3 signals can be directed to various pads, but I am not sure if such pads are brought out to Teensy pins, according to the pin list in message #3.
I will be using gcc and gdb under the MCUXpresso or perhaps some other IDE:
https://www.nxp.com/support/develop...valuation-kit:MIMXRT1060-EVK?tab=In-Depth_Tab
The "Use MCUXpresso" page there mentions an inbuilt debug circuit on that development board, while the "Use Arm GCC" page mentions an SWD/JTAG connector on that board. To what extent will gdb debugging be possible with the Teensy 4.0?
... which is the tiny copy of a Blink+RawHID program stored in the top 4096 byte sector of the flash chip. When you hold the pushbutton for 15 seconds, after the flash is fully erased (except that top 4096 bytes),
...
That sounds like a great idea - makes it almost foolproof.My hope is this restore feature together with the red LED will finally give us a good answer to the very common question "something went wrong, is my Teensy dead, how do I revive it".
Maybe do some measurements with some memcpy?
// Create 6 different frequencies on the SD card pins
// for easy testing whether all 6 signals are connected.
void setup()
{
GPIO3_GDIR |= (0x3F << 12);
}
uint32_t n=0;
void loop()
{
n++;
GPIO3_DR = (GPIO3_DR & ~(0x3F << 12)) | ((n & 0x3F) << 12);
delayMicroseconds(100);
}