This e-ink screen cannot be driven on some Raspberry Pi newer systems, or the Raspberry Pi zero 2 w.
The I2C bus rate for this e-ink is fixed at 100kbps. you need to check the /boot/firmware/config.txt file for the following line:
dtparam=i2c_arm=on, and then add after this line: i2c_arm_baudrate=100000
It has to be ended exactly like this:
dtparam=i2c_arm=on,i2c_arm_baudrate=100000
Is it normal that the screen flashes for a long time when refreshing?
Although E-ink display is a very popular type of electronic paper display technology, due to the imaging principle, there are also some defects including screen splash and afterimage issue. After repeatedly turning the page, the ink will remain, which causes the afterimage problem. To deal with that, manufactures designed the full refresh function, however, another issue occurred: the screen will flashes for a while when refreshing fully.
This e-ink screen cannot be driven on some Raspberry Pi newer systems, or the Raspberry Pi zero 2 w.
The I2C bus rate for this e-ink is fixed at 100kbps. you need to check the /boot/firmware/config.txt file for the following line:dtparam=i2c_arm=on, and then add after this line: i2c_arm_baudrate=100000It has to be ended exactly like this:dtparam=i2c_arm=on,i2c_arm_baudrate=100000
Is it normal that the screen flashes for a long time when refreshing?
Although E-ink display is a very popular type of electronic paper display technology, due to the imaging principle, there are also some defects including screen splash and afterimage issue. After repeatedly turning the page, the ink will remain, which causes the afterimage problem. To deal with that, manufactures designed the full refresh function, however, another issue occurred: the screen will flashes for a while when refreshing fully.