MicroPython Forum (Archive)

mcauser wrote: ↑

Fri Feb 23, 2018 3:53 pm

It's still a work in process, but complete enough for you to start experimenting.
Various size panels, Black/White, Black/White/Red and Black/White/Yellow displays.
https://github.com/mcauser/micropython-waveshare-epaper

I only own the 2.9" B/W display and i've got it working with my STM32F407VET6 board, drawing images generated with PIL and using the frame buffer (MONO_HLSB).

Drivers for:
* 1.54inch e-Paper Module
* 1.54inch e-Paper Module (B)
* 1.54inch e-Paper Module (C)
* 2.13inch e-Paper HAT
* 2.13inch e-Paper HAT (B)
* 2.13inch e-Paper HAT (C)
* 2.7inch e-Paper HAT
* 2.7inch e-Paper HAT (B)
* 2.9inch e-Paper Module <-- mine
* 2.9inch e-Paper Module (B)
* 2.9inch e-Paper Module (C)
* 4.2inch e-Paper Module
* 4.2inch e-Paper Module (B)
* 4.2inch e-Paper Module (C)
* 4.3inch e-Paper UART Module
* 7.5inch e-Paper HAT
* 7.5inch e-Paper HAT (B)
* 7.5inch e-Paper HAT (C)

All of the (B) modules are Black/White/Red.
All of the (C) modules are Black/White/Yellow.

mcauser wrote: ↑

Sun Mar 04, 2018 10:27 pm

Din and Clk are SPI pins. Data In and Serial Clock.

Din on a module would connect to the MOSI pin on a microcontroller. MOSI = master (data) out, slave in.

GPIO23 = MOSI
GPIO18 = SCK

The CS pin is for telling the SPI module that you are speaking to it and not others on the bus. If there are no other SPI devices on the bus, you could connect this pin to GND to save an IO pin. Haven’t tested this though.

The DC pin is for toggling between they command and data registers.

The RST pin is so you can reset the display.

The BUSY pin is so you can execute slow running commands then can poll the pin until it’s low before continuing.

mcauser wrote: ↑

Mon Mar 05, 2018 9:46 pm

As long as you pass it a valid SPI object which has a .write() method, it should work.

I haven't used the loboris build, so I'm not sure what the SPI syntax is. Maybe something like this:

Code: Select all

from machine import Pin, SPI
spi = SPI(1, baudrate=2000000, polarity=0, phase=0)
 
from machine import Pin, SPI
spi = SPI(-1, baudrate=2000000, polarity=1, phase=0, sck=Pin(0), mosi=Pin(2), miso=Pin(4))

import epaper4in2b
from machine import Pin, SPI

# SPI3 on Black STM32F407VET6
# spi = SPI(1, baudrate=2000000, polarity=0, phase=0)
spi = SPI(-1, baudrate=2000000, polarity=1, phase=0, sck=Pin(0), mosi=Pin(2), miso=Pin(4))
cs = Pin(6, mode=Pin.OUT)
dc = Pin(7, mode=Pin.OUT)
rst = Pin(8, mode=Pin.OUT)
busy = Pin(9, mode=Pin.OUT)

e = epaper2in9.EPD(spi, cs, dc, rst, busy)
e.init()

w = 400
h = 300
x = 0
y = 0

. Exception was unhandled.
Guru Meditation Error: Core  0 panic'ed (IllegalInstruction)

loboris wrote: ↑

Wed Mar 07, 2018 12:16 am

@devrosx

On ESP32 boards GPIO6 - GPIO11 are used to access the SPI Flash from which the program is running and cannot be used for other purposes.

Try to use some other GPIOs.

spi = SPI(SPI.HSPI, baudrate=2000000, sck=19, mosi=23, miso=25, cs=26)