The PCAL9555, PCAL9554 series is a low-voltage 16-bit/8-bit General Purpose Input/Output (GPIO) expander with interrupt. This conponent library is compatible to basic operation os GPIO expanders: PCAL9555, PCA9555, PCA9535, PCA9539, PCAL9554, PCA9554 and PCA9538. On addition to this, this library is including mbed-SDK-style APIs. APIs that similar to DigitaiInOut, DigitalOut, DigitalIn, BusInOUt, BusOut and BusIn are available.

Dependents:   PCAL9555_Hello OM13082-JoyStick OM13082_LED OM13082-test ... more

What is this?

This conponent library is compatible to basic operation os GPIO expanders: PCAL9555, PCA9555, PCA9535, PCA9539, PCAL9554, PCA9554 and PCA9538 .

On addition to this, this library is including mbed-SDK-style APIs. APIs that similar to DigitaiInOut, DigitalOut, DigitalIn, BusInOut, BusOut and BusIn are available.

How to use?

Wiring

/media/uploads/nxp_ip/gpio16.png
Wiring between mbed and 16-bit GPIO expander

/media/uploads/nxp_ip/gpio08.png
Wiring between mbed and 8-bit GPIO expander

Very basic register level I/O bit operation

PCAL9555 and PCAL9554 are class libraries for those compatible GPIO expander chips.
Those class libraries provides interface for bit operation of its I/O port.
For 16-bit GPIO expanders, the input/output access and its direction setting can be done by 16-bit data. For 8-bit GPIO expanders, those can be done by 8-bit data.

  #include    "mbed.h"
  #include    "PCAL9555.h"
 
  PCAL9555    gpio( p28, p27, 0xE8 );     //  using PCA9539
 
  int main() {
      gpio.configure( 0xFFFF );           //  Set all pins: input
      printf( "  0x%04X\r\n", (int)gpio );//  Print pins state
 
      gpio.configure( 0x0000 );           //  Set all pins: output
      int count   = 0;
      while(1) {
          gpio.write( count++ );
      }
  }


High level APIs

To use the GPIO expanders more simple, this library is including mbed-SDK-style APIs.
APIs that similar to DigitaiInOut, DigitalOut, DigitalIn, BusInOut, BusOut and BusIn are available.

GpioDigitalOut, GpioDigitaiInOut, GpioDigitalIn

Next code shows sample of DigitalOut equivalent API GpioDigitalOut usage.
A pin on the PCAL9555 is defined as pin and its state is changed by assignment.
(For single pin operation, GpioDigitaiInOut and GpioDigitalIn are available also.)

  #include "mbed.h"
  #include "PCAL9555.h"
  
  PCAL9555        gpio_exp( p28, p27, 0xE8 );    //  SDA, SCL, Slave_address(option)
  GpioDigitalOut  pin( gpio_exp, X0_0 );
   
  int main() {
      while( 1 ) {
          pin = 1;
          wait( 0.2 );
          pin = 0;
          wait( 0.2 );
      }
  }


GpioBusOut, GpioBusInOut, GpioBusIn

BusOut equivalent API GpioBusOut is available too.
In next code, pins are grouped as mypins to manage the output as bus output.
(Same as GpioDigitalInOut and GpioDigitalIn APIs, GpioBusInOut and GpioBusIn are available also.)

  #include "mbed.h"
  #include "PCAL9555.h"
  
  PCAL9555    gpio_exp( p28, p27, 0xE8 );    //  SDA, SCL, Slave_address(option)
  GpioBusOut  mypins( gpio_exp, X0_0, X0_1, X0_2, X0_3 );
   
  int main() {
      while( 1 ) {
          for( int i = 0; i < 16; i++ ) {
              mypins  = i;
              wait( 0.25 );
          }
      }
  }


The high level APIs can be used in combination

Those high level APIs can be used in combination.
Each pins can be managed by instances.

  #include    "mbed.h"
  #include    "PCAL9555.h"
 
  PCAL9555        gpio( p28, p27, 0xE8 );     //  using PCA9539
 
  //  The GPIO pins are grouped in some groups and operated as bus I/O
  GpioBusIn       bus_in( gpio, X0_0, X0_1, X0_2, X0_3 );
  GpioBusOut      bus_out( gpio, X0_4, X0_5, X0_6 );
  GpioBusInOut    bus_io( gpio, X1_7, X1_6, X1_5, X1_4, X1_3, X1_2, X1_1, X1_0 );
  GpioDigitalOut  myled( gpio, X0_7 );
 
  int main() {
      bus_io.input();
      printf( "I/O = 0x%02X\r\n", (int)bus_io );
      printf( "In  = 0x%01X\r\n", (int)bus_in );
 
      bus_io.output();
 
      int count   = 0;
      while(1) {
          bus_out = count;
          bus_io  = count;
          myled   = count & 0x1;
          count++;
          wait( 0.1 );
      }
  }
Committer:
nxp_ip
Date:
Thu Mar 19 02:21:57 2015 +0000
Revision:
1:fd7cfa821b6a
Parent:
0:6c9a51a50eea
API document update

Who changed what in which revision?

UserRevisionLine numberNew contents of line
nxp_ip 0:6c9a51a50eea 1 #include "mbed.h"
nxp_ip 0:6c9a51a50eea 2 #include "GpioBusIn.h"
nxp_ip 0:6c9a51a50eea 3
nxp_ip 0:6c9a51a50eea 4 GpioBusIn::GpioBusIn(
nxp_ip 0:6c9a51a50eea 5 CompGpioExp &gpiop,
nxp_ip 0:6c9a51a50eea 6 GpioPinName p0, GpioPinName p1, GpioPinName p2, GpioPinName p3,
nxp_ip 0:6c9a51a50eea 7 GpioPinName p4, GpioPinName p5, GpioPinName p6, GpioPinName p7,
nxp_ip 0:6c9a51a50eea 8 GpioPinName p8, GpioPinName p9, GpioPinName p10, GpioPinName p11,
nxp_ip 0:6c9a51a50eea 9 GpioPinName p12, GpioPinName p13, GpioPinName p14, GpioPinName p15 )
nxp_ip 0:6c9a51a50eea 10 :
nxp_ip 0:6c9a51a50eea 11 GpioBusInOut( gpiop, p0, p1, p2, p3, p4, p5, p6, p7, p8, p9, p10, p11, p12, p13, p14, p15 )
nxp_ip 0:6c9a51a50eea 12 {
nxp_ip 0:6c9a51a50eea 13 this->input();
nxp_ip 0:6c9a51a50eea 14 }
nxp_ip 0:6c9a51a50eea 15
nxp_ip 0:6c9a51a50eea 16 GpioBusIn::GpioBusIn( CompGpioExp &gpiop, GpioPinName pins[ 16 ] )
nxp_ip 0:6c9a51a50eea 17 : GpioBusInOut( gpiop, pins )
nxp_ip 0:6c9a51a50eea 18 {
nxp_ip 0:6c9a51a50eea 19 this->input();
nxp_ip 0:6c9a51a50eea 20 }
nxp_ip 0:6c9a51a50eea 21
nxp_ip 0:6c9a51a50eea 22 GpioBusIn::~GpioBusIn()
nxp_ip 0:6c9a51a50eea 23 {
nxp_ip 0:6c9a51a50eea 24 }
nxp_ip 0:6c9a51a50eea 25
nxp_ip 0:6c9a51a50eea 26 GpioBusIn::operator int( void )
nxp_ip 0:6c9a51a50eea 27 {
nxp_ip 0:6c9a51a50eea 28 return( read() );
nxp_ip 0:6c9a51a50eea 29 }