[riot-notifications] [RIOT-OS/RIOT] WIP: IL3829 e-Paper/e-Ink display driver (#11078)
notifications at github.com
Tue Mar 5 12:49:38 CET 2019
> We have a board here (PHYTEC's reel board, see #11096 ) that uses the SSD1673. Looking at the datasheet, they are so similar that it is almost the same chip. They even seem to have the same command.
It's close, but not compatible: all commands for the Y counters/area are a single byte instead of two. This is because the SSD1673 is a 150x250 controller, and the IL3829 200x300.
>From the datasheet it also looks like the waveform lookup table (LUT) should be different, but the implementation for the [Zephyr project](https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/ssd1673.c) has definitions that match the ones in this driver.
Looking at some other implementations there seem to be some different LUTs floating around, so there is something to say for making this configurable. I'm not entirely sure how much that matters, but I will investigate once I have received the second display.
Also: the SSD1607 does seem to be identical, and there are probably others.
> Just a thought: did you consider to also port the driver to the `u8g2` library? It is working as a package for RIOT and provides many useful things when working with a display...
No, but if I have some time I can take a look. As noted by @jcarrano, is seems e-paper is not the main target for the library. It does have *some* support (according to [the reference](https://github.com/olikraus/u8g2/wiki/u8g2reference)), but lacks partial updates.
> @silkeh, do think this PR could be compatible with the display that is on the board provided by #9517 ?
The display seems to have a SSD1606, which also uses a single byte for the Y values. Additionally, the size of the LUT for this display is 90 bytes instead of 30. At first glance it looks to be pretty much identical otherwise.
At this point it looks like it may be a good idea to start reworking this to support generic monochrome e-paper displays.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications