Search results

It works! Thanks! There's another https://blogs.windows.com/windowsexperience/2017/05/11/build-2017-sparking-the-next-wave-of-creativity-with-the-windows-10-fall-creators-update/?OCID=WIP_r_25_Body_FallCreatorUpdate#8bDVcavlXH4MKda4.97creator update under the corner (later this year), finger...

Thanks a lot Paul, I try it in a min. Btw I just discovered that on Firefox 53.0.3 (32 bit) / Win10 cannot see any attachment in this thread, ouch. Had to use Microsoft Edge

TyTools solved the problem, at list with Arduino IDE, will try on Visual Studio in minutes. I didn't know about this tool, very cool!.

Thanks guys, happy to be here alive and kicking again, missed all :) I think this issue is related to the infamous Windows 10 Creators Update ? I have another notebook still running legacy Win 10 and works without reset as it should. I'm try to find a link where explain Windows 10 Creators...

Hi guys, after very long time it's nice to be here again and say hello to everybody using my hands again. after long time and long disease I finally get out, only sad for lost my mother in maintime... but I'm well and my wife and son perfect so I'm happy, really. Anyway, I was freaking out to...

I had a surgical operation in July and still not 100% ok, I'm late with everithing, when I'm ok I will take care of all libraries, sorry but before I cannot even use keyboard!

Amazing KurtE, this is a great new! Version in my github is from last year, I remember that I had some troubles to add transactions, had to move things in code to get the right SPI flow.

KurtE, I haved to modify a lot to get really working SPI with transactions with radiohead library, even paul's version have issues with SPI transactions. Unfortunatly this library is a big mess, put hands on it's a nighmare and author seems don't like github so there's tons of unofficial forks...

did you try the display alone at 96Mhz? I have 2 different one here (not adafruit, all chinese) and works at all freq. What you mean for SDCS? The CS for the SD card? Another question, did you using other SPI devices in the same time?

My SSD1351 works even at 120Mhz! Witch SSD1351 display you have?

Pin 2 doesn't seem a legal pin for CS/DC! This library uses SPI/FIFO so you have to apply at DC pin the same limitations of the CS pin, this mean not all pins can be used (see the informative double sided printed doc you get when you buy Teensy and look at CS pins) It works with Adafruit (slow)...

The TFT7735 library uses the same SPI FIFO of ILI9341, it uses the 4 byte buffer for SPI0 and of course is really fast, expecially with small displays. With Teensy 3.2, speed overclock and SPI fifo I really reach the ST7735 limits (and probably worked out of his parameters).

I have a SPI fifo version for TFT7735 here, maybe take a look.

I hate to say but, the editor it still indigestive (and I forced myself to use a polite word). The biggest change is the ability to react at negative numbers (!).

I wonder if SPIFIFO.h in teensy core needs a upgrade, for sure pin 26 is missed.... I never used it, someone knows anything that use it?

Thanks Kurt, reached the same conclusions, without your work on SPI cannot be possible. Ive used this library for testing stuff with SPI_FIFO, maybe can be useful to someone. thanks defragster, I've upgraded all libraries with a k64/66 additional fork. I'm sure is possible increase speed by...

The last RA8875 on github is fine, I'm currently testing also RA8876/77

Cannot get work, setting same pin as mine doesn't do nothing, no activity on PIN 6 or 10 but MOSI and SCLK are fine, also the function pinIsChipSelect(_cs, _dc) cannot get true in SPI1 since only one pin is available (6). Accordly this table, in SPI1 only pin 6 (or 31) should be usable and the...

SPI1 test Kurt, nevermind, it's too weird to me, finded a better solution. Thanks anyway! defragster, I got SPI1 working on a test version of TFT_ILI93XX, you don't need to do anything special or change any define. The SPI1 is used only on K64/k66 and when MOSI=0,SCLK=32 and DC=6, in this case...

Kurt, I'm confused about K65/K66 pin you used for SPI1 experiments. I was supposing use: MOSI:0 SCLK:32 CS:6 but you are using: DC = 0xe4 CS = 0xe5 SCK = 0xe2 MISO = 0xe3 MOSI = 0xe1 Probing with oscilloscope I've seen activity only on PIN 20 and 0 (this one should be MOSI) Can you tell me witch...

I think I've got it working, I don't use at all pcs_command, always pcs_data ( cs pin ) and separate conventional (for now) gpio method for dc so it can be any pin. Since it's K66 related, maybe we can stop discussion about this, it can be interesting only for understand how to deal with extra...

Since DC is used only during data strem it can be done, I will try later, will be not as fast. For sure I have to avoid pinIsChipSelect(uint8_t pin1, uint8_t pin2) an use pinIsChipSelect(uint8_t pin1), but how this impact on FIFO routines? es: pcs_command = pcs_data | SPI1.setCS(_dc);

Thanks Kurt, was really easy to do something, at list it compile. I'll try in a min. I have modded another library, really similar to t3_ILI9341, at list can drive the same display so it's possible to do some comparison: Library is here, it's nice to compare speeds since it can handle any SPI...

Defragster, it should work! This library uses the same SPI FIFO of t3_ILI9341. Thanks Kurt for the overall work on SPI, I was working last week and followed every update, tested as well between all Teensy's to be sure nothing broken and I have to say, all is apparently working till now.

