readme_EN.txt (4102B)
1 /***************************************************************************** 2 * | File : Readme_CN.txt 3 * | Author : Waveshare team 4 * | Function : Help with use 5 * | Info : 6 *---------------- 7 * | This version: V1.0 8 * | Date : 2019-07-31 9 * | Info : Here is an English version of the documentation for your quick use. 10 ******************************************************************************/ 11 This file is to help you use this routine. 12 Since our ink screens are getting more and more, it is not convenient for our maintenance, so all the ink screen programs are made into one project. 13 A brief description of the use of this project is here: 14 15 1. Basic information: 16 This routine has been verified using the e-paper Driver HAT module. 17 You can view the corresponding test routines in the \lib\Examples\ 18 of the project. 19 20 2. Pin connection: 21 Pin connection You can view it in DEV_Config.h in the \lib\Config\ directory, and repeat it here: 22 EPD => Jetson Nano/RPI(BCM) 23 VCC -> 3.3 24 GND -> GND 25 DIN -> 10(SPI0_MOSI) 26 CLK -> 11(SPI0_SCK) 27 CS -> 8(SPI0_CS0) 28 DC -> 25 29 RST -> 17 30 BUSY -> 24 31 32 3. Basic use: 33 Since this project is a comprehensive project, you may need to read the following for use: 34 You can see the 19 functions that have been annotated in lines 19 through 43 of main.c. 35 Please note which ink screen you purchased. 36 Chestnut 1: 37 If you purchased 5.83inch e-paper, then you should remove the comment for the corresponding 39 lines of code, ie: 38 // EPD_5in83_test(); 39 changed to: 40 EPD_5in83_test(); 41 Chestnut 2: 42 If you buy a 2.9inch e-paper (B), since the 2.9-inch Type B and Type C are common driver codes, 43 Then you should remove the comment for the corresponding 28 lines of code, ie: 44 // EPD_2in9bc_test(); 45 changed to: 46 EPD_2in9bc_test(); 47 Note: For EPD_1in54_V2_test() and EPD_2in13_V2_test(), please note that the V2 logo is attached to the back of your screen. 48 49 Then you need to execute: 50 make 51 compile the program, will generate the executable file: epd 52 Run: 53 sudo ./epd 54 If you modify the program, you need to execute: 55 make clear 56 then: 57 make 58 59 4. Directory structure (selection): 60 If you use our products frequently, we will be very familiar with our program directory structure. We have a copy of the specific function. 61 The API manual for the function, you can download it on our WIKI or request it as an after-sales customer service. Here is a brief introduction: 62 Config\: This directory is a hardware interface layer file. You can see many definitions in DEV_Config.c(.h), including: 63 type of data; 64 GPIO; 65 Read and write GPIO; 66 Delay: Note: This delay function does not use an oscilloscope to measure specific values. 67 Module Init and exit processing: 68 void DEV_Module_Init(void); 69 void DEV_Module_Exit(void); 70 Note: 1. Here is the processing of some GPIOs before and after using the ink screen. 71 2. For the PCB with Rev2.1, the entire module will enter low power consumption after DEV_Module_Exit(). After testing, the power consumption is basically 0; 72 73 \lib\GUI\: This directory is some basic image processing functions, in GUI_Paint.c(.h): 74 Common image processing: creating graphics, flipping graphics, mirroring graphics, setting pixels, clearing screens, etc. 75 Common drawing processing: drawing points, lines, boxes, circles, Chinese characters, English characters, numbers, etc.; 76 Common time display: Provide a common display time function; 77 Commonly used display pictures: provide a function to display bitmaps; 78 79 \lib\Fonts\: for some commonly used fonts: 80 Ascii: 81 Font8: 5*8 82 Font12: 7*12 83 Font16: 11*16 84 Font20: 14*20 85 Font24: 17*24 86 Chinese: 87 font12CN: 16*21 88 font24CN: 32*41 89 90 \lib\E-paper\: This screen is the ink screen driver function; 91 Examples\: This is the test program for the ink screen. You can see the specific usage method in it.