Topics created by grundprinzip

My question is, if the behavior is required or an artifact of the integration with the driver?

I think this is required.
When actually transferring data to the screen, this is done 4 pixels at a time.

Shouldn't the library simply forbid creating a canvas that is not a multiple of 4?

Probably, yes.

@fonix232 Thanks! For me the exercise is much more exploring how the epaper display works when drawing the different components and how to optimize partial updates.

I will have a look at the projects you mentioned and see if I can find some inspiration!

@jop said in M5Paper Shutdown() / Deep Sleep / Wakeup:

overload-2 int shutdown( int seconds );

The timer function of the BM8563* is based on a 8 bit counter which can be set to be controlled by a clock frequency of 4096, 64, 1 or 1/60 Hz. This means it can timeout with following max interval @ resolution:

62,3 ms @ 244,1 µs
4 s @ 15,5 ms
255 s @ 1 s
15300 s (255 min) @ 60 s (1 min)

so intervals above 255 seconds (4 min and 25 seconds) needs to be timed at one minute resolution.
I have however tested this on my CoreINK (UiFlow/mocropython) and found that it rounds down in intervals of 2 minutes (120 s) for some reason.
I made a script to that just put the unit to sleep but increases the sleep interval with 10 sec every time and then uses the clock to measure the actual sleep time. This was the result:

0_1683278473886_4835f713-9fcf-4986-a3f7-f9f9ca8e3512-image.png

*) BM8563 datasheet