What is this project?

[bsabiston]

What does it do?

[rowdy15]

It allows you to use GFX library in the nRF5 SDK with epaper displays with the IL0373 IC driver controller. see here. I just took the epaper.c and epaper.h files and included them in my project with sdk 15.3 and took the structures in the main.c and added to my main.c and it works. I did have to make a couple of other changes, but the debugger told me everything that needed to be fixed in order to compile.

Just be sure to write:

lcd.lcd_display();

after having created your graphics (rectangles circles, lines, strings), otherwise you might be wondering why its not working.

[leonrinkel]

Oops, that somehow slipped through, sorry. Thank you @rowdy15 for answering. This repo is my example of getting an eink display to run with nordics nRF52 series ICs. I used nordics GFX library, which allows to draw lines, circles, text, images etc. in a very convenient way. Also this is probably not a perfect ready-to-run solution, just a little example of how one could do it.

[rowdy15]

It's an excellent implementation. Thank you heaps for it. I have used it with the nRF52832, using Segger Embedded Studio, and it works very well with full screen updates (actually very fast, after modifying the lookup tables (LUT) see here), but I haven't been able work out how to implement partial updates yet. I need to learn a bit more about the bit calculations etc. If I do find a solution to this I will post it in here.

[toxicOxygen]

what pins on the nRF kit did you connect the e-paper to

[leonrinkel]

There are #defines for the pins in paper.c

[toxicOxygen]

oh thanks, I did not see that

[rowdy15]

I think you can change the pins on the #defines to suit your nRF kit (pretty sure that's what I did from memory). I think I've seen it written that just about any pins can be used for SPI (and probably I2C and UART too). So if you can't get access to the pins on board physically, don't stress. Just try other pins on the board that are available (just remember to change the #defines accordingly).

[toxicOxygen]

where should we write the lcd.lcd_display();? Do I write before the nrf_gfx_line_draw function ?

[kwaku96]

is the PAPER_SPI_INSTANCE the same as the busy pin?

[leonrinkel]

@kwaku96 There are multiple SPI peripheral instances on the nRF hardware which can be used in parallel. PAPER_SPI_INSTANCE defines which instance to use. It's not a pin. You should be fine with using 0 if you're not using this instance somewhere else.

[kwaku96]

i'm really sorry as i am very new to coding in general, but what pin did u use as your busy pin, or it doesn't matter?

[leonrinkel]

No need to excuse, I'm happy to help. I don't use the busy pin in this example. Instead I wait arbitrary delays, which is not the best solution but the easiest. You can just leave the pin disconnected.

nRF52-eink-epaper/src/paper.c

Line 246 in 1e4f002

nrf_delay_ms(100); // TODO use busy pin rather than arbitrary delays

[kwaku96]

thank you very much. One more question (please don't be upset), I am using the waveshare epaper 2.13 and you used waveshare epaper 2.13 revision D, will that make any difference or the same code will run for me too

[leonrinkel]

https://www.waveshare.com/wiki/2.13inch_e-Paper_HAT This site suggests that there are differences in the controllers that require different code. If you have v2 it might work, otherwise it probably won’t but I’m not sure.

…

On 28. Jul 2020, at 13:40, kwaku96 ***@***.***> wrote:  thank you very much. One more question (please don't be upset), I am using the waveshare epaper 2.13 and you used waveshare epaper 2.13 revision D, will that make any difference or the same code will run for me too — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[kwaku96]

Thank you very much, I will check that out