diff options
| author | JF002 <JF002@users.noreply.github.com> | 2020-07-25 14:36:58 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-25 14:36:58 +0200 |
| commit | 22fe96f69a3d6960ac132710d073df36ffd8be4b (patch) | |
| tree | 741b9279ffbbd363b5cd7cfdf0b109c1cb0bd499 /doc | |
| parent | 515a90f7b359c93dc7aaa3e7d5b1a0b16df234f9 (diff) | |
| parent | 381ac4d7dadd07d5bc7acef6596e5910bd2b105f (diff) | |
Merge pull request #46 from sethitow/master
Edit README and docs
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/SPI-LCD-driver.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/SPI-LCD-driver.md b/doc/SPI-LCD-driver.md index 3c33c258..f787aab7 100644 --- a/doc/SPI-LCD-driver.md +++ b/doc/SPI-LCD-driver.md @@ -24,17 +24,17 @@ As I said in the introduction, the datasheet will be your bedside book during yo The schematic of your board (the Pinetime schematics in this case) will also be very important, as you'll need to know how the LCD controller is physically connected to the MCU. -How to read the datasheet? I recommand to read it from the beginning to the end (no joke) at least once. You certainly do not need to read everything in details, but it's good to know what information is available and where in the document. It'll be very useful during the developpment phase. +How to read the datasheet? I recommend to read it from the beginning to the end (no joke) at least once. You certainly do not need to read everything in details, but it's good to know what information is available and where in the document. It'll be very useful during the development phase. You'll want to read some part with more attention : - Data color coding in 4-Line Serial Interface : how to send the pixel to be display to the controller -- Display Data Ram : how is the memory organised +- Display Data Ram : how is the memory organized - Power On/Off sequence - System function commands : all the commands you can send to the controller. ## One Pixel at a time -## Bulk transfert +## Bulk transfers ## DMA |