Home > programming-stuff > Gboard: Arduino-compatible board with integrated GSM/GPRS

Gboard: Arduino-compatible board with integrated GSM/GPRS

Mon Feb 11 2013 01:00:00 GMT+0100 (Central European Standard Time)

With my recent work (aka pet project) on embedded systems mainly based on Arduino I finally came across an Arduino board with built-in GSM/GPRS connectivity. Getting an Arduino with an GSM/GPRS shield is pretty straight forward, but if the device is meant to be strong and durable, these shields don't feel good.

Itead's Gboard does. And it is also pretty cheap; definitely cheaper than e.g. the ordinary Arduino Uno with a GSM/GPRS shield from Seeedstudio.

However. The Gboard is "Arduino-compatible" and as such I was expecting a few hiccups to get it up and running. And as usual a few turns quickly into a lot. So let's have a look.


Like most communication boards the GSM chips is connected through a serial port. But the Gboard just like the Arduino Uno only has one. And this one is also used for programming purpose. In order to use both programming and GSM connection, make sure jumpers are set to ST-D2 and SR-D3 ('Software UART to SIM900, Hardware UART to Specific').

Programming connection

Just like the Arduino Ethernet board (and others) the Gboard doesn't have its own USB connection. So a 'FTDI-style basic USB-to-serial board' is required. But unfortunately the ones from Adafruit or Sparkfun don't work out of the box. First you need to be careful as the boards from Arduino itself require 5 Volts. But the FTDI connection on the Gboard only takes 3.3 Volts. Don't mix this up! Additionally the wires aren't compatible. It seems best to spend the few additional dollars to get the dedicated FOCA board from Itead. But of course this removes the fun of tinkering and I wanted to reuse my existing programming board. Connecting GND, DTR, TX, and RX with dedicated wires does the trick (I had to swap the TX and RX connections). In order to power up the board either a 3.3V connection is required, or simply remove the VCC connection at all and power the Gboard through an external power supply.

External power source

If you need to test the GSM features, make sure you have an external power source connected. Just because the lights go on with a FTDI connection doesn't make the GSM chip work.

Digital ports

The connections of the Gboard differ quite a bit from the default Arduino layout. In particular the board doesn't list any digital ports; just connections labeled with A0 to A7. But in the Arduino world the first 6 analog ports can be used as digital ones as well. Address them by starting from digital pin 14 for A0. The interface on the Arduino is called 'Electronic brick interface' and it seems to be used in other boards as well. So there are pre-made 3 pin connections with sensors available. But as long as you connect +, -, and Signal in the proper way, most other sensors will work too.

Arduino IDE

I assume other options might work as well, but for me the board 'Arduino Duemilanove w/ ATmega328' and Programmer 'Arduino as ISP' did the trick. Sometimes an upload to the board fails, but most often a single repeat will be successful.

If it still doesn't work, consider this trick by pressing the Arduino RST button at the right point in time.

GSM/GPRS features

Finally there is a dedicated lib to ease the use of the GSM chip. I assume sending AT command straight to the soft serial port will work as well, but I haven't tried it. But even though the lib claims it is compatible with the Arduino 1.x IDE, it didn't work in my environment. I had to do a couple of tweaks to the lib (but I don't remember every single step). Steps like removing newsoftserial from lib folder and adding '#include' in GSM_Shield.cpp.

Driver hiccups

Sometimes, especially under Windows it seems as if the wrong drivers are taken for the FTDI communication. Check here to see get an idea of the correct ones. Note that installing the correct driver might fail as a wrong one is somehow blocking it. Follow FTDIs uninstall instructions and try re-installing the driver again.

Categories: programming-stuff
Comments are closed.