My book is available now !!!!

After 11 months working all weekends and mostly all nights (late nights) and besides my duty on Intel, the book “Intel Galileo and Intel Galileo Gen 2: API Features and Arduino Projects for Linux Programmers” is ready in the printers and it will be available for shipping.

One of the conditions that make me to accept the proposal to write this book is “the digital book must be FREE”. The focus is to attend our maker/open-source community, colleges or any individual interested in our boards… You will be able to download the digital content on Apress website or you can order the hardcopy here

The book has a little more than 700 pages (in fact was more than 800 but we reduced) and covers several topics like details of our Yocto build process, the integration of 7160 LTE modem, OpenCV with emotion recognition, 6 analog board control channels to control robotic arms, and much more info.

The front matter is below:

 What is in the book ?

Chapter 1 discusses the hardware design of Intel Galileo and Intel Galileo Gen 2, and the construction of serial and FTDI cables for debugging using Linux terminal consoles.

Chapter 2 explains how the Yocto build system works, and how to generate your custom SPI and SD card images. It also presents how to compile, install and use the toolchains for native applications development, and discusses procedures to recover bricked Intel Galileo boards.

Chapter 3 shows how to install and use Arduino IDE;  how to install the drivers needed in the computer or virtual machine used, running real examples of interacting sketches with simple circuits. It also brings a practical project that integrates Python, POSIX calls and sketches to send an alert when an email is received.

Chapter 4 discusses the new APIs and hacking techniques created especially for Intel Galileo and Intel Galileo Gen 2 boards. It contains a broad discussion about clusters architecture, how GPIOs are distributed and their respective speed limits.

A practical project of how to overcome Intel Galileo’s limitation and make the temperature sensor DHT11 work is presented.

Chapter 5 presents networking APIs and hackings using Ethernet adapter and Wi-Fi mPCIe cards. Also explains how to install new Wi-Fi cards and how to share Internet access between Intel Galileo and computers. This chapter also explains how to hack the Arduino IDE to download sketches using network interfaces instead of USB.

Chapter 6 is a practical project about tweeting using Intel Galileo boards with new OAuth authentication without intermediary computers or servers. The project uses RTC (Real Time Clock) with external coin batteries and Wi-Fi mPCIe cards.

Chapter 7 shows techniques to use V42L and OpenCV libraries and how to capture images, videos and detect face and emotions using a webcam. This chapter also explains how to change the Linux BSD to support eglibc instead uClibc and generate the toolchain to compile C/C++ programs. There are also examples of OpenCV in Python.

Chapter 8 presents a low cost project to create moisture sensors based in scrap materials and galvanized nails.

Chapter 9 shows a practical home automation project implementing a webserver using node.js , interacting with multiples sensors as motion and temperature, keypads and switch relays.

Chapter 10 explains how to install and use PoE (Power of Ethernet) modules with Intel Galileo Gen 2.

Chapter 11 discusses basic principles in robotics, how to design and control a robotic arm using analog controllers and shows a practical project using a 6 DOF robotic arm with a mechanical gripper and another one built with ground coffee.

Chapter 12 discusses how to connect a XMM 7160 LTE modem and use data channels in real networks using Intel Galileo boards.

Chapter 13 is only available online. It shows a practical project of how to design and build a low cost robot head with animatronic eyes and mouth that  expresses emotions. This chapter is available online at, under the Source Code/Downloads tab.

What about Intel Edison ?

In few months we will have a “mini version” of this book including Intel Edison and the digital version will be also FREE.

Many thanks for ALL!!! I hope you appreciate the book.

Debugging tombstones with ndk-stack and addr2line


I really like to work with several components in a system including linux kernel or keep my emotions on userspace.

If you work with android and your are a real engineer, it is very difficult to resist the native support using Android NDK. If your software requires performance using graphic API like in OpenGL or if you need to access some specific information provided by some native library, the NDK fits for you.

However, bugs in native side sometimes takes time and usually it is not an easy and fast task. If you have the device and an easy way to reproduce the issue, it is ok but suppose you need to collect logs from remote users and the scenario is very difficult to reproduce. Some cases the users even see the crash visually but the system contains the logs blocking the approval of your software that must be completed to some costumer.. at this point the program/project managers team are “talking” in your ears… “fix it!”.

Working with Android, every time a process that runs on native side crashes, we have some small pieces of your stack in files called tombstones.

The tombstones are located at /data/tombstones as isolated files (one files represents one crash) or you can see them in your logcat Take a look in the adb shell:

root@android:/ # find . |grep tombs

root@android:/ #

The tombstone inform you about:

  1. Build fingerprint
  2. Crashed process and PIDs
  3. Terminated signal and fault address
  4. CPU registers
  5. Call stack
  6. Stack content of each call

I will not post a full tombstone here. Check the /data on your device and you will observe the 7 sessions mentioned above . Let’s go straight to the point.. how to debug the stack in tombstones files!

Continue reading

Android Services: Recommendations when using AIDL for continuous service and low current drain impact

Last month a lot things happened.. I lost my dad, moved to another location .. thus, this blog was not the priority but was not forgotten.

This post is related to some issues I have observed in some Dalvik implementation and some recommendations is you want to create a service that must remains running all the time even after a device power on/off or reset.

Suppose you need to create a “light” service that must be:

1) starts when every time your devices boots.

2) contains very nice parcelable objects using aidl syntax sharing them thru IPC

3) is used to monitor something every X minutes but cannot impact the current drain.

4) the service must use the “uptime”, I mean, must reports “how long” is running

5) must be able to receive interruptions and reports them

A good application of this service could be an alarm central unit for your car. You could create this project using your old Android phone and transforming your old phone and hidden it in your car. You can also connect this old phone disassembling a 12V charging and connecting in some spot using the terminals of your battery.

So, let’s go to some mistakes.. see the list below:

Continue reading