@fast_code_r_us
I am thinking about replacing the display on my long -term construction LCD with E -Paper GDWE0215T11 - 112x208 BW.
The heart of the structure is #riscv CH32V003 with 2K RAM and 16K Flash.
How functional is your library in such harsh conditions? It will not work to keep the entire screen in the RAM, I need a partial redrawing.
Although for a periodic full redrawing I can use a static piece from Flash, right? ...🤔
=> More informations about this toot | More toots from yrabbit@mastodon.sdf.org
@yrabbit Would you like to beta test the code I'm working on?
=> More informations about this toot | More toots from fast_code_r_us@floss.social
@fast_code_r_us
undoubtedly! Not instantly - this display is designed to solder on the PCB and therefore I had to cut off the excess so that the cable enters the controller connector, but it does not hold there because it is too thin, and I will come up with something, maybe I will stick a piece of isolation. And then I will need to assemble a stand from CH32V003 and this display. :)
=> More informations about this toot | More toots from yrabbit@mastodon.sdf.org
@fast_code_r_us
It didn't work out with the small display - it's easier to order with a normal connector. In the meantime I'm thinking of playing with the big screen. Do you have a repository for the CH32V003 or should I just start with SPI programming and then look at your Arduino library and rewrite it in C?🤔
=> More informations about this toot | More toots from yrabbit@mastodon.sdf.org
@yrabbit No need to rewrite anything. I have a few I/O wrapper functions that you need to implement and then the rest of the code will compile unchanged. It's best to wait for my newer code - much smaller and easier to manage. I'm working as quickly as I can; hopefully by the end of today I'll have a lot of the features working. I just added support for 3 color panels.
=> More informations about this toot | More toots from fast_code_r_us@floss.social
@fast_code_r_us
That's great! Especially since my big display is a GDEW042T2, which is unclear about its capabilities - it was sold as 4-gray, but the documentation only shows two modes BW and BWR :)
=> More informations about this toot | More toots from yrabbit@mastodon.sdf.org
@yrabbit That panel is B/W, but the controller (UC81xx) supports B/W or B/W/R. In your case, it normally is only 1-bit B/W, but it has a 2-bit grayscale mode too. I support that panel in my code (I own a few).
=> More informations about this toot | More toots from fast_code_r_us@floss.social
@fast_code_r_us
It would be nice to activate this 2-bit mode :)
=> More informations about this toot | More toots from yrabbit@mastodon.sdf.org
@yrabbit Another challenge when using no RAM is that you can't read the memory back from the eink framebuffer, it's write-only. Any lettering that's not on byte boundaries will get clipped.
I chose this font because it's monospaced and exactly 40 pixels (5 bytes) wide (using your display panel).
=> More informations about this toot | More toots from fast_code_r_us@floss.social This content has been proxied by September (3851b).Proxy Information
text/gemini