arduino:displays_for_classic_arduinos:1.8_and_1.44_tft_displays_and_classic_arduinos
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
arduino:displays_for_classic_arduinos:1.8_and_1.44_tft_displays_and_classic_arduinos [2018/01/28 03:35] – [Summary evaluation] mithat | arduino:displays_for_classic_arduinos:1.8_and_1.44_tft_displays_and_classic_arduinos [2018/01/31 04:55] (current) – [Ucglib] mithat | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Summary evaluation ===== | ===== Summary evaluation ===== | ||
- | These small 1.8" (160x128) and 1.44" (128x128) TFT displays with ST7735 controllers have been [[https:// | + | Small 1.8" (160x128) and 1.44" (128x128) TFT displays with ST7735 controllers have been [[https:// |
- | One of the concerns with with TFT displays is that they are data gluttons, | + | One of the concerns with with TFT displays is that they are data gluttons, |
Unfortunately, | Unfortunately, | ||
Line 11: | Line 11: | ||
The results are a bit of a disappointment because the displays are otherwise incredibly charming. | The results are a bit of a disappointment because the displays are otherwise incredibly charming. | ||
- | ===== Libraries | + | ===== Tests ===== |
- | These are the libraries I know of that let you interface to a ST7735-based display. | + | I ran a number of tests using all the libraries I know of that let you interface to a ST7735-based display. |
==== Ucglib ==== | ==== Ucglib ==== | ||
Oli Kraus' [[https:// | Oli Kraus' [[https:// | ||
- | I ran two test cases: one using transparent | + | I ran two test cases: one using solid font rendering and the other with transparent. In both cases, faster hardware SPI was used over slower software SPI. I ran both test cases with both a 3.3V 8 MHz Pro Mini and a 5V 16 MHz Nano, for a total of four tests. |
As you can see from the videos, the speed isn't entirely acceptable. I am assuming this is mostly due to the burden placed by the pretty fonts' data. Frame rates with a 16 MHz processor are double those of an 8 Mhz processor (no surprise). Even though the transparent font rendering is technically faster, the solid rendering artifacts are less annoying. | As you can see from the videos, the speed isn't entirely acceptable. I am assuming this is mostly due to the burden placed by the pretty fonts' data. Frame rates with a 16 MHz processor are double those of an 8 Mhz processor (no surprise). Even though the transparent font rendering is technically faster, the solid rendering artifacts are less annoying. | ||
Line 34: | Line 34: | ||
=== Transparent font rendering === | === Transparent font rendering === | ||
- | {{youtube> | + | {{youtube> |
{{youtube> | {{youtube> | ||
Line 59: | Line 59: | ||
The Adafruit library with its default font performs and looks almost the same as the Arduino TFT library. | The Adafruit library with its default font performs and looks almost the same as the Arduino TFT library. | ||
- | FIXME video | + | {{youtube> |
[[display_st7735_1.44_adafruit_st7735.ino | source code]] | [[display_st7735_1.44_adafruit_st7735.ino | source code]] | ||
Line 67: | Line 67: | ||
When a large fancy font is used, the performance between the Adafruit library and Uclib narrows. I suspect that with a font as large as that used in the Uclib examples, the results would be close to identical. Which is to say, not fast (or light?) enough. | When a large fancy font is used, the performance between the Adafruit library and Uclib narrows. I suspect that with a font as large as that used in the Uclib examples, the results would be close to identical. Which is to say, not fast (or light?) enough. | ||
- | FIXME video | + | {{youtube> |
[[display_st7735_1.44_adafruit_st7735_fonts.ino | source code]] | [[display_st7735_1.44_adafruit_st7735_fonts.ino | source code]] | ||
arduino/displays_for_classic_arduinos/1.8_and_1.44_tft_displays_and_classic_arduinos.txt · Last modified: 2018/01/31 04:55 by mithat