<![CDATA[Let's speed up DrawLine and DrawPixel?]]>The esp32 is a beast and can fill byte arrays in a blink and the ILI is a fast controller when sent tons of data in one batch, as proof is the arkanoid example, and all other bitmap based M5 games.
So I'm thinking that the Display.cpp library is doing things inefficiently. DrawPixel is writing to the SPI (hardware?) byte by byte as we send them.
So a better way to feed the screen would be to batch commands.
Display.BeginCommand();
do the draw thingies and then
Display.Dispatch()
so DrawPixel would only fill a static array and the Dispatch command sends that to the ILI frame buffer.
There are libraries for arduino that do just that.
And if I know it, someone else already ported it over to M5. Google not collaborating, anyone has seen that?

]]>https://community.m5stack.com/topic/155/let-s-speed-up-drawline-and-drawpixelRSS for NodeWed, 29 Apr 2026 04:56:46 GMTWed, 04 Apr 2018 04:31:45 GMT60<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Wed, 11 Apr 2018 20:17:54 GMT]]>Bodmer wrote a nice article on this https://github.com/Bodmer/TFT_eSPI/issues/121#issuecomment-380245040
When un-commenting Display.h/#define SPI_FREQUENCY 40000000, fillscreen nearly doubles.
80M doesn't work on some M5.

]]>https://community.m5stack.com/post/813https://community.m5stack.com/post/813Wed, 11 Apr 2018 20:17:54 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Tue, 10 Apr 2018 18:08:33 GMT]]>@pkourany inside user_setup.h comment out the generic setups and uncomment m5. Then most examples work.
Result: same performances as m5 lib.
EDIT: even with SPI_FREQUENCY at 80,000,000 ... weird

]]>https://community.m5stack.com/post/792https://community.m5stack.com/post/792Tue, 10 Apr 2018 18:08:33 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Sat, 07 Apr 2018 11:41:21 GMT]]>I compiled the first example after making the necessary changes doe the M5Stack without errors. However, it would not load onto my M5Stack.

]]>https://community.m5stack.com/post/763https://community.m5stack.com/post/763Sat, 07 Apr 2018 11:41:21 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 23:57:50 GMT]]>@dda how much faster is it?

]]>https://community.m5stack.com/post/754https://community.m5stack.com/post/754Fri, 06 Apr 2018 23:57:50 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 16:08:09 GMT]]>@dda - good point!

]]>https://community.m5stack.com/post/749https://community.m5stack.com/post/749Fri, 06 Apr 2018 16:08:09 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 16:04:07 GMT]]>@jimit Now all we need is to have that officially included in the M5Stack library.

]]>https://community.m5stack.com/post/748https://community.m5stack.com/post/748Fri, 06 Apr 2018 16:04:07 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 15:53:27 GMT]]>@reaper7 @dda

Nice work dda !

Reaper those gui slice screens look awesome !! Glad you added M5Stack support and thanks for pointing them out

]]>https://community.m5stack.com/post/747https://community.m5stack.com/post/747Fri, 06 Apr 2018 15:53:27 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 16:00:54 GMT]]>@dda 在 Let's speed up DrawLine and DrawPixel? 中说：

Yep. And I managed to integrate this to the M5Stack library. I am doing tests, but so far so good. I've run a few modified sketches without issue. The TFT_ArcFill example is quite impressive.
.
.
.
There may be others, I'll see what happens when I compile the non-touch examples.

TFT_eSPI is the best lib, we added m5stack support some time ago:
https://github.com/Bodmer/TFT_eSPI/pull/88
btw, m5stack display lib based on the early version of TFT_eSPI
but since then, TFT_eSPI has developed a LOT!!!

P.S. for advanced GUI we also added m5stack support for GUIslice:
https://github.com/ImpulseAdventure/GUIslice/pull/34
which uses TFT_eSPI as display driver.

]]>https://community.m5stack.com/post/746https://community.m5stack.com/post/746Fri, 06 Apr 2018 16:00:54 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Fri, 06 Apr 2018 13:35:36 GMT]]>@daslolo Yep. And I managed to integrate this to the M5Stack library. I am doing tests, but so far so good. I've run a few modified sketches without issue. The TFT_ArcFill example is quite impressive.

Replacing the Display.h/.cpp files with the TFT_eSPI library was pretty easy. The Display library has a couple of M5-specific functions, but once added to the driver, everything works well:

void setBrightness(uint8_t); //Specific to M5Stack
void sleep();                //Specific to M5Stack

There may be others, I'll see what happens when I compile the non-touch examples.

]]>https://community.m5stack.com/post/744https://community.m5stack.com/post/744Fri, 06 Apr 2018 13:35:36 GMT<![CDATA[Reply to Let's speed up DrawLine and DrawPixel? on Thu, 05 Apr 2018 21:11:27 GMT]]>It looks like someone already did it
https://github.com/Bodmer/TFT_eSPI

]]>https://community.m5stack.com/post/728https://community.m5stack.com/post/728Thu, 05 Apr 2018 21:11:27 GMT