You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- This library is still work in progress. There may be breaking changes happening while work on this library progresses.
22
+
- So far only SPI interface has been implemented.
23
+
24
+
Check the [samples](https://github.com/nanoframework/Samples#graphics-for-screens) for more detailed usage.
25
+
26
+
### Initializing the screen
27
+
28
+
It is important to understand that the driver will be loaded when the screen routing will be initialized from the managed code. Also keep in mind that most screens are actually smaller than the size the driver is capable of handling, also that the real screen can start at a position that is not the typical origin (0,0).
29
+
30
+
You **must** initialize the screen before being able to create a bitmap or display anything.
31
+
32
+
This code snippet works with the ESP32 WROVER KIT pinout, in this case, the screen size matches the driver size:
Note that depending on your target, especially for ESP32, you may have to setup the pins. Even if physically not used, the MISO pin **must** be setup to a valid pin.
59
+
60
+
As you can see it is possible as well not to define the backlight pin. It is the same for the rest pins. Both can be set to -1. Note that in most of the cases, both are connected and needed. In the case of the M5 Stick, the backlight pin is managed thru an AXP192. If you don't switch on the backlight pin, your screen will always be black. It is important to check how this pin can be switched on.
61
+
17
62
## Feedback and documentation
18
63
19
64
For documentation, providing feedback, issues and finding out how to contribute please refer to the [Home repo](https://github.com/nanoframework/Home).
0 commit comments