Highlight incompatibilitiy with Adafruit ecosystem
I try to manage expectation about this board and avoid short circuit or broken sensor. 1) I almost burned myself by mixing LOLIN I2C JST SH accessories and Adafruit QTPy, reverse way, I could have destroyed an Adafruit sensor by connecting it to Lolin S2 Pico. 2) The screen does not work as expected for a build-in screen, DISPLAY is not defined when you `import board` I did hesitate between making a special section like "Caveats" or highlighting how it deviate from one can expect from a board running CircuitPython.
This commit is contained in:
parent
b118f472d2
commit
ca4fc8be24
1 changed files with 2 additions and 2 deletions
|
|
@ -43,8 +43,8 @@ A development boards with an OLED and a small form factor.
|
|||
- `EN` RESET button
|
||||
- `GPIO0` BOOT button
|
||||
- `GPIO10` LED (blue status LED)
|
||||
- Lolin I2C JST SH 4-pin port (not QWIIC/Stemma-Qt pinout) using `GPIO8` (SDA) and `GPIO9` (SCL)
|
||||
- 128 x 32 SSD1306 OLED display internally connected to the same I2C bus as the external port, reset pin connected to `GPIO18`, I2C address `0x3C`
|
||||
- Lolin I2C JST SH 4-pin port (**not QWIIC/Stemma-Qt pinout**) using `GPIO8` (SDA) and `GPIO9` (SCL)
|
||||
- 128 x 32 SSD1306 OLED display internally connected to the same I2C bus as the external port, reset pin connected to `GPIO18`, I2C address `0x3C` (**not supported in CircuitPython firmware, require user code initialisation**)
|
||||
- Compatible with CircuitPython, MicroPython (default firmware), Arduino and ESP-IDF
|
||||
|
||||
## Purchase
|
||||
|
|
|
|||
Loading…
Reference in a new issue