i.MX28 LTIB on UBUNTU 13.04

I tried Ltib installation in Ubuntu 13.04 for i.MX28 board which completed successfully

First install required packages

sudo apt-get update
sudo apt-get install build-essential zlib1g-dev rpm libncurses5-dev m4 bison liblzo2-dev uuid-dev tcl

Configure sudo

The LTIB installation script runs several commands with sudo where the user should not be prompted for a password. sudo without password must be configured for the current user to execute the script correctly.

sudo visudo

the file /etc/sudoers is opened for editing.

The following line should be inserted in the file, where user has to be changed to your user name:

# Allow user to run commands for ltib.
user ALL = NOPASSWD: /usr/bin/rpm, /opt/freescale/ltib/usr/bin/rpm

Save with Ctrl+o, then close with Ctrl+x.

Download BSP source for Ltib for iMX281


Extract it

tar -xvf L2.6.35_1.1.0_130130_source.tar.gz

cd L2.6.35_1.1.0_130130_source


The installer will ask you to read and accept a EULA and then ask you for the install directory. For this example, choose your home directory.
After the installation, there will be a new directory named “ltib” under the install directory you specified. This new directory contains the actual
ltib Perl script, config files, package specs, and utilities.

so now change directory to newly created ltib directory

cd ~/ltib

Now we must patch some files of the folder.Note that ,this must be done from ltib folder itself.

wget https://community.freescale.com/servlet/JiveServlet/downloadBody/93455-102-2-2825/patch-ltib-ubuntu12.04.sh


It will download ubuntu-ltib-patch.tgz

tar -xzvf ubuntu-ltib-patch.tgz


You can download the shell script and files from this link


Configure and Build

To configure and build your LTIB installation the first time, run this command from the ~/ltib directory:


This command invokes LTIB with its default behavior of performing a build. Since the installation has not yet been configured, LTIB will present
the ncurses configuration screen before building. Then, when you exit the configuration screen, LTIB will build the target image.you can see installed host tools in /opt/freescale/ .

When you invoke ./ltib the screen will be like this and a log file will be created inside the ltib folder


If there is any dependency problem the the building process may stop like this
Here the issue is that zlib is missing then you must install zlib

Then you will get the first time configuration window
Because the i.MX BSP contains only the i.MX platform, you don’t need to change anything on this screen.
When is selected, you can hit the return key to exit the current screen. On most main screens, exiting will bring up the following dialog
asking if you want to save changes.Here, use the right and left arrow keys to select between and . Press return to activate your selection. Selecting will cause LTIB to not continue to the following step. We must save the configuration when asked. This will bring up another sub-platform screen


The first option available on this screen is used to choose the sub-platform type. For the i.MX platform, the sub-platform is the specific chip family combined with the board type. For the i.MX28, this is the EVK board. The second option on this screen, under the Choose the packages profile item, lets you select the default set of packages. Individual packages can be enabled and disabled later, as you need. The default choice is sufficient for now.
If you need to change the sub-platform later, use the command:

./ltib -m selectype

Move the cursor down to the Selection item below the Choose the platform type line and press return to open up a platform selection

Select the imx28 platform, which is near the top of the list, and press return to return to the main screen.Exit the sub-platform selection screen and save the configuration. This will bring you to the main LTIB configuration screen.

Here you can change the settings such as packages kernel version build parameters etc



After modifying the parameters you must exit from configuration menu saving the settings and run ltib again without any arguments


Possibly you may get an error like this

Can’t get: gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12-1.i386.rpm at ./ltib line 2560.

CONFIG_TOOLCHAIN forced a full rebuild
Installing: gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12-1.i386.rpm
Testing network connectivity
Try gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12-1.i386.rpm.md5 from the GPP
21:59:11 ERROR 404: Not Found.
Try gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12-1.i386.rpm from the GPP
21:59:11 ERROR 404: Not Found.
Can't get: gcc-4.6.2-glibc-2.13-linaro-multilib-2011.12-1.i386.rpm at ./ltib line 2560.
Died at ./ltib line 2560.
Started: Sun Mar  3 21:17:48 2013
Ended:   Sun Mar  3 21:59:11 2013
Elapsed: 2483 seconds
Build Failed
Exiting on error or interrupt


To fix this error chnage the toolchain configuration

./ltib -m config

in the Toolchain selection choose “ARM, gcc-4.4.4, multilib, neon optimized” instead of default “ARM, gcc-4.6.2, multilib, neon optimized, gnueabi/eglibc2.13”.



One more serious error that you will encounter is this

Couldn’t link to symbol lroundf@@GLIBC_2.2.5


To avoid this error you need to edit makefile.rules of elftosb-

cp /opt/freescale/pkgs/elftosb- ~/Desktop
tar -zxvf elftosb-
cd elftosb-
vim makefile.rules

Inside that file there is a line that reads

 LIBS = -lstdc++

change it to

LIBS = -lstdc++ -lm

to add the standard math library to the build.
After editing compress the folder back to tar.gz and place it in pkgs folder

tar -zcvf elftosb- elftosb-
cp  ~/Desktop /opt/freescale/pkgs/elftosb-

Now delete the old file from BUILD folder.Else you will get an error saying delete that file.

rm -rf /opt/freescale/ltib/usr/src/rpm/BUILD/elftosb-

Now again start building using the command


After sucessful build you will be seeing this


After you have completed a build by using LTIB, you will have a target root filesystem in the rootfs directory inside the LTIB install directory. For instance, if you installed LTIB in your home directory, there will be a ~/ltib/rootfs directory containing the target rootfs.
Inside the ~/ltib/rootfs/boot directory, you will find a set of .sb files. These are the boot streams that the i.MX28 ROM interprets to boot the system.


Happy Hacking 🙂


6 thoughts on “i.MX28 LTIB on UBUNTU 13.04

  1. Thanks for every other fantastic article. The place else
    could anybody get that type of info in such an ideal approach of writing?
    I have a presentation next week, and I am on the look for such info.

  2. I know this article was posted awhile back but thank you! It was just what I needed to help our developers build out a fresh dev setup on a newer version of Ubuntu. The NXP forums are full of ideas but your article provided the best step-by-step instructions.
    Thank you again!

  3. Hi Ganesh,

    Thanks for such great article. I have successfully installed LTIB on my machine with help of your article.
    But in my /ltib/rootfs/boot directory I was unable to find boot streams. All I have in my directory are below items
    bootable_kernel linux.config System.map u-boot u-boot.bin uImage vmlinux zImage.

    Please help to understand where I did wrong ?

    • Hi Ganesh,

      Thanks for such great article. I have successfully installed LTIB on my machine with help of your article.
      But in my /ltib/rootfs/boot directory I was unable to find boot streams. All I have in my directory are below items
      bootable_kernel linux.config System.map u-boot u-boot.bin uImage vmlinux zImage.

      I was also unable to found the mk_mx28_sd script required to burn the Image on SD card.

      Please help to understand where I did wrong ?

      • Hi Ganesh,

        Solved the problem of boot streams. But still unable to find mk_mx28_sd file in ltib directory.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s