Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • Maybe that "fast" library is just too fast? Have you tried the Adafruit ST7789 library? We know that one works properly. Commented Oct 25, 2020 at 20:36
  • Did your program constantly clear the screen (with fillScreen()) in a loop? Commented Oct 26, 2020 at 7:14
  • As different UNOs as well as different displays show the same behaviour, it's the software, most probably. Did you try what Majenko suggests? Commented Oct 26, 2020 at 7:26
  • Regarding fillscreen, no. In the besnchmark test shown fillscreen is used to clear the screen inbetween benchmark tests. The setup function ploughs through each test. At the end is prints the results to the screen and leaves it like that. The loop function is empty. So you are left with a static screen of results (shown in my pictures above). The corruption is constant throughout regardless of animation, clearing screen or static images. Only press-holding the rest make the image full and clear. Perhaps something to do with grounding / changing constant voltages somewhere caused by the reset? Commented Oct 26, 2020 at 9:16
  • 1
    I managed to load an example that uses the standard Adafruit libraries (not the fast libraries) - from here link. It 'works' but with the same problem described above - corrupt image until press-hold of reset then image becomes full and clear. So not a problem with the 'fast' library. Commented Oct 26, 2020 at 15:21