Datasheet

3
updateRequest
curDisplay
nextDisplay
Some of the important preprocessor definitions that may change according to your requirements are:
SEG_DELAY
NUM_FENCES
PICKET_SHORT
NUM_SEGMENTS
TOP_PLANE
USING_PICKET_FENCE
USING_SLIDESHOWS
USING_GLOBAL_UPDATES
An important structure definition to look at:
einkScreenDef
Some important functions to look over are:
initEInkHardware
einkDriver
Connecting the hardware to EInk displays
EInk displays are usually terminated with stiffeners that can slide into FPC connectors. For the purpose of
development, one may use the YLPDSKRL78EINK daughter board which connects to the
YRPBRL78G14. The sample project provided is an IAR Workspace that runs on the YRPBRL78G14. In
the case of the YRPBRL78G14, the segments are driven directly from the MCU pins. The EInk display
requires atleast 5V to be able to drive the display. Note that an EInk segmented display cannot be driven
using 3.3V.
Incorporating EInk driver into your application
Step 1: Defining the segments
In the file rEInkHardwareAbstraction.h you will find the preprocessor definitions for each pin connected
to each segment of the EInk display screen.
You may add or delete some of these definitions depending upon the screen you choose to drive and the
number of segments it needs.
Also make changes to the function SetOutput and initEInkHardware in the file rEInkDriver.c while noting
the format of the previously written statements.
Step 2: Positioning the driver function and delay
Ensure that you have provision for atleast one interval timer interrupt. Within this periodic timer interrupt
place the function call to einkDriver. Also ensure that you also calling the function TimerTick defined in
timing.h.