Added SSD1351 and started beta stage. Modified the first post. Officially those libraries are now part of SSD_13XX.

Support for SSD1332 done, and works in any rotation, it's a bit slower than SSD1331 but much faster than before. Please report in github any problem!

A preview is Online, tested only with SSD1331 and all Teensy's (should be compatible with K's as well) It's really fast (much more than benchmarks above). UPDATE: I'm currently adding SSD1332, not easy since it's similar to SSD1331 but the rotation stuff not and several command missed...

I just tested with T3.0, T3.2 and T3.5 (180Mhz) and works, there's no so big changes from p7, a couple of bug fixed and the K64/66 identifiers. I have a couple of yellow pin display here, the quality of the pins is so bad that I have to clean/revive pin really often since it oxidate really fast.

In SPI library.cpp, function bool SPIClass::pinIsChipSelect(uint8_t pin1, uint8_t pin2) There's a debug serial that should be commented: Serial.printf("pinIsChipSelect %d %d %x %x\n\r", pin1, pin2, pin1_mask, pin2_mask);

The right one is the 1.0p8, sorry for the github confusion, I keep master for legacy purposes

Paul, you can include TFT_ILI9163C with mods for K64 and K66?

installed and run fine here so far... Win 10/64

The SSD1331 it's hard, it has lot of hardware issues and again the datasheet is almost useless so it's a slow process but at the end I'm getting slowly out of this. Currently library is not public, have to fix a lot of issues and I'm currently busy with K64/66 stuff, but here's the bechmarks...

I had the same issue one week ago. I was on Win 10, 2 different PC, no way, unrecognized device and no serial port appears. In the past I've experienced similar issues with 3.2, it was the serial port get stuck, a PC reboot normally fix that, but this time no way, restarting PC was not useful...

Only with Teensy is possible sharing (always in theory) DC, this is a feature of SPI FIFO that is not possible with other CPU's. Also, Zero is NOT supported (now and in the near future).

Many? did you mean multiple instances on the same CPU? On Teensy it's possible (in theory) have many OLED 1331 by sharing MOSI,SCLK,DC, just CS should be separate for each display, but I need to do some extra work for multiple instances...

I know, I'm terrible late on this but had to get more of these display's because I'm ran out. I have started a new library for this display series, I'm still a little busy on K66 changes but at list library started and will published soon. It has the same features of TFT_9163C and it's really...

I thought I was reading a book Of Edgar Allan Poe for the holidays but I think it's inevitable that I read 2Kpages K66 sub family manual...

Thanks manitou, this explain my headaches of today! So the SPI1 and SPI2 should be similar to Teensy LC? At list it should be slower, have to rewrrite my testing SPI_FIFO... Thanks KurtE, I've used your changes already for testing purposes, Have tried to update also: void...

KurtE, in your mods in SPI.h, should correct this? SIM_SCGC6 |= SIM_SCGC6_SPI1;//was SIM_SCGC6_SPI0 Currently working on avr_emulation.h for enabling SPI1 FIFO, still not working but at list not freeze...

I quote this, looks better!

This library is old, I have abandoned it. New one il called TFT_ILI93XX and it's ready for K64/K66 Thanks kurtE for the SPI mods, even if not officially accepted I'm currently testing with this raw llibrary that uses Fifo even for SPI1 (and SPI2). It's just for test new stuff!

what about a Teensy 1000 (1000 core) :rolleyes: 1.78 Trillion Ops/sec Just joking...

I've runned some SPI as burn test for a while. Get stuck a couple of times (SCLK HIGH and CPU freezed). Doing same at lower speed was not a problem.

Not really, the serial remain stuck but appears correctly in arduino or terminal and, most interesting, remain stuck between restarts! I have installed a serial analyzer yesterday to understand what's broken and the receiving part of the serial port in computer side it act like disconnected. To...

About serial hangs.... Remove driver and reinstall not works, looks like the port is stuck and remain stuck between restarts. I got the same problem on a second laptop, win7/64 as well, happened an hour ago. To get it back I have completely reset all serial ports on both computers. Weird, never...

Ok, now I have this issue. On Win7/64 from yesterday the K66 continue asking: "Teensy did not respond to a USB-based request to automatically reboot. Please press the PROGRAM MODE BUTTON on your Teensy to upload your sketch." Tryed upload blink.ino, changed port, disinstalled driver, no matter...

EEPROM confirmed work, writed some data and get back after a power cycle. Tested Serials at various speed and all seems work (btw,not tried the lower speeds) Noticed that SPI performances vs CPU clock are not as I expected, for example 180Mhz has better performances than 192Mhz, I know...

About SPI, just a placeholder for testings.... #if defined(__MK64FX512__) || defined(__MK66FX1M0__) //Teensy 3.4/3.5 if ((_mosi == 11 || _mosi == 7) && (_miso == 12 || _miso == 8) && (_sclk == 13 || _sclk == 14)){ // SPI } else if (_mosi == 9 && _miso == 1 &&...

Nevermind. SPI1 and SPI2 for KINETISK are currently not present inside SPI.cpp Trying to update SPI library...