Universal GPIO library for Arduinos, Teensy 2/3/3.x, Teensy LC
An attempt to create an universal library that works with many common GPIO chips and can be used with Arduino's and Teensy's (my preferred choice)
Here's a list of the GPIO's chip managed:
| chip | company | pins | protocol | features | status |
| mcp23s17 | Microchip | 16 | SPI | HAEN/INT | done |
| mcp23017 | Microchip | 16 | I2C | INT | done |
| mcp2308 | Microchip | 8 | I2C | INT | done |
| mcp23s08 | Microchip | 8 | SPI | HAEN/INT | done |
| mcp23s18 | Microchip | 16 | SPI | OPEN DRAIN/INT | done |
| mcp23018 | Microchip | 16 | I2C | INT | done |
| mcp23016 | Microchip | 16 | I2C | INT | done |
| pcf8574 | NTX | 8 | I2C | INT | done |
| pcf8574a | NTX | 8 | I2C | INT/different address range | done |
| pcf8575 | NTX | 8 | I2C | INT | planned |
| pca9698 | NTX | 40 | I2C | INT/64adrs | planned |
| pca9555 | NTX | 16 | I2C | INT/64adrs | testing |
| tca9555 | TI | 16 | I2C | INT/64adrs | testing |
| pca9655 | ON | 16 | I2C | INT/64adrs/1Mhz I2C | testing |
| max6957 | TI | 20/28 | I2C | INT/64adrs | testing |
| max7301 | TI | 20/28 | I2C | INT/64adrs | testing |
| max7311 | TI | 16 | I2C | INT/64adrs/hot insertion | testing |
| max7318 | TI | 16 | I2C | INT/64adrs/hot insertion | testing |
| rd1073 | LATTICE | 16 | SPI | INT | planned |
| xra1200 | EXAR | 8 | I2C | INT | planned |
| xra1201 | EXAR | 16 | I2C | INT | planned |
| xra1405 | EXAR | 16 | SPI | INT/24Mhz SPI | dev |
| fxl6408 | FAIRCHILD | 8 | I2C | INT | planned |
| bu1852guw | ROHM | 20 | I2C | INT | planned |
| cy8C9560 | CYPRESS | 60 | I2C | INT/EEPROM/max 100Khz I2C | planned |
| sx1505 | SEMTECH | 8 | I2C | INT/Indipendent rails | dev |
| sx1506 | SEMTECH | 16 | I2C | INT/Indipendent rails | dev |
| sx1509 | SEMTECH | 16 | I2C | INT/LED driver/Level Shifter | dev |
Status Legend:
- done:
- fully working.
- dev:
- currently in development.
- testing:
- currently in testing, may works or partially.
- planned:
- will be developed soon and added before the release.
- planned[R2]:
- will not included in the release but planned for version 2.
When working with microcontrollers it's common run quickly out of I/O's, that because these small chips have few
pins and some periferal (like LCD) uses many pins. For this reason I use a lot external GPIO's chips.
Microchip series MCP23xxx GPIO expanders are great chips but they can be a nightmare if you want to deal with registers, timings, etc., for these reasons a lot of coders prefere the supereasy to use PCF series from NTX.
I personally prefere the Microchip series because I can choose from I2C and SPI and they have an extra feature called HAEN that allow me to share CS pin between 8 different chips in SPI mode!
This library it's an improvement of my old MCP23xxx library since it's smaller, faster and deal with all MCP23xx series plus PCF series from NTX.
I designed as a small and easy library that can be easily expanded but still have the ability to handle directly the registers for special purposes.
If you need a simple expander, use this library and choose between many GPIO's chip by using really simply commands, but if you need a specialized GPIO you can still use this library and use the direct access to chip registers (see the keypad demo).
The MCP23xxx registers are stored in each chip library extension so you can share demos between different chips (there's some exceptions like the MCP23016 that has limited features and you cannot share some features between NTX and MCP ones since they are internally very different).
Library is modular, every chip it's an extension of the same library so it's easy to expand.
Why create an unified library? It's better create single libraries for chip families? Seems no!
Almost all GPIO chips have really similar programming, only Microchip families has more features and looks more complicated but the access it's almost the same for all so it have sense to build up an unified way to access these chips with common commands so you can easily use the chip you like without have to recode anithing, just be sure you don't need some special features of some particular chip.
[TIP] I got a compile error with a chip library I'm not plan to use!
Since there are many chip drivers inside library, the compiler open every file but optimizations cause that unused stuff will not be included so do not worry if you see compiler include all the files, at the end it will not do this!. But for the same reason if there's any error or uncompatible stuff inside any of those files, the whole library will not compile! To solve this it's really simple, just move out from the library folder the driver .cpp and .h files that give the error, close and reopen IDE and try to compile again! Do not forget to drop me a note and I will fix it!
[TIP] Can I update many pins individually in a fast way?
Yes! This library have an internal mirror of the pin registers so you can use the new function gpioDigitalWriteFast, you can use a lot since it will not communicate with te chip, once you have updated all pins you call gpioPortUpdate and the whole register will be sent to the chip in one cicle (or 2 for 16 bit ones).
[TIP] I will like to use the library inside another library, it's possible?
Yes! I've a special initialization command called postSetup. Follow instructions below...
[TIP] What about SPI transactions?
The library it's fully compatible with SPI transactions! But it's not automatic since many users use this library inside other libraries so you can still use in legacy mode even if you have a SPI Transaction compatible IDE. You need to add a parameter to the instance to force SPI Transaction! es. mcp23s17 mcp(gpio_cs_pin,gpio_adrs,30000000); I've added a 30Mhz parameter to the end, Teensy will automatically select the higher frequency but you can use any frequency (supported) you want in relation tho the chip you are using, the lenght of SPI lines, etc. If you use SPI transactions remember that the other SPI devices have to use SPI Transaction compatible libraries too!
How To Use:
Library it's unified so you just need toi include the chip and his protocol, example for mcp23017
#include <Wire.h>
#include <mcp23017.h>
then you need an instance:
mcp23017 gpio(address);//instance
// NOTE: If you need to include library in other libraries you can use mcp23017 gpio(); (empty address)
// then call postSetup!!
where the address it's specific to the chip (read chip.h file)
From below the commands are the same for all chip with some exceptions:
- Some chip it's 8 bit so it doesn't have the writeWord command
- Some chip has limited features so not all registers are accessible, take a look to the chip.h file)
Commands are:
gpio.postSetup(depends of chip);//Useful when you want include in other libraries
gpio.begin();//gpio.begin(1); will not init the protocol (useful when multiple chip are used or you want to manually init it
gpio.gpioPinMode(INPUT or OUTPUT or data);//set all pin accordly
gpio.gpioPinMode(pin,mode);//set an individual pin as INPUT or OUTPUT
gpio.port(data or HIGH or LOW);//data=8..xx bits, depends of chip. set all pins at once
gpio.port(low byte,high byte);//useful for 16 bit GPIOs that have 2 ports of 8 bit
gpio.readGpioPort();//read the state of all pins, it returns 8...xx bits depending of chip
gpio.readGpioPortFast();//experimental. Read the state of the library buffer instead of the chip.
gpio.gpioDigitalWrite(pin,state);//set individual pin HIGH or LOW
gpio.gpioDigitalRead(pin);//read the state of one pin
gpio.gpioDigitalReadFast(pin);//experimental. Read the state of a pin from the library pin register buffer
gpio.gpioRegisterReadByte(register);//not available to all chip, read a byte from the specific register
gpio.gpioRegisterReadWord(register);//not available to all chip, read a word from the specific register
gpio.gpioRegisterWriteByte(register,data);//write byte directly in chip register
gpio.gpioRegisterWriteWord(register,data);//write word directly in chip register(not 8 bit chip)
gpio.portPullup(HIGH or LOW or data);//Set pullup on input pin (not all chip!)
//new commands from release 0.8b3
gpio.gpioDigitalWriteFast(pin,Val);//It updates only the library pin register buffer! It do not send data to the GPIO
//this actually update only the mirrored register in library and act really fast since no communication with the chip
//so you can use to update many pins, when you call the command gpioPortUpdate you will send the updates to the chip!
gpio.gpioPortUpdate();//this will effectively send the pin register to the GPIO chip!
Another example: How to include in another library?
Here's how to inlude and use this library inside an existing one. In the .h file of your existing library add this lines just after the aruino.h include or library protection declaration:
#ifndef _YOURLIB_H_
#define _YOURLIB_H_
#include <inttypes.h>
#include "yourlib.h"
//here start the include
#include <../SPI/SPI.h>//this chip needs SPI
#include <../gpio_expander/mcp23s17.h>
//here ends
Now you have to provide an instance! Go to the private section of your library .h file and add to existings:
private:
bla
bla
uint8_t _cs;//needed for this chip
uint8_t _adrs;//needed for this chip (if you using HAEN)
mcp23s17 mygpio;//here the instance
As you noticed I have included also the _cs pin var and _adrs var needed for the chip I choose for demo.
Now open the .cpp file of your library and add these lines to your initialization function:
void myLibrary::begin(bla, bla){
bla
bla
mygpio.postSetup(_cs,_adrs);//you should set these 2 vars before! (I2C use ALWAYS this)
//if you want use SPI.Transactions you have another parameter...
//mygpio.postSetup(_cs,_adrs,30000000);//set SPI transaction speed (Only for SPI!!!)
mygpio.begin();//put true if you want to init SPI (or I2C, depends of chip) manually!
mygpio.gpioPinMode(OUTPUT);//es.
mygpio.gpioPort(0xFFFF);//es.
etc...
}
Since the library was already instanced and inited you can use the library function inside your library where you want but not forget to initialize it as I show above!
version 0.8b4 - beta release - only some driver released and partially tested!!!
coded by Max MC Costa for s.u.m.o.t.o.y [sumotoy(at)gmail.com]
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